Understand instruction scope
Project instructions can be layered by directory. Determine which files apply to the current working directory and task; review conflicting guidance before changing a sensitive area.
What is it?
Project instructions can be layered by directory. Determine which files apply to the current working directory and task; review conflicting guidance before changing a sensitive area.
Why it matters
Reusable rules help keep work consistent across sessions.
When to use it
When the same rules apply to repeated project tasks.
How to do it
- Read the explanation and identify the files or environment involved.
- Draw a root folder with frontend and backend subfolders. Give each a distinct testing instruction, then ask which instructions apply when working inside frontend.
- Compare the result with the verification criteria below. Record what worked and what remains unclear.
Worked example
Draw a root folder with frontend and backend subfolders. Give each a distinct testing instruction, then ask which instructions apply when working inside frontend.
Try it yourself
Repeat the exercise with your own wording or a second sample. Use the smallest change that demonstrates the idea.
Prompt builderVerify your result
Your answer identifies the working directory and cites the applicable instruction files.
Common mistakes
Assuming every AGENTS.md is always loaded. Verify the discovery behavior in the official guide.
How to recover
Stop at the first unexpected result. Preserve your current work, re-check the named file or environment, and repeat only the failing step. Ask for an explanation if the recovery is unclear.
Official references
Product interfaces and access can change. Use the linked official guide for current installation and account requirements.
OpenAI · AGENTS.md ↗Source review: 2026-09-16