📝 Docs & writing

Builds a non-technical how-to page for any app or repo, from install to full understanding, with real screenshots, step-storyboard Remotion demos, page-wide search, redaction of real people, a currency check, a password-gated static deploy, and the CLAUDE.md rules that keep it current. Use when asked for a user guide, how-to, onboarding walkthrough, help page or instructions page for an app, product or internal tool.

Matches every user-facing string — email subjects, notifications, buttons, errors, empty states — to the product's vibe and the reader it is written for. Use when writing or reviewing any copy a user will see.

Pulls the current documentation for any library, API, app, or vendor into the repo as short dated notes agents read before working, and keeps them fresh with a weekly check that flags which sources changed, starting from the changelog. Use when setting up AI context for a tool or vendor, when the model's knowledge of a fast-moving product may be stale, when asked to refresh, sync, or check docs, or before relying on a vendor's API, CLI, or limits.

Writes short, human-legible READMEs that lead with a quick start and surface the manual steps the human still needs to do. Use when creating or updating a README.

Docs site with quick starts, task guides, and generated reference.

Builds a customized training document for one reader — a how-to guide, onboarding walkthrough, study course, or app manual — from what that reader already uses and what they want to be able to do, about any topic, tool, or repository. Asks only the intake questions the context leaves open, then delivers one of three formats — a single-file HTML guide, a keyboard-navigable slide deck, or a standalone searchable Next.js docs site. Use whenever someone asks to teach, train, onboard, explain, document how to use, write a tutorial or course, or make learning material for a person or team, even if they never say "training".