docs-architect

Structure and refactor technical documentation for developer products and SaaS.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/dataroaring/skills --skill docs-architect-dataroaring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-architect
Source: https://github.com/dataroaring/skills/tree/main/skills/docs-architect
Command: npx skills add https://github.com/dataroaring/skills --skill docs-architect-dataroaring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires wordfreq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you structure, write, review, and refactor technical documentation so readers can quickly find the right page, understand it, and take the next step without getting lost.

Core Features & Use Cases

  • Information architecture: Organize docs by user task, not internal product structure.
  • Page design and review: Apply Diátaxis, landing-page patterns, and long-form page structure to tutorials, how-tos, reference pages, explanations, and topic surveys.
  • Docs quality and clarity: Improve headings, prose, cross-linking, examples, and AI-readability for developer documentation.
  • Use case: A docs team can use this Skill to decide whether a section should be split, how a landing page should route readers, and how to rewrite a guide so it is clearer for both humans and LLMs.

Quick Start

Ask the docs architect skill to review this documentation section and recommend the best page structure, headings, and next-step links.

Frequently Asked Questions about docs-architect

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

FAQPage Schema
How do I improve technical documentation structure for developer products?

Improve technical documentation structure by organizing content by user task rather than internal product structure, applying Diátaxis patterns to tutorials and reference pages, and refactoring headings for clearer navigation.

What is the best way to make SaaS docs readable for both humans and LLMs?

Make SaaS docs readable for humans and LLMs by applying AI-readable markdown guidance, editing prose for clarity, and structuring sections with cross-link strategies that help readers and models find related pages.

How do I use Diátaxis to plan docs architecture and section landing pages?

Use Diátaxis to plan docs architecture by separating content into tutorials, how-tos, reference, and explanation, then design section landing pages that route readers to the correct page type based on their intent.

When should I split a long documentation guide into separate pages?

Split a long documentation guide into separate pages when user intent splits across task types, using page refactoring and landing-page patterns to route readers to tutorials, how-tos, or reference pages without getting lost.

Can I use this approach to review and refactor existing markdown documentation?

Use this approach to review and refactor existing markdown documentation by applying a docs review checklist that evaluates information architecture, page structure, cross-linking, and prose clarity for developer products.