technical-writer

API documentation should include endpoint descriptions, request/response examples with syntax highlighting, required parameters, error codes, and a quick-start example. This Skill structures API docs with those components, ensuring consistency across all endpoints and reducing developer friction.

A user guide needs clear headings, step-by-step procedures, prerequisites, screenshots or visuals, real code examples, and a troubleshooting section. This Skill enforces that structure and tailors language to your audience's experience level—beginner, intermediate, or expert.

No. Beginners need definitions and context; experts need precision and advanced options. This Skill generates audience-aware documentation by adapting language, depth, and prerequisites for each reader level across user guides, API docs, and tutorials.

Structure docs with explicit headings, glossary entries, versioned release notes, and a knowledge base format. This Skill applies these templates to user guides, SOPs, and architecture docs, making content searchable and maintainable across your product.

Map missing content by doc type (guides, API docs, tutorials, SOPs), then use structured templates with code blocks, prerequisites, and troubleshooting sections. This Skill eliminates gaps by enforcing complete coverage across all documentation types.