skills.rest
WebMCP-org
WebMCP-orgOFFICIAL
Explore all skills by this author →
WebsiteGitHub

diataxis

Classify and structure documentation by purpose using the Diátaxis framework.

2|2|Updated Aug 4, 2025
Search Tags:#documentation#explanation#tutorials#diataxis#how-to-guides#classify#content-type
One-click install
npx skills add https://github.com/WebMCP-org/docs --skill diataxis-webmcp-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diataxis
Source: https://github.com/WebMCP-org/docs/tree/main/_diataxis
Command: npx skills add https://github.com/WebMCP-org/docs --skill diataxis-webmcp-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diátaxis provides a framework to write and restructure technical documentation by aligning content with four core needs—tutorials, how-to guides, reference, and explanation—so teams classify and present information clearly.

Core Features & Use Cases

  • Clear separation of documentation types and guidance on when to use each.
  • Practical workflows for writing, reviewing, and reorganizing content according to the Diátaxis compass.
  • Use cases span tutorials for learning, how-to guides for tasks, references for instruction, and explanations for context.

Quick Start

Classify a new page by user need and assign it to the appropriate Diátaxis type.

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 by purpose instead of topic?▼

Structure technical documentation by aligning content with four Diátaxis types: tutorials, how-to guides, reference, and explanation, ensuring clear placement based on user needs.

What is the difference between a tutorial and a how-to guide in documentation?▼

Tutorials are designed for learning and study, guiding users through a practical task, while how-to guides address specific work scenarios, helping users solve a problem at hand.

When should I use reference material versus explanation in technical docs?▼

Use reference material to provide precise technical instruction for users at work, and use explanation content to provide context and deeper understanding for users at study.

How do I classify a new documentation page using the Diátaxis framework?▼

Classify a new page by identifying the user need and determining whether the user is at study or work, then assign it to the appropriate Diátaxis type and enforce frontmatter requirements.

What is the best way to separate content types in a documentation project?▼

The best way to separate content types is to apply the Diátaxis compass, which enforces strict boundaries between tutorials, how-to guides, reference, and explanation for clear user guidance.

Does Diátaxis enforce specific metadata or frontmatter for documentation pages?▼

Yes, Diátaxis enforces frontmatter requirements and separation of content types, providing guidance for writing and validating skill metadata to maintain structural integrity.

Related Skills

Explore More Content & Communication Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
Tresillo2017Tresillo2017
4

documentation-writer

Generate Diátaxis-style tutorials, how-to guides, references, and explanations for software features.

Community
Advanced
ddttomddttom

md-workflow

Create, edit, and lint Markdown files with YAML frontmatter awareness.

Community
Intermediate
kitchen-engineer42kitchen-engineer42
130

file-organization-and-structure

Organize source code files with conventional content ordering and routine separation.

Community
Intermediate