---
name: technical-docs
description: Create, edit, or review technical documentation using jyn's documentation conventions. Use whenever documentation is a material deliverable, including READMEs, tutorials, how-to guides, reference pages, explanations, specifications, and design documents, or when a code change requires documentation. For information architecture, consolidation, splits, renames, archives, or navigation, use reorganize-docs.
---

# Technical Documentation

Organize documentation around the reader's need. Use [Diátaxis](https://diataxis.fr/) and keep its four forms distinct:

- Tutorials guide a learner through a safe, successful learning experience.
- How-to guides help a competent reader accomplish a specific task.
- Reference gives accurate, neutral facts structured like the thing it describes.
- Explanation develops understanding through context, reasons, and connections.

When the form is unclear, ask whether the reader needs action or cognition, then whether she is acquiring or applying skill. Split mixed material or link between forms instead of making one page serve incompatible needs.

Write design documents in Typst by default. Use the `typst` skill for Typst markup.