curating-global-instructions
Curating Global Instructions
The global instruction file is read at the start of every session, whatever the project. Its length is a cost paid by every session that follows, so it should hold what governs the work: rules, invariants and decisions that must not be re-derived.
Core principle: every section is either a rule — something that must fire unconditionally — or a technique, which needs a trigger. Rules stay. Techniques move to a skill, where they load when wanted.
The one question
Ask it of every section, and of everything you are about to add:
Is this a rule, or a technique?
A rule — a constraint, a decision, a precedence — fires whether or not anything else loads. It stays. A technique — how to do something, once you know you are doing it — has a trigger, and belongs in a skill. Adding without asking this is how the file grows; trimming without asking it is how a rule disappears.
Before moving anything to a skill
Compare against the skill's BODY, not its description. A description answers "should I open this?"; it does not answer "what is inside?". A section is a duplicate only if the body already carries it — and then it is pure duplication, however useful it reads.
Test the trigger, honestly. Content may move only when the trigger names a situation the agent can recognise from the request: "I am building a UI" and "review this diff" pass. It fails when the trigger requires the skill's own diagnosis first — "the code feels brittle", "cleanup looks missing" — because the agent cannot know it needs the skill until it has already learned what the skill teaches. Where the trigger is weak, keep the rule and point at the skill in one line.