create-documentation

Generate Divio-style documentation with tutorials, how-to guides, reference, and explanations.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill create-documentation-tomzx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-documentation
Source: https://github.com/tomzx/agents/tree/main/skills/create-documentation
Command: npx skills add https://github.com/tomzx/agents --skill create-documentation-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create consistent, Divio-style documentation for features or components following a formal framework, saving time and ensuring structure.

Core Features & Use Cases

  • Organize docs into tutorials, how-to guides, reference, and explanations.
  • Consult the divio-documentation skill for guidance on DO/DON'T rules, templates, and structure.
  • Manage production workflow: decide which documentation types to produce and generate the output accordingly.

Quick Start

Document the feature by outlining its purpose, deciding which documentation types are needed, and producing tutorial, how-to, reference, and explanation sections following the Divio framework.

Frequently Asked Questions about create-documentation

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

FAQPage Schema
What is Divio-style documentation and when do I need it for feature development?▼

Divio-style documentation is a structured framework that separates docs into tutorials, how-to guides, reference, and explanations. You need it for feature development workflows requiring clear separation of concerns across different documentation types.

How do I generate feature documentation that includes tutorials, how-to guides, and reference content?▼

To generate feature documentation, outline the feature purpose, decide which documentation types are needed, and produce tutorial, how-to, reference, and explanation sections following the Divio framework with a structured front-matter-driven output.

Can I produce only reference documentation without generating tutorials and explanations?▼

Yes, the production workflow lets you decide which documentation types to produce. You can select only the reference content type and generate the output accordingly, skipping tutorials, how-to guides, or explanations if they are not needed.

What's the best way to structure component documentation for onboarding and reference?▼

The best way to structure component documentation is using the Divio framework, which organizes content into tutorials for onboarding, how-to guides for tasks, reference for technical details, and explanations for concepts, ensuring clear separation of concerns.

Do I need any specific dependencies or components to automate Divio documentation generation?▼

No specific dependencies or components are required to automate Divio documentation generation. The skill operates independently to produce a multi-section documentation layout with structured front-matter-driven output for your features.

Why does my feature documentation lack a clear separation of concerns between guides and reference?▼

Feature documentation lacks clear separation when not using a formal framework. Applying the Divio structure separates tutorials, how-to guides, reference, and explanations into distinct sections, preventing mixed concerns and ensuring consistent, structured output.