Documents the authentication layer of a project — flow, session or token handling, middleware / guards / decorators, and the permission model. Use when the user says "document auth", "write docs for authentication", "document the login flow", "document how sessions work", "document the permission model", or similar. Hands off to /rosetta:write-docs with the auth playbook; lets write-docs decide single-page vs landing + children based on the researcher's brief.
Documents the cross-cutting patterns in a codebase — decorators, middleware, filters on controllers, factory / repository / service conventions, the transversal techniques a contributor needs to recognize. Use when the user says "document the patterns", "document the conventions", "document how decorators are used here", "document the middleware stack", or similar. Hands off to /rosetta:write-docs with the patterns playbook; lets write-docs decide single-page vs landing + children based on how many distinct techniques the researcher surfaces.
Documents the data-layer surface of a project — schemas (as logical groupings), flow, relations, invariants, ORM patterns, AND the migration workflow. One skill for the whole data area. Use when the user says "document the database", "document the tables", "document the data model", "document the schema", "write docs for the entities", "document migrations", "write the migration runbook", or similar. Produces a landing page + subsystem children by default (not a per-table dump — schema files are the DDL reference).
Documents a feature, concept, API, or workflow in a Rosetta docs site at rosetta-docs/. Use when the user says "document X", "write docs for Y", "write a how-to for Z", "explain how A works", "add a reference page for B", or asks to capture knowledge about a code area. Delegates code exploration to the rosetta-code-researcher subagent, classifies via Diátaxis (tutorials / how-to / reference / explanation), and drafts EITHER a single page OR a landing + children split when the topic has orthogonal subsystems. Relies on the plugin's Stop hook to auto-run `astro check` at end-of-turn.
Updates an existing MDX page in a Rosetta docs site at rosetta-docs/. Use when the user says "update X", "fix the Y page", "revise Z", "expand the W section", "correct V in the docs", "amend the docs for U", or "add a paragraph/section to A". Locates the page by explicit path, /llms.txt title match, or NL search; refuses if the page is missing (defers to /rosetta:write-docs). Applies a targeted Edit by default; opts into a full-section rewrite only on explicit rewrite phrasing. Dispatches the rosetta-code-researcher subagent only when the requested change asserts code behavior (symbols, endpoints, flows). Stamps `last_updated` to today's date on every patch. Validation runs via the plugin's Stop hook.
Personalizes a freshly-scaffolded Rosetta docs site with the project's name, tagline, repo URL, and stack. Use right after /rosetta:init-docs, or when the user says "personalize the docs", "customize the docs for this project", "brand the docs with this project's name". One-shot — detects if it has already been run (via the personalized flag in rosetta.config.json) and refuses to re-run. Changes to the landing page later go through /rosetta:write-docs.
Scaffolds a Rosetta.md documentation site into the current project at rosetta-docs/. Use when the user wants to set up docs, initialize documentation, bootstrap rosetta-docs, add a docs folder, or says things like "init rosetta", "scaffold starlight docs", "start a docs site for this repo". Clones the latest tagged release of rosetta-template (resolved from the remote at runtime — no manual version pin), installs deps with the user's preferred package manager (pnpm or npm), starts the dev or docker server, and verifies via /health.
Retrieves context from an existing Rosetta docs site to answer a question with citations. Use when the user asks "how does X work in this project", "what do the docs say about Y", "find docs for Z", "is this documented anywhere", or whenever Claude needs documentation context to perform another task (e.g. fixing a bug in a documented area). Checks /health, fetches /llms.txt, ranks pages by relevance, pulls the raw-MD twins of the top matches, and synthesizes a cited answer. Degrades to local file reads when the docs server is down.