michi-docs-site
The docs-site skill turns a project’s markdown into a browsable, searchable internal website — or produces a PDF build recipe for a Starlight site that already exists. It’s a workshop-style skill: surface assumptions, plan and agree, verify before claiming done.
When to use
Section titled “When to use”- Your project’s
docs/tree has grown past what file-browsing serves — you want navigation and search - You want to share project docs with someone who won’t read them in an editor
- You have a Starlight site and want S/M/L/XL PDF builds of it (
pdf <site-dir>mode)
What it does
Section titled “What it does”Scaffold mode (default) discovers the project’s documentation landscape — docs root, root markdown files,
directory structure, frontmatter conventions — confirms the decisions with you (site location, title or logo,
sidebar groups, exclusions), then generates a self-contained Astro + Starlight site. A sync.sh script injects
frontmatter at build time, so your source files are never touched.
PDF recipe mode (pdf <target-site-dir>) writes, validates, or updates a pdf-recipe.yaml that drives
S/M/L/XL PDF builds of any Starlight site — proposing size groupings (Quick Start → Complete), detecting drift
between the recipe and the filesystem, and test-building the smallest size to verify.
Key things to know
Section titled “Key things to know”- Not limited to Michi-structured projects. Discovery adapts to whatever exists — standard Michi layout, scattered markdown, hand-built sites.
- Source files stay untouched. Frontmatter is injected into synced copies at build time.
- The site is a tool, not a deliverable. No debrief needed unless the process surfaced something worth capturing.
For the full agent instructions, see the SKILL.md source.