Structure: Role, Task, Context, Format
Four blocks that turn a vague request into an engineering prompt.
The four blocks
A good prompt isn't one long question — it's four blocks:
- The model's role. "You are a business-email editor" beats a role-less request. The role sets the style, vocabulary, and level of formality.
- The task. A concrete action: "rewrite", "compare", "build a list". Verb + object.
- Context. Everything the model can't figure out on its own: data, preferences, constraints, ICP, brand tone of voice.
- Output format. Exactly what you want back: a list, a table, markdown, JSON, length, sections.
Example of a "bad" prompt
Write a LinkedIn post about AI.
What's wrong: no role, fuzzy task, no context about the business, no format.
Example of a "good" prompt
You are a B2B startup founder writing a LinkedIn post in the first person. Style: calm, no hype, no emoji at the start of lines. Task: write a post based on my note below. Length 800-1100 characters. End with a single question to the audience. Context: ICP — operations directors at SaaS companies. We sell a tool that automates finance operations. Note: "Today a customer told me our integration saved them 12 hours a month..."
The principle
The less guessing you leave to the model, the more stable the result.
Take your usual prompt and break it into 4 blocks (role/task/context/format). Compare the result before and after.
Copy and adapt to your context. Text in angle brackets should be replaced.
Help me rewrite a prompt. I'll give you the original request; you break it into 4 blocks — role, task, context, format — and propose a final version. Original request: <...>
- People think the longer the prompt, the better — sometimes it's the opposite.
- They don't specify the format — and get "text".
- They state the role abstractly ("you are an expert") — the model doesn't know what kind.
- First ask the model to draft the prompt itself, then refine it.
- Save 3-5 "reference" prompts for your recurring tasks.
- For long tasks, put the format at the very end of the prompt — it sticks better.
Any task you'll repeat.
A one-off everyday question ('what can I cook from these ingredients') — one line is enough for that.