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.
Keeps long-lived project docs from rotting: gives existing docs constitution, map, status, and history roles and wires AGENTS.md or CLAUDE.md to them, plus onboarding guides, CodeTour walkthroughs, domain glossaries with ADR handoff, and growth-log entries. Use when docs drift from code, agents lose context, deleted files come back, you need a project map, status page, delete-zone, or decision log, onboard to a repo, write a starter CLAUDE.md, create a .tour file, define terms in CONTEXT.md, or record lessons. Sub-skills: codebase-onboarding, code-tour, context-and-decisions, growth-log.
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.
Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs
Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs
Documentation strategy and artifact-selection protocol. Use when updating README/changelog/docs, choosing timestamped vs cumulative records, or producing validation and fixes-applied artifacts after substantive changes.
Documentation audit, writing and upkeep - starts from who needs which answers (new contributor, operator, API consumer, user, coding agent), maps the docs that exist, checks them against the code for accuracy, and finds what is missing, misplaced or stale. Writes README, guides, reference, decision records, runbooks and agent files on approval, marking anything the code cannot prove. Stack-agnostic.
Technical documentation workflow for capturing work done — decisions, commands, issues, and resolutions — into structured Markdown notes saved to an Obsidian vault.
Writing documentation people actually read — READMEs, API docs, ADRs, comments, changelogs, and technical writing style. Use when writing any docs, README, comments, or explaining a system in writing.
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
1.1k8mo agoReviewMountCreate a free account to mount
Defines authoring, multi-version tabbing, multi-SDK code example, and diagram standards for the A2UI developer site (docs/site/). Use when creating, editing, or reviewing public documentation, conceptual guides, tutorials, or quickstarts.
Surging12 mentions in 2 weeks
1 project uses a version of this
17k6d agoReviewMountCreate a free account to mount
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.