Prompt library · AI · 11 prompts
Prompts from the guide
Role, context, task, format: anatomy of a prompt that gets work done
11 prompts from this guide. Fill in whatever sits in [square brackets] — your own context, the document text or the name of your tool. That context is exactly what separates a generic answer from a usable one.
Format: how the output will actually get used
You're an experienced commercial lawyer specializing in commercial leases in the Czech Republic. Situation: I own a studio with 7 people, and we're moving into an office of [size] in [city]. The lease runs 3 years. My biggest client accounts for roughly half of revenue — if I lost them, I'd need to be able to get out of the lease early. I can't afford to fund a renovation myself. Treat the deposit and the rent amount as fixed — don't touch those. Contract text: [paste the contract] Task: go through the contract clause by clause and find spots that could hurt me given the situation above. Format: a table with columns risk | clause and paragraph | how serious (high/medium/low) | a specific fix, worded so I can send it straight to the landlord. Don't write generic advice about leases. Only things that are actually in this text, or conspicuously missing — list any missing provisions separately at the end.
Version 2: add context and a task
Write web copy about my service. I'm an accountant, I do full bookkeeping for small businesses with up to 15 employees, mostly tradespeople and online shops. The copy is for a "Services" page, around 250 words.
Version 3: all four pieces
You're a copywriter who writes for small Czech businesses — plainly, no marketing phrases, no superlatives. About me: I'm a freelance accountant, I do full bookkeeping for companies with up to 15 employees, mostly tradespeople and online shops. Eight years of experience. What sets me apart: clients send me receipts by phone as they go instead of dropping off a binder once a quarter, and I respond to questions by the next day. Who I DON'T want: businesses looking to "sort it out somehow" after a deadline has passed, and companies with revenue above [threshold]. What clients are most afraid of: getting fined, missing a change in the law, and not being able to reach anyone by phone. Task: write copy for the "Services" page. Format: - an opening paragraph under 60 words that talks about the client's worry, not about me - 4 bullets covering what's included in the service, one sentence each - a paragraph on "how we'll work together" in 3 steps - 2 sentences on who I'm not a good fit for - a closing call to action (a no-obligation call) Under 300 words total. No phrases like "personal approach," "tailored," "in today's world." Write in second person, addressing the reader directly.
When to skip the role
I want you to [describe the task]. Don't do it yet. Write me 4 different roles I could assign you for this task. For each one, note: - exactly how the first sentence of the prompt would read - what you'd notice in this role that you wouldn't notice in the others - what kind of decision this answer would be good for - what you'd necessarily miss in this role At the end, recommend one role for my situation: [situation in one or two sentences], and justify it in one sentence.
The safest way to find out what's missing
I want you to [task]. Here's the context I could think of: [3-8 lines of context] Don't start working yet. First tell me: 1. Which pieces of information are missing enough that you'd have to guess — ranked by how much they'd change the result. 2. What you'd guess if I didn't fill it in (give a specific guess, not "it depends"). 3. Which of the things I gave you are actually irrelevant to this task. Then wait for my answer.
Formats you can actually keep working with
I have [description of source material, e.g. seven supplier quotes in emails]. I'm pasting them in below. Task: turn them into one comparison table so we can decide based on the same criteria across the board. Format: table, one row per supplier, columns: supplier | exactly what's offered | delivery date | warranty length | what's missing or unclear in the quote | what to ask about Rules: - write prices exactly as they appear in the quote, don't recalculate or sum anything - where a field is missing from a quote, write "not stated" — don't guess - below the table, add 3 questions I should send to all suppliers at once, so the quotes finally become comparable Don't recommend a winner — that's my call. [paste the quotes]
A fill-in template
ROLE: You're [profession or perspective] who [what defines them — e.g. writes plainly with no fluff / hunts for risk / watches deadlines]. CONTEXT: - Who I am and what I do: [one sentence] - Situation: [what happened, where I am now] - Who the output is for and what they'll do with it: [recipient] - Constraints: [time, scope, rules, what to stick to] - What must not happen: [worry] - Source material: [paste text, numbers, notes] TASK: [Verb] [exactly what] [scope]. If there's more than one task, number them: 1. ... 2. ... FORMAT: [length, structure, table columns, tone, language] WHAT I DON'T WANT: [phrases, generic advice, suggestions that require X, intro and closing summaries]
Rewrite 1: an email to your boss
You're an experienced manager who gets emails like this yourself. You write plainly, without apologizing and without explaining yourself in advance. Situation: I owe [deliverable] by Friday. I won't make it, because [the real reason — e.g. the supplier sent the material 8 days late]. I can realistically deliver by [new date]. My boss hates surprises and wants to know what I'm doing about it. We've had this kind of slip once before on [project], so I don't want this to read like it's happening again with no fix in place. Task: write an email that informs him about the delay and offers a solution right away. Format: subject line + body under 150 words. Structure: 1. the fact, one sentence (what's slipping and to when) 2. why — one sentence, no blaming the supplier 3. what I've already done to limit the impact 4. what I need from him (a decision, not sympathy) 5. what I'll do so this doesn't happen again No apologetic phrases up front. Don't write "sorry for the inconvenience," and don't say it's regrettable.
Rewrite 2: a brief for a designer
You're an art director who briefs external designers and knows that a bad brief costs two extra rounds of revisions. Context: [company's field], we're doing [event/product]. The flyer will run [where it'll be distributed — noticeboards, mailboxes, an event booth], target audience [description]. Our visual style: [description or link to a style guide]. Print: [format, color, single-sided?]. Print deadline [date], so the artwork needs to be done by [date]. The budget is fixed, but don't put the figure in the brief — I'll add it myself. The designer is working with us for the first time and doesn't know our materials. Task: write a brief that's enough for the designer to produce a first draft without having to ask follow-up questions. Format: - the flyer's goal in one sentence (what someone should do after seeing it) - required elements (copy, logo, contact info, QR code, mandatory disclosures) - hierarchy: what must be readable from three meters away, what only up close - technical specs (dimensions, bleed, color mode, file format) - what we'll supply, and by when - how many revision rounds, and what approval looks like - 3 examples of what we DON'T want (styles, clichés, elements) At the end, list any information I didn't give you that would leave the brief with gaps.
Rewrite 3: a budget request
You're the CFO this request lands on. Read it first the way a decision-maker would, not the way the person who wrote it would. Context: I run [team/project]. I need to increase the budget for [what specifically]. Reason: [what changed — volume, prices, scope, a shortfall]. Data I have: [list what you can back up — counts, hours, dates; I'll add the amounts myself, don't put them in the text]. Who decides on this: [role]. What they care about most: [return on investment / risk / impact on deadlines]. What happens if it isn't increased: [consequence]. Alternative I considered: [narrowing scope / delaying]. Task: 1. Write a one-page request. 2. Then, separately, write 5 questions the decision-maker will likely ask in response, and for each one, what I should have ready to back it up. Request format: a heading, 3 paragraphs (what I need, why now, what the company gets for it), a table "option | impact | what it means for deadlines," and a final sentence that's a specific ask for a decision by [date]. Don't use the words "unfortunately," "we're trying to," or "it would be good." Don't invent any numbers — where one's needed, write [FILL IN].
When a prompt doesn't land: tune it, don't rewrite it
Here's the prompt I wrote you, and the answer I got back. The answer doesn't work for me because [what specifically is wrong]. Prompt: [paste the original prompt] Answer: [paste the answer, or the start of it] Break it down for me: 1. Which of the four parts — role, context, task, format — is missing or weak in my prompt. 2. What exactly you had to guess, and how you guessed it. 3. Write a corrected prompt. Mark the changes so I can see what you added and why. Don't regenerate the answer yet.