メニュー
Write a reference document — the reader wants to look up an exact fact (API surface, config options, CLI flags). Invoked from the docs-write pipeline; also usable directly when the task is unambiguously reference material.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | docs-write-reference |
| description | Write a reference document — the reader wants to look up an exact fact (API surface, config options, CLI flags). Invoked from the docs-write pipeline; also usable directly when the task is unambiguously reference material. |
Load docs-write first if its core rules are not already in context. Draft by the rules below, then finish with the pipeline's review step: spawn prose-editor on the draft and apply its findings before publishing.
Group code by business domain, never by technical kind. Use when refactoring or restructuring a codebase, creating new folders/modules, deciding where a new file goes, or reviewing a structure proposal. Triggers on module layout, folder structure, "where should this live", or plans that add folders like components/, store/, hooks/, services/.
Write a deep-explanation document (concept) — the reader wants "help me understand why/how it works". Invoked from the docs-write pipeline; also usable directly when the task is unambiguously conceptual explanation.
Write a problem-solving document (how-to / guide) — the reader has a specific task and wants to be unblocked. Invoked from the docs-write pipeline; also usable directly when the task is unambiguously a how-to.
Entry point for writing any outside-facing document — READMEs, guides, tutorials, API references, design/status docs, issue bodies, PR bodies, release notes. Use BEFORE drafting anything a reader other than the author will see. Classifies the document's purpose, routes to the matching docs-write-* purpose skill, and mandates a prose-editor review pass on every draft. Also holds the shared core rules: information architecture, sentence craft, Korean prose, labels & jargon.
Write a status/design document — living issue bodies, ADRs, design docs, PR bodies. The reader wants "what's the state, what was decided, and why". Invoked from the docs-write pipeline; also usable directly for issue/ADR/PR-body writing.
Write a learning document (tutorial) — the reader wants "teach me to do this, step by step". Invoked from the docs-write pipeline; also usable directly when the task is unambiguously a tutorial.
