trimming-project-instructions

Installation
SKILL.md

Trimming Project Instructions

A project instruction file is loaded at the start of every session in that project. Its length is a tax paid there, on every task, whether or not the task touches the area a section covers.

Core principle: every section is either a verdict — a rule, a decision, a "do not re-open" — or evidence: how the verdict was reached. The verdict stays, with the shortest warrant that stops it being re-opened. The evidence — the gates, the measurements, the dates, the sequence — moves to a document.

The one question

Is this the verdict, or the evidence for it?

Adding without asking it is how the file grows. Trimming without asking it is how a rule disappears. Most sections are half-live by construction — a durable head and a narrative tail — so the work is splitting them, not relocating them whole.

This is not the global file's problem. There the destination is a skill, which loads on a trigger. Here the destination is a document, which nothing loads — so the pointer is the trigger, and a moved rule nothing points at is a rule that gets re-derived. (For the global tier, see curating-global-instructions.)

The pointer rule

A pointer names the trigger, never a bare "see Y". "Before touching X, read Y" survives; "see Y" does not — the reader has no way to know they are in the situation Y covers.

Mechanics

Installs
49
First Seen
Oct 30, 2026