diataxis

Classify technical documentation into tutorials, guides, references, and explainers.

2|Updated Aug 24, 2024
One-click install
npx skills add https://github.com/ghalactic/provision-github-tokens --skill diataxis-ghalactic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diataxis
Source: https://github.com/ghalactic/provision-github-tokens/tree/main/.agents/skills/diataxis
Command: npx skills add https://github.com/ghalactic/provision-github-tokens --skill diataxis-ghalactic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the confusion of choosing the right documentation format, ensuring your technical content is structured, purposeful, and easy for users to navigate.

Core Features & Use Cases

  • Systematic Classification: Uses the Diátaxis framework to categorize content into Tutorials, Guides, Reference, or Explainers based on user intent.
  • Content Optimization: Provides clear principles for writing each documentation type to improve clarity and reduce cognitive load.
  • Use Case: When you need to write a new README or technical guide, use this Skill to determine whether you are teaching a skill (Tutorial) or providing a reference for an expert (Reference), ensuring the tone and structure match the user's needs.

Quick Start

Use the diataxis skill to help me classify and outline a new documentation set for my project.

Frequently Asked Questions about diataxis

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

FAQPage Schema
How do I structure technical documentation to improve clarity and reduce cognitive load?

Structure technical documentation by applying the Diátaxis framework, which classifies content into tutorials, guides, reference materials, and explainers. This systematic classification reduces cognitive load by enforcing strict separation of content types based on user intent.

What is the difference between a tutorial and a guide when writing a README?

A tutorial teaches a skill by guiding beginners through a practical exercise, whereas a guide helps users solve specific real-world problems. The Diátaxis framework ensures your README matches the correct tone and structure for the user's needs.

How do I classify technical writing into the right documentation format?

Classify technical writing using a decision-making compass based on the axes of action versus cognition and acquisition versus application. This determines whether content should be a tutorial, guide, reference, or explainer.

When should I write reference materials instead of an explainer for my project?

Write reference materials when providing factual information for experts to consult during application, and write explainers to illuminate topics for cognition and understanding. The Diátaxis framework enforces this strict content separation.

What is the best way to outline a new documentation set for a software project?

Outline a new documentation set by systematically categorizing content into tutorials, guides, reference, and explainers using the Diátaxis framework. This provides a decision-making compass for content organization and ensures documentation consistency.

Does applying a content strategy framework help with separating technical writing formats?

Yes, applying a content strategy framework like Diátaxis helps by providing specific writing principles for each category and enforcing strict separation of content types. This ensures your technical writing remains purposeful and easy to navigate.