A few habits make the catalogue earn its keep:
- Route before you load. A short prompt to
rust-routercosts little and avoids loading skills you will not use. - Prefer one language skill plus at most one domain or architecture skill for any single task.
- Stop when the answer is turning into a tutorial. Cut back to the decision that actually matters and the skill that owns it.
- Treat verification as a layered investment. Miri and proptest pay off early; Kani and Verus pay off when the property is small, load-bearing, and hard to test by example.
- Record the decision, not the discussion. ADRs are for the hard-to-reverse parts; routine choices belong in code review.