documentation

Organize technical documentation into tutorials, how-to guides, references, and explanations.

7|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Harmeet10000/skills --skill documentation-harmeet10000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/Harmeet10000/skills/tree/main/skills/writing-docs/documentation
Command: npx skills add https://github.com/Harmeet10000/skills --skill documentation-harmeet10000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation teams often wrestle with scattered information, inconsistent structure, and slow onboarding. This Skill helps you create, structure, and review documentation consistently according to the Diátaxis framework, reducing ambiguity and speeding up delivery.

Core Features & Use Cases

  • Organizes content into tutorials, how-to guides, references, and explanations to address different user goals
  • Provides a standardized workflow for drafting, reviewing, and restructuring documents
  • Facilitates fast onboarding and cross-linking between related content

Quick Start

Ask the AI to classify your docs into tutorials, how-to guides, references, and explanations, then draft an initial outline.

Frequently Asked Questions about documentation

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

FAQPage Schema
What is the Diataxis framework for technical documentation?

The Diataxis framework structures technical documentation into four distinct types: tutorials, how-to guides, references, and explanations. This classification addresses different user goals, reducing ambiguity and ensuring content serves its specific purpose.

How do I organize technical documentation into tutorials and how-to guides?

You can organize technical documentation by classifying existing content into the Diataxis categories. Ask the AI to categorize your docs into tutorials, how-to guides, API references, and explanations, then generate an initial structured outline.

What is the best way to structure API references and user guides consistently?

Structuring API references and user guides consistently requires a standardized workflow. This approach enforces a metadata-driven process with YAML frontmatter requirements and a three-part description structure, ensuring uniform validation and cross-linking across documents.

Does this documentation approach require YAML frontmatter for content organization?

Yes, this content organization approach requires YAML frontmatter. It enforces a metadata-driven workflow where each document must include specific name and description fields within the YAML frontmatter to validate structural consistency.

How do I write consistent Quick Start instructions for a technical project?

To write consistent Quick Start instructions, apply the Diataxis framework to classify and refine content. This process guides you through crafting clear usage steps and validation criteria, ensuring your quick start instructions remain consistent and actionable.

When should I use Diataxis over standard technical writing methods?

Use Diataxis over standard technical writing methods when your documentation suffers from scattered information and inconsistent structure. It provides a standardized workflow for drafting and reviewing, which accelerates onboarding and clarifies content boundaries.