Every high-performing Breeze prompt follows the same five-block structure: Role, Task, Context, Constraints, and Output. Each block does a specific job. Together, they give Breeze enough information to act like a specialist rather than a generalist.
This page breaks down each block, explains what belongs in it and why, and shows you exactly how to apply the framework to any prompt you write inside HubSpot.
Every strong prompt has five core building blocks, and they work best when provided in this order:
- ROLE - Who should the AI "be" when writing?
- TASK - What exactly do you need it to produce?
- CONTEXT - Who is the audience, and what's the situation?
- CONSTRAINTS - What rules, limits, or guardrails apply?
- OUTPUT - What format should the result take?
If this looks familiar, it should; it follows the same structural thinking as the assistant instructions we configured in the custom Breeze Assistant from last week. The difference is that here we're crafting a single-use prompt rather than a persistent personality, but the principles remain the same.
Now, let us talk a little more about the individual building blocks:
Role sets the expertise level and perspective. Telling Breeze to act as "a retention-focused email copywriter" produces very different output than just saying "write an email." The more specific the role, the more targeted the language and strategy in the output.
Task defines the deliverable in concrete terms. Instead of "help me with email," you say "write a 3-email re-engagement sequence" or "generate 5 subject lines and preview text pairs." Breeze performs dramatically better when it knows exactly what shape the output should take.
Context is where you feed in the details that make the output relevant to your business. This includes your audience segment, their lifecycle stage, your industry, and what action you want the reader to take. This is also where Breeze's CRM integration shines — it can pull in data you reference, so naming specific segments or properties helps ground the output.
Constraints are the guardrails that prevent generic or off-brand results. Word limits, tone restrictions, things to avoid (like spam-trigger words), and structural requirements all go here. Think of constraints as the difference between a first draft you'll rewrite entirely and one you can edit lightly and send.
Output format tells Breeze how to present its work. A table, a numbered sequence, labelled sections, specifying this saves you from having to reorganise the response and makes it easier to copy directly into HubSpot's email editor.
