From trogonstack-diataxis
Reorganize documentation into the Diataxis framework structure. Splits existing docs into tutorials, how-to guides, reference, and explanation sections.
How this skill is triggered — by the user, by Claude, or both
Slash command
/trogonstack-diataxis:diataxis-organize-docsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reorganize documentation by classifying content into the four Diataxis quadrants and creating a structured documentation hierarchy.
Reorganize documentation by classifying content into the four Diataxis quadrants and creating a structured documentation hierarchy.
| Quadrant | Orientation | Purpose | User Need |
|---|---|---|---|
| Tutorial | Learning | Teach through doing | "I want to learn" |
| How-to | Task | Solve specific problems | "I want to accomplish X" |
| Reference | Information | Describe the machinery | "I need facts about Y" |
| Explanation | Understanding | Clarify concepts | "I want to understand why" |
Scan the documentation directory and classify each file or section:
For each document/section, determine:
- Does it walk through steps to learn? → Tutorial
- Does it solve a specific problem? → How-to
- Does it describe APIs/configs/specs? → Reference
- Does it explain concepts/rationale? → Explanation
Organize docs into this hierarchy:
docs/
├── tutorials/ # Learning-oriented
│ ├── getting-started/
│ └── {topic}/
├── how-to/ # Task-oriented
│ ├── {task-category}/
│ └── troubleshooting/
├── reference/ # Information-oriented
│ ├── api/
│ ├── configuration/
│ └── architecture/
├── explanation/ # Understanding-oriented
│ ├── concepts/
│ ├── decisions/
│ └── background/
└── README.md # Navigation hub
Characteristics:
Example titles:
DO NOT include:
Characteristics:
Example titles:
DO NOT include:
Characteristics:
Example content:
DO NOT include:
Characteristics:
Example titles:
DO NOT include:
When a document contains multiple types:
Before (mixed document):
# Authentication
Authentication uses JWT tokens. (explanation)
## Quick Start
1. Install the package... (tutorial)
## API Reference
- `authenticate(user, pass)` - Returns token (reference)
## Troubleshooting
### Token Expired
If you see error X, do Y... (how-to)
After (split):
tutorials/authentication-quickstart.md
how-to/troubleshooting/token-expired.md
reference/api/authentication.md
explanation/concepts/authentication.md
Always use README.md as the root navigation file — never index.md.
Build a documentation hub that helps users find content by their need:
# Documentation
## Learning
New here? Start with our tutorials:
- [Getting Started](tutorials/getting-started.md)
- [Your First App](tutorials/first-app.md)
## Guides
Solve specific problems:
- [Deployment](how-to/deployment/)
- [Troubleshooting](how-to/troubleshooting/)
## Reference
Technical specifications:
- [API Reference](reference/api/)
- [Configuration](reference/configuration/)
## Understanding
Deep dives and background:
- [Architecture](explanation/architecture.md)
- [Design Decisions](explanation/decisions/)
After reorganization, verify:
| Problem | Solution |
|---|---|
| Tutorial with exhaustive options | Move options to reference, link to it |
| How-to explaining fundamentals | Extract to tutorial, assume knowledge |
| Reference with usage examples | Move examples to how-to |
| Explanation with code snippets | Keep only conceptual snippets |
| One giant README | Split into proper quadrants |
After analysis, report:
## Documentation Audit
### Current State
- Total documents: X
- Mixed documents: Y
- Missing quadrants: [list]
### Classification Results
| Document | Current Type | Recommended Type | Action |
|----------|--------------|------------------|--------|
| ... | ... | ... | Split/Move/Keep |
### Proposed Structure
[Directory tree with file placements]
### Cross-References Needed
- [doc A] should link to [doc B]
- ...
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub trogonstack/agentskills --plugin trogonstack-diataxis