Technical Writing
Overview
Three leaves cover docs-as-product. technical-docs.md chooses the doc set: README, tutorial, how-to, explanation, reference, release notes. procedures-sops.md writes the numbered steps: procedures, SOPs, runbooks, KB articles. ui-microcopy.md writes the strings inside the product: labels, errors, empty states.
When to use
- Building or restructuring a documentation set.
- Writing procedures and SOPs where a skipped step has a cost.
- Writing release notes and READMEs.
- Writing in-product copy the UI must render: errors, buttons, empty states.
When not to use
- Designing the UI, its layout or its components — outside this skill.
- Marketing copy, blog posts or persuasive pages — outside this skill.
- Client-facing memos or general business writing — outside this skill.
Precedence
The deepest loaded instruction governs its uniquely-claimed scope; every
scope:string is claimed by exactly one file in this tree; no leaf may widen a prohibition declared by an ancestor — leaves narrow, never override upward.
Subskill index
| Leaf | Task | Trigger |
|---|---|---|
subskills/technical-docs.md |
Doc types, README, guides, release notes | "write a README" |
subskills/procedures-sops.md |
Steps, SOPs, runbooks, KB | "write a procedure" |
subskills/ui-microcopy.md |
Buttons, errors, empty states | "write this error message" |
See also
subskills/technical-docs.md— pick the doc set first.subskills/ui-microcopy.md— the strings the reader meets mid-task.