Keep specialized detail available without loading everything at once.
1. Progressive detail
Keep the entry point short and link supporting references for specific branches of work. Loading all examples on every task wastes context and can introduce irrelevant instructions.
2. Script contracts
Document inputs, outputs, exit codes and side effects. Validate paths and arguments and prefer read-only checks by default for analysis workflows.
3. Template discipline
Templates should express real project constraints while leaving task-specific choices explicit. Avoid placeholders that look complete but silently omit required configuration.
Worked scenario
A review script prints lint failures and exits nonzero. A wrapper must not convert that failure into a success message.
Apply it
Add one focused reference and one check script. Run the script on a passing and failing fixture.
Check your understanding
Supporting files have clear ownership and observable behavior. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.