/docs-site¶
Authoring class
Writes exactly one artifact into the repo, then proposes the commit — never runs git itself. Shared rules: CONVENTIONS-authoring.md.
By DEFAULT it builds a generated multi-page site (MkDocs Material + gen-files + literate-nav) with a tree/sidebar nav, one page per entity, and embedded diagrams — rebuilt from the source files on every commit so it cannot drift. Pass --single for one self-contained theme-aware HTML page instead (a snapshot, for hand-maintained prose). Pass --docusaurus for a Docusaurus 3 site (custom React navbar/homepage, MDX pages, npm toolchain) when the deliverable needs that branded look — regenerated from source before every build rather than virtually built, so its anti-drift guarantee is weaker than the MkDocs default. Auto-derives the menu/sections, grounds everything in the source (flags gaps rather than inventing), embeds auto-redacted screenshots via the capture-screenshots pipeline when needed, and PROPOSES the commit.
At a glance¶
| Run it | /docs-site |
| Class | authoring |
| Version | 0.3.0 |
| Author | navjyotnishant |
| Cost | 1–2 agent calls |
| Needs | mkdocs + mkdocs-material + mkdocs-gen-files + mkdocs-literate-nav · mkdocs-glightbox · node + npm/pnpm (to run @docusaurus/core) |
| Source | skills/docs-site/SKILL.md |
What it needs, and what happens without it¶
Every tool is detected at runtime — none is installed for you.
| Tool | Without it |
|---|---|
mkdocs + mkdocs-material + mkdocs-gen-files + mkdocs-literate-nav |
say so and offer --single (Mode B), which needs no toolchain |
mkdocs-glightbox |
diagrams render inline, shrunk to the column |
node + npm/pnpm (to run @docusaurus/core) |
say so and offer --single (Mode B) instead |
The pipeline¶
Agents it spawns¶
docs-architect— Turn documentation sources (existing docs, a codebase, an outline, or structured definition files like…docs-designer— Turn a structured doc model into a browsable documentation surface. By default it emits a GENERATED…
The procedure¶
The executable steps live in the skill file itself and are deliberately not reproduced here: they are instructions to the model at runtime, not documentation.