domains / families / documents / documentation

documentation

combined

Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing. Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.

When to use

• Creating user guides
• API documentation
• Tutorial content
• Restructuring existing documentation to better serve different user needs and contexts
• Creating project documentation
• Generating API documentation
• Writing architecture docs
• Documenting code

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies overlap in scope (both cover creating and structuring technical documentation) but each contains material steps the other lacks. The mcollina copy is a self-contained Diátaxis procedure with type-specific patterns, validation checks, and a decision tree. The sickn33 copy is a workflow bundle that orchestrates other skills for API docs, architecture diagrams, READMEs, wikis, and changelogs, and includes quality gates and a scope/authorization constraint. Neither is a reproduction of the other, so crowning one would hide a real alternative.