make-docslisted

Create, edit, and validate technical documentation using the Diataxis framework. Use when writing tutorials, how-to guides, reference docs, or explanations. Use when reviewing or auditing existing documentation for structural correctness. Use when deciding what type of document to write. Also use when the user mentions Diataxis, documentation quality, documentation types, or asks to write 'deep dive' articles, onboarding guides, API docs, or architectural explanations. Do NOT use for code comments, commit messages, changelogs, or README generation.
sergeyklay/.agents · ★ 5 · Code & Development · score 80

Install: claude install-skill sergeyklay/.agents

# Diataxis Documentation Framework Diataxis (from Greek *dia* "across" + *taxis* "arrangement") organizes documentation around **what the reader needs**, not what the author knows. It was created by Daniele Procida and adopted by Django, Canonical, Cloudflare, Gatsby, and hundreds of other projects. ## The Two Axes Documentation sits on two independent dimensions: ``` PRACTICAL (action) | Tutorials | How-to Guides learning by | achieving a specific doing | result | ACQUISITION --------- NEED ---------- APPLICATION (study) | (work) | Explanation | Reference understanding | looking up exact why | information | THEORETICAL (cognition) ``` **Axis 1 -- Action vs. Cognition.** Does this content serve what the reader *does*, or what the reader *understands*? **Axis 2 -- Acquisition vs. Application.** Is the reader *learning* something new, or *applying* what they already know? These axes are independent. Conflating them is the root cause of most documentation failures. ## The Compass -- Identify the Right Type When writing or reviewing any piece of documentation, ask two questions: | Question | Answer A | Answer B | |----------|--