Design and organize complex technical documentation for developers.
Technical Documentation Architect
Diataxis, Docusaurus, MkDocs
Best for
- ▸Design scalable docs architecture for multi-version API products using Diataxis framework
- ▸Plan content reuse strategies across tutorial, reference, and guide documentation
- ▸Architect developer documentation sites with proper versioning and localization workflows
- ▸Structure technical writing workflows for docs-as-code with automated publishing pipelines
What you'll get
- ▸Comprehensive site map with Diataxis categorization, URL hierarchy, cross-linking strategy, and progressive disclosure patterns for different user journeys
- ▸Technical implementation blueprint specifying documentation toolchain, CI/CD pipeline, versioning approach, and content governance workflows
- ▸Information architecture diagram showing content relationships, user flows, and maintenance responsibilities across documentation types
Product details, user personas (developers, admins, end-users), existing documentation audit, team capacity, and technical constraints for the documentation system.
Complete documentation architecture blueprint including Diataxis-based information structure, versioning strategy, toolchain recommendations, and content governance framework.
What's inside
“You are a Technical Documentation Architect. You design information architecture, content systems, and developer experiences for documentation at scale. - **Apply Diataxis rigorously**: Classify all documentation into Tutorials (learning-oriented), How-to Guides (task-oriented), Reference (informati...”
Covers
Not designed for ↓
- ×Writing individual documentation pages or tutorials (content creation vs architecture)
- ×Marketing website copy or sales collateral (developer-focused technical docs only)
- ×General copywriting or business writing without technical documentation requirements
- ×Simple single-product documentation that doesn't need complex architecture
SupaScore
88.3▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (1 industry frameworks, 2 books, 4 official docs, 1 community practice)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
v5.5 distilled from v2 via Claude Sonnet
Pipeline v4: rebuilt with 3 helper skills
Initial release
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
Common Workflows
API Platform Documentation Design
Design API structure, architect comprehensive docs system, then create detailed API documentation content
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice