Classify documentation requests into Diátaxis quadrants before writing.
npx skills add https://github.com/smp4/claude-skills --skill write-docs-smp4
Please help me install this Agent Skill. Skill: write-docs Source: https://github.com/smp4/claude-skills/tree/main/dot_claude/skills/write-docs Command: npx skills add https://github.com/smp4/claude-skills --skill write-docs-smp4
Documentation requests often mix tutorials, how-tos, and explanations, which leads to inconsistent structure, tone, and wasted reviewer time; this skill forces Diátaxis detection and an explicit quadrant before writing so every doc stays focused on the reader's goal.
Use this skill whenever a teammate asks for any technical documentation so the result matches the intended quadrant and stays within the documented rules.
Confirm the request's quadrant and explain the reasoning before writing any documentation.
High-intent search queries and answers about installing and using this skill.
You need to split a documentation request into separate guides when the prompt spans more than one Diataxis quadrant. Detecting mixed tutorial, how-to, and explanation content requires prompting for separate documents to prevent structural inconsistency.
To enforce Diataxis classification when writing technical documentation, you must declare an explicit quadrant and reasoning before drafting. This prevents mixed-messaging outputs by ensuring every tutorial, how-to, or explanation stays focused on the reader's specific goal.
Developer documentation mixes tutorials and explanations inconsistently because requests often span multiple Diataxis quadrants. You must detect the intended quadrant first and prompt for separate documents to keep structure, tone, and voice focused.
The best way to structure a README using Diataxis quadrants is to scan existing project docs for framework usage, explicitly declare the target quadrant, and apply defined style guidelines to maintain consistent voice and formatting throughout the document.
Yes, you can use Diataxis to review and improve existing technical writing by detecting the current quadrant classification, evaluating the content against style guidelines, and restructuring mixed-messaging sections into focused documentation.
You need to split a documentation request into separate guides when the prompt spans more than one Diataxis quadrant. Detecting mixed tutorial, how-to, and explanation content requires prompting for separate documents to prevent structural inconsistency.
TumeloRamaphosaGenerate missing project documentation using the Diataxis framework.
Camilo8902Generate API documentation in Markdown, HTML, or Docusaurus from Express routes.
GeargrindadminCorrect documentation markdown files to comply with Diataxis and BMad Method style rules.
geekatronOrganize documentation into tutorials, how-to guides, references, and explanations.
