Prompting that actually lands

Prompting is not incantation. It is specification with the boring parts removed. These are the patterns that consistently produce work you keep.

Lead with the shape of the thing

Models are excellent at execution and mediocre at guessing intent. Name the artefact first — landing page, dashboard, checkout, admin table — then the audience, then the constraint. Everything after that is refinement.

Build the booking page for a two-chair barbershop.
Audience: walk-in customers on a phone, mid-afternoon.
Must have: service picker, next-3-days slots, £5 deposit.
Tone: warm, slightly old-fashioned, no gradients.
Reference: the calm of a paper appointment book.

One change per message

A message with eight instructions is a queue the agent has to serialise, and the last three always get the least attention. Send them separately; each lands with full context and you can stop the moment it looks right.

Say what to keep, not only what to change

"Tighten the hero" invites a rewrite. "Tighten the hero spacing, keep the headline wording and the photograph" preserves the parts you already paid for.

Vocabulary that carries weight

• "Keep the current structure" — protects layout while you change surface details.
• "Only touch <file>" — narrows the blast radius on a delicate change.
• "Show me before you build" — gets a plan back instead of a diff.
• "Use the existing token, don't invent a colour" — keeps the design system intact.
• "Verify it in the preview" — pushes the agent to check its own work before finishing.

The prompt is not the product. It is the brief — and briefs get better by being shorter and more specific, never longer and more decorative.