📝 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 on Fumadocs or Starlight with generated OpenAPI and TypeDoc reference, tested snippets and llms.txt.

Check each quote and statistic in a draft against primary sources and return a table of fixes.

Drafts the customer recap after a recycling or ITAD job closes (what came in, what was destroyed, what was resold, what the customer is owed or owes) in your own voice from a processing export, with the math shown and a list of numbers to check before sending. Use when an account manager or operations person writes settlement or certificate-of-destruction cover emails by hand.

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".

Turns a rough voice-memo transcript of someone explaining a task into a step-by-step SOP with safety callouts, a one-page checklist, common mistakes, the questions the memo left unanswered, and a five-question quiz for new hires. It never invents steps. Use when a supervisor or operator wants to capture know-how that lives in people's heads, for training or onboarding.

Builds a reusable voice guide from emails you actually sent, asks you a few questions before it writes anything, then rewrites a draft in your voice to prove it works. Use when someone wants AI drafts to sound like them instead of like a generic assistant, in any AI app, with or without an email connector.