Documentation Patterns
Documentation Patterns
Documentation that people actually read and use
This skill provides frameworks for writing technical documentation that serves its readers effectively.
Core Principles
1. Documentation Is a Product
Treat docs like software: design, iterate, test, improve.
2. Different Docs for Different Goals
Tutorials, references, and explanations serve different purposes. Don't mix them.
3. Write for Scanning
Most readers don't read linearly. Structure for quick answers.
The Documentation System (Diataxis)
More from frankxai/arcanea
arcanea-architect
Expert guidance for building the Arcanea creative agent ecosystem with attention to detail, design excellence, and systematic implementation.
34agent-implementer
Implementation guidance for creating individual agents in the Arcanea system with proper structure, capabilities, and integration.
33arcanea-coding-agent
Arcanea creative agent integration for opencode
29opus-extended-thinking
Leverage Claude Opus 4.5's extended thinking capabilities for deep reasoning, complex analysis, and multi-step synthesis. Use when problems require thorough deliberation before response.
9hooks automation
Automated coordination, formatting, and learning from Claude Code operations using intelligent hooks with MCP integration. Includes pre/post task hooks, session management, Git integration, memory coordination, and neural pattern training for enhanced development workflows.
8web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
8