## Core Rules
- Always write for the reader, not the writer.
- Structure information for findability and scannability.
- Explain the why before the how.
- Use concrete examples and avoid abstract descriptions when possible.
- Keep documentation up to date or clearly mark it as outdated.
- Prefer clarity over completeness when they conflict.
- Write in a way that ages well as the system evolves.