Documentation Patterns

Organize technical documentation using Diataxis framework types and actionable templates.

6|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/frankxai/arcanea --skill documentation-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Documentation Patterns
Source: https://github.com/frankxai/arcanea/tree/main/.claude/skills/community/documentation-patterns
Command: npx skills add https://github.com/frankxai/arcanea --skill documentation-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical writing frameworks for clear, maintainable documentation.

Core Features & Use Cases

  • Tutorials (Learning)
  • How-To Guides (Goals)
  • Reference (Information)
  • Acquisition/Applications (Working)

Quick Start

Create a Tutorial or How-To with clear learning outcomes, actionable steps, prerequisites, and scannable sections.

Frequently Asked Questions about Documentation Patterns

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

FAQPage Schema
How do I structure technical documentation so readers actually use it?

Structure documentation into four distinct types: Tutorials for learning by doing, How-To Guides for task-driven workflows, Reference entries for lookup accuracy, and Explanations for conceptual understanding. This Diataxis framework ensures each section serves a specific reader need and supports different learning styles.

What's the difference between a tutorial and a how-to guide in documentation?

Tutorials teach concepts through hands-on learning with clear outcomes and prerequisites; how-to guides help readers accomplish specific goals with actionable steps. Tutorials build foundational knowledge; how-to guides solve immediate problems.

How do I write documentation that's scannable and easy to navigate?

Use reader-centered structure with clear headings, numbered steps, checklists, and prerequisites. Format content for scanning by breaking long text into short sections, highlighting key actions, and grouping related information so readers find answers quickly.

When should I use the Diataxis documentation framework instead of other approaches?

Use Diataxis when documentation lacks clarity or consistency across tutorials, guides, and reference material. It's effective for software and technical documentation where readers need different content types—learning resources, task instructions, lookup material, and explanations—in one system.

Can I apply documentation patterns to non-software technical writing?

Yes. The Diataxis framework applies across software and technical documentation domains. Its four types—tutorials, how-to guides, references, and explanations—solve clarity and consistency problems wherever technical knowledge needs structured, reader-centered documentation.

What should I include in a how-to guide template?

Include prerequisites, clear goal statement, numbered actionable steps, relevant examples, and a checklist for verification. This template structure ensures readers know what they need before starting and can verify they completed the task successfully.