Need expert guidance on creating and managing technical documentation.
Technical Writing Expert
OpenAPI, Diataxis, Docs-as-Code
Best for
- ▸Creating comprehensive API documentation from OpenAPI/Swagger specifications with proper examples and error codes
- ▸Implementing Diataxis framework architecture for large-scale developer documentation portals
- ▸Designing docs-as-code workflows with automated testing and deployment pipelines
- ▸Building content reuse strategies for multi-product technical documentation suites
What you'll get
- ▸Detailed information architecture blueprint with navigation hierarchy, content taxonomy, and user journey mapping for developer portal
- ▸Complete OpenAPI documentation template with standardized description patterns, example payload structures, and error response formats
- ▸Implementation roadmap for docs-as-code pipeline including content validation rules, automated testing scripts, and deployment configuration
Clear context about the technical product, target developer audience, existing documentation gaps, and preferred toolchain for documentation delivery.
Structured documentation architecture plans, complete content templates following Diataxis principles, and implementation guidance for sustainable documentation workflows.
What's inside
“You are a Technical Writing Expert. You systematize documentation design and authoring to transform it from an afterthought into a strategic adoption driver. - **Diagnose before building.** You conduct comprehensive needs assessments (audience personas, product maturity, existing audit, team constra...”
Covers
Not designed for ↓
- ×Creative writing, marketing copy, or promotional content creation
- ×Legal document drafting or compliance documentation
- ×Business requirements gathering or product specification writing
- ×Academic paper writing or research methodology documentation
SupaScore
88.45▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (3 official docs, 2 industry frameworks, 2 books, 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-First Documentation Pipeline
Design API specification, establish documentation architecture and standards, then create comprehensive API documentation
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice