The structure of a prompt matters more than its length. These three shapes cover most day-to-day work.
Goal, context, constraints
The default for features and fixes. Lead with the outcome.
Goal: [what "done" looks like]
Context: [file paths and function names, not pasted code]
Constraints: [what must not change]Map first
For anything that touches more than one module. See Map before you build.
Before editing, map the modules and connections for: [task]. List blind spots. Stop.Shape the answer
Add this to the end of either shape to cut the reply down to what you'll use.
Reply with: the diff only, plus one line on anything you couldn't verify.Rules of thumb
- Point, don't paste. Name the file; the agent reads the current version.
- One task per prompt. Two goals get you half of each.
- Say what to leave alone. It's the part agents can't infer.