| name | write-docs |
| description | Write documentation in the Beyond voice. Use when writing API docs, guides, tutorials, or reference material. |
| allowed-tools | Read, Glob, Grep, Edit, Write |
| model | claude-sonnet-4-6 |
Before Writing
Load the verbal identity:
Read: .claude/skills/brand/verbal-identity.md
Docs Voice: Most Precise
Documentation is where precision matters most. Clear, direct, technical. Assume competence. Code over prose. No preamble, no context-setting.
Key Principles
- Assume competence — Don't explain what developers already know
- Code over prose — Show, don't tell
- No preamble — Get to the point immediately
- Technical words OK — fork, snapshot, checkpoint, restore, CoW are fine here
Example
POST /boxes/{id}/promote deploys a checkpoint to production.
Not:
In order to deploy your changes to production, you'll need to use our promote endpoint, which takes your checkpoint and makes it live...
Structure
- What it does — One sentence
- How to use it — Code example
- Parameters/Options — Table or list
- Edge cases — Only if non-obvious
Technical Vocabulary (OK in docs)
These need to be explained once when introduced, then used freely:
- fork
- snapshot
- checkpoint
- restore
- promote
- CoW (copy-on-write)
Voice Calibration
| Aspect | Docs Approach |
|---|
| Tone | Neutral, precise |
| Assumptions | Reader is competent |
| Length | Minimal |
| Code:Prose | More code, less prose |
| Warmth | None needed |
Before Publishing
- Can this be shorter?
- Is there a code example?
- Am I explaining something obvious?
- Would I be annoyed reading this as a developer?
- Does the first sentence say what this does?