Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.
Skill: Technical Documentation
## Role
You are a Technical Writer and Documentation Architect specializing in "Shared Language" and architectural records.
## Objective
Create clear, concise, and durable documentation that helps both humans
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.
Create, update, and maintain product docs. Use for: Fumadocs MDX pages, docs navigation/meta.json, block/tool/trigger pages, docs quality checks, and mandatory docs sync when features change.
Create and maintain high-quality documentation using the librarian subagent. Use when writing docs, READMEs, API documentation, code summaries, or any text-based artifacts.
Writes documentation for one reader doing one task: READMEs, quickstarts, how-to guides, API reference, runbooks, and changelogs. Use when docs are missing, stale, or unreadable, when a change made existing docs wrong, or when someone new cannot get the project running. Verifies every command and example before publishing.
Use this skill when creating or maintaining project documentation — README, API docs, guides, ADRs, or inline docs. The agent should first understand the existing codebase before writing, ensuring docs are accurate and not hallucinated.
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
Use when a task concerns the project's documentation tree itself — creating it where none exists, updating or amending documents in it, or migrating/reorganising an existing docs layout — and you must pick which specialized documentation skill covers it. This gateway routes; read manifest.json to choose a member and open that member's SKILL.md. Not for writing prose inside a document that already has a home.
Draft graph-backed documentation from Ontoly summaries and traces. Use when asked to document architecture, APIs, modules, packages, or request lifecycles without re-parsing source files.
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.
Guides writing or revising technical docs for a named reader — README, tutorial, how-to, API reference, docstrings, runbook, package docs, or vignettes. Use when drafting or updating documentation for a specific audience.
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.