docs-information-architecture

Organizes documentation sets using the Diátaxis framework of tutorials, how-tos, reference, and explanation.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Nandansai08/skillz --skill docs-information-architecture-nandansai08
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-information-architecture
Source: https://github.com/Nandansai08/skillz/tree/main/skills/writing-docs/docs-information-architecture
Command: npx skills add https://github.com/Nandansai08/skillz --skill docs-information-architecture-nandansai08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation sets grow into disorganized collections where users cannot find answers, pages mix tutorials with reference dumps, and navigation mirrors the org chart instead of user tasks. This Skill provides a structured workflow to audit, restructure, and maintain a docs site so users can actually find what they need. ## Core Features & Use Cases - Diátaxis Classification: Sorts every page into tutorial, how-to guide, reference, or explanation quadrants and splits fused multi-quadrant pages. - Corpus Audit and Curation: Labels each page by quadrant, findability, and currency, then decides keep, split, merge, or delete. - Journey-Priority Planning: Ranks documentation gaps by support ticket and search-query evidence rather than quadrant symmetry. - Use Case: A developer platform with 210 pages and 25 docs-answerable support tickets per week uses this workflow to audit the corpus, rebuild the sidebar around user goals, write the top missing how-tos, and cut tickets to 9 per week. ## Quick Start Use the docs-information-architecture skill to audit our documentation set and propose a restructured site organized by user tasks.

Frequently Asked Questions about docs-information-architecture

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

FAQPage Schema
How do I organize a documentation site users can't navigate?▼

Audit every page against the Diátaxis quadrants (tutorial, how-to, reference, explanation), then rebuild navigation around user goals rather than your org chart. Rank gaps by support ticket frequency and zero-result search queries to decide what to write first.

What is the difference between a tutorial and a how-to guide?▼

A tutorial is a learning-oriented guided lesson where the author controls everything for guaranteed success. A how-to guide is a task recipe for a competent user who is working, stating assumptions up front and getting straight to the steps.

When should I delete documentation pages?▼

Delete pages that are wrong, stale, or duplicated — wrong docs are worse than missing ones. Multiple outdated pages on the same topic erode user trust and pollute search results, so curation is a core part of the architecture.

Should I write the individual docs with this skill?▼

No. This skill covers the structure and placement of documentation, not authoring individual documents. Use readme-authoring, api-documentation, or runbook-authoring for writing the pages themselves.

How do I measure whether a docs restructure worked?▼

Track zero-result search queries, docs-answerable support tickets per week, and time-to-first-success on the getting-started tutorial. Capture baselines before restructuring and review the metrics on a regular cadence.