Why it's worth the line
Describing a style is lossy; showing it is exact. One worked example pins down tone, length, structure, and level of detail all at once — things you'd need a dozen adjectives to approximate and still miss.
Without a reference, the model anchors on its own average. With one, it anchors on YOUR bar. That single shift is the difference between "technically followed the brief" and "this is exactly what I meant."
How to catch it in your own prompt
- You've written three sentences trying to describe a style you could just show.
- The output is plausible but off — right shape, wrong feel.
- You have a past example you loved and didn't include it.
What to write instead
- Paste one ideal example — real or hand-made — and label it clearly as the target.
- For repeatable work, show input → output as a pair so the model learns the mapping, not just the look.
- If you have a good one and a bad one, show both: "like this, not like this."
Seen side by side
Write a few taglines in our brand voice.
Write a few taglines in our brand voice — match the rhythm of these two we love: 'Ship it Friday.' / 'Less meeting, more making.'
Why it lands — Two real taglines transmit the short, punchy, imperative rhythm instantly — no amount of describing "our voice" would land it as fast.
Turn these support tickets into structured tags.
Turn these support tickets into tags. Example — input: "app crashes when I upload a PDF" → output: {area: "uploads", type: "crash", severity: "high"}. Now do the rest the same way.
Why it lands — One input→output pair teaches the exact schema and judgment calls; describing the rules in prose would leave a dozen edge cases ambiguous.
Stop fixing this by hand.
Paste a prompt — Meerkat catches this and the seven other weak spots before you send it. Free, no signup.