メニュー
Domain logic for documentation — injected into the docs-keeper agent. Provides guidance on creating and maintaining separate documentation files (README, API docs, guides). Not invoked directly.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | kb-documentation |
| description | Domain logic for documentation — injected into the docs-keeper agent. Provides guidance on creating and maintaining separate documentation files (README, API docs, guides). Not invoked directly. |
| user-invocable | false |
| disable-model-invocation | true |
Guidance for creating and maintaining separate documentation files. This skill covers README files, API documentation, architecture docs, and user guides. Inline code documentation (JSDoc, docstrings, etc.) is handled by the implementer during coding — do not duplicate what's already in the code.
In the devline pipeline, read the plan and git diff to understand what changed. Focus on the delta — don't re-describe unchanged features. Inline docs were handled by implementers.
Every project needs a README covering:
For projects exposing APIs:
For complex projects:
For end-user-facing projects:
Before writing documentation, check what already exists:
docs/ directory, README.md, CHANGELOG.mdtypedoc.json, mkdocs.yml, docusaurus.config.js, .readthedocs.yml, javadoc).claude/devline.local.md for doc_format overrideIdentify what changed, find all docs referencing changed code, update to match, verify examples still work.
For format-specific patterns:
references/doc-templates.md — Templates for README, API docs, architecture docsreferences/doc-tools.md — Documentation generators and their configurationGrep-based reverse dependency analysis — injected into planner, reviewer, and deep-review agents. Computes which files are affected by changes to a set of seed files. Not invoked directly.
This skill should be used when the user asks to "brainstorm", "refine an idea", "flesh out a feature", "define requirements". Guides interactive refinement of rough ideas into concise, actionable feature specifications. Focuses on the "what" and architecture — never the "how".
This is the default skill for all development work. It orchestrates the entire development lifecycle from idea to merge-ready code, coordinating multiple agents for brainstorming, planning, implementation, review, documentation, and final approval. Use this for any development task that is non-trivial and could benefit from structured planning, parallel execution, and rigorous review or require more than 3 lines of code changed.
Retrieves authoritative, up-to-date technical documentation, API references, configuration details, and code examples for any developer technology. Use this skill whenever answering technical questions or writing code that interacts with external technologies. This includes libraries, frameworks, programming languages, SDKs, APIs, CLI tools, cloud services, infrastructure tools, and developer platforms. Common scenarios: - looking up API endpoints, classes, functions, or method parameters - checking configuration options or CLI commands - answering "how do I" technical questions - generating code that uses a specific library or service - debugging issues related to frameworks, SDKs, or APIs - retrieving setup instructions, examples, or migration guides - verifying version-specific behavior or breaking changes Prefer this skill whenever documentation accuracy matters or when model knowledge may be outdated.
Implement tasks using TDD. Accepts a plan or specific task description. Runs implementer agents in parallel where possible.
Design intelligence for UI/UX — injected into the frontend-planner agent. Provides BM25-searchable database of 67 styles, 161 color palettes, 57 font pairings, 160 animated component patterns, 161 industry rules, plus framework-agnostic design guidelines. Not invoked directly.