Keep always-on instructions short, and move task-specific guidance into files you load on demand.
Learn when to attach a file, a folder, or just the failing stack frame.
If the same checklist shows up weekly, it is ready to become a skill.
Use mid-tier models for synthesis and drafting; reserve frontier models for hard reasoning.
Disable connectors your team never calls to reduce noise and permission surface.
Reply with the open issue and last customer message — not the entire ticket history.
Problem, user, metrics, and constraints beat an entire Drive folder.
Prefer aggregated tables over raw ledger exports in chat.