What problem does it solve? Technical documentation for web projects often mixes page types, buries prerequisites, and ships stale or unrunnable examples, leaving readers confused and maintainers overwhelmed. This Skill provides a structured workflow for planning, writing, and reviewing developer docs that are scannable, accurate, and maintainable. ## Core Features & Use Cases - Page-type discipline: Separates README/landing pages, quickstarts, tutorials, how-to guides, reference pages, explanations, troubleshooting, and migration guides so each page serves one reader intent. - Ready-made templates and checklists: Ships Markdown skeletons for every page type plus a documentation brief, information architecture template, and a final review checklist. - House style and web-project rules: Enforces active voice, task-based headings, runnable code examples, version and prerequisite hygiene, accessibility, and docs-as-code maintenance habits. - Use Case: When asked to write a quickstart for a new SDK, the Skill inventories facts (install commands, runtime versions, environment variables), builds a skeleton, writes one happy path with a visible success state, and runs the review checklist before delivery. ## Quick Start Ask the assistant to write or review a documentation page for your web project, specifying the page type such as quickstart, tutorial, reference, or migration guide.
