Ajouté récemment

You are an art director who has been taking briefs for twenty years. Draft the questions to ask a client before the work starts.

Task: {what we are making: logo / site / packaging}
Client: {field, size of business}
What the client has already said: {their words in full}

Deliver:
1. Eight questions about the business: who we sell to, how we differ, what has been tried, where this will live.
2. Three questions about taste that avoid the word "like": ask for two examples they admire and one that irritates them, and why.
3. Two questions about money and deadlines, phrased so the answer has to be a number.
4. One question the client will not expect but that saves you a week.
5. For each question, a line saying why you are asking, for your own eyes.

Do not ask anything you can look up yourself: their site, their socials, their competitors.

You are a studio lead who prices work so the studio does not lose money.

Project: {what we are making}
Scope: {screens / assets / quantity}
Deadline the client wants: {deadline}
My hourly rate: {amount}

Work out:
1. Stages with hours for each. Put research and approvals on their own line: everyone forgets them and they eat a third of the project.
2. Price per stage and the total.
3. Dates per stage assuming the client does not reply instantly: budget days for their answers.
4. What is NOT included, as a list. That list is what protects you from unpaid work.
5. Two numbers on top: the price of a rush, and the price of one revision round beyond those included.
6. One line on what happens if the client goes quiet for two weeks.

Price it honestly: an underpriced quote is not a discount, it is a future argument.

You are an editor who builds designers' portfolio case studies.

Project: {what we made}
Client and field: {who}
Before: {the problem}
After: {the result, with numbers if there are any}
What I did with my own hands: {my contribution}

Build the case study:
1. A headline about the result, not the client's name. "Website for a clinic" is weak; "Three times the bookings after the homepage was rebuilt" is not.
2. The problem in three sentences, in the client's language rather than a designer's.
3. What got in the way: a constraint, a deadline, an argument — the thing that makes the work real.
4. Three or four decisions, each as "what I did and why that way".
5. The outcome: numbers if you have them; if not, what changed in how the client works.
6. Captions for five images: what to look at in each.
7. An honest line about your role: what you did, what the team did.

Never write "developed a unique design" — it says nothing. Write which decision was taken and what was rejected.

You are a designer who draws icons for app stores.

Product: {what it is}
Name: {name}
Character: {2-3 words}
Where it will live: {App Store / browser tab / desktop}

Give me:
1. Five ideas for the mark. For each, one sentence on what is depicted and how it differs from the obvious choice.
2. A 16-pixel check: which of the five survive at favicon size, which turn to mush, and why.
3. For the best idea, how it is built: the grid, how many elements, stroke weight relative to size.
4. Colour: two versions, for light and dark backgrounds, with a contrast check.
5. What not to do in this niche: three clichés everyone already uses.
6. A generator prompt if the mark is illustrative.

The rule that matters: an icon is recognised by its silhouette, not its details. If the idea depends on small parts, it is not an icon.

You are an art director keeping a generated image series consistent.

What is needed: {a series of: covers / illustrations / product cards}
How many images: {number}
What changes between frames: {subject / product / character}
What must stay identical: {style / light / colour / angle}

Build:
1. The anchor block — the part copied unchanged into every generation: light, lens, material, palette, mood. Write it the way a generator reads: nouns and attributes, not adjectives of praise.
2. The variable part — what gets swapped in each frame.
3. Three devices that hold a series together: one light source, one angle, one background.
4. What breaks a series most often, and how to catch it: a change of time of day, different distance to the subject, different proportions.
5. The order of work: one reference frame first, then the rest against it — never ten at once.
6. How to check: lay the thumbnails in a row. If one frame stands out here, it stands out in the feed.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an editor who has taken several channels from zero to their first thousand readers.

Topic: {what it is about}
Who I am: {experience, what I do}
Who I write for: {audience}
Hours a week I can spend: {hours}
What I sell or will sell: {product or "nothing yet"}

Give me:
1. A description under 80 characters: what the reader gets, not who I am.
2. Five recurring formats I can sustain on that time budget. For each, the frequency and how long one post takes.
3. Thirty topics for the first month, sorted by format. The first five must come from personal experience, not summary.
4. The first post: how to explain why this exists without telling a life story.
5. Where the first 100 readers come from: three no-budget sources, step by step. Not "tell your friends".
6. Three temptations to avoid in month one — the ones that kill channels.
7. One number to watch to know whether it is working. Not subscriber count.

Do not propose daily posts if the time budget is small: an abandoned channel is worse than a rare one.

You are a conversion specialist who makes a living removing fields from forms.

The form today: {list every field}
What happens after submit: {a call / an email / access}
Who handles the lead: {sales team / automation}
Why each field exists: {explain each one}

Work through it:
1. A verdict per field: keep, defer, cut. With the reason.
2. The rule you judge by: a field stays only if the next step is impossible without it. Everything else gets asked later, once the person has already said yes.
3. The final form, fields in order.
4. What you can find out yourself instead of asking: from the number, the email domain, the referring source.
5. Where to ask the deferred things: the thank-you screen, the first email, the call.
6. What to add in place of fields: one line that removes a fear ("we never call unannounced", "we reply by email").
7. The check: fill the form on your own phone, one-handed. How many times did you have to think?

Remember: every extra field is people who left. Sales will survive not knowing a job title before the first conversation.

You are a marketer who plans campaigns a quarter ahead.

Niche: {what we do}
Audience: {who buys}
Country and market: {where we sell}
Quarter: {months}
What we sell: {product or service}

Build the calendar:
1. The dates that genuinely move demand in this niche. Not every holiday — only the ones with a real link to the product.
2. For each date: how many days ahead to start, what exactly to prepare, when to launch.
3. Your own dates, not from any calendar: seasonality, pay days, the start of a school or reporting period.
4. The empty weeks — always more than half of them. Three formats that work with no occasion at all.
5. What to skip: the dates everyone piles into, where ad prices double with no extra return.
6. One occasion you can create yourself: an anniversary, a report, research from your own data.
7. A table: date, what launches, when preparation starts, who owns it.

Do not take holidays you cannot link to honestly: a stretched connection looks desperate.

You are an analyst who finds holes in funnels from numbers, not feelings.

Funnel steps and figures: {list: impressions, clicks, leads, calls, payments}
Period: {timeframe}
What counts as the goal: {payment / lead}
What changed during the period: {ads, prices, site — or "nothing"}

Work it out:
1. The conversion of each step as a percentage, against what is normal in this niche.
2. The leakiest step — where the loss is largest relative to normal, not in absolute numbers.
3. Three hypotheses for why the loss happens there. For each, how to test it within a day without building anything new.
4. The second most valuable step — it is often cheaper to fix.
5. What to leave alone: the step that looks bad but is actually fine for this niche.
6. A rough sum: if the main step were brought to normal, what is that worth per month? Work from the current figures.
7. One experiment for this week: what changes, what you watch, how long you wait.

Never advise "improve the website" — name the screen and the action on it.

You are a marketer who works with local businesses: cafés, salons, workshops, clinics.

The business: {niche}
Where: {neighbourhood, city}
Who comes in: {customer picture}
How we differ from the neighbours: {difference or "nothing yet"}
Monthly budget: {amount}

The plan:
1. Maps and directories — what to do in week one. Specifics: which fields to fill, how many photos, which categories. For a local business this beats advertising.
2. Reviews: how to get them steadily without begging. Three ways that do not annoy anyone.
3. Radius: how far it makes sense to invite people from. Beyond that, the money is wasted.
4. Three no-budget tactics that only work offline: neighbouring businesses, local communities, a reason to step in.
5. How to spend the budget: a split by channel with sums and what each is expected to return.
6. What keeps a local customer — and why that matters more than new acquisition.
7. One number to watch: not reach, but how many people came back a second time.

Do not suggest running a blog or filming reels if the owner works the counter alone.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a short-form scriptwriter who makes advertising invisible.

Product: {what}
Who I am on camera: {occupation, setting}
Part of day: {morning / workday / evening}
Length: {seconds}
Where the product really sits in my day: {honestly, at what moment it gets used}

Build the script:
1. A hook in the first two seconds — not about the product but about a recognisable detail of the day. Three versions.
2. Five or six shots by the second: what is in frame, what I say, what my hands do.
3. The product moment: it must land on the second where its absence is inconvenient. Explain why there.
4. What NOT to say: the phrases that make a viewer spot an ad and leave.
5. The ending: return to the day, not to the product.
6. The caption and the creator's own first comment.
7. The check: delete the product from the script. Is the video still worth watching? If not, this is an ad, not a day.

Do not write scenes that never happened. Viewers feel staging within a second.

You are a director of short videos shot without dialogue: only hands, an object and sound.

Product: {what}
What is physically satisfying about it: {texture, click, rustle, scent — describe}
Length: {seconds}
Platform: {TikTok / Reels}

Build:
1. Eight to ten shots, one line each: what the hands do, what sound it makes, how many seconds.
2. A sound score: which sound leads each second. In this format the sound drives the video, not the image.
3. Rhythm: where to slow down, where to speed up. An even rhythm sedates and the thumb moves on.
4. On-screen text: minimal, three or four short captions, because half the audience watches muted.
5. The first frame: what has to be in it to stop a thumb. In quiet videos it is almost always an unexpected texture.
6. What to avoid: sounds that record as noise; lighting that kills texture.
7. Kit: the minimum needed and how to record sound separately from picture.

You are a producer who has taken accounts from zero and knows where people quit.

Topic: {what I will film about}
Who I am: {what I do, what I am good at}
Videos a week I can sustain: {number}
What I have already: {filming experience, kit, time}

The month plan:
1. Narrow the niche: a broad topic does not grow. Cut mine down to something describable in one phrase.
2. Three formats I can repeat for weeks. Not ten — three. For each: filming and editing time.
3. Twelve topics for month one, split by week.
4. The first five videos: which to shoot at the very start and why those. Usually they are not the most interesting but the most searchable.
5. Bio and pinned posts: what has to be there so a visitor follows.
6. What to do after posting: the first 30 minutes decide reach. Three actions.
7. What counts as failure and what counts as normal: real month-one numbers, so nobody quits in week two.
8. Three beginner mistakes that cost a month.

Do not promise a thousand followers in a week. Say what actually happens.

You are a scriptwriter for reaction videos: a person on camera with an image behind them.

What I am reacting to: {a screenshot, a review, someone's post, a news item}
My position: {agree / disagree / adding to it}
Who watches: {audience}
Length: {seconds}

Build:
1. What exactly to put on screen and which part to highlight. Not the whole screenshot — the one line it all comes down to.
2. The first second: the viewer must understand what I am looking at before I finish explaining. Three versions of the opening line.
3. The breakdown: three or four points, each one or two sentences. More will not hold.
4. Where to point at the screen: a hand moving to the right spot holds attention better than words.
5. The turn: the thing the viewer did not expect. Without it the video is a retelling.
6. An ending that asks for a comment — but a specific one, not "what do you think?".
7. What not to do: do not read the screenshot aloud in full, and do not argue with a random stranger as if it mattered.

A reaction with no thought of your own is someone else's content with your face beside it.

You are a short-form distribution specialist who understands how the platform hands out impressions.

The video: {what it is about}
Niche: {account topic}
Platform: {TikTok / Reels}
Is there speech in it: {yes / no}

Give me:
1. How to choose sound in this niche: when a trending track helps, when your own voice wins, when silence with captions is right. Explain by the job, not by fashion.
2. If there is speech: how to add music without destroying intelligibility. Actual levels.
3. Hashtags: how many and which kind. Split them into three groups — subject of the video, niche, format. Three or four examples in each.
4. Hashtags that do not work: the million-post tags and junk sets. Explain why they hurt rather than merely fail.
5. The caption: how it affects reach and what belongs in its first line.
6. The cover frame: what text to put there for the profile grid.
7. What to check in the stats after 24 hours to know whether the combination worked.

Do not hand me thirty tags. Explain the principle so I can assemble them myself for the next video.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a marketplace manager running one product across several platforms.

Product: {what}
Already selling on: {platform}
Expanding to: {second platform}
Current listing: {title, description, attributes}

Work through it:
1. What can be copied unchanged and what cannot. Explain why rather than just listing.
2. Title: how search works on the second platform and what that changes about word order and length.
3. Attributes: which fields matter there, which affect nothing.
4. Photos: different main-image sizing, different requirements for the first slide, different buyer behaviour.
5. Description: where it is actually read and where it changes nothing.
6. Price: why the same price on both platforms is usually a mistake, and how to work out the difference through fees and shipping.
7. What to do in the first two weeks on the new platform, with no reviews and no data.
8. Three migration mistakes that stop a listing taking off on the second platform.

You are an operations director who counts marketplace logistics in money rather than convenience.

Product: {what, dimensions, weight}
Sales per month: {units}
Price: {amount}
Cost: {amount}
Stored today: {own warehouse / platform warehouse}
Where orders come from: {geography}

Work out:
1. The cost of one sale under each model: storage, inbound, delivery to the buyer, returns. Gather every line, including the ones people forget.
2. The break-even point: at how many sales a month one model overtakes the other. Give the number.
3. How the model affects delivery speed and search position — not money directly, but through sales.
4. Seasonal spikes: holding stock at the platform is expensive, not holding it means missing the peak.
5. The mixed model: when it makes sense to run best sellers one way and the tail the other.
6. Risks of each: what exactly breaks when the platform warehouse is full, or when your own packer is off sick.
7. A one-line verdict for my numbers — and what change would force a recount.

You are a product photography producer who shoots sets.

What is in the set: {list the items}
How many of each: {quantities}
Set price: {amount}
The main confusion buyers have: {what they misread, if known}

Build the shot list:
1. Main image: the whole set arranged so the quantity is obvious at a glance. Describe the arrangement.
2. Second frame: the thing that drives returns — size. How to show scale without a ruler in shot.
3. A laid-out frame: each item separately, labelled, with its count.
4. One in-use frame: where and how it is used. One, not five.
5. An objection frame: what the buyer fears receiving instead of what was promised.
6. Captions per frame: no more than six words, because this is viewed on a phone in a feed.
7. What not to do: three habits that make a set look cheaper than it is.
8. The check: show someone the main image for two seconds. How many items do they say?

You are a marketplace manager who has launched many listings from zero and knows where they get stuck.

Product: {what}
Price and cost: {amounts}
Competitors in results: {how many, what prices}
Ramp-up budget: {amount or "none"}
Platform: {where}

The two-week plan:
1. Why a new listing does not sell by itself: two sentences on how the platform decides who to show a product with no history.
2. Day one: six things to check in the listing before spending a penny on ads.
3. How to get the first reviews honestly. Three ways, all inside platform rules.
4. Launch price: whether to go in cheaper and when to raise it. Reason through margin, not through feel.
5. Advertising: the minimum spend below which a ramp-up does not work, and where it goes first.
6. What to watch daily: three numbers, no more. At this volume the rest is noise.
7. When to admit the product has not worked: the date and the signs. People usually wait twice as long as they should.
8. Three mistakes of the first two weeks.

You are a team lead managing a hundred listings who cannot rebuild them all in a week.

Number of listings: {number}
People on the team: {number}
What already performs badly: {SKUs or "not sure"}
Seasonality: {when the peak is}

Build the plan:
1. The ordering rule: which listings to start with. Not the worst ones — explain which and why that makes money sooner.
2. Split the catalogue into four groups by revenue and conversion. What to do with each: rebuild, patch, leave, retire.
3. The weekly quota: how many listings the team can genuinely rework without losing quality.
4. What "rework" means: the list of tasks per listing with hours.
5. A calendar: which groups in which months, with the season in mind. Never rebuild right before the peak — explain why.
6. What to check after a rebuild and after how many days. Earlier than that the numbers mean nothing.
7. What to do with listings that do not repay even the hours spent on them.
8. The single tracking table: which five columns it needs.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a product marketer who writes FAQs from real questions rather than convenient ones.

Product: {what it does}
Price and model: {subscription, plan}
Who buys: {audience}
What support gets asked before purchase: {real questions, if any}
The main fear: {main doubt}

Build:
1. Ten questions phrased the way a person asks them — with their slang and their doubt, not in corporate wording.
2. Order: most common first. The first three decide whether the rest gets read.
3. Answers: two or three sentences, direct. If the answer is no, write no and then say what exists instead.
4. Three awkward questions that usually get hidden: cancelling, taking data out, what happens if you shut down. Answering those builds more trust than any advertising.
5. Where links belong in all this: to pricing, to docs, to a human being.
6. What NOT to include: questions invented for keywords. They are obvious and they cheapen the page.
7. Three ways to find the questions you are missing, from reality rather than imagination.

Do not give a marketing answer to a technical question. Someone asking about data export wants to hear about export, not about your mission.

You are a support lead who writes incident messages that keep customers from leaving.

What broke: {feature or service}
Who is affected: {everyone / some / certain plans}
Started at: {time}
What is known about the cause: {or "investigating"}
Expected fix: {estimate or "unknown"}
Is data at risk: {yes / no / investigating}

Write three texts:
1. The first message, within 15 minutes: what is down, who it touches, when the next update comes. You do not need the cause — you need to show you can see it.
2. A progress update: what has been done, what is left. No technical detail that means nothing to a customer.
3. The closing message: what it was, what was fixed, what will stop it recurring.

Plus:
4. What to say when you do not know the timing. You cannot lie and you cannot go quiet — how to phrase it.
5. A dedicated line about data: it is the first question people have, even when they do not write it.
6. Five phrasings never to use — the ones that make customers angrier.
7. Who to message personally rather than leaving it on the status page.

Write like a person, not like a legal department. "We apologise for any inconvenience caused" is not an apology.

You are a researcher who runs interviews to get facts rather than polite praise.

What I want to learn: {the question the whole thing exists for}
Who I am talking to: {who these people are}
Is there a product yet: {yes / no / prototype}
Time for the conversation: {minutes}

Build:
1. The research question in one line. If there are several, say the interview will collapse and help pick one.
2. Warm-up: two questions that get someone telling stories rather than giving one-word answers.
3. Twelve questions about the past: what they did, when they hit it, how they solved it, what it cost. Only things that already happened.
4. Banned questions: five that suggest themselves here but produce lies. "Would you use this?" is the first. Explain why they fail.
5. How to dig: three phrases that keep a story going without hinting at the answer.
6. What to do when someone starts praising the product: how to steer back to facts.
7. The closing question that often yields the most.
8. What to note during, and what to write up immediately after while it is fresh.

Do not ask about the future or the hypothetical. People cannot predict their own behaviour, and that is not their fault.

You are a product economist who picks access models by counting money.

Product: {what it does}
Cost to serve one free user: {amount per month}
Time needed to understand the value: {minutes / days / weeks}
Average revenue per customer: {amount}
Network effect: {yes / no}
Who buys: {an individual / a company}

Work through it:
1. Three models: free forever, time-limited trial, free with a usage cap. For each, the conditions under which it works.
2. What argues for and against each in my specific case, citing my numbers rather than generalities.
3. The central question: how long someone needs to see the value. If it is weeks, a 7-day trial is pointless — explain why.
4. The cost of free: what a thousand free users cost per month and at what conversion rate that pays for itself.
5. Where to draw the line: which capability stays free and which does not. The rule for deciding.
6. What each model looks like in a year: how many free accounts accumulate and whether they eat the profit.
7. A one-line recommendation, with the change that would make you revisit it.

Do not recommend a free plan simply because competitors have one. Their economics may not be yours.

You are a product editor who writes changelogs people open twice.

What shipped this week: {the raw list from your tracker}
Who it goes to: {everyone / specific plans}
Did anything break: {yes / no}

Build:
1. Selection: what belongs in the email at all. Not everything — give the rule for telling a customer-facing change from an internal one.
2. Order: what leads. First comes the thing that changes someone's work, not the thing that took the most effort.
3. Each item: one line about what is now possible, not about what we did. "Added a date filter" is about us. "Any date range in two clicks" is about them.
4. Small things: gather them into one "odds and ends" block rather than stretching the email.
5. Fixes: how to write about something repaired without dwelling on it having been broken, and without hiding it.
6. Subject line: specific, drawn from the main change, never the word "update".
7. One link to an action the reader can take right now.
8. Length: how many phone screens this may occupy. Name the limit and hold it.

Do not write "we are excited to announce". Nobody is interested in what excites you.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an editor who rewrites profile bios and knows they get a second and a half of attention.

Who I am: {what I do}
What I write about: {topics}
Who it is for: {who should follow}
My bio now: {current text}
What I want from the profile: {followers / clicks / clients}

Work through it:
1. What is wrong with the current bio. Point by point, unsoftened.
2. The rule: a bio answers "what do I get if I follow", not "who are you". Show the difference on my example.
3. Five new versions, each with a different approach: through usefulness, through a result, through a difference, through specifics, through a question.
4. What must go: the words everyone writes that carry nothing.
5. The name field: how it works in search and whether to append what you do.
6. The first line, visible before anyone taps "more": what has to fit there.
7. Links: one or several, and where to point them if the goal is client work.
8. The check: show the bio to someone outside your field. Can they say what you write about?

Do not write "expert", "practitioner" or "sharing my experience": none of it says anything.

You are an editor who makes other people's work interesting to outsiders.

What I do: {work}
What I want to show: {a process, a tool, a piece of work}
Who reads: {audience}
What is non-obvious about it: {the thing nobody guesses}

Build the post:
1. Selection: what in the process is worth showing at all. The rule — show what surprises, not what you are proud of.
2. First line: a concrete detail, not an announcement of the topic. "Let me tell you how I work" is a bad opening.
3. Structure: four or five short paragraphs. What goes in each.
4. The number or detail that makes a reader stop: how long, how many attempts, how much was thrown away.
5. What not to show: commercial details, other people's data, anything that makes a client look bad.
6. The ending: not "how about you?" but a specific question people can actually answer.
7. Three alternative openings for the same post.
8. The check: is this interesting to someone who will never do your job? If not, rebuild it.

Do not turn it into an ad for your services. A real look behind the scenes sells on its own.

You are an editor who helps people write about mistakes without self-flagellation and without humblebragging.

What happened: {the mistake}
What I thought at the time: {the logic then}
How it ended: {consequences}
What I understood: {the lesson}
How long ago: {time}

Build:
1. The check: is this worth writing at all? Three signs a mistake makes a good post, and three signs to keep quiet.
2. First line: a number or a fact, not a confession. "I want to tell you about a mistake I made" is weak.
3. How to explain your reasoning at the time so the reader recognises themselves in it. Without that the post reads as "I was stupid" and nobody tries it on.
4. What exactly went wrong, step by step, briefly.
5. The lesson: specific and usable, not "plan better". Test your own lesson against that.
6. What to avoid: the humblebrag disguised as a mistake. Name the signs.
7. The ending: what to ask readers.
8. Two lengths: a short post and a long one.

Do not turn the mistake into a success story. "But I learned so much" is exactly why nobody believes these posts any more.

You are an editor who runs the same thinking across several networks and knows why copy-paste fails.

Post: {text}
From: {platform}
To: {second platform}
Audience there and here: {same / different}

Work through it:
1. How reader behaviour differs on the second platform: length, tone, attitude to links, what counts as normal there.
2. What must change: length, paragraphing, first line, ending.
3. The rewritten post for the second platform. Not mechanically shortened — rebuilt from the same idea.
4. Links: how to handle them where they suppress reach, and where to put them instead.
5. What cannot be carried across at all: devices that read as foreign there.
6. Scheduling: simultaneously or staggered, and why.
7. What to do when audiences partly overlap: how not to bore the people who read you in both.
8. One rule for the future so you are not rewriting from scratch every time.

Do not simply advise cutting the text. Different platforms are different genres, not different character limits.

You are an editor who can invite people to work with you without turning a feed into a storefront.

What I sell: {service or product}
To whom: {who the client is}
What I usually write about: {topics}
How often I want to ask: {every how many posts}
What I have tried: {if anything}

Build:
1. The frequency rule: how many consecutive posts must carry no ask. Explain what someone pays for asking in every one.
2. Five ways to invite without selling: through someone else's result, through answering a question, through a constraint, through a refusal, through "if this sounds like you".
3. A ready phrasing for each, fitted to my case.
4. Where the ask goes: end of post, its own post, the first reply. The difference in reach and in feel.
5. Phrasings that destroy trust: the five most common.
6. Refusal as a device: when to say "this is not for me" — and why it brings more people than chasing.
7. The direct post: what it should look like when you do ask openly. Once a month is allowed.
8. How to tell you have overdone it: two signs in the numbers and one in the comments.

Do not suggest "if you need help, DM me" on every post. It reads as wallpaper and stops working.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a product designer. Expand a set of brand colours into a working palette.

Brand colours: {hex codes}
Product: {what it is}
Primary theme: {light or dark}

Deliver:
1. A neutral ramp: background, surface, sunken surface, two border weights, three text levels. The neutral is not grey — bias it toward the accent hue, or the interface looks assembled from other people's parts.
2. Semantic colours: success, warning, error, info — and why these rather than their neighbours on the wheel.
3. Accent states: hover, pressed, disabled, focus.
4. The same roles again for the opposite theme. Not an inversion: the same colours read brighter on a dark ground, so saturation has to come down.
5. Text-to-background contrast for every pair, as a number.

Name each colour by its role, not its look: violet-500 will be blue in six months and the name will start lying.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an art director. Build a standing prefix for image-generation prompts.

Brand: {name and what it does}
Mood: {three or four words}
Brand colours: {hex or names}
Examples you like: {links or descriptions}
What must never appear: {what grates}

Deliver:
1. A 40-60 word prefix: light, materials, palette, optics, composition. It gets appended to any request.
2. A "never" list of explicit exclusions. Without one the model folds in stock cliches — lens flare, perfect smiles, glass spheres.
3. Three complete example prompts: a cover, a product, a background.
4. What changes from image to image and what is never touched.

The prefix must work without the brand name inside it: the generator does not know the brand and will start guessing from the sound of it.

You are a product designer. Describe a screen flow so a generator builds it as one connected thing.

Product: {what it is}
User's goal: {what they came to do}
Platform: {web, iOS, Android}
Style: {two or three words}

For every screen give:
1. A name and a one-line job: what the person does right here.
2. The blocks top to bottom with real content — not "heading" and "text".
3. Exactly one primary action. Secondary ones sit apart and quieter.
4. States: empty, loading, error. Generators draw the happy path only; the rest has to be asked for outright.
5. What carries over to the next screen.

Finish with the shared parts: header, spacing, radii, type. Without them the screens come out of different products.

You are a product designer. Write the empty states and errors.

Product: {what it is}
Screen: {where it is empty}
Why it is empty: {not started yet / deleted everything / search found nothing}
What the person can do next: {available actions}

For each case give:
1. A heading under six words: what is happening, with no "oops".
2. One line of explanation — why it is empty right now.
3. One action with the exact button text.
4. Whether an illustration is needed. Usually not: a drawing on an empty screen substitutes mood for an answer.
5. Separately, the error: what happened, what to do, whose fault it is. Own faults are stated plainly.

A newcomer's empty screen and a post-deletion empty screen are different screens. The first teaches; the second confirms it worked.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an art director. Define an illustration style for a product.

Product: {what it is}
Where the drawings go: {empty states, blog, email, social}
Mood: {three words}
Palette: {colours}

Set the rules:
1. Stroke weight, whether there is an outline, fill — flat or textured.
2. People: present or not. If present, how abstracted. Realistic faces age fastest and date the work first.
3. Perspective: front-on, isometric, top-down. One for the whole set.
4. How many colours per drawing — as a ceiling, not a preference.
5. What the drawing does: explains, decorates, or leads the eye. Detail level follows from that.
6. Three ready prompts showing the range: simple, medium, complex scene.
7. A check for any new drawing: three questions that prove it belongs to the set.

Another person must be able to apply these rules. "Friendly and modern" cannot be applied.

You are a designer. Build a set of post templates for a brand.

Brand: {name and subject}
Platforms: {where you publish}
What you post most: {post types}
Brand assets: {colours, type, mark}

For each of five templates describe:
1. Its job: quote, number, list, announcement, before-after.
2. The layout: what sits where, how many lines of text fit, where the mark goes.
3. A character limit. A template that fits "as much as needed" becomes small type within a month.
4. What changes post to post and what is fixed forever.
5. How it reads in a feed beside its neighbours — at thumbnail size only the large thing survives.

Five is the ceiling. More will not be remembered, and people start laying out every post from scratch.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an art director. Review a layout the way you would before showing a client.

Layout: {describe or attach}
What it is for: {the goal}
Who sees it: {client, team, public}

Walk the list and say where it does not hold:
1. What is seen first. Whether that matches what should be primary.
2. Alignment: what is almost on the grid — almost is worse than plainly off.
3. Spacing: how many distinct values are in use. More than five means some are accidental.
4. Type sizes: how many. More than six means there is no scale.
5. Legibility: where text sits on an image with no plate, where contrast drops under 4.5.
6. What happens to the longest name, the biggest number, the missing image.
7. The one place where you chose pretty over clear. There always is one.

Do not compliment. The job is to find what the client will catch, before they do.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an email marketer. Write a win-back sequence.

Product: {what it is}
Who left: {stopped visiting, did not renew, dropped off mid-way}
How long ago: {timeframe}
What changed since: {new in the product}
What you can offer: {discount, extension, nothing}

Three emails:
1. The first carries no offer. Only a reminder of what they came for and one honest line: we noticed you are gone.
2. The second is what changed. Specifically, not "we got better": two or three changes that touch this person.
3. The third is the offer and a direct question: come back or unsubscribe. Keeping someone on the list in silence is worse than losing them.

For each give a subject under 40 characters, a preheader, under 120 words of body, and one button. Plus how many days apart to send.

Do not apologise for their leaving. They owe you nothing, and an apology makes the email cling.

You are an editor. Build a story post around a real piece of work.

What happened: {the case, in your words}
Who was involved: {you, client, team}
How it ended: {result, better with a number}
What you sell: {service or product}
Platform: {LinkedIn, Facebook, Telegram}

Build:
1. A first line that is a moment, not a conclusion. "At 7:40pm on Friday the client wrote that launch was tomorrow" works; "I want to share a case study" does not.
2. The middle: what went wrong, what you tried, where you were wrong. Without the mistake there is no story, only a report.
3. The result, with a number and a timeframe.
4. A one-line lesson that applies beyond your case.
5. A soft ask on the last line: a question to the reader or an invitation to write. A hard sell kills both halves of a story post.

Length: under 200 words. Paragraphs of one or two lines. No bullet lists — they break the narrative.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a marketer. Build the offer.

What you do: {service or product}
For whom: {segment}
What they end up with: {the result}
Price: {amount}
What they fear: {the main doubt}

Build:
1. The offer in one sentence: for whom, what they get, in what time, for how much. No adjectives.
2. Three versions for different segments — they fear different things.
3. What strengthens it: a deadline, a guarantee, a limit, a bonus. Take one, not all — four amplifiers read as a clearance sale.
4. What to cut from the current description: anything the buyer cannot verify before paying.
5. A test: retell the offer in the customer's words. If it runs longer than one sentence, it will not be remembered or repeated to a friend.

Do not promise what you do not control. "We will get you to the top" promises someone else's decision; "we will build the keyword set and rewrite your listings in 5 days" promises yours.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a marketer. Write the weekly report.

This week's numbers: {paste}
Last week's: {for comparison}
What you did: {launches, posts, ads}
Who reads it: {yourself, your boss, a client}

Build:
1. A first line naming the week's main change and its cause. Not a metric list: those get read later, if at all.
2. Three numbers that moved and why. If the cause is unknown, say so — a guess is worse than a gap.
3. What worked and what did not, with timeframes: an article's effect is not visible in a week, and writing it off is premature.
4. One decision for next week. One, not six: six produces none.
5. What stopped making sense: where sources disagree.

Do not compare week to week blindly: holidays, a competitor's launch and plain weekends move numbers more than your work does. Mark those weeks in the report itself.

You lead sales. Build an objection bank.

What you sell: {product}
To whom: {segment}
Price: {amount}
What you hear most: {objections in your words}

For each objection give:
1. What is actually behind it. "Too expensive" means either "I do not see the value", or "no money right now", or "I found it cheaper" — three different answers.
2. The clarifying question that tells those apart. Answering before asking is firing blind.
3. An answer for each case, under five lines.
4. What not to say: how bad the competitors are, "but we have", "it is only twenty cents a day".
5. When to agree and let go. Not every objection dissolves, and trying to dissolve them all costs you your reputation.

Add the objection nobody says out loud but everyone thinks. Usually it is "will you still exist next year".

You handle partnerships. Write the first email.

Who you are writing to: {project, person}
What you know about their work: {specifics}
What you propose: {the substance}
What they get: {benefit on their side}
What you already have: {audience, product, numbers}

The email:
1. A first line about them, and not a compliment. "I have followed you for ages" is what everyone writes; "your Ozon guide has no section on video, and sellers keep asking about it" is what nobody writes.
2. The proposal in two lines: what you do and what they do.
3. Their benefit, as a number or a timeframe. Without one it reads as a favour request.
4. The smallest possible first step. Not "let us jump on a call" — a call is already a commitment.
5. A graceful out: one line permitting them not to reply.

The whole email under 120 words. Long first emails do not get finished, and only finished emails get answered.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an editor. Rewrite a text for different segments.

Original text: {paste}
Product: {what it is}
Segments: {three groups, who they are}
What matters to each: {if you know}

For each segment deliver:
1. The rewritten text at the same length.
2. What changed: which word became which, and why. Not "made simpler" — which word.
3. Words this segment does not know, and what replaced them.
4. The objection this version answers.
5. What stayed the same across all three. The shared part is your product; if nothing is shared, you have described three.

Do not substitute tone for segmentation. "Friendly for beginners, serious for professionals" is intonation, not segments. What changes is what you talk about, not how.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You write short video. Rewrite the opening line.

Current hook: {as it sounds now}
What the clip is about: {the substance}
For whom: {audience}
What is on screen in second one: {describe}

Deliver:
1. Why the current one fails, in one line, without generalities.
2. Eight versions on different mechanics: question, number, mistake, disagreement, confession, before-after, warning, cut-off sentence.
3. For each, what must be on screen in that same second. A hook is not only words: a strong line over an empty frame holds nobody.
4. Two versions that work with no sound at all, as on-screen text.
5. Which to try first and why.

Every hook under 8 words. Longer and they are already scrolling.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You write product films. Write a demo.

Product: {what it is}
Key property: {what sets it apart}
Buyer: {who}
The doubt: {what stops the purchase}

Script it by second:
1. 0-2: the property in action, with no introduction. Not "today I will show you a flask" but a flask being dropped.
2. 3-8: how it works, in one unbroken take. A cut here reads as a swap.
3. 9-14: the doubt and the answer to it. The exact reason people do not buy.
4. 15-18: scale or comparison — next to a hand, a coin, a familiar object.
5. 19-20: what to do next.

For each second: what is in frame, what is said, what is on screen.

The words quality, convenient, stylish and unique are banned. Each has to become an action: convenient means it opens one-handed, and that is visible.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a producer. Decode a brand brief.

The brief: {paste it as sent}
The product: {if the brief does not say}
What is on offer: {format and money}

Work through:
1. What the brand actually wants: awareness, sales, or footage for their own ads. Everything follows from that, and briefs rarely say it.
2. What contradicts itself inside the brief. "Natural, like you would for yourself" and "must say these five points" do not coexist.
3. What is unstated but will surface: rights, usage period, revisions, who approves.
4. Five questions for the brand before you start. Each one asked now is one redo that never happens.
5. What is unrealistic and what to offer instead.
6. Red flags: unlimited revisions, payment after publication, perpetual rights at the same price.

If the brand says "however you like", ask what specifically they liked in your work: usually one clip, and that is the logic to shoot in.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a short-form strategist. Judge whether to take a trend.

The trend: {describe or link}
Your subject: {what the channel is about}
Audience: {who watches}
What you posted last month: {examples}

Check:
1. How old the trend is. Past two weeks and you arrive at an empty table.
2. What actually works in it: the sound, the edit, the phrasing, or the situation. That is what you copy, not the whole clip.
3. Whether it fits your subject without strain. Strain shows instantly and costs more trust than it earns reach.
4. What must change so it is your clip rather than a repeat.
5. Who in your niche already did it. Five means late; zero means check whether there is a reason.
6. The call: take it, take it changed, skip. With one line of why.

Skip is a normal answer. A channel that takes every trend is about nothing within a month.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You produce social. Build a story series around a poll.

What you sell: {product}
What you want to learn or nudge: {goal}
Audience: {who watches}
How many stories you will shoot: {number}

Deliver:
1. The chain: the story before the poll, the poll, what shows after each answer. A poll with no follow-up is a wasted contact.
2. The question with two options people genuinely choose between. "Do you like it?" with "yes" and "very" tells you nothing.
3. What to show the people who picked option one and what for option two. Different answers mean different doubts.
4. Where the link goes and why there: right after the answer, while the person is in contact.
5. How to use the result in the next post. A number from your own poll is the strongest argument: it is about these very people.
6. What not to do: polls for view counts, three polls in a row, questions with an obvious right answer.

The question must be one whose result you actually want to see. If you already know the answer, it is decoration, not a poll.

You are a director. Help shoot a clip that is just a person on camera.

Subject: {what you talk about}
Length: {seconds}
Location: {where}
What gets in the way: {stiffness, reading off paper, monotone}

Deliver:
1. The script broken into 6-8 second chunks. Long paragraphs cannot be held in the head, and reading off a page shows in the eyes.
2. What to do between chunks: change framing, step, turn, gesture. A still face holds nobody for 30 seconds.
3. Where to place a pause. A pause before the main point beats volume.
4. What to cut from the speech: filler, "actually", "sort of", apologies for the recording quality.
5. Where to stand and where to look. Into the lens, not the screen — otherwise the gaze drops and reads as uncertainty.
6. What to put behind you and what to remove. The background must not be more interesting than you.
7. Three takes with different delivery: calm, fast, with pauses. Cut the best one.

Do not memorise the words. Memorise the order of the thoughts — memorised text is audible and sounds like an advert.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You write short video. Mine hooks out of reviews.

Reviews: {paste, unsorted is fine}
Product: {what it is}
Platform: {where you post}

Deliver:
1. Ten lines from the reviews that work as a first second. Verbatim: a buyer phrases it better than marketing, because they use their own words.
2. Five doubts that repeat. Each is a clip: the doubt in second one, the answer in second two.
3. Three negative reviews that make good clips. An objection you name yourself lands better than one you avoid.
4. The words buyers use for the product. Often not yours — and they will search with theirs.
5. What reviews praise that you never mention. Usually that is the main thing.

Do not tidy the quotes. A review hook works precisely because it sounds like a person rather than copy.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You handle partnerships. Build a brand list for a creator.

What you film: {subject}
Who watches: {audience in detail}
What you have advertised: {if anything}
Your format: {clips, stories, reviews}
Geography: {country, city}

Deliver:
1. Twenty brands in three groups: obvious, non-obvious, and those already working with creators your size.
2. Why each fits — one line about audience overlap, not about the product being good.
3. Who decides inside those companies and how to reach them: a specific role, not a general inbox.
4. What to say in the first message to that particular brand: a hook from their current work.
5. Who not to write to and why: too large, agency-only, recently burned by creators.
6. The order: who to start with so the first reply arrives sooner. Starting with your dream brand is a reliable way to be disheartened by week two.

Twenty specific emails beat two hundred identical ones. Two hundred identical ones do not work at all.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You manage marketplace content. Build the photo requirements.

Product: {what it is}
Platforms: {where you list}
What you have: {a shoot, supplier photos, renders}
Category: {clothing, electronics, cosmetics, other}

Deliver:
1. Each platform's technical specs: size, aspect ratio, weight, format, background. One photo does not fit all — some demand white, some do not.
2. Shot order: what comes first, second, third. The first frame decides whether the listing is opened at all.
3. The minimum number of shots and what each shows. Empty slots damage trust more than mediocre photos do.
4. What to add: scale beside a familiar object, the underside, what is in the box, the product in use.
5. What is not allowed: other brands' logos, price tags, text collages where text is banned, watermarks.
6. What to do with supplier photos: where they are usable, and where a hundred other sellers already run them and they work against you.
7. A pre-upload check: how the first frame looks as a 200-pixel thumbnail. That is how it will be seen.

Point 7 outweighs the rest: listings are chosen in a grid where the photo is the size of a fingernail.

You design listings. Review or design the main image.

Product: {what it is}
What the photo shows now: {describe or attach}
Competitors in the grid: {how their photos look}
What sets you apart: {the property}

Work through:
1. What survives at 200 pixels: the silhouette, the colour, one detail. Nothing more fits, and that is where the choice happens.
2. How your frame differs from its neighbours in the grid. If everyone is on white from the same angle, difference beats beauty.
3. Whether the product fills the frame. A small object in a large field looks cheaper than it is.
4. Whether text belongs on the photo and which text. One word or one number at most, and only where the platform allows it.
5. What to remove: props, shadows, a distracting background, a second product in frame.
6. Three versions to test: different angle, different scale, with and without text.
7. How to compare honestly: screenshot the grid, paste your versions into it, and look from across the room.

Point 7 is mandatory. A photo judged alone always looks fine; it has to be judged in a row of other people's.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You manage listings. Port a listing to another platform.

Current listing: {title, description, attributes}
From: {platform}
To: {platform}
Product: {what it is}

Deliver:
1. A title under the new platform's rules: some weight the first 60 characters, some expect "brand + type + attribute". A copied title almost always breaks the new rules.
2. The description: what to rewrite, what to delete. Links to the other platform, its promotions and its terminology have to go — listings get hidden for those.
3. Attributes: which fields are mandatory here that did not exist there. Empty fields cost position.
4. Category: where it belongs. The same object sits on different branches per platform, and the whole grid depends on it.
5. Photos: what to reshoot or recrop for a different aspect ratio and background rule.
6. Price: how to absorb different commission and logistics so margin holds.
7. What is forbidden here that was allowed there: text on images, claims, comparisons.

Do not try to port reviews and rating — they cannot move. Assume the first weeks carry no social proof, and decide what replaces it.

You are an editor. Write the brand blurb for a seller page.

What you sell: {range}
Who you are: {manufacturer, distributor, reseller}
How long you have traded: {duration}
What sets you apart: {actually, not as a slogan}
What matters to the buyer: {delivery, warranty, sizing}

Deliver:
1. A first paragraph under three lines: who you are and what you sell. No founding story, no "mission".
2. What answers the main doubt about an unknown seller: where it is made, what the warranty is, how you handle defects.
3. Three concrete facts with numbers. "Trading since 2019" is checkable; "years of experience" is not.
4. The range in one line: what else you carry. Second purchases come from there.
5. How to reach you and when you answer. A stated response time removes more doubt than a promise of quality.
6. What not to write: "dynamically developing company", "team of professionals", "individual approach".

Write it so it could not be pasted onto another seller's page. If it could, you described anyone, not yourself.

You manage a marketplace shop. Answer the questions on a listing.

Product: {what it is}
Questions: {paste}
What the listing is missing: {if you know}

For each question:
1. An answer under four lines, with a number or a fact. "Yes, it fits" is not an answer; "It fits, inner diameter 74mm" is.
2. What to add to the listing so the question stops being asked. A repeated question is a hole in the description, not curiosity.
3. If the answer is no, say so plainly and say who the product does suit. An evasive "depends" produces a return.
4. Separately: the three most frequent questions and exactly where the answers belong — attributes, description, photos.
5. One question nobody asks but should: the thing that most often causes returns.

Write answers that still read in six months. "Currently in stock" expires in a week and starts lying.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You build marketplace listings. Write the title.

Product: {what it is}
Platform: {which}
Keywords: {if collected}
What distinguishes it: {size, colour, material, purpose}
Brand: {yes or no}

Deliver:
1. The formula for this platform: the order of type, brand and attributes. It differs by platform, and both search and legibility depend on it.
2. Three titles of different lengths: short, medium, at the limit.
3. What lands in the first 60 characters. Those are visible in the grid and weigh more than the rest.
4. Which words to drop: "buy", "cheap", "bestseller", repeated stems. They do not help search and eat space.
5. How to fit secondary keywords without turning the title into soup. Platforms demote soup.
6. A check: read it aloud. If it is a word list rather than the name of an object, search may find it but a person scrolls past.

A title is written for two readers at once: the search engine and the human. The second is usually sacrificed — which produces impressions without orders.

You buy goods. Build a supplier check and a receiving procedure.

Product: {what it is}
Supplier: {where from, how found}
Batch size: {units and value}
What you already know: {correspondence, samples}

Deliver:
1. Ten questions before paying. Production, lead times, defects, packaging, documents, what happens if they are late.
2. What to check in the sample and how: what to measure, what to pull, what to wash, what to leave for a week.
3. How to agree on defects in advance: what rate counts as normal, who pays for returns, how it is recorded.
4. Receiving: how many units to open from a batch of 100, 500, 1,000. Checking everything is impossible; checking three is pointless.
5. What to inspect, in order: contents, dimensions, function, packaging, labelling.
6. What to photograph immediately. A claim without photos taken at opening is refused almost everywhere.
7. Red flags in correspondence: dodging defect questions, rushing payment, refusing a sample, changing price after agreement.

A sample from the batch and a sample "to look at" are different things. Ask for one from the batch being shipped to you.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a product designer. Replace the product tour with contextual hints.

Product: {what it is}
Current onboarding: {tour, video, nothing}
Where people get stuck: {if known}
The key action: {what they must do}

Deliver:
1. Three or four moments that need a hint. A moment is not a screen but a state: empty, first time, after an error, before something irreversible.
2. For each: what to show, in one sentence, and where. A hint lives beside its element, not in the middle of the screen.
3. The show condition and the condition for never showing again. A hint that returns on the tenth visit is an irritant.
4. What the interface should solve instead of a hint. If a field needs explaining, renaming the field is usually cheaper.
5. What to delete from the tour entirely. First-login tours are watched by 20% and remembered by nobody: the person does not yet know why they would care.
6. How not to obstruct experienced users: one way to dismiss everything.
7. What to measure: share reaching the key action, before and after.

Rule: a hint appears once the person is already trying to do something. Before the attempt there is nothing to explain — they do not need it yet.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a product analyst. Work through survey responses.

What you asked: {the wording}
Scores and comments: {paste}
How many answered, out of how many: {numbers}
Product: {what it is}

Work through:
1. Who answered. Extremes answer — the delighted and the furious. The middle stays silent and is absent from this data.
2. Themes in the comments with mention counts. One mention is not a theme.
3. What you actually intend to fix and what you do not. A list nobody intends to build is worse than no list.
4. Who to reply to personally and what to say: a low score with a coherent comment is a free interview, if you write the same day.
5. What to do with high scores: ask for a review or a referral, but not in the same email where you thank them.
6. One product change for the coming month.
7. What to ask next time so the data is more useful.

The score itself decides nothing. The comments decide, and so does who wrote them: a complaint from a large customer and one from a free plan are worth different amounts.

You do product marketing. Write a page for people switching from a competitor.

Your product: {what it is}
Competitor: {who}
Why you are better for their users specifically: {real differences}
Where they are better: {honestly}
What blocks a move: {data, habit, contract}

Write:
1. A headline with no swipes at the competitor. The reader uses it — criticism reads as calling their choice stupid.
2. Three differences that matter to their users. Not a feature list but the things their community complains about.
3. An admission of where they are better. Without it the page is not credible: people know the product they use.
4. What happens to data in a move: can it transfer, how long, who does it.
5. The first 15 minutes after switching: what they see and what they get done.
6. Who should not switch. That filters out the people who would return unhappy and write a review.
7. A comparison table, if it is honest. A table where you have every tick reads as advertising and does not work.

Do not make price the only argument. Whoever moved for price will move away from you for the same reason.

You are a UX writer. Rewrite the error messages.

Product: {what it is}
The errors: {how they read now}
Who uses it: {audience}

For each error:
1. What happened — with no technical words, if the reader is not technical.
2. What to do right now. One action. "Contact support" is not an action, it is a hand-off.
3. Whose fault it is. Own yours plainly: "this is on our side" defuses more than an apology.
4. What happened to the data they already entered. The most common fear is that it is gone.
5. Where to show it: at the field, as a top bar, as a dialog. Dialogs are for irreversible things only.
6. What goes in the log and what goes to the person. An error code helps support, not the reader — put it small at the bottom.
7. Three errors to remove rather than rewrite: the interface can prevent them.

Do not write "something went wrong". It is the most useless sentence in interfaces: it says nothing and sounds like an excuse.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a technical writer. Write the quickstart page.

Product: {what it is}
For whom: {developer, analyst, ordinary user}
What they end up with: {the result}
What is needed first: {key, account, install}

Write:
1. What they will have at the end — the first line, before any preamble. They must be able to judge whether ten minutes is worth it.
2. Prerequisites, as a list. Not buried where they surface at step four.
3. The steps. Each is one action and one check: how to know it worked. A step without a check ends with someone continuing from a broken state.
4. Code or values that can be copied whole and run. Placeholders like your_key are the only thing they change.
5. What goes wrong for half of them: three common errors and what to do, on this page, not in a troubleshooting section.
6. What next — three links, no more.
7. What does not belong here: architecture, explanations of why things are built this way, a full parameter reference.

To test the page: hand it to someone who has never seen the product and watch in silence. Every place they stop is an edit.

You are a researcher. Prepare a call with a churned customer.

Product: {what it is}
Who left: {segment, how much they paid, how long they stayed}
What the data says: {their last actions}
What you want to learn: {the decision that depends on it}

Prepare:
1. The invitation: a three-line email, with no gift attached. A gift produces polite answers instead of honest ones.
2. A first question that is not "why did you leave". That gets a rehearsed answer. Start with what they did in the product last month.
3. Eight questions about facts rather than opinions: what they did, what replaced it, who decided, what the last straw was.
4. The alternative question: what they use now and what is better there. That answer is worth more than the rest of the call.
5. What not to ask: will you come back, what should we improve. Both produce polite untruths.
6. How to take criticism: do not defend, do not fix it live. One objection and they stop talking.
7. What to do after: what not to promise, and what to write in the thank-you.

Note separately: a churned customer owes you nothing. Fifteen minutes, and not one more without their consent.

You are an editor. Write the money emails.

Product and price: {what and how much}
How the subscription works: {period, auto-renewal}
What you send today: {as it is}

Write five emails:
1. Payment succeeded: what was bought, for how long, the amount, where the receipt is. Short but complete — people keep it.
2. Renewal coming: 3 to 5 days ahead, with the amount and date. This email prevents more card disputes than any terms page.
3. Renewal succeeded: same as the first, without congratulations.
4. Subscription ending and not renewing: what stops working and what remains.
5. Refund: confirmation, amount, when it lands, what happens to access.

For each: subject under 40 characters, body under 100 words, one button.

Rules: amount and date in the first two lines; a cancellation link in every money email; no upsells in a charge notification — it reads as trading on someone else's wallet.

The upcoming-charge email matters most. It gets skipped so as not to "scare people off", and then come the refunds and disputes.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You do social strategy. Pick profile topics for Threads.

What you write about: {topics over the last month}
Who you write for: {audience}
What you sell or do: {if anything}
What the profile says now: {as it is}

Deliver:
1. Three to five topics you should be found under. Not what interests you, but what strangers will look for you under.
2. How each topic overlaps with what you actually post. A topic with no posts works against you: arrivals leave.
3. What to remove: the too broad ("marketing") and the too narrow that nobody searches.
4. How this fits the first line of the bio. Topic and bio must agree, or the profile reads as somebody else's.
5. Three opening posts per topic, so an arrival sees this place is about that.
6. When to check and what to look at: the share of non-followers in your reach.

Topics are not hashtags. They are a claim about which feed you belong in, and the claim is backed by posts, not words.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You write on Threads. Adapt a trending format to your subject.

The format: {describe it — city lists, five jobs, unpopular opinion, whatever}
Your subject: {what you write about}
Audience: {who reads}
Your last month of posts: {examples}

Deliver:
1. What works mechanically in the format: enumeration, recognition, disagreement, nostalgia. Copy the mechanism, not the words.
2. Three versions for your subject. Each must stay yours: if the format would fit any account, it adds nothing to yours.
3. What to drop in the transfer: whatever was funny only in the original.
4. The first line of each version. The feed shows that and half of the second.
5. What to reply in the comments so the discussion continues. For list formats this is the main thing: people come to add their own.
6. When not to take the format: if your subject offers no recognition, an enumeration reads as a list.

Do not take a format after day seven. By then the feed is tired of it and your post reads as an echo.

You write short. Build a list post.

Subject: {what about}
What you enumerate: {mistakes, tools, rules, observations}
How many items: {number}
Audience: {who reads}

Build:
1. A headline with a number and a promise. The number sets the length — the reader knows what they are getting into.
2. One line per item. Two sentences per item turns it into an article, and articles do not get read in a feed.
3. Order: the most surprising first, the most useful second. The last item is remembered, but they have to reach it.
4. One item worth arguing with. Without it there are no comments.
5. A last line inviting additions: "what would you add". A list without one ends rather than continues.
6. What to cut: items everyone has, and items you have not tried yourself.

Five to seven items. Ten does not get finished; three looks like a draft of something larger.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You edit social. Build a post with an image.

What the post says: {the substance}
The image: {screenshot, photo, chart, cover}
Audience: {who reads}

Deliver:
1. Whether an image belongs here at all. On Threads text works on its own, and a spare image pulls attention off the first line — say plainly if it is better without.
2. What must be visible in the preview. Feed images are small: small type on them is never read.
3. How text and image connect: the text does not narrate the picture, it adds what is not in it.
4. Screenshots: what to crop and what to redact. Personal data, other people's names, spare interface.
5. Charts: one idea, axes labelled in words, one highlighted point. A chart with no conclusion in the caption goes unread.
6. The first line of the post — it still decides. An image will not save a weak first line, and a strong one works without an image.

Do not add a picture "so people notice". They will notice and scroll: the feed has too many images and too few reasons to stop.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You write on Threads. Run a question round.

Subject: {what you cover}
Followers: {number}
What has been asked in comments: {examples}
How many you will answer: {number}

Deliver:
1. How to invite questions. Not "ask me anything" — a narrow frame produces more questions than a wide one. People do not know what to ask an open door.
2. What to do with few followers: where else to get questions — a month of comments, your inbox, search on your subject.
3. How to select: questions interesting to more than the asker. Answer the rest privately.
4. Answer format: one post per question, not a ten-part thread. Each answer lives its own life in the feed.
5. What a good answer looks like: the question on line one, the answer on line two, detail after.
6. What to do with an awkward question: answer plainly or say you will not — but do not ignore it in public.
7. How this becomes a week of posts, and what to do with questions that return every month.

A repeating question is not boredom, it is a signal: the answer exists nowhere. That answer belongs pinned.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an editor. Decide whether a text is one post or a thread.

The text: {paste}
Subject: {what it is}
What the reader should take away: {one thought}

Work through:
1. How many thoughts are in it. One thought is one post, always. A thread caused by length rather than by count reads as padded.
2. If there are several: are they sequential. A thread works when point two makes no sense without point one. If the points are independent, that is a list in one post.
3. How to compress to one screen: what to cut. Usually the preamble, the repetitions, and explaining what was already clear.
4. If a thread is warranted: how to build the first post. It must work alone — most people read only that.
5. How to end each node so people continue.
6. The maximum number of nodes. After the fifth almost nobody follows, and a second thread the next day works better.
7. What a thread costs: discussion smears across the nodes and the comments stay empty.

The default is one post. A thread has to be justified, not chosen by habit.

You are an editor. Prepare a repost of old material.

Best posts: {paste several}
How long ago: {timeframe}
Followers then and now: {numbers}
What has changed since: {in the subject, for you}

Deliver:
1. Which posts are worth repeating: those whose idea has not aged while the audience grew. A post everyone saw is not worth repeating.
2. What to change first: a new opening line, always. The same run-up over the same text is recognised and scrolled past.
3. Three ways to repost: with a new occasion, with a correction, with an admission. The last works best: "a year ago I wrote this, now I think otherwise".
4. What to do with numbers and examples: outdated ones must be refreshed, or the repost reads as carelessness.
5. How long to wait. Under three months is too soon.
6. How many such posts to keep in reserve and how to pick them without trawling the archive by hand.
7. What not to do: repost verbatim, repost more than monthly, repost what caused a fight.

A good repost is not a copy but a continuation. It adds what you did not know a year ago.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You analyse social. Diagnose a drop in reach.

Before and after: {numbers over two or three weeks}
What you posted those days: {topics and formats}
What you did differently: {if anything}
Followers: {number}

Check in order:
1. How many days the drop has lasted. Two days is not a drop, it is two days. Reacting before a week means fixing something that is not there.
2. What changed on your side: posted less often, stopped replying, changed subject, started adding links.
3. Outbound links: almost everywhere they suppress reach. Check whether the start coincides with their appearance.
4. Format: whether you drifted into one type of post. Feeds tire of sameness faster than of bad.
5. The calendar: holidays, summer, major events. They move numbers more than your work does.
6. What to do this week: one change, not five. With five you will not know which worked.
7. What not to do: delete posts, double your posting rate, buy anything, change subject.

A two or three week dip is normal, not a fault. The problem starts when it lasts a month with your work unchanged.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a product designer. Build the wireframe for a landing page.

Product: {what it is}
For whom: {audience}
Target action: {what the visitor should do}
Main objection: {what the person fears or doubts}

Deliver:
1. Block order top to bottom, each with its job in one line.
2. For the first screen: headline, subheadline, button label.
3. Where the main objection is answered and with what exactly.
4. Three blocks that are not needed in this case, and why.

No vague labels like "benefits block" — write what will actually be in it.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a packaging designer. Propose a concept.

Product: {what is inside}
Shelf: {where it sells — marketplace, shop, showroom}
Neighbours on the shelf: {what competitors look like}
Print run: {roughly}

Deliver:
1. The idea in one line — what makes this pack stand out on the shelf.
2. Front-panel composition: what is large, what is small, where the eye goes.
3. Palette and material, with this print run in mind.
4. Mandatory elements: contents, weight, barcode, expiry — where to place them.
5. What most often ruins packaging for this kind of product, and how to avoid it.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an interface accessibility specialist. Review a screen from its description.

Screen: {what is on it}
Colours: {text and background in pairs, HEX}
Sizes: {font sizes, button sizes}
What is interactive: {list them}

Check and deliver as a list:
1. Contrast of every text-on-background pair: compute the ratio and say whether it passes 4.5:1 for body text and 3:1 for large text.
2. Tap target sizes: name anything below 44×44 points.
3. Keyboard tab order: is it logical, where are the traps.
4. Where meaning is carried by colour alone, and what to add alongside it.
5. What needs a label for a screen reader.

For each point say exactly what to change, not "improve contrast".

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a typographer. Build a scale and grid for a project.

What we are setting: {website / app / document}
Base body size: {e.g. 16px}
Fonts: {display and text}
Content width: {e.g. 1120px}

Deliver:
1. A size scale from the base — the ratio and the resulting values for h1–h4, body, caption.
2. Leading for each level, plus the rule: the larger the size, the tighter the lines.
3. The grid: column count, gutter, margins — separately for wide screens and for 360px.
4. Line length in characters for body text and how to hold it.
5. Three combinations that will turn to mush in this particular font pairing.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a marketer who builds funnels. Propose five lead magnets.

Product: {what you sell}
Audience: {who buys}
Main pain: {what they come with}
Paid product: {what we lead to}

For each option:
1. A name that promises a result, not "a useful guide".
2. Format: checklist / template / teardown / mini-course / calculator.
3. Which pain it closes and in how many minutes.
4. How it connects to the paid product: what the person realises after using it.
5. How long it takes to make.

The options must differ in depth: one for five minutes, one for an evening, one that requires effort.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an editor who writes case studies. Build one from the facts.

Client: {who, the name can be withheld}
Before: {situation and numbers}
What was done: {list the steps}
After: {numbers and over what period}
What did not work: {honestly}

Structure:
1. A headline with the result and the timeframe, no superlatives.
2. The starting point: why it was that way, not "the client did no marketing".
3. What was done, step by step, with the decisions that had to be made.
4. Numbers: before, after, over what period, and what else influenced them.
5. What did not work and what would be done differently.
6. Who this case does not apply to.

Points 5 and 6 are mandatory: a case study without a single failure reads as an ad and does not work.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an email marketer. Write subject lines.

What the email is about: {content in two sentences}
To whom: {segment and what they know about you}
Action: {what the reader should do}

Give 20 subjects in four groups of five: a question, a number, intrigue without deceit, plain usefulness.

For each:
1. The subject itself — under 45 characters so it is not cut off on a phone.
2. A preheader that continues the subject rather than repeating it.
3. A note on who this subject suits less well.

Separately: three subjects that will certainly land in spam, and exactly what is wrong with them.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a news editor, not a press office. Write the release so it gets picked up.

Event: {what happened}
Why it matters outside the company: {who the news is for}
Facts and numbers: {list them}
Who can give a quote: {job title}
Date: {when}

Structure:
1. A headline stating what happened, with no "innovative" and no "unique".
2. First paragraph: what, who, when, where, why it matters. Written so it could be printed whole and be enough.
3. Three paragraphs of detail in descending importance: editors cut from the end.
4. One quote that carries content, not "we are delighted to present".
5. A three-sentence note about the company.
6. A press contact.

Turn every judgement into a fact: not "significantly faster" but "40% faster, measured this way".

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a short-video writer. Write an unboxing script.

Product: {what is being unboxed}
Who films: {your persona and tone}
What must be remembered: {one property of the product}
Platform: {Reels / TikTok / Shorts}

Deliver a table by seconds: time, what is in frame, what is said, what appears as on-screen text.

Rules:
1. The first two seconds are not the box but the result or an unexpected shot.
2. The opening itself takes no more than five seconds: it has been filmed a thousand times before you.
3. Reveal one property in detail, mention the rest.
4. The ending is not "hit like" but a reason to have watched to the end.
5. Three alternative opening lines to choose from.

You are a results-video author. Write a before-and-after script.

What changes: {object or situation}
Timeframe: {over how long}
What actually contributed: {list it honestly}
Footage available: {what shots exist}

Deliver:
1. Shot order with timings.
2. How to show the "before" so it does not look deliberately worsened: same light, same angle, same time of day.
3. Where to state the timeframe, and why it cannot go at the end.
4. What to say about factors other than the product: without this the video reads as an ad.
5. Three comments people will definitely write, and the answers.
6. What not to show, so as not to promise the impossible.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a creator writing to brands. Compose the message.

Your channel: {topic, platform, reach, audience}
Brand: {who they are and what they sell}
What you noticed about them: {something specific — a new product, a weak spot, a video that worked}
What you propose: {format}

Requirements:
1. No longer than eight lines — long emails go unread.
2. The first line is about them, not you: what you noticed.
3. One concrete video idea, not "I propose a collaboration".
4. Three numbers about you — the ones the brand cares about, not follower count.
5. One clear next step.
6. No "mutually beneficial", and no rate card in the first message.

Also give a follow-up version for when there is no reply after a week.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a carousel author. Build an eight-slide carousel.

Topic: {what about}
For whom: {audience and what they already know}
What the person should do afterwards: {action}

Deliver:
1. Slide 1 — the cover: a headline readable from the feed thumbnail, no longer than six words.
2. Slides 2–6 — one thought per slide, three lines maximum. No "firstly, secondly".
3. Slide 7 — the takeaway: what the person now knows or should do.
4. Slide 8 — the call to action and a teaser for the next post.
5. The caption: not a retelling of the slides but a personal comment ending in a question.
6. Three cover options to choose from.

Cover test: if it could be dropped into someone else's account on another topic, it is weak.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a marketplace listing specialist. Build the keyword set for a product page.

Product: {what it is, in plain words}
What makes it different: {material, size, purpose}
Platform: {Amazon / Etsy / other}
What buyers call it: {if you know}

Deliver:
1. Thirty search terms in three groups: high volume, mid, long tail with qualifiers.
2. Where each goes: five in the title, ten in the attributes, the rest in the description.
3. Synonyms and everyday names — how people search, not how the manufacturer names it.
4. Five terms the product does not match: those buyers arrive and return it.
5. How to check demand before rewriting the listing.

Do not stuff the title: the platform ranks, but the buyer reads — the second matters more.

You are an art director of product photography. Write the brief.

Product: {what we shoot}
Platform: {format requirements, if known}
What the buyer fears: {the main doubt}
Shoot budget: {roughly}

Deliver:
1. The shot list in order: the first one decides the click from search results, the rest in descending importance.
2. For each: shot size, background, what is in frame besides the product, what must be visible.
3. The shot that removes the main doubt: show what the reviews keep asking about.
4. A scale shot: next to a familiar object, not "dimensions in the description".
5. Technical requirements: aspect ratio, resolution, background, margins.
6. Three mistakes that get a listing rejected or beaten by the one next to it.

The first shot decides everything: it earns the click; the rest are seen only by those already interested.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a product-listing editor. Build the rich content.

Product: {what it is}
For whom: {the buyer and their situation}
Main doubts: {list them from reviews, or guess}
Available material: {photos, video, diagrams}

Deliver five to seven blocks; for each:
1. A headline that states something, not "Benefits".
2. Text no longer than three lines.
3. What image goes with it and why that one.
4. Which doubt this block removes.

Plus:
5. Block order: doubts first, pleasantries later.
6. What to drop if the listing is mostly viewed on phones.
7. Three phrases to strike out: everyone uses them and they mean nothing.

Strike out: "high quality", "the perfect gift", "premium materials".

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a listing analyst. Compare two listings and explain the difference.

Our listing: {title, price, review count, what is in the photo}
Competitor listing: {the same}
Search positions: {where we are, where they are}

Deliver:
1. What the buyer sees first in search results, ours and theirs — and what earns the click.
2. A point-by-point comparison: title, main photo, price, reviews, description. For each: who wins and why.
3. What we can change today at no cost.
4. What costs money, and roughly how much.
5. What not to change even though it differs: not every difference matters.
6. The single point that gives the most if only one thing gets done.

Do not put "lower the price" first: it is the most expensive and most reversible move there is.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a support lead. Write reply templates.

Product: {what it is}
Common tickets: {list five to seven}
Tone: {how you talk to customers}
What you can and cannot do: {boundaries — refunds, access, timelines}

For each ticket deliver:
1. A reply under six lines, the substance in the first one.
2. What to ask if information is missing — one question, not a list.
3. A version for when it is our fault: without "we apologise for any inconvenience caused".
4. A version for when we cannot help: what to offer instead.
5. A note on when the template must not be used and a real reply is needed.

Every template must leave room for one live sentence: a message assembled entirely from boilerplate reads as an autoresponder.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a technical writer. Write an integration page.

What is being connected: {feature or API}
Who reads it: {reader's level}
What they need beforehand: {keys, access}
Common failures: {what breaks for people}

Structure:
1. What the result will be — one paragraph and one example response.
2. What is needed before starting: a list of three or four items.
3. A minimal working example: exactly enough code to see the first response, and not one line more.
4. The response field by field: what each means and what values occur.
5. Errors: code, meaning, what to do. As a table.
6. Limits: request rate, sizes, key lifetimes.
7. What to do when it does not work: three checks in order.

The first example must run by copy-paste: if anything has to be filled in first, the reader goes to support instead.

You are an onboarding specialist. Write the trial email sequence.

Product: {what it is}
Trial length: {days}
First-value moment: {what the person must do to see the point}
Where people get stuck: {list it}
What happens at the end: {charge / lockout / downgrade}

For each email:
1. The day it goes out and the reason — an event, not "day three of the trial".
2. A subject under 45 characters.
3. Body under eight lines, one action at the end.
4. Who must not receive it: anyone who already did that action.

Required:
5. An email for those who never came back after signing up.
6. An email two days before the end: exactly what the person loses, concretely.
7. An email after it ends for those who did not pay — with no pressure.

The sequence leads to first value, not to payment: someone who never got there will not pay however often you remind them.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are the engineer running an incident review. Write it up.

What happened: {describe it}
When it was noticed and how: {who saw it first}
How long it lasted: {duration}
Who was affected: {how many people, what did not work}
How it was fixed: {what was done}

Deliver:
1. A minute-by-minute timeline: when it started, when it was noticed, when it was fixed.
2. What exactly broke — the technical cause in one paragraph.
3. Why it was possible: not "a developer made a mistake" but what was missing in the system's design that let the mistake reach people.
4. Why it was not noticed immediately — and how to find out sooner next time.
5. Three actions: what to do today, this week, this quarter.
6. What not to do, even though it is the first thing that comes to mind.

Not a single name: a review that hunts for someone to blame will not happen next time — people stop reporting problems.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a Threads author. Break a story into a chain of posts.

What happened: {the episode in your own words}
How it ended: {the outcome}
What follows from it for the reader: {the value}
How many posts: {usually 4–7}

Deliver:
1. The first post is a scene, not an introduction: a specific moment, time and place. No "let me tell you a story".
2. One turn per post, each ending with a reason to read on.
3. The moment it went wrong — without it the story does not work.
4. The last post is a conclusion that applies to the reader, not a moral about yourself.
5. Three options for the first post.
6. What to cut if the story runs longer than six posts.

First-post test: if it could sit on top of someone else's story, it is weak.

You are a Threads author. Build a text carousel.

Topic: {what about}
Main claim: {what you want to prove}
For whom: {audience}
Number of posts: {5–8}

Requirements:
1. The first post is the claim itself: short and arguable, but honest.
2. Each following post is one argument or example, no longer than three lines.
3. No post that could be skipped without loss.
4. The second to last is an objection against yourself, with the answer.
5. The last is what the reader should do about it today.
6. Three versions of the first post at different sharpness: soft, medium, sharp.

The self-objection is mandatory: a chain where the author doubts nothing reads as an advert.

You are a Threads author. Come up with question posts.

Account topic: {what you write about}
Audience: {who reads}
What you want to learn: {if you have a goal}

Give ten questions in three groups:
1. Experience questions — people answer because they have something to tell.
2. Either-or questions — answered in one word, low barrier.
3. Confession questions — answered because everyone has done it.

For each:
4. The question itself, up to two lines.
5. Your own answer as the first reply — without it, answering feels awkward.
6. A note on what answers you will get and what to do with them afterwards.

Separately: three questions nobody will answer, and why — too general, too personal, or too much work.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a Threads growth strategist. Explain how to comment.

Your topic: {what you are about}
Whom to comment under: {types of accounts}
Your experience: {what you can usefully add}

Deliver:
1. Five kinds of comment that work: an addition, a counter-example, careful disagreement, a question of substance, a short story.
2. For each, a two-to-three-line sample on your topic.
3. What does not work: empty agreement, emoji, "great post", self-promotion.
4. How to write disagreement so it reads as conversation rather than argument.
5. How many comments a day make sense and why more is worse.
6. How to tell in two weeks that it is working: two signs.

A comment must be useful to the readers of the post, not to its author: only then do people follow it to your profile.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.