When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions "docs," "documentation site," "docs subdomain,"…
Pages: Documentation Site Guides documentation site structure, navigation, and content organization. Typically hosted on docs.* or help.* subdomain. Includes Getting Started, guides, tutorials, API Reference (endpoint docs), and troubleshooting. Distinct from API introduction page (api-page-generator). When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output. Initial Assessment Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and use cases. Identify: Product type: Software, API, hardware, service Audience: End users, developers, admins Content sources: Markdown, MDX, Git, CMS Subdomain: docs., help., or path (/docs) Documentation Structure
don't have the plugin yet? install it then click "run inline in claude" again.