Rules files are loaded often, so every unnecessary paragraph uses context on many requests. Long files also make important guidance harder to notice. Conflicting or overly detailed rules can cause the assistant to follow the wrong instruction or spend time reconciling advice that does not apply.
Keep only stable, high-impact facts that change how work should be done. Use clear commands, short examples, and links to deeper documentation. Move subsystem guidance into scoped files when supported. Remove rules that a formatter, type checker, or test already enforces automatically. Review the file after repeated agent mistakes and after architecture changes. Lean rules reduce cost, improve attention, and are easier for people to keep accurate.
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
