documentation

The Diátaxis framework structures documentation into four distinct quadrants: tutorials, how-to guides, reference materials, and explanations. This skill enforces this standardized architecture to ensure content remains coherent, maintainable, and easily discoverable across your project.

To prevent documentation drift, maintain API references through version-aware updates triggered by API changes. This skill provides maintenance automation guidance to update docs, configuration notes, and architecture decision records whenever features are modified or released.

Add frontmatter to documentation entries by applying mandatory metadata fields and consistent tagging. This skill enforces frontmatter governance standards across all docs, ensuring your tutorials, how-tos, and references remain uniformly tagged and structured.

You need to create Architecture Decision Records when documenting significant architectural choices to ensure traceability. This skill supports ADR adoption by maintaining linked content and cross-references between your core documentation and architectural decisions.

You can update tutorials and how-tos while preserving cross-referencing links by following standardized maintenance workflows. This skill maintains linked content across the docs root and subprojects to ensure references remain intact during updates.

This documentation approach works for multiple subprojects by applying consistent Diátaxis alignment and frontmatter standards across the entire docs root. It ensures all subproject documentation maintains the same structural coherence and discoverability.