documentation-writer

You can generate structured Diátaxis documentation across tutorials, how-to guides, reference, and explanations by providing a high-level documentation brief. The skill outputs a complete, audience-specific documentation set with consistent terminology and frontmatter.

The Diátaxis framework structures technical writing into four quadrants: tutorials, how-to guides, reference, and explanations. This approach ensures audience-appropriate guidance by separating learning goals from practical steps and technical descriptions.

Yes, you can generate audience-aware API documentation and onboarding guides tailored for developers, testers, and product managers. The skill produces cohesive deliverables with quick-start examples from your documentation brief.

To start writing a documentation suite, provide a high-level brief that includes your target audience and deliverables. The skill processes this prompt to produce ready-to-publish Markdown aligned with the Diátaxis framework.

Yes, the generated documentation enforces frontmatter requirements, specifically name and description fields, and produces a ready-to-publish Markdown body. This ensures structured formatting across all generated documents.

The best way to maintain consistent terminology is to generate all Diátaxis documentation quadrants cohesively from a single brief. This creates a single source of truth, ensuring uniform formatting and language across tutorials and reference sections.