# Project Instructions
## Code Changes
- Add concise comments at important rules, invariants, protocol details, and non-obvious decisions. Do not add comments that merely restate the code.
- Do not overuse tuples. When a tuple has several fields or its values have distinct meanings, use a named `struct` instead. Small tuples are acceptable for simple, obvious pairs.
- Keep the project skill synchronized with the implementation. The skill at `.agents/skills/rust-codebase-navigation/SKILL.md` is developed from this project, so update it in the same change whenever commands, flags, workflows, or supported behavior change.
## Development and Verification
- Use `cargo run -- ...` for development and CLI verification. Do not run a stale binary directly from `target/debug`.
- Before finishing a change, run:
```powershell
cargo clippy
cargo fmt
```