documentation

Generate Diataxis-compliant documentation guidance across four documentation types.

2|2|Updated May 30, 2025
One-click install
npx skills add https://github.com/wodsmith/thewodapp --skill documentation-wodsmith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/wodsmith/thewodapp/tree/main/.claude/skills/documentation
Command: npx skills add https://github.com/wodsmith/thewodapp --skill documentation-wodsmith

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes Diataxis documentation guidance so Claude can write, review, or improve documentation following the four distinct types (tutorials, how-to guides, reference, explanation).

Core Features & Use Cases

  • Unified guidance: Access the specific principles and patterns for Tutorials, How-to Guides, Reference, and Explanation on demand.
  • On-demand references: Claude lazy-loads the chosen type reference before drafting or reviewing.
  • Quality guardrails: Helps ensure documentation adheres to the Diataxis framework.

Quick Start

Load the relevant documentation type reference (Tutorials, How-to Guides, Reference, or Explanation) before writing or reviewing, then apply its guidance to produce consistent, purpose-driven docs.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I write documentation that follows the Diataxis framework?

Diataxis documentation separates content into four distinct types—tutorials, how-to guides, reference, and explanation—each with specific purposes and principles. Load the relevant reference file for your documentation type to apply its guidance, ensuring your content serves its intended user goal and follows consistent structural patterns.

What's the difference between a tutorial, how-to guide, reference, and explanation?

Tutorials teach by doing and build confidence; how-to guides solve specific problems step-by-step; reference provides facts and specifications for lookup; explanation builds understanding through context and narrative. Each type serves a different user need and requires distinct writing patterns and organization.

How do I review documentation for Diataxis compliance?

Review documentation to verify it adheres to its declared type by loading the type-specific reference guidance, then checking whether structure, tone, examples, and goals align with Diataxis principles. Misclassified content should be reorganized or rewritten to match its intended purpose.

Can I mix tutorials, how-to guides, reference, and explanation in one document?

Mixing documentation types within a single document creates confusion because each type optimizes for different user goals and reading patterns. Keep each type separate and link between them; use the type-specific reference guidance to ensure boundaries are clear.

What should I do before writing documentation with Diataxis principles?

Before writing, identify which documentation type—tutorial, how-to guide, reference, or explanation—fits your user's goal, then load its corresponding reference file to understand its specific principles, structure, and patterns before drafting.

Does Diataxis work for technical and non-technical documentation?

Diataxis principles apply across domains because they address how users learn and retrieve information regardless of subject matter. The four types—tutorials, how-to guides, reference, explanation—work for any field; load the relevant reference to adapt the framework to your context.