docs-designer¶
Turn a structured doc model into a browsable documentation surface. By default it emits a GENERATED multi-page site — the MkDocs config, the gen-files hook that builds pages into the virtual tree at build time, and the SUMMARY.md that gives literate-nav a tree/sidebar nav — so pages cannot drift from what they document. With --single it emits one self-contained, theme-aware page instead (a snapshot): sidebar navigation derived from the sections, tiered content, light/dark support, no external dependencies. With --docusaurus it emits a Docusaurus 3 site (docusaurus.config.ts, sidebars.ts, a generator script, MDX pages) for a branded custom-navbar look — regenerated-not-virtual, so weaker anti-drift than the default. Reuses an existing design system if the repo has one. Read-only over the repo; the skill writes the files.
At a glance¶
| Model | inherits the session's |
| Tools | Read Grep Glob |
| Author | navjyotnishant |
| Source | agents/docs-designer.md |
Returns content — does not write files
Like all but two of the agents, this one returns its output to the skill that spawned it, and the skill writes the file. It holds no write tools, so it cannot modify the repo even if asked to.
When it runs¶
docs-architect returned an ordered doc model and any redacted screenshot paths.
build the documentation site
The docs-site skill spawns this agent with the doc model; it returns the site config and generator (or, with --single, the complete self-contained page) for the skill to write.
What it returns¶
Return the complete artifact for the mode you were asked for — the site config +
generator + SUMMARY.md (default), the single self-contained page (--single), or the
Docusaurus config + sidebars + generator + generated MDX pages (--docusaurus). Do
not write files (the skill writes them), do not run git. If the doc model flagged gaps,
render them visibly (e.g. a muted "not documented" note) rather than hiding or filling
them.
Spawned by¶
Derived, not declared
No agent file records which skills call it — this list is recovered from the skill definitions at build time, so it cannot go stale.
See the /docs-site pipeline for where this fits in the whole run.