Free prompt library

Free AI prompt templates you can copy right now

Seventeen engineered prompts for ChatGPT, Claude, Gemini, AI images and AI video. Fill in the brackets, paste them in, and you will get output that is specific to your business instead of generic. No email required.

Why these work

Role

Tell the AI who to be so it uses the right standards.

Context

Your business, audience and what already failed.

Goal

The outcome you want, not just the task.

Constraints

Length, tone, banned words, facts it may not invent.

Format

Exactly how the answer should come back.

Missing info

Ask it what it still needs before it writes.

Marketing prompts

Power prompt

Turn One Offer Into a Landing Page That Answers the Real Objection

Diagnose the buying decision first, then write the page around it.

You are a direct-response conversion strategist and copywriter. You will work in five stages and show your work at each stage. Do not skip ahead.

MY INPUTS
Offer: [YOUR OFFER — what it is and what it does]
Price and billing: [PRICE]
Target audience: [TARGET AUDIENCE — who they are, what they already tried]
Their main problem, in their words: [MAIN PROBLEM]
Biggest reason they hesitate: [MAIN OBJECTION]
Proof I can honestly use: [AVAILABLE PROOF — results, reviews, numbers, credentials]
Audience awareness level: [unaware / problem-aware / solution-aware / product-aware / most-aware]
Brand voice: [BRAND VOICE — or write "neutral and plain"]
Primary goal of the page: [DESIRED OUTCOME — purchase, book a call, start trial]

STAGE 1 — DIAGNOSE
Before writing anything, list:
1. The single belief the reader must accept before they will buy.
2. What they currently believe instead.
3. The three strongest competing options in their head, including "do nothing."
4. What my proof actually supports, and what it does not.
If any critical information is missing, ask me at most 5 short questions and stop. Do not guess business facts.

STAGE 2 — STRATEGIZE
Choose and justify in 3 sentences: the page's core angle, the order of arguments, and where the objection gets handled.

STAGE 3 — WRITE
Write the page in this order:
- 5 headline options, each testing a different angle (outcome, objection, mechanism, identity, cost of inaction)
- Subheadline
- Opening section that states the problem in the reader's language
- How it works, in exactly 3 steps
- 5 benefit bullets, each tied to a specific outcome rather than a feature
- Objection section that names the hesitation out loud and answers it
- Proof section using only the proof I supplied
- FAQ, 5 questions, the ones a hesitant buyer asks right before paying
- Final call to action matching my stated goal

STAGE 4 — CRITIQUE
Review your own draft against these checks and answer each honestly:
- Could this copy be pasted onto a competitor's site unchanged? Mark every sentence that could.
- Did you invent any statistic, testimonial, result, guarantee or feature I did not supply?
- Is the main objection actually answered, or just acknowledged?
- Does every benefit connect to something this audience said they want?
- Does the CTA match the stated goal and the awareness level?

STAGE 5 — REFINE
Rewrite only the weak parts you identified. Deliver the final page cleanly, with no commentary.

RULES THROUGHOUT
- Never invent proof. If a claim needs evidence I did not give you, write [PROOF NEEDED] in its place.
- Write in plain, specific language. Avoid "unlock", "game-changing", "revolutionary", "supercharge", "elevate", "take it to the next level", "in today's fast-paced world".
- No manufactured urgency or scarcity unless I supplied a real deadline or limit.

Engineered

A 5-Email Welcome Sequence Built Around One Buying Decision

Move a new subscriber from curious to ready, without sounding automated.

Act as a lifecycle email strategist who writes the emails as well as plans them.

CONTEXT
Business: [WHAT YOU DO]
Offer I want them to buy eventually: [YOUR OFFER] at [PRICE]
Where the subscriber came from: [LEAD MAGNET / AD / REFERRAL]
What they were promised when they subscribed: [THE PROMISE]
Target audience: [TARGET AUDIENCE]
Their biggest objection: [MAIN OBJECTION]
Proof I can honestly use: [AVAILABLE PROOF]
Brand voice: [BRAND VOICE]

SEQUENCE LOGIC
Each email must do one job and set up the next. Assign the jobs in this order:
1. Deliver what they signed up for and set the expectation for what comes next.
2. Show you understand their situation better than they expected — one specific insight, not a life story.
3. Teach one thing they can use today that quietly proves the method works.
4. Handle the objection directly, by name.
5. Make the offer with a real reason to act now, drawn only from facts I supplied.

FOR EACH EMAIL RETURN
- Send day
- The job this email does
- 3 subject lines, under 45 characters, no clickbait, no false personalization
- Preview text that adds information instead of repeating the subject
- Body under 200 words, short paragraphs, written to one person
- One call to action

CONSTRAINTS
- Never invent results, testimonials or statistics. Use [PROOF NEEDED] where evidence is required and missing.
- No fake deadlines. If I gave no real deadline, use a genuine reason (next cohort, price change I stated, seasonal relevance) or make the CTA low-friction instead.
- Avoid: "unlock", "game-changing", "supercharge", "elevate", "in today's fast-paced world".

BEFORE YOU WRITE
If anything critical is missing, ask me up to 4 questions and wait. Otherwise proceed.

AFTER YOU WRITE
List any email that would still read the same if a different business sent it, and rewrite that one.

Power prompt

Extract Your Brand Voice From Your Own Writing, Then Reuse It

Get a voice instruction block that makes every future output sound like you.

You are a linguist and brand voice analyst. Analyze observable patterns in my writing. Do not describe my voice with adjectives until you have evidence for each one.

MY SAMPLES
[PASTE WRITING SAMPLES — 3 to 5 pieces I actually wrote, not edited by anyone else]

STAGE 1 — MEASURE
Report, with a short quoted example for each:
- Average sentence length and how much it varies
- Paragraph length and rhythm (do I stack short lines, or build long ones?)
- Vocabulary level and any specialist or regional words
- Formality level and where it shifts
- Humor: present or not, and what type (dry, self-deprecating, absurd, none)
- Emotional intensity and where I raise or lower it
- How I open a piece — pattern across all samples
- How I close — pattern across all samples
- Transitions I actually use between ideas
- Punctuation habits, including dashes, ellipses, parentheses, sentence fragments
- Phrases and constructions I repeat
- Persuasion style: evidence, story, direct assertion, questions, contrast
- Point of view and how often I address the reader directly

STAGE 2 — INFER
Only now, name 5 adjectives for my voice. Each must cite a specific pattern from Stage 1 as evidence. Discard any adjective you cannot evidence.

STAGE 3 — DEFINE THE EDGES
List what my voice never does — words, structures, tones absent from every sample. This is what stops future output sounding like generic AI.

STAGE 4 — BUILD THE INSTRUCTION
Write a reusable "write in this voice" block under 200 words that I can paste at the top of any future prompt. It must contain concrete rules (sentence length targets, punctuation, opener style, banned constructions), not adjectives.

STAGE 5 — PROVE IT
Rewrite this sentence in my voice: "We help businesses improve their marketing results." Then explain which of my patterns you applied.

If my samples are too short or too inconsistent to support this analysis, say so directly and tell me what to send instead.

Engineered

Build a Buyer Profile From Real Customer Evidence

Turn reviews, comments and call notes into a usable messaging profile.

You are a customer research analyst. Build a buyer profile using only the evidence I supply. Do not invent a persona.

EVIDENCE
[PASTE RAW MATERIAL — reviews, support tickets, survey answers, DMs, comments, sales call notes. Messy is fine.]
What I sell: [YOUR OFFER] at [PRICE]

METHOD
1. Extract the recurring language. List the exact phrases customers use for their problem, their goal, and their frustration — verbatim, with how many times each theme appears.
2. Separate what they SAY they want from what their behavior suggests they want. Flag any gap.
3. Identify the trigger event that made them start looking for a solution.
4. Identify what they tried before and why it failed them, in their words.
5. List objections and hesitations that appear in the evidence, ranked by frequency.
6. Note who else is involved in the decision, if the evidence shows it.

OUTPUT
- Profile summary in 150 words, written as one specific person, not a demographic
- Their problem in their own words, top 5 verbatim phrases
- Desired outcome, top 5 verbatim phrases
- Trigger events
- Failed alternatives and why
- Objections, ranked
- Words and phrases to use in my copy, taken straight from the evidence
- Words and phrases to avoid, because customers never use them or react badly to them
- The three strongest messaging angles this evidence supports, and one angle the evidence does NOT support even though I might assume it

RULES
- Every claim must trace to something in the evidence. Mark anything you inferred as [INFERRED] and say what it is based on.
- If the evidence is too thin for a section, write [INSUFFICIENT EVIDENCE] and tell me what to collect.
- Do not fill gaps with typical industry assumptions.

Sales prompts

Sharp

Cold Email That Earns a Reply From One Specific Person

Write to a real prospect using a real observation, not a merge field.

Write a cold email to one specific person.

Who I am: [YOU AND YOUR BUSINESS]
Who I'm writing to: [NAME, ROLE, COMPANY, INDUSTRY]
Specific, real thing I noticed about them or their business: [PASTE THE DETAIL]
The outcome I can create for them: [DESIRED OUTCOME — result, not service]
Proof I can honestly reference: [AVAILABLE PROOF, or "none yet"]
The ask: [ONE SMALL NEXT STEP]

Rules:
- Under 120 words. One idea per sentence. One ask only.
- Open with the observation, not with me and not with flattery. No "I hope this finds you well."
- Say the outcome in their terms, not the deliverable in mine.
- If I gave no proof, do not imply any. Never invent clients, numbers or results.
- The ask should be easy to say yes to and easy to say no to.

Give me 3 versions using different angles: the observation angle, the problem-cost angle, and the specific-idea angle. Each with 3 subject lines under 45 characters that read like a human wrote them.

Then tell me which version you'd send and why, in one sentence.

Engineered

Objection Responses You Can Actually Say Out Loud

Answer price, timing and trust without pressure or scripts that sound canned.

You are a sales coach who trains consultative sellers, not closers.

CONTEXT
Offer: [YOUR OFFER] at [PRICE]
Buyer: [TARGET AUDIENCE]
What they are comparing me to: [ALTERNATIVES, including doing nothing]
Objections in their exact words: [PASTE THE OBJECTIONS]
Proof I can honestly use: [AVAILABLE PROOF]
What my offer genuinely cannot do: [LIMITATIONS]

FOR EACH OBJECTION RETURN
1. What they most likely mean underneath it (state your reasoning in one line).
2. A one-sentence acknowledgement that does not sound rehearsed.
3. A reframe grounded in a fact, a limitation or a result I actually supplied.
4. One question that moves the conversation forward without cornering them.
5. The version to use when the objection is genuine and I should let them go.

RULES
- Every response under 60 words and speakable. Read it back to yourself; if it sounds like a script, rewrite it.
- Never invent numbers, guarantees or client results. Use [PROOF NEEDED] when evidence is required.
- No pressure tactics, false scarcity, or "what would it take to get you started today".
- If an objection is legitimate given my stated limitations, say so and give me the honest response.

End with the one objection I am most likely handling badly, based on how I phrased it, and what that reveals.

Engineered

Pressure-Test an Offer and Its Price Before You Launch It

Get a real strategic read on the offer, not encouragement.

You are a strategy advisor. Your job is to find the weaknesses, not to validate the idea. Be direct.

THE SITUATION
Business model: [HOW YOU MAKE MONEY]
Current stage: [REVENUE, CUSTOMERS, HOW LONG RUNNING]
The offer: [YOUR OFFER — what's included, how it's delivered]
Proposed price: [PRICE] billed [FREQUENCY]
Target audience: [TARGET AUDIENCE]
What they use instead today: [ALTERNATIVES, including doing nothing]
My resources: [TIME, MONEY, TEAM, AUDIENCE SIZE]
Constraints I cannot change: [CONSTRAINTS]
What success looks like in 90 days: [DESIRED OUTCOME]

ANALYSIS
1. State the offer back to me in one sentence a buyer would recognize. If you cannot, the offer is unclear — say so and stop there.
2. Value logic: what measurable outcome justifies [PRICE], and does the buyer believe it before purchase or only after?
3. Pricing read: is this priced by cost, by competitor, or by value? Give the strongest argument for pricing higher and for pricing lower, then commit to a recommendation.
4. Demand risk: name the assumption this offer depends on most, and the cheapest way to test it in the next 14 days.
5. Delivery risk: what breaks if 50 people buy at once, given my stated resources?
6. Two credible alternative structures for the same offer, with the trade-off of each.
7. Decision criteria: the 3 numbers or signals I should use to decide go / adjust / kill, with thresholds.

RULES
- No generic advice. Every point must reference something I told you.
- Do not invent market data, competitor pricing or industry benchmarks. Where you would need data, write [DATA NEEDED] and say what to look up.
- If my inputs are contradictory, name the contradiction rather than working around it.

Ask up to 4 questions first if a critical input is missing. Otherwise proceed.

Content prompts

Engineered

30 Days of Content Built Around One Business Goal

A month of posts that ladder to a single outcome instead of random ideas.

You are a content strategist who plans for a specific business result, not for posting volume.

CONTEXT
Platform: [PLATFORM — Instagram, TikTok, LinkedIn, YouTube, email]
Business: [WHAT YOU SELL]
Target audience: [TARGET AUDIENCE]
The one goal for this month: [PRIMARY GOAL — e.g. 200 email signups, 30 sales calls, launch a product]
Content pillars: [3-5 THEMES]
Posting frequency: [POSTS PER WEEK]
Brand voice: [BRAND VOICE]
What I will NOT talk about: [OFF-LIMITS TOPICS]

PLANNING RULES
- Split the month into four weeks with a stated purpose each: attract, build trust, handle objections, convert. Weight the posts accordingly, most attract early and most convert late.
- Every post must map to one pillar and one funnel stage.
- Vary hook style: no hook style used more than twice in the entire month. Name the style you used.
- No topic repeats. If two ideas overlap, replace one.
- Match the platform: hook length, format, caption length and CTA should be what actually works on [PLATFORM], not a generic social post.

OUTPUT
A table with: day, week purpose, pillar, funnel stage, format, hook (the literal first line), core idea in two sentences, CTA, hook style used.
Below the table, list the 5 posts most likely to drive the stated goal and one sentence on why.

CONSTRAINTS
- No "post consistently" or "know your audience" advice. Every row must be a specific post I could film or write today.
- Do not invent statistics, client results or trends. If a post needs data, write [PROOF NEEDED].
- Avoid hype language: "game-changing", "unlock", "elevate", "next level".

If the goal or audience is too vague to plan against, ask me up to 3 questions first.

Engineered

An Article Outline Built From Search Intent, Not a Topic Guess

Plan a piece that matches what the searcher actually wanted to find.

Act as an SEO content strategist who has read the SERP before writing an outline.

INPUTS
Primary keyword: [KEYWORD]
Who is searching and what they already know: [TARGET AUDIENCE]
What we sell and how it honestly fits the topic: [YOUR OFFER]
Anything I already know ranks for this: [PASTE COMPETING TITLES, or write "unknown"]

STEP 1 — INTENT
State the dominant search intent (informational, comparison, transactional, navigational) and the specific question the searcher is really asking. Then state what the article must deliver for the reader to stop searching.

STEP 2 — OUTLINE
Return:
- 5 title options under 60 characters, each with the keyword placed naturally
- Meta description under 155 characters, written to earn the click, not to stuff keywords
- H2 and H3 structure, with one line under each heading describing exactly what it covers
- A 40-60 word direct answer to the main question, written for a featured snippet, placed near the top
- 5 related terms to work in naturally, with the heading each belongs under
- 5 questions to answer for AI answer engines, phrased as real user questions
- The one place a CTA belongs, and why there

CONSTRAINTS
- No filler sections. If a heading exists only to hit a word count, cut it.
- Do not invent statistics or studies. Where the article needs data, write [SOURCE NEEDED] and say what kind of source would qualify.
- The product mention must be honest. If our offer does not genuinely fit, say so instead of forcing it.

Finish by naming the weakest section of the outline and what would make it stronger.

Power prompt

Diagnose Why a Prompt Keeps Producing Generic Output

Find the actual failure in your prompt, then get a rebuilt version.

You are a prompt engineer performing a diagnosis. Work in stages and do not rewrite anything until stage 3.

MY MATERIALS
The prompt I used: [PASTE CURRENT PROMPT]
What it produced: [PASTE OUTPUT, or describe it]
What I actually wanted: [DESIRED OUTCOME]
The tool I'm using: [CHATGPT / CLAUDE / GEMINI / OTHER]

STAGE 1 — DIAGNOSE
Categorize every problem you find into:
- Missing context the model could not have known
- Ambiguity, where two readings are both valid
- Internal conflict, where two instructions fight each other
- Unstated success criteria, where I never said what good looks like
- Wrong format specification, or none at all
- Over-constraint, where I strangled the useful output
Quote the exact fragment causing each problem. If the output was generic, name the specific missing input that caused it — do not answer "add more detail".

STAGE 2 — EXPLAIN
In 3 sentences, state the single root cause. Most weak prompts have one, not six.

STAGE 3 — REBUILD
Rewrite the prompt. Include only the components this task actually needs — role, context, audience, goal, inputs, constraints, output format, missing-information handling, quality check. Justify in one line why you included or excluded each. Do not pad it into a giant template.

STAGE 4 — TEST
Run the rebuilt prompt mentally and show a short sample of the output it would now produce. If the sample is still generic, fix the prompt again and say what you changed.

STAGE 5 — HAND OFF
Give me:
1. The final prompt, clean and copy-ready.
2. The 3 questions you would still need answered to make it materially better.
3. One reusable lesson about my prompting habits, based on what you found.

Operations prompts

Engineered

Turn Messy Notes Into an SOP Someone Else Can Run

Document a process so a new person completes it correctly the first time.

Convert my notes into a standard operating procedure written for someone doing this for the first time.

Process name: [NAME]
Who performs it: [ROLE and experience level]
How often: [FREQUENCY]
Tools and access required: [TOOLS]
What "done correctly" looks like: [DESIRED OUTCOME]
My messy notes: [PASTE EVERYTHING — out of order is fine]

Return in this structure:
1. Purpose — why this process exists and what breaks if it is skipped
2. Trigger — the exact event that starts it
3. Prerequisites — access, files, approvals needed before step 1
4. Steps — numbered, each written as a command starting with a verb, one action per step
5. Decision points — "if X, do this; if Y, do that", pulled from my notes
6. Quality check — what to verify before marking it complete
7. Common mistakes and how to catch them
8. Escalation — when to stop and ask a human, and who

RULES
- Use only what is in my notes. Do not invent steps, tools, timings or approvals.
- Where my notes are ambiguous or a step is clearly missing, insert [GAP: what you need from me] inline rather than filling it in.
- No corporate padding. If a section adds nothing for this process, write "not applicable" and move on.

Before you write, list up to 5 gaps that would most affect whether a new person could actually complete this, then write the SOP with those marked.

Sharp

Pull Decisions, Owners and Deadlines Out of a Messy Transcript

Get an accountable action list from an hour of conversation.

Read the transcript below and extract only what changes what happens next.

Transcript: [PASTE TRANSCRIPT]

Return four sections:
1. Decisions made — what was decided and by whom. Only include things actually settled, not things discussed.
2. Open questions — the question, who needs to answer it, and what is blocked until they do.
3. Action items — action, owner, due date. One line each.
4. Risks and disagreements — anything raised and left unresolved, including who disagreed.

Rules:
- Quote or closely paraphrase the transcript. Do not infer intent, add tasks nobody mentioned, or smooth over conflict.
- If an owner or date was never stated, write "unassigned" or "no date". Never guess.
- Keep every line under 20 words.
- If something was said ambiguously and it matters, list it under a final "Needs confirmation" heading with the exact quote.

Engineered

Run a Research Brief Without Getting Confident Nonsense

Separate verified facts from inference before you make a decision on them.

Act as a research analyst. Accuracy matters more than completeness here.

RESEARCH QUESTION
[YOUR QUESTION — as specific as you can make it]
Why I need it / the decision it feeds: [DESIRED OUTCOME]
Scope: [GEOGRAPHY, INDUSTRY, TIME PERIOD]
How current it must be: [RECENCY REQUIREMENT]
Tool: [CHATGPT / CLAUDE / GEMINI / PERPLEXITY — note whether browsing is enabled]

METHOD
1. Restate the question and state explicitly what would count as a good answer.
2. Answer in three clearly separated tiers:
   TIER A — Verified: things you can cite to a source. Include the source and date. If browsing is not available to you, say so and put nothing in this tier that you cannot attribute confidently.
   TIER B — Reasoned inference: your conclusions and the reasoning chain behind each.
   TIER C — Unknown: what would change the answer but you cannot determine.
3. Where sources disagree, present both positions and say what the disagreement hinges on.
4. Rate your confidence per tier-A claim as high, medium or low, and say why.

HARD RULES
- Never fabricate a source, statistic, study, URL, quote or date. If you cannot verify it, it belongs in Tier B or C.
- Do not present a recalled figure as a current one. Flag anything whose value changes over time.
- Do not smooth over uncertainty to sound helpful.

CLOSE WITH
- The three things I should verify myself before acting, and where to look.
- The single assumption in this brief that, if wrong, would most change the decision.

Customer service prompts

Sharp

Rewrite a Support Reply So the Customer Feels Handled, Not Managed

Answer an unhappy customer clearly, without corporate hedging or grovelling.

Rewrite this customer support reply.

Customer's message: [PASTE MESSAGE]
What actually happened, internally: [THE FACTS]
What we can offer: [REFUND / FIX / WORKAROUND / NOTHING]
What we cannot do: [LIMITS]
Timeline I can honestly promise: [TIMELINE]
Brand voice: [BRAND VOICE — or "warm, direct, not corporate"]

Rules:
- First sentence names their specific problem, not a generic apology.
- State plainly what we can and cannot do. No hedging, no passive voice hiding who did what.
- Give the exact next step and who does it.
- Never promise anything outside what I listed. Never invent a cause, a compensation or a timeline.
- Do not write "we apologize for any inconvenience" or "we value your feedback".
- Under 150 words.

Give me two versions: one standard, one for a customer who is genuinely angry — the angry version should be shorter and more concrete, not more apologetic.

Then flag anything in my facts that the customer will notice we avoided saying.

Sharp

Build an FAQ From the Questions That Actually Block the Sale

Turn repeat questions into a page that removes hesitation before checkout.

Build an FAQ section for a buyer who is one click from paying and looking for a reason not to.

Product: [YOUR OFFER] at [PRICE]
Questions people actually ask: [PASTE THEM RAW]
Refund and cancellation policy, exactly: [THE REAL POLICY]
What the product genuinely does not do: [LIMITATIONS]

For each question:
- Keep the customer's own wording in the question.
- Lead with the direct answer in the first sentence, then explain.
- Under 70 words.
- Never soften a limitation into a benefit. If the answer is no, say no and say what we do instead.
- Use only my stated policy. Do not invent guarantees, timelines or features.

Then add up to 5 questions I did not include that a hesitant buyer would ask before paying — sort them by how likely they are to stop a purchase, and mark any that I need to answer with real information by writing [I NEED YOUR ANSWER].

Creative prompts

Engineered

Turn a Product Idea Into a Production-Ready AI Image Brief

Get the shot you pictured instead of generic stock-looking output.

You are an art director writing a prompt for an AI image generator. Write creative direction, not adjective piles.

BRIEF
Subject: [WHAT OR WHO — describe physically, including anything that must stay consistent]
Action or pose: [WHAT IT IS DOING]
Setting: [WHERE]
Intended use: [AD / THUMBNAIL / HERO IMAGE / PRODUCT SHOT / PACKAGING]
Mood: [FEELING]
Brand colors: [COLORS]
Aspect ratio: [ASPECT RATIO]
Realism level: [PHOTOREAL / STYLIZED / ILLUSTRATION]

Write ONE flowing paragraph prompt that specifies, in this order: subject and physical detail, action, environment and background depth, composition and framing, camera angle and height, lens feel and depth of field, lighting setup including direction and quality, color palette, materials and surface texture, atmosphere, and realism level.

Rules for the prompt you write:
- Concrete visual nouns over vague praise. Do not use "beautiful", "stunning", "cinematic", "amazing", "ultra-premium", "masterpiece", "8k" as substitutes for actual direction.
- Describe light physically: where it comes from, how hard or soft, what it does to the shadows.
- Leave clear negative space if the intended use needs room for text, and say where.
- If the image should contain no text or logos, state that explicitly.

Then return:
1. A negative prompt listing what to exclude, specific to this subject and setting.
2. Two variations: one more editorial, one more documentary/photographic — changing lighting and framing, not just adjectives.
3. The one element most likely to render wrong, and how to reword it if it does.

Engineered

Direct an AI Video Shot by Shot, With Continuity That Holds

Control pacing, camera and character consistency instead of hoping.

You are directing an AI video generator. Write shot-level direction with continuity locked.

BRIEF
Concept: [WHAT HAPPENS]
Total length: [SECONDS]
Aspect ratio: [ASPECT RATIO]
Where it will be seen: [PLATFORM]
Mood and pace: [DESCRIBE]
Subject: [DESCRIBE — appearance, clothing, anything that must not change between shots]
Style: [PHOTOREAL / ANIMATED / STYLIZED]

FIRST, write a continuity block: a fixed 25-40 word description of the subject and the lighting world, worded identically for reuse in every shot. Do not vary it.

THEN, break the video into shots that add up to the stated length. For each shot give:
- Timestamp range
- Opening frame, described as a still
- Subject action within the shot
- Camera movement (static, push in, pull out, pan, orbit, handheld) and speed
- Framing (wide, medium, close, macro) and angle
- Lighting and environmental motion (wind, dust, steam, traffic)
- Ending frame, described as a still, and how it hands off to the next shot

Each shot must be written as one continuous prompt paragraph the tool can read, with the continuity block included verbatim.

FINALLY return:
1. Text overlay direction, or state clearly that no text should be generated in-frame.
2. A negative list for artifacts likely in this specific concept (warped hands, drifting faces, flickering text, morphing objects, extra limbs).
3. The riskiest shot for continuity, and a simpler alternative version of it.

Do not invent brand names, logos, real people or recognizable trademarks unless I supplied them.

Templates only get you so far

A template does not know your business. The Prompt Engineer asks you the questions these brackets cannot — then writes the prompt around your actual goal, audience and tone. $19/month, cancel anytime.