docs
the archivist
docs work has a direction: retrieve primary facts, publish an index or site, or review long markdown. source authority and rendered output matter more than a documentation tool's search result. Mintlify owns its site configuration.
current source onlycites the versionshort routes to depth
Use for documentation work -- current library and framework documentation, llms.txt indexes, long Markdown review, and Mintlify documentation sites. TRIGGER when the user needs current API documentation, an llms.txt index, Markdown review, or a Mintlify change.
methodology
- current API question: start at the publisher's official documentation; docs-seeker may discover an
llms.txtentry, but its result is not authority. - llms.txt index: use the llms guide and validate the generated links. a Mintlify site owns its generated AI assets and its
docs.jsoncontract. - Mintlify change: use the current
mintCLI, then validate the changed site with the commands the installed CLI exposes. - long markdown review: use markdown-novel-viewer only when its local reader adds value; it is not a publication or validation surface.
- read the distilled rules first. guide material is reference context; update a stale local command or link only with current evidence.
contents
- trainedlearned layer -- read first
- docs-seekerfind current library/framework docs and inspect an upstream repository when primary docs are absent
- llmsgenerate an llms.txt index from docs or codebase scanning per the llmstxt.org spec
- markdown-novel-viewerread long markdown comfortably in the browser -- rfc, runbooks, specs, reports
- mintlifyanything mintlify -- docs.json, mdx components, navigation, theming, openapi, ai docs assets, deployment, validation cli
procedures
procedures the guru runs, one page each. read it, then follow it.
- ingestimport external content into repo and update context tracking
- ipcoredocanalyze techstack and ensure llms.txt docs exist in docs/lib for all libraries used
- ipmintautonomously audit and improve Mintlify docs -- structure, clarity, best practices
- ck-docs-initanalyze the codebase and create initial documentation
- ck-docs-summarizeanalyze the codebase and update documentation
- ck-docs-updateanalyze the codebase and update documentation
- docs-cdrcoredoc researcher -- deep knowledge search across the coredoc folder
- docs-decentralizedecentralize docs into folder-level README.md files with links to core docs
- docs-refinerefine and fix markdown documentation issues