docs▌

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

Generate structured project documentation by analysing the codebase. Produces docs that reflect the actual code, not aspirational architecture.

Use this skill when the user gives a product name and asks for an end-to-end documentation/API quality review.

Use this skill when the user wants cross-cloud documentation/API comparison for similar products.

@./../_shared/metabase-style-guide.md

No Chat Output: Produce the handoff document only. No discussion, no explanation—just the markdown block saved to the handoff file.

Generate a complete, production-ready documentation site for any project.

User can provide specific focus areas or documentation types:

Four slash commands for creating, maintaining, and auditing project documentation with smart templates. \n \n Provides /docs-init to scaffold CLAUDE.md, README.md, and docs/ structure for new projects, with auto-detection of project type (Cloudflare Workers, Next.js, or generic) \n Includes /docs-update for full documentation audits covering date freshness, version accuracy, broken links, redundancy, and orphaned files \n Offers /docs-claude for focused CLAUDE.md maintenance, checking tech stack

Category: test