docs-as-code plugins

by Matt Corbett

Technical-writing & docs team — agents (docs-architect, api-reference-writer, docs-site-engineer) for developer and product documentation that people actually use: the Diataxis framework (tutorial / how-to / reference / explanation — and not mixing them), docs-as-code (docs in the repo, reviewed and CI-checked, versioned with the product), accurate API/SDK reference (spec-driven, examples that run, errors documented), and a maintainable docs site (Docusaurus/Mintlify/MkDocs, IA, search, versioning). Deepens ravenclaude-core/documentarian. skills, a decision-tree knowledge bank (doc-type, docs-tooling, Diataxis content-type, lint-in-CI-vs-manual + a dated 2026 map), a bank, best-practices, templates, commands, an advisory hook, a prose-linter LSP tier (Vale-LS + Marksman) and a stdlib readability/prose checker. Seams: dev portal/SDK -> api-engineering, site design -> web-design, prose polish -> ravenclaude-core/documentarian. Requires ravenclaude-core@>=0.7.0.

by claude-skills

Keeps repository documentation consistent and honest. Scaffolds a universal document set scaled by repo archetype, audits existing repos for missing, stale, or off-standard docs, enforces append-only architecture decision records, compacts the oldest of them into a digest once fifty exist, and regenerates the generated ones so drift from the code is reported rather than discovered. Ships a plain-English Vale style alongside it, plus optional compliance overlays for IEC 62304, the OSPS Baseline, the EU Cyber Resilience Act and NIST SSDF, each describing document structure only and never inventing regulatory content.