메뉴
Use when the user wants to strip AI-generated style tics from documentation — emojis, excessive lists, all-caps filenames, fragmented structure. Triggers on phrases like "declaude the docs", "clean up documentation style", "remove emojis from docs", "apply style guide".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user points at a GitHub repo (an agent skill, MCP server, or "Claude plugin"-ish project) and wants to install or register it. Routes between native plugin install, MCP server registration, and adding to the user's third-party marketplace. Triggers on phrases like "install this from GitHub", "add this skill to my setup", "register this as a third-party plugin", "is this available as a Claude plugin".
Reference and worked example for the CONTEXT.md / CLAUDE.md two-file workflow. Use when the user asks "what is CONTEXT.md", how the human-context vs agent-briefing split works, or wants a copyable example pair to seed a new repo. Pairs with the operational skills (context-to-claude, claude-to-context, add-to-context, remove-from-context, manual-context-update, chunk-repo-context) — this skill explains the model; those skills do the work.
Use when the user wants to prune and chunk a bloated CLAUDE.md into a structured context/ store with pipeline folders and subagent templates. Triggers on phrases like "chunk claude", "prune CLAUDE.md", "set up context store", "split CLAUDE.md".
Use when the user wants to install a new user-level slash command at ~/.claude/commands/. Triggers on phrases like "install a slash command", "add a /command", "create a user-level slash command", "save this as a slash command".
Save a Claude Code plan (from ExitPlanMode, design discussion, or multi-step task) to persistent storage. ONLY invoke when the user explicitly asks to save/stash/store a plan (e.g. "save this plan", "stash the plan", "store the plan in the planning repo"). Do NOT auto-invoke after planning. Routes to the active project's `planning/` folder when one exists, else to the user's configured central planning repo.
Synthesize a new SKILL.md from the procedure that was just followed in this session, so the next session can replay it without being briefed from scratch. Use when the user says "extract this as a skill", "save this process", "make a skill from what we just did", "this should be a skill", "let's not have to explain this again next time", or after a long worked example whose procedure has clear reuse value.
| name | declaude-docs |
| description | Use when the user wants to strip AI-generated style tics from documentation — emojis, excessive lists, all-caps filenames, fragmented structure. Triggers on phrases like "declaude the docs", "clean up documentation style", "remove emojis from docs", "apply style guide". |
Navigate the repository, identify all documentation files, and ensure they adhere to the style guide below.
This guide establishes mandatory stylistic, structural, and tonal constraints for all generated text, documentation, and code artifacts.
Maintain a professional, serious, authoritative tone. Emojis, excessive enthusiasm markers, and informal slang are forbidden.
| Guideline | TO DO | NOT TO DO |
|---|---|---|
| Emoji Policy | The validation failed due to a timeout. | The validation failed due to a timeout! ⚠️ |
| Exclamations | Use period or colon instead. | Function execution is complete!!! |
| Slang/Informality | Formal, objective, third-person. | Make sure you initialize the cool parameters. |
Only README.md conventionally uses all-caps. All other docs use lowercase kebab-case. Code files follow language conventions.
| Guideline | TO DO | NOT TO DO |
|---|---|---|
| README Exception | README.md | ReadMe.md |
| General Docs | installation-guide.md | INSTALLATION_GUIDE.MD |
| Code Files | data_processor.py | DATA_PROCESSOR.PY |
ARCHITECTURE.md, GOALS.md, ROADMAP.md, or detailed INSTALLATION.md for trivial steps unless asked.README.md.Heading Constraint: A subheading must be followed by substantial development (3+ sentences or a complex example) before the next subheading.
Tables: Reserved for comparative data, summary statistics, or structured mappings. Do not summarize prose into tables.
Lists: For enumerating steps, assumptions, or distinct items. Not a substitute for paragraph development.
Limit nesting to H1–H3 unless the document exceeds 3,000 words.
README.md.