folio

This skill should be used when the user asks to "create a demo", "build a code demonstration", "write a vignette", "generate tutorial code", "make live-coding examples", "demo this package", or wants runnable instructional code for teaching, presentations, vignettes, or documentation. Designs progressive code examples that build from simple to complex with explanations, expected outputs, and common variations.

This skill should be used when the user asks to "classify docs", "what documentation do I need", "analyze doc needs", "documentation audit", or needs to determine what documentation types are needed based on code changes. Analyzes git commits and feature scope to return structured classification data.

This skill should be used when the user asks to "validate Mermaid diagrams", "lint diagrams", "check diagram syntax", "mermaid health score", or needs to validate Mermaid diagrams in markdown files for syntax errors, configuration, and rendering quality. Uses mcp-mermaid for full validation and local regex for fast pre-checks.

This skill should be used when the user asks to "update nav", "sync mkdocs navigation", "add a doc page", "reorganize navigation", "fix orphan docs", or needs to keep mkdocs.yml in sync with the docs/ directory. Handles directory-driven nav updates, new-page scaffolding with auto-nav insertion, and ADHD-friendly nav reorganization (≤7 top-level sections, ≤3 nesting depth).

Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.

This skill should be used when the user asks to "set up a docs site", "build the site", "preview docs locally", "deploy docs", "publish the site", "audit site content", "change site theme", "check site health", "show site status", or otherwise manages the lifecycle of a documentation site (MkDocs, Quarto, pkgdown). Covers init/create/theme through build/preview/audit through deploy/publish/update.