diataxis

Classify documentation content into Diátaxis tutorial, how-to, reference, and explanation categories.

6|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/markacianfrani/armor --skill diataxis-markacianfrani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diataxis
Source: https://github.com/markacianfrani/armor/tree/main/skills/diataxis
Command: npx skills add https://github.com/markacianfrani/armor --skill diataxis-markacianfrani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves documentation bloat and confusion by enforcing the Diátaxis framework, preventing the common pitfall of mixing tutorials, how-to guides, reference material, and conceptual explanations.

Core Features & Use Cases

  • Documentation Classification: Instantly categorize existing content to identify boundary violations.
  • Structural Guidance: Provides clear rules for writing tutorials, how-to guides, reference docs, and explanations.
  • Use Case: Use this when you are unsure if a new document should be a step-by-step guide or a technical reference, or when you need to audit a messy wiki to improve its scannability and utility.

Quick Start

Ask the diataxis skill to review the current document and suggest how to split it into appropriate tutorial and reference sections.

Frequently Asked Questions about diataxis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to structure technical documentation to avoid content bloat?

Applying the Diátaxis framework resolves documentation bloat by separating content into four distinct categories: tutorials, how-to guides, reference material, and explanations. This structured approach prevents the common pitfall of mixing action-oriented tasks with cognition-oriented knowledge.

How do I audit existing technical writing to identify structural issues?

To audit technical writing, classify existing documentation content into the four Diátaxis categories to instantly identify boundary violations. This classification reveals where a messy wiki mixes tutorials with reference docs, helping you improve scannability and overall utility.

When do I need to separate tutorials and reference material in my documentation?

You need to separate tutorials and reference material whenever you are unsure if a new document should be a step-by-step guide or a technical reference. Enforcing the Diátaxis framework provides clear rules for writing action-oriented tutorials distinct from reference docs.

Can I use this approach to plan documentation architecture for a complex knowledge base?

Yes, you can use the Diátaxis framework for documentation architecture planning across a complex knowledge base. It satisfies the requirement for structured, user-centric documentation by categorizing existing content and providing rules for content refinement workflows.

How does the Diátaxis framework improve content strategy for technical writing?

The Diátaxis framework improves content strategy by providing structural guidance that categorizes documents into tutorials, how-to guides, reference, and explanation. This enforces a structured, user-centric approach that separates action-oriented tasks from cognition-oriented knowledge.