跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 reclaude

Reclaude

修改CLAUDE.md文件,以遵循渐进披露原则. 当CLAUDE.md太长或组织混乱时使用.

2766 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

修改CLAUDE.md文件,以遵循渐进披露原则

何时用

CLAUDE.MD太长或无组织

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:reclaude、Prompt、1. Check length、2. Integrate workflow orchestration、3. Ensure verification section exists、4. Find contradictions。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Refactor CLAUDE.md files to follow progressive disclosure principles. Use when CLAUDE.md is too long or disorganized.

reclaudePrompt1. Check length2. Integrate workflow orchestration3. Ensure verification section exists4. Find contradictions5. Check for global skill extraction candidates6. Identify essentials for root CLAUDE.md7. Group remaining content8. Flag for deletionTarget TemplateProject Name

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
reclaude
description
Refactor CLAUDE.md files to follow progressive disclosure principles. Use when CLAUDE.md is too long or disorganized.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「reclaude」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-ffd362499eb17eec-%E9%87%8D%E6%96%B0%E5%A3%B0%E6%98%8E.html
请存为 .cursor/skills/reclaude/SKILL.md 或 .claude/skills/reclaude/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/brianlovin/agent-config' --list

npx skills add 'https://github.com/brianlovin/agent-config' --skill 'reclaude'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: reclaude description: Refactor CLAUDE.md files to follow progressive disclosure principles. Use when CLAUDE.md is too long or disorganized.

reclaude

Refactor CLAUDE.md files to follow progressive disclosure principles.

Prompt

I want you to refactor my CLAUDE.md file to follow progressive disclosure principles.

Follow these steps:

1. Check length

Report the current line count. Flag issues:

  • Ideal: <50 lines
  • Acceptable: 50-100 lines
  • Needs refactoring: >100 lines (move content to .claude/rules/ files)

2. Integrate workflow orchestration

Read the workflow skill at ~/.claude/skills/workflow/SKILL.md and incorporate its principles into the CLAUDE.md or a .claude/rules/workflow.md file. Adapt the content to fit the project — don't copy verbatim, but ensure the key behaviors are represented:

  • Plan mode for non-trivial tasks
  • Subagent strategy
  • Self-improvement loop with tasks/lessons.md
  • Verification before marking tasks done
  • Elegance checks for non-trivial changes
  • Autonomous bug fixing

For short CLAUDE.md files, add a concise workflow section. For longer ones, create .claude/rules/workflow.md and link to it.

3. Ensure verification section exists

Check for a ## Verification section with commands Claude can run after making changes. If missing:

  • Look in package.json for test/lint/typecheck/build scripts
  • Look for Makefile, justfile, or other task runners
  • Add a ## Verification section with discovered commands

This is critical—Claude performs dramatically better when it can verify its work.

4. Find contradictions

Identify any instructions that conflict with each other. For each contradiction, ask me which version I want to keep.

5. Check for global skill extraction candidates

Look for content that could become a reusable global skill in ~/.claude/skills/:

  • Is about a tool/framework (not project-specific)
  • Same instructions appear (or would apply) in 2+ projects
  • Is substantial (>20 lines)

If found, suggest creating a global skill with name and description.

6. Identify essentials for root CLAUDE.md

Extract only what belongs in the root CLAUDE.md:

  • One-line project description
  • Package manager (if not npm)
  • Non-obvious commands only (skip npm test, npm run build if standard)
  • Links to .claude/rules/ files with brief descriptions
  • Verification section (always required)

7. Group remaining content

Organize remaining instructions into .claude/rules/ files by category (e.g., TypeScript conventions, testing patterns, API design, Git workflow).

8. Flag for deletion

Identify content that should be removed entirely:

  • API documentation — link to external docs instead
  • Code examples — Claude can infer from reading source files
  • Interface/type definitions — these exist in the code
  • Generic advice — "write clean code", "follow best practices"
  • Obvious instructions — "use TypeScript for .ts files"
  • Redundant info — things Claude already knows
  • Too vague — instructions that aren't actionable

Target Template

# Project Name

One-line description.

## Commands
- `command` - what it does (only non-obvious ones)

## Rules
- [Topic](/.claude/rules/topic.md) — brief description

## Verification
After making changes:
- `npm test` - Run tests
- `npm run lint` - Check linting

What to Keep vs Remove

Keep in CLAUDE.md:

  • Commands Claude can't guess from package.json
  • Non-standard patterns specific to this project
  • Project gotchas and footguns
  • Links to detailed rules files

Move to .claude/rules/:

  • Detailed conventions (>10 lines on a topic)
  • Style guides
  • Architecture decisions
  • Workflow documentation

Remove entirely:

  • Anything Claude can infer from reading the codebase
  • Standard practices for the language/framework
  • Documentation that exists elsewhere (link instead)

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…