Why This Matters

A vague prompt is a slot machine — sometimes good, often bad. A specific prompt is a precision tool. The difference between 'write a function' and 'write a function that takes a Date and returns an ISO 8601 string in UTC' is the difference between useless and useful.

Concept Explained

Specificity is the practice of telling Copilot exactly what you want: inputs, outputs, constraints, conventions, examples, edge cases. The specificity ladder goes from one-word prompts ('sort') to fully-specified prompts with examples and constraints.

How It Works

Specificity works because it narrows the model's probability distribution. 'Write a function' could mean thousands of things; 'write a TypeScript function that takes a Date and returns an ISO 8601 UTC string, throwing on invalid input' means essentially one thing. Narrower distributions produce more useful outputs.

Step-by-Step Tutorial

1. Identify vague prompts

2. Apply the specificity ladder

3. Use constraints

4. Provide examples

5. Stop before micromanaging

Real-World Example

A developer asked Copilot to 'write a function to validate email'. Copilot produced a 30-line regex monster that failed on edge cases. The developer upgraded: 'write a TypeScript function isValidEmail(s: string): boolean that returns true for RFC 5322-compliant emails, false otherwise, no external dependencies, with a single test case showing it accepts user@example.com and rejects user@'. Copilot produced a clean 5-line function using a focused regex, plus the test case.

Example Prompts / Commands / Code

Level 0 (vague):     'write a sort function'
Level 1:             'write a TypeScript function that sorts an array of numbers ascending'
Level 2:             'write a TypeScript function sortAsc(nums: number[]): number[] that returns a new sorted array, doesn't mutate input, throws on null'
Level 3:             same as Level 2 + 'use quicksort, here's an example: sortAsc([3,1,2]) → [1,2,3]'
Level 4 (micromanage): 'write a sort function. Define a function called sortAsc. Take one parameter called nums. Use quicksort. The pivot should be the middle element...' ← TOO MUCH

Common Mistakes

• Stopping at Level 0 or 1 — too vague for useful output.
• Jumping to Level 4 — micromanaging kills Copilot's pattern-matching value.
• Adding constraints without examples — constraints alone are ambiguous.
• Specifying implementation instead of behavior.

Best Practices

• Aim for Level 2–3: types, constraints, one example.
• Specify behavior, not implementation.
• Use examples to clarify ambiguous constraints.
• Iterate: start specific, add more if needed.

Troubleshooting

Practical Exercise

Frequently Asked Questions

Further Reading

• Prompt engineering with Copilot

Official References

• Prompt engineering for Copilot

Related lessons: BE-15, BE-19