prompts.md

Prompts (.prompt.md)

Reusable task templates triggered on-demand in chat. Single focused task with parameterized inputs.

Locations

Path	Scope
.github/prompts/*.prompt.md	Workspace
<profile>/prompts/*.prompt.md	User profile

Frontmatter

---
description: "<recommended>" # Optional, but improves discoverability
name: "Prompt Name"          # Optional, defaults to filename
argument-hint: "Task..."     # Optional: hint shown in chat input
agent: "agent"               # Optional: ask, agent, plan, or custom agent
model: "GPT-5 (copilot)"     # Optional: selected model, or fallback array
tools: [search, web]    # Optional: built-in, tool sets, MCP (<server>/*), extension
---

Model fallback is supported:

model: ['GPT-5 (copilot)', 'Claude Sonnet 4.5 (copilot)']

Template

---
description: "Generate test cases for selected code"
agent: "agent"
---
Generate comprehensive test cases for the provided code:
- Include edge cases and error scenarios
- Follow existing test patterns in the codebase
- Use descriptive test names

Context references: Use Markdown links for files ([config](./config.json)) and #tool:<name> for tools.

Invocation

• Chat: Type / → select from prompts and skills

• Command: Chat: Run Prompt...

• Editor: Open prompt file → play button

Both prompts and skills appear as slash commands in chat. Skills provide multi-step workflows with bundled assets; prompts are single focused tasks.

Tip: Use chat.promptFilesRecommendations to show prompts as actions when starting a new chat.

Tool Priority

When both prompt and custom agent define tools:

1. Tools from prompt file

2. Tools from referenced custom agent

3. Default tools for selected agent

When to Use

• Generate test cases for specific code

• Create READMEs from specs

• Summarize metrics with custom parameters

• One-off generation tasks

Core Principles

1. Single task focus: One prompt = one well-defined task

2. Output examples: Show expected format when quality depends on structure

3. Reuse over duplication: Reference instruction files instead of copying

Anti-patterns

• Multi-task prompts: "create and test and deploy" in one prompt

• Vague descriptions: Descriptions that don't help users understand when to use

• Over-tooling: Many tools when the task only needs search or file access