# Skill: Write Documentation
**Trigger:** documentation, docs, README, docstring, explain
**Description:** Write documentation from real code — never invent or guess API behavior.
## Body
When writing documentation:
1. READ the actual source code of the module/function first.
2. Document: purpose, parameters, return values, examples.
3. For READMEs: installation, usage, architecture overview.
4. For docstrings: follow language conventions (/// for Rust, """ for Python).
5. Include real code examples that work.
6. NEVER document behavior you haven't verified in the actual source.