Agent instructions
Describe how to operate this repository, then point to the rules needed for each task.
Operating contract
Why
A root instruction file should not repeat every language rule. Canonical references let agents retrieve the relevant material without contradictory copies.
Rules
MUST provide the consumer's commands and permission boundaries.[review]
MUST distinguish Always, Ask first, and Never requirements.[review]
MUST keep repository-specific credentials, release authorization, and runtime procedures out of reusable packs.[review]
MUST require reading the applicable standard before an edit.[review]
MUST route detailed topics to their canonical component pages.[review]
MUST preserve generated regions and their exact delimiters.[review]
MUST reserve nested instruction files for scope-specific differences.[review]
SHOULD keep hand-authored root instructions below 200 lines.[review]
[review]
Generators can check managed-region drift. Review checks authority, length, scope, and accurate operating commands.
Enforcement
Generators can check managed-region drift. Review checks authority, length, scope, and accurate operating commands.