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.
41k7d 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.
4297mo agoReviewMountCreate a free account to mount
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).
8517d agoReviewMountCreate a free account to mount
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
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.
Redaction de documentation technique: README, docs API, guides, changelogs. Use when writing or improving technical documentation, README files, or developer guides.
Rédiger de la documentation technique ou utilisateur. À utiliser pour commencer une fonction ou un script, pour expliquer comment un module fonctionne, pour créer un tutoriel, une notice d'utilisation, ou compléter le README.
After finishing a non-trivial code change (new feature, bug fix, refactor, architecture decision), update the project's root documentation files — CLAUDE.md, SPEC.md, README.md, or whatever equivalent already exists — so a future agent or teammate can open the project cold and understand what it does, what changed, and how to continue. Create these files if none exist. Use at the end of a change, not before or during. Do not use for trivial edits (typo fixes, one-line tweaks, formatting) or read-only/exploratory work with no code change. Works in any conversation language, English or French included — write the documentation in whatever language the existing docs use, or the user's language if there's no precedent.
Write clear, comprehensive documentation with language-specific patterns. Use when writing docstrings, module docs, README files, API references, or architecture decision records. Covers Python, TypeScript, Go, and Rust documentation conventions. Do NOT use for code style (use vibe skill).
Writes and updates docs, READMEs, runbooks, specs, and ADRs. Use when documenting a feature, writing a runbook, updating README/setup docs, or recording decisions. Do not use for competitive research briefs or for code comments that only restate the next line.
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.
Documentation practices — comment guidelines, ADR conventions, API documentation, inline docs philosophy, doc health scanning and maintenance. USE WHEN documentation, write docs, comment guidelines, ADR, architecture decision, API docs, JSDoc, OpenAPI, document code, when to comment, how to document, self-documenting code, README, doc health, doc drift, stale docs, fix docs, doc maintenance, check docs.
Use when writing or updating specs, READMEs, API/reference docs, ADRs, or runbooks — record an ADR per decision, update docs when a feature ships, fix drifted docs.
Write effective documentation for SaaS projects covering code comments, API docs, README files, and technical specifications. TRIGGER this skill automatically when the user mentions: writing docs, README, API documentation, JSDoc, TypeDoc, inline comments, "how do I document this", onboarding docs, CHANGELOG, technical spec, ADR (Architecture Decision Records), "the team doesn't understand this code", or any request to make code or systems easier to understand. Also trigger when public APIs or complex logic have no documentation.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.