Use before you write or edit a README.md, a crate README, anything under docs/, an architecture doc, a protocol doc, or a code comment, before you add a rule to AGENTS.md or CLAUDE.md, 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.
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.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Maintain project documentation: README (Standard README spec), Architecture Decision Records, Diátaxis technical docs, and Keep a Changelog CHANGELOG.md. Use when writing or auditing README, ADR, docs site content, or changelog entries, or when the user mentions documentation structure or doc maintenance.
Write documentation that stays true, and find what a change just made false. Covers picking the right kind of document (tutorial, how to, reference, explanation), auditing docs for drift after shipping, writing a runbook someone can follow at 3am, and deciding what not to write. Use when adding or updating a README, runbook, or API docs, when a change alters behaviour someone has written down, after shipping a feature, when onboarding docs are wrong, or on any mention of documentation, docs, or a runbook.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
文档更新与维护。检查并更新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, guides, product comparisons, release notes, code comments, TSDoc/JSDoc, and public API reference. Use when editing documentation or comments, writing comparison content, reviewing a diff that touches them, or deciding what to document and where it belongs.
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
Steady1 mention in 2 weeks
43 projects use a version of this
41k22d agoReviewMountCreate a free account to mount
Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.
4387mo agoReviewMountCreate a free account to mount
Create and update documentation articles for the Heym platform. Use when adding docs pages, writing reference articles from summaries, or when the user provides an outline for a new article.
1.7k7mo agoReviewMountCreate a free account to mount
Records decisions and documentation, and detects when documentation has drifted from the code it describes. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, when docs may be stale or out of sync with the code they describe, when working out which module docs are still accurate, or when setting up a check so docs cannot silently go out of date again.
Go documentation conventions: godoc comments, package docs, testable Example functions, deprecation notices, doc links, and project docs (README, CHANGELOG, llms.txt). Use when: "add godoc", "document this package", "write doc comments", "add examples to docs", "deprecate a function", "write a README", "update the changelog", "improve the docs". Not for: commit messages (git-commit), code style (go-coding-standards).
8532d agoReviewMountCreate a free account to mount
Use when writing or updating package AGENTS.md files, interface summaries, README sections or, rarely, ADRs in a backend repo in any language pack, without duplicating canonical specs or recording reasoning transcripts.
Use when writing a README, documenting a module or component, recording a decision, or deciding whether something needs explaining at all. Also when documentation has drifted from the code.
Documentation suites: audit or plan docs, write with Diátaxis/Info Mapping/EPPO, review for scannability and AI-readiness. Trigger for doc planning, writing, or review. Broken links are doc-link-verifier, not this.
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.