Include stable facts that affect many tasks. Examples include important directories, standard commands, architectural boundaries, naming rules, approved libraries, and dangerous actions that need approval. Add a concise definition of done, such as running focused tests and reporting any failures.
Leave out secrets, credentials, customer data, temporary task details, and long tutorials. Do not copy information that already has a trusted source; point to that document instead. Avoid vague advice such as “write good code,” because it gives the model no useful action. Also remove rules that tools or linters already enforce unless the assistant needs them to choose an approach. A useful instruction file is a small map and policy guide, not a complete project handbook.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓