documentation-writer

The Diátaxis framework structures technical documentation across four quadrants: Tutorials, How-to guides, References, and Explanations. This Skill generates content aligned to each quadrant, ensuring audience-specific guidance with consistent tone and Markdown-ready outputs.

The best way to structure software documentation is separating content by intent. This Skill uses the Diátaxis method to distinguish learning-oriented Tutorials from task-oriented How-tos, information-oriented References, and understanding-focused Explanations.

Yes, you can generate API documentation and user guides in Markdown format. This Skill produces Markdown-ready outputs across all Diátaxis quadrants, supporting onboarding, API references, and user guides requiring structured, audience-specific content.

Yes, the Diátaxis documentation method works effectively for developer onboarding. This Skill creates learning-oriented Tutorials and task-oriented How-tos that guide new developers through software workflows with clear, step-by-step, audience-specific instructions.

You maintain consistent tone and terminology across user guides by using guided prompts and templates. This Skill enforces Diátaxis structure and consistency, reducing maintenance time while ensuring clear intent across all generated documentation.

You should not use template-based documentation generation when content requires highly unstructured, narrative formats outside the Diátaxis quadrants. This Skill enforces strict separation into Tutorials, How-tos, References, and Explanations, which may not suit free-form documentation needs.