A good prompt is the difference between a draft you can use and one you throw away. This guide covers what to include, what to avoid, and prompts you can reuse.
1. The 4 parts of a good prompt
Most weak prompts are missing 1 of these.
| Part | What to say | Example |
|---|---|---|
| The format | What shape the output should take | "a 5-step checklist" |
| The reader | Who will read it | "for a new SDR" |
| The source | What to work from | Attach the call, then say "from the attached transcript" |
| The scope | What to change and what to leave | "rewrite the intro only, keep everything else as it is" |
2. Prompt patterns that work
These 6 patterns cover most of what people need. Use them as a starting point and adjust the wording to your own content.
| Pattern | Example |
|---|---|
| Be clear and specific | Create a 5-step onboarding checklist for SDRs focused on lead qualification. |
| Give context | Rewrite this internal product update into a customer-friendly announcement for a Deal Room. |
| Ground it in a source | Use the attached discovery transcript to identify the prospect's top 3 pain points. |
| Say where it goes | Insert a short summary at the very top of this Spek, based on the text below. |
| Refine step by step | This is good, but make it 30% shorter and more direct. |
| Ask for structure | Convert this paragraph into a comparison table of our Pro and Enterprise tiers. |
3. Common mistakes
These are the mistakes that waste the most time. Each one has a simple fix.
| Mistake | What happens | Do this instead |
|---|---|---|
| "Make it look nice" | Generic output, because the builder has to guess the layout | Describe the layout. "A card grid with 4 sections and a clear header." |
| No source attached | The builder writes from general knowledge, not your business | Attach a transcript, a Spek, or a web source first |
| Asking for 5 changes at once | Some get done well, others get missed | Run 1 instruction at a time |
| Not saying what to protect | The builder edits sections you wanted left alone | Add "keep everything else exactly as it is" |
| Publishing the first draft | Wrong facts and figures reach your team | Read it, check the numbers, then publish |
💡 Pro Tip: Name a layout style in your prompt. The builder knows your design system, so asking for a card grid, a hero, or a callout gives you an on-brand result rather than plain text you then have to format.
4. Reusable refinement prompts
Keep these for polishing almost anything.
| Goal | Prompt |
|---|---|
| Simplify | Keep everything the same, but simplify it. |
| Make it scannable | Make this easier to scan for a busy reader. |
| Mobile | Improve mobile readability. |
| Less dense | Reduce text and increase spacing. |
| Better grouping | Group related content more clearly. |
| Add structure | Turn the second section into a card grid so it is easier to scan. |
| Executive tone | Shorten the intro to 2 sentences and make the tone more direct for an executive audience. |
5. Best practices
These are the habits that separate people who get good output from people who give up on the tool.
| Practice | Why it matters |
|---|---|
| Treat the first output as a draft | The builder gets you 80% there. The last 20% is you. |
| Write the prompt like an instruction to a new hire | Say the goal, the reader, and the format. Assume no shared context. |
| Keep a note of prompts that worked | Your best prompts are reusable. Save them in a Spek for your team. |
| Check facts against a real source | The builder can produce confident wrong answers, especially with numbers, dates, and names. |
| Stay under 1700 characters | That is the prompt limit. Long context belongs in an attached source, not in the prompt. |