vaathi.dev

Prompting as clear communication

Goal, context, constraints, format — iteration over magic prompts.

Good prompting is less spellcasting and more clear communication. You’re briefing a fast, literal collaborator that doesn’t share your unspoken context.

AnimationFrom a vague ask to a clear brief — four parts, one idea at a time
Building a clear promptA vague request, help with my resume, transforms into a clear brief with four parts: Goal, Context, Constraints, and Format. Each part appears in order with a short example line.Vague“help with my resume”briefClear briefSame ask — four clear parts1GoalDraft a 3-bullet summary for a hiring manager2ContextCareer switcher · pasting bullet notes below3ConstraintsUnder 80 words · plain language · no fluff4FormatBullets only · no intro paragraph

Clarity beats cleverness: say the job, give context, set limits, ask for a shape.

A simple template

  1. Goal — What do you want done? (“Draft a 3-bullet summary for a non-technical reader.”)
  2. Context — What does the model need to know? (Audience, background, source text.)
  3. Constraints — Limits: length, tone, must/avoid, reading level.
  4. Format — How should the answer look? (Bullets, table, email, JSON-ish structure.)

You don’t need all four every time. Start with goal + format; add context when results miss.

Few-shot, lightly

Showing one or two examples of the shape you want often works better than abstract instructions. Keep examples short.

Iterate

First answers are drafts. Refine: “Shorter.” “More skeptical.” “Only use facts from the text I pasted.” Iteration beats hunting for a mythical perfect one-liner.

Next

When you’re ready for reusable patterns and fuller examples, continue to Prompt engineering in practice.

Takeaway

Prompting skill is briefing skill. Clarity beats cleverness.

Try this

Rewrite a vague ask (“help with my resume”) into goal + context + constraints + format. Run both versions and compare which output you’d actually use.