Documentation Skill

Unifies all Diataxis documentation guidance into one Skill. Claude activates this Skill whenever documentation should be written, reviewed, or improved, and then "lazy loads" the exact documentation type guidance by opening the reference docs linked below.

Critical Workflow

REQUIRED: Before writing or reviewing ANY documentation, you MUST load the relevant documentation type reference file(s) using the Read tool.

•Use the Compass to identify the documentation type needed (see below)
•
Read the matching reference file(s) BEFORE writing/reviewing:
- •Learning experiences → Read references/tutorials.md
- •Task-oriented guides → Read references/how-to-guides.md
- •Information lookup → Read references/reference.md
- •Understanding & context → Read references/explanation.md
•Apply the documentation type's principles from the loaded reference
•Write or review documentation according to that type's standards

DO NOT attempt to write or review documentation without first loading the appropriate reference file(s).

The Diataxis Compass

The compass is your primary decision-making tool. Ask two questions:

Question 1: Action or Cognition?

•Action = Practical steps, doing things, hands-on work
•Cognition = Theoretical knowledge, thinking, understanding

Question 2: Acquisition or Application?

•Acquisition = Study, learning something new
•Application = Work, using skills to accomplish tasks

The Four Quadrants

code

                    ACQUISITION              APPLICATION
                    (Study)                  (Work)
              ┌─────────────────────┬─────────────────────┐
              │                     │                     │
   ACTION     │     TUTORIALS       │    HOW-TO GUIDES    │
   (Doing)    │   Learning-oriented │    Task-oriented    │
              │   "Teach me"        │    "Help me do X"   │
              │                     │                     │
              ├─────────────────────┼─────────────────────┤
              │                     │                     │
   COGNITION  │    EXPLANATION      │     REFERENCE       │
   (Knowing)  │ Understanding-      │  Information-       │
              │    oriented         │     oriented        │
              │   "Help me          │    "What is the     │
              │    understand"      │     spec for X?"    │
              └─────────────────────┴─────────────────────┘

Quick Decision Guide

User Need	Action/Cognition	Acquisition/Application	→ Type
"How do I get started?"	Action	Acquisition	Tutorial
"How do I deploy to prod?"	Action	Application	How-to
"What parameters does X accept?"	Cognition	Application	Reference
"Why does the system work this way?"	Cognition	Acquisition	Explanation

Key Distinctions (Critical!)

Tutorial vs How-to Guide

Both contain steps, but serve fundamentally different purposes:

Aspect	Tutorial	How-to Guide
User	Learner, may not know enough to ask questions	Competent practitioner who knows their goal
Responsibility	Teacher bears responsibility for success	User bears responsibility for outcomes
Approach	Concrete, specific, controlled environment	General, adaptable to real-world variation
Path	Single path, no choices	Multiple routes, branching options
Completeness	Must be complete end-to-end	Can start/end at reasonable points
Safety	Must be safe, can always restart	Cannot promise safety
Focus	Learning through doing	Getting work done

Reference vs Explanation

Both provide knowledge, but for different contexts:

Test Question	If Yes →	If No →
Would someone turn to this while actively working?	Reference	Explanation
Could you imagine reading this in the bath?	Explanation	Reference
Is it lists, tables, or technical specs?	Reference	Explanation
Does it answer "why?" questions?	Explanation	Reference

Applying Diataxis: Iterative Approach

Do NOT create empty structures. Don't create /tutorials, /how-to, /reference, /explanation folders with nothing in them.

Start small:

•Pick any existing documentation
•Apply compass to determine what type it should be
•Improve it according to that type's principles
•Repeat

Let structure emerge: As you improve individual pieces, patterns will emerge that suggest organizational structure. The top-level structure forms from the inside out.

Documentation Type References (load on demand)

•Tutorials - Learning-oriented experiences enabling skill acquisition through guided practice
•How-to Guides - Task-oriented directions for accomplishing specific goals
•Reference - Information-oriented technical descriptions for authoritative lookup
•Explanation - Understanding-oriented discussions providing context and answering "why?"

Key Principles

•Different contexts need different documentation - Users learning need tutorials; users working need how-to guides or reference; users seeking understanding need explanation
•Separation of concerns - Keep documentation types distinct to prevent confusion
•User-centered approach - Consider what the user is trying to accomplish and in what context
•Iterative improvement - Enhance documentation incrementally by applying Diataxis principles
•Purpose-driven structure - Each type has specific characteristics that make it effective for its intended purpose