What problem does it solve? Documentation often fails because pages mix teaching, instruction, reference, and explanation into one unfocused document. This Skill classifies each page into the correct Diátaxis type (Tutorial, How-to guide, Reference, or Explanation) and enforces the structure, voice, and code-example standards that make documentation actually serve its readers. ## Core Features & Use Cases - Diátaxis Classification: Decide whether a page is a Tutorial, How-to guide, Reference, or Explanation before drafting, with per-type rules that prevent mixing concerns. - Structured Writing Workflow: Follow a four-step process — clarify audience and scope, propose an outline, write the full page, then verify against a completion checklist. - Style and Example Standards: Enforce active voice, second person, American English, complete runnable code examples, and Mermaid diagrams for architecture and flows. - Use Case: When adding a new feature to a Cratis-based project, use this Skill to draft a how-to guide showing users the exact steps, with a complete working code example and links to related reference pages. ## Quick Start Ask the assistant to write a how-to guide for configuring a feature in your Cratis project, following the Diátaxis documentation standards.
