Write rules that can be checked
Start with the commands that verify a change, the source directories that matter and one or two architectural constraints. “Use the existing form validation helper” is more actionable than “write clean code”. Treat these as suggested authoring practices; filenames and activation rules differ by tool.
A starter instruction
Adapt this example to your repository, then save it through your tool’s documented rules or instructions feature.
Before editing, inspect the nearest existing implementation.
Use the package manager already configured in this repository.
Run the relevant checks for changed behavior.
Report any check you could not run and why.
Do not edit generated output directly.Verify that a rule actually applies
Try a small task where the instruction changes an observable action. Inspect the output and commands, then narrow the rule if it fires in unrelated work. Rules should be reviewed with the repository, just like build instructions.