doc-skills

Use when authoring or updating developer-facing design specs under docs/design for one or more canonical functional specs (many-to-many via tags), especially architecture decisions, technical tradeoffs, states, data flows, schemas, source-file references, and gaps between flow behavior and current design coverage

Use when creating or updating a functional spec for a user flow listed in column B of the User-Flows-Details Sheet

Use when creating or updating end-user help pages, user documentation, screen docs, feature help pages, or docs under `docs/user-guide/`. Trigger on "author user guide", "create user guide", "new user guide", "update user guide", "document <screen>", "help page for <feature>", or "/authoring-user-guide".

Use when the user wants to write or improve a prompt for Claude, ChatGPT, Gemini, Cursor, Claude Code, GitHub Copilot, Windsurf, Bolt, v0, Midjourney, DALL-E, Stable Diffusion, or another AI-powered tool.

Use when writing or tightening prose for functional specs, design documents, user guides, or implementation plans, especially when draft text is wordy, vague, passive, duplicative, or hard to scan. Do not use for AI prompt-writing, code comments, commit messages, general chat, or unrelated prose.