How does a prompt file differ from custom instructions?
Why A is the answer
You choose when to use a prompt file in chat, while instructions apply by themselves
Prompt files give task-specific instructions that you choose to use. Custom instructions supply context automatically.
In detail
- You choose when to use a prompt file in chat.
- Custom instructions apply by themselves.
- Use prompt files for tasks, and instructions for standing rules.
Use case
An illustrative scenario, not a real incident.
A team saves a "write a migration" prompt file that people run on purpose, and it keeps style rules in instructions that always apply.
See it in different ways
flowchart TD
A{"What do you need?"} -->|"Rules for the whole repo"| B[".github/copilot-instructions.md"]
A -->|"Rules for some paths"| C[".github/instructions/NAME.instructions.md"]
A -->|"Rules for agents"| D["AGENTS.md"]
A -->|"A task you start yourself"| E["Prompt file"]mindmap
root((Instructions))
Repository wide
copilot-instructions.md
One path
NAME.instructions.md
Agents
Nearest AGENTS.md
Chosen by hand
Prompt filesflowchart TD
Q{"When should it apply?"}
Q -->|"Always"| A0["Custom instructions"]
Q -->|"When you choose"| A1["Prompt file"]Key point: You choose prompt files, and instructions apply themselves.
Why the other options are wrong
- B. Prompt files replace all of the repository instructions while they are in use
- A prompt file does not replace repository instructions.
- C. Prompt files are only available to enterprise administrators to create
- Prompt files are not limited to administrators.
- D. Prompt files apply automatically, and custom instructions are chosen by hand
- This has the two the wrong way around.