gistfile1.txt

## Learning-first documentation style

This project is primarily for learning. Optimize for teaching clarity over terseness.

- Use Rust doc comments (`///` and `//!`) liberally on modules, types, fields, and functions.
- It is acceptable for docstrings to be repetitive if repetition helps learners connect concepts.
- Prefer didactic explanations of "what", "why", and "how" even when this increases verbosity.
- Include concrete API context in docs (for example, what schedule/system set a Bevy system belongs to, or why a specific Bevy/egui type is used).
- When in doubt, choose more explanation rather than less.