Author and verify documentation, diagrams, and programmatic office documents. Use for README, docs verification, Mermaid diagrams as code, ASCII and terminal figures, code snippet images, PDF/DOCX generation, and OpenAPI reference. Trigger on 'write the README', 'document this', 'draw a diagram', 'generate a PDF', 'are these docs still true'.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Enforce minimum documentation standard across uFawkes* repos. Use when auditing a repo before release, onboarding a new repo to the suite, or implementing roadmap item 0.6 (cross-repo README links). Directly supports DORA AI Capability 3 and the 2023 DORA finding that documentation quality amplifies all technical capabilities.
Expert technical documentation architect specializing in developer experience, API portals, interactive documentation, and documentation-as-code strategies.
Documents code the way the language's own toolchain expects: the native doc format per language, contract-first doc comments on every public symbol, module-level overviews, examples the test suite runs so they cannot drift, and inline comments that explain why rather than what. Use whenever code is written, added, refactored, or reviewed, whenever a public API changes, and whenever asked to write, fix, or review comments, docstrings, doc comments, or API reference documentation.
Durable Documentation
**Status:** experimental.
Governs durable, edited repository knowledge. Unlike the append-only log, documentation is actively edited as plans and decisions evolve.
## Directory Structure
A project managed by Agent
Write and maintain the /docs knowledge base. Apply when adding or changing a page under /docs, or when a code change makes existing documentation wrong.
Use before you edit a README.md, a crate README, anything under docs/, an architecture doc, or a protocol doc, when a behaviour change could leave a doc stale, when the code and a protocol doc disagree, when you decide whether a sentence belongs in a protocol doc, a README, a plan, a test, or the code, and when a change or a review option conflicts with a protocol doc.
Write and maintain the /docs knowledge base. Apply when adding or changing a page under /docs, or when a code change makes existing documentation wrong.
文档更新与维护。检查并更新README.md、CHANGELOG.md、SECURITY.md、部署文档和.gitignore模板。Use when the user asks to update documentation, sync changelog, or prepare release docs.
Documentation standards and required templates for this project. Use this skill whenever producing any project document — feature plans, handoffs, release notes, capability documentation, production release records, or incident reports. Also trigger it when a plan, release, deployment, or incident occurs without documentation, because in this project undocumented work is unfinished work.
Software delivery documentation dispatcher. Routes to the correct document standard for the artifact being written or reviewed, following the BRD -> PRD -> FRD/NFR -> TRD -> SAB -> SAD -> ADR lifecycle. Use whenever creating, reviewing, auditing, or improving any software project document. Trigger on: "write a BRD", "PRD", "product requirements", "functional spec", "FRD", "TRD", "NFR", "document review", "business requirements", "acceptance criteria", "developer handoff", "write an ADR", "architecture decision", "write a SAD", "solution architecture", "traceability", "epic", "user story", "feature list", "roadmap", "release plan", "prioritize features", "MoSCoW", "RICE", "runbook", "postmortem", "go-live checklist", or any request to produce or improve a software delivery document.
Write, review, and organize project documentation, including READMEs, user guides, code comments, TSDoc/JSDoc, and public API reference. Use when editing documentation or comments, reviewing a diff that touches them, or deciding what to document and where it belongs.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.