---
alwaysApply: true
---

# Documentation quality standards

1. Start with prerequisites and intended audience.
2. Include runnable examples and expected outcomes.
3. Keep terminology consistent with code and APIs.
4. Document failure modes and troubleshooting steps.
5. Prefer concise task-oriented structure over long narrative.