Gamma AI Prompts: 22 Presentation Prompt Templates by Deck Job

TL;DR: Gamma AI prompts fail when they name a topic and nothing else, because a deck generator is a structure generator. Gamma documents the controls that matter — slide count, split, text density, tone, audience — and this page maps them onto 22 copy-paste prompt templates organised by the job the deck has to do.

Why do generic Gamma prompts produce generic decks?

Because everything your prompt leaves open, Gamma decides. Ask for "a deck about our Q3 results" and something still has to choose how many slides there are, what the opening slide argues, whether slide four is a chart or a list, and who the thing is pitched at. Those decisions get made either way. The only question is whether you made them.

That is the structural difference between prompting a chat model and prompting a deck generator. A chat prompt asks for text, and you edit the text. A Gamma prompt asks for an artefact with a fixed shape: a sequence of slides, each carrying one idea, arranged into an argument. The narrative arc is not decoration on top of the content. It is the content, and if the prompt does not carry it, the generator supplies a default arc: the flat one where every slide is an equally weighted section heading.

You can watch this happen. Gamma's slide-count control defaults to 10 in the API, so a bare topic prompt reliably produces a ten-slide deck whether the idea needs four slides or twenty-two. That is not a flaw. It is a default filling a gap you left.

The fix is not longer prompts or better adjectives. It is deciding the structure first and writing it down. Everything below is a way of doing that quickly.

What does a Gamma prompt actually control?

More than the UI makes obvious, and Gamma publishes the full list. The clearest inventory sits in the API documentation at developers.gamma.app, where every knob has a name, a type and a default. Read on 27 August 2026, these are the generation parameters.

That table is the anatomy of a good deck prompt, whether or not you ever touch the API. In the UI those decisions live in the advanced options and the prompt box; either way, an unset one becomes a default. Two are worth understanding properly, because they decide who owns the output.

textMode decides who owns the words. Gamma documents generate as working best "when you have brief text in the input that you want to elaborate on" and condense as best "when you start with a large amount of text that you'd like to summarize". The third option, preserve, keeps your text as written. If you have already drafted the content, generate will rewrite your sentences.

cardSplit decides who owns the boundaries. Left on auto, Gamma divides your content to hit the slide count. Set to break on your own markers, it splits exactly where you put a --- line and ignores the count. That is the difference between asking for twelve slides and specifying twelve.

What did Gamma rename, and why does older advice break?

Three renames explain most of the stale advice you will find. Gamma calls its current generation "Gamma 3.0", and the Help Center is explicit that Agent is not the old Chat with AI feature relabelled: "No, Agent is a completely new AI collaborator."

The bigger one for prompt writers is the vocabulary. Cards are now slides. The Help Center uses that word throughout, while the developer API still names the same object numCards, cardSplit and per-card analytics. Gamma's own pages slip: the slides article, mid-answer, warns that Agent "can sometimes misinterpret the instruction and update or overwrite the existing card". A tutorial talking about cards is older, not wrong.

The third is the mode list, where two Gamma pages published on the same day disagree outright. The creation article states that "Gamma provides three different modes to help users create visually appealing and structured content" and lists Generate, Paste and Import. The Create with Agent article, dated identically, says Agent "sits alongside Generate, Paste in text, Create from template, and Import file or URL as another mode of creation", which makes five counting itself. Both were read on 27 August 2026. Take the second as the fuller list and expect the count to move again.

Create with Agent changes the workflow rather than the wording: instead of one prompt producing a deck, you chat, hand it sources, and approve an outline before anything is built. It adds four steerable deck styles, minimal, visual, classic and consultant, and Gamma notes that "Each style affects both layout and writing voice, so the same outline will feel meaningfully different across them." It is documented as available on Plus, Pro, Ultra and Teams plans, and not on Free.

What shape should a Gamma deck prompt be?

Six slots, in this order. The controls above are Gamma's; the arrangement is ours, built from watching which omissions cost the most.

1. Job and artefact. What this deck is for and what kind of thing it is. "A 12-slide investor update", not "a presentation".
2. Audience. Who is in the room, and what they already know. This is the slot people skip, and it changes every sentence.
3. The arc. The slide list, numbered, one line each. This is the whole game.
4. Density. Brief, medium, detailed or extensive, plus any hard rule like "headline plus three lines maximum".
5. Tone. Two or three words. More than that and they start contradicting each other.
6. Constraints. What not to do: no invented figures, no stock-photo people, visible placeholders where data is missing.

Gamma's published prompt library at gamma.app/prompts uses a compressed version of the same shape: a verb, an artefact, an audience, then a colon and a comma-separated list of sections. One of its sales examples, reproduced exactly as published:

Create a proposal handling the "we need to think about it" objection: summarize what they said matters most, show how you solve those specific problems, include a limited-time implementation discount

The list after the colon is the arc, and the number of items in it is effectively the slide count. Gamma's education examples routinely run to eight or ten sections, roughly where the generator's default of ten slides sits anyway. The templates below expand that pattern rather than replacing it.

22 Gamma prompt templates by deck job

Organised by what the deck has to do, because that determines the arc. Replace the bracketed slots and delete any line you do not need. The templates are ours; the controls are Gamma's.

Pitch and fundraising decks

Create a [seed / Series A] fundraising deck for [company], which [one-line description], for an audience of [investor type] who see 30 decks a week.

12 slides, in this order:
1. The problem, told through one named customer and what it costs them
2. Why the obvious fix has not worked
3. What we built, in one sentence, and what it replaces
4. How it works, in three steps
5. Traction: [paste your figures here]
6. Business model and unit economics
7. Market, sized bottom-up from customers and price, not top-down
8. Competition, named, and the specific wedge we have
9. Go-to-market for the next 12 months
10. Team, and why this team
11. The ask and use of funds
12. Contact

Text: brief. Headline plus at most three supporting lines per slide.
Tone: direct, numerate, no hype.
Do not invent any number. Where I have not given a figure, write a visible placeholder.

Rewrite this pitch as a single argument rather than a list of sections.

Thesis: [the one sentence an investor should repeat to a partner].
Each slide must advance that thesis or be cut.
Source material: [paste your existing outline or deck text].

10 slides. Preserve my figures exactly as written; you may restructure everything else.
Tell me at the end which slides you cut and why.

Build a 5-slide follow-up deck answering the three objections we heard in the first meeting: [objection 1], [objection 2], [objection 3].

Slide 1: what we heard, restated in their words
Slides 2-4: one objection each, with evidence, not reassurance
Slide 5: what we are asking for next

Audience: [investor name and firm], who is [what they care about].
Tone: calm, specific. Text: brief.

Internal updates

Create a [weekly / monthly] internal update deck for [team or company].

8 slides:
1. The one thing that changed this period
2. Metrics against target: [paste figures]
3. What shipped
4. What slipped, and the new date
5. What we learned that changes the plan
6. Blockers, with the named owner and the decision needed
7. Next period's three priorities
8. Questions for this room

Audience: [who reads this], who did not attend the meetings behind it.
Text: brief. Tone: plain, unpolished, no celebration language.
Preserve every figure I gave you exactly. Do not add commentary to numbers.

Turn these raw notes into a status update deck without adding anything I did not say.

[paste notes]

Split into slides at each --- break I have inserted. Do not merge or resequence them.
Keep my wording. Add only headings and structure.
Tone: neutral. No images.

Create a 6-slide decision memo deck for [decision to be made].

1. The decision, stated as a question with a deadline
2. Why it matters now
3. Option A: what it is, cost, risk
4. Option B: what it is, cost, risk
5. Recommendation and the reasoning behind it
6. What we need from this group today

Audience: [decision makers], who have 10 minutes.
Text: brief. Tone: even-handed until slide 5, then committed.

Quarterly business reviews

Build a QBR deck for [customer or account] covering [quarter].

11 slides:
1. Where we were at the start of the quarter
2. Goals we agreed, restated verbatim
3. Results against each goal: [paste the figures]
4. Usage and adoption trend
5. Wins, with the person who made them happen named
6. What did not work, stated plainly
7. Open issues and their status
8. What changed on our side this quarter
9. Their roadmap needs for next quarter
10. Our proposed plan and owners
11. Decisions we need today

Audience: [customer's exec sponsor plus day-to-day team].
Text: medium. Tone: candid, partner-not-vendor.
Use my numbers exactly as written. Do not calculate anything.

Create the internal-only version of this QBR: same quarter, same account, but written for our own leadership.

Add: renewal risk with a reason, expansion opportunity with a size, the account's true health in one word, and what we need internally to keep it.
Remove: anything written to reassure the customer.

7 slides. Text: brief. Tone: honest, including where we underperformed.

Training and workshop decks

Create a training deck teaching [skill] to [audience and their current level].

Structure it around one thing they will be able to do at the end: [the capability].

14 slides:
1. What you will be able to do by the end
2. Why the current way breaks
3. The core idea in one diagram-friendly explanation
4-6. The three steps, one per slide, each with a worked example
7. A common mistake, and what it looks like
8. A second common mistake
9. Practice exercise 1, with the answer hidden on the next slide
10. Answer and explanation
11. Practice exercise 2
12. Answer and explanation
13. When this technique does not apply
14. Where to go next

Text: detailed. Tone: patient, concrete, second person.
Every abstract point must be followed by an example.

Take this documentation and turn it into a workshop deck without losing accuracy.

[paste the documentation]

Condense to 10 slides. Keep every technical term exactly as written in the source.
Where the source is ambiguous, say so on the slide rather than resolving it.
Audience: [role], who has never used [the tool].

Create a 6-slide facilitator guide to accompany a workshop on [topic].

1. Timing plan, minute by minute, for a [duration] session
2. What to say in the first two minutes
3. The three questions to ask the room, and what good answers sound like
4. Where people usually get stuck, and the unsticking prompt
5. How to run the exercise, including group size and materials
6. How to close and what to send afterwards

Audience: a colleague delivering this for the first time.
Text: detailed. Tone: practical, instructional.

Sales one-pagers and leave-behinds

Create a one-page leave-behind for [product] aimed at [buyer role] at [company type].

Format: a single page, not a slide deck.

Sections in order:
- The problem in their words, one sentence
- What we do, one sentence, no jargon
- Three outcomes with numbers: [paste the figures]
- How it works, three steps
- Proof: [customer names or results you are allowed to use]
- What happens next, with a specific action and timeframe

Text: brief. Tone: confident, plain, zero adjectives that cannot be measured.
Nothing on this page should require me to be present to explain it.

Create a 4-slide pricing and packaging explainer for a prospect who asked how we compare on cost.

1. What they are paying for today, including the hidden costs
2. What our pricing is based on, and why
3. A worked example at their size: [paste their numbers]
4. The three questions to ask any vendor in this category

Audience: [role], who is presenting this internally to someone more sceptical.
Text: medium. Tone: unspun. Do not disparage any named competitor.

Build a 5-slide objection-handling one-pager for the objection: [the exact wording they used].

1. Restate the objection more precisely than they did
2. What is genuinely true about it
3. What the evidence actually shows: [paste your evidence]
4. What we would do if it turned out to be a problem
5. The smallest next step that tests it

Text: brief. Tone: calm, non-defensive.

Conference talks

Create a conference talk deck for a [duration] slot at [event] on [topic].

Audience: [who attends], who will have seen [the obvious version of this talk] before.

Structure as a talk, not a document:
1. A cold open: one specific moment, no agenda slide
2. The claim I am making, stated once, plainly
3-5. Three pieces of evidence, one per slide, each concrete
6. The strongest objection, given honestly
7. Why the claim survives it
8. What to do differently on Monday
9. The one sentence I want repeated in the hallway

Text: extensive in the speaker notes, near-empty on the slides.
Each slide: a maximum of eight words plus one visual idea.
Tone: [two words].

Turn this talk outline into speaker notes I can rehearse from.

[paste outline]

Preserve my slide order exactly. For each slide write: the opening sentence verbatim,
three bullets I can improvise around, the transition line into the next slide,
and a timing target in seconds. Total target: [duration].

Create a 3-slide lightning version of this talk for a [5-minute] slot.

Source: [paste the full outline].
Keep only the claim, the single strongest piece of evidence, and the action.
Text: brief. Every slide must work with the sound off.

Research summaries

Summarise this research into a deck for [audience] who need to make a decision, not learn the field.

[paste the source material]

9 slides:
1. The question we were trying to answer
2. What we did, in two sentences, including sample size and dates
3. The headline finding, with the number
4-6. Three supporting findings, one per slide, each with its evidence
7. What we did not find, and what stayed inconclusive
8. Limitations, stated without hedging
9. The decision this supports, and the confidence level

Condense my source text rather than rewriting it. Keep every figure exactly as given.
Text: medium. Tone: neutral, non-promotional.
Do not smooth over contradictions in the source. Show them.

Create a 7-slide literature summary comparing [n] sources on [question].

For each source: what it claims, the method, the sample, and the year.
Then one slide showing where the sources agree and one showing where they conflict.
Final slide: what a reader should conclude, and what remains open.

Preserve every citation exactly as I have written it. Do not add sources.
Text: detailed. Tone: academic but readable.

Compress this report into a 3-slide executive summary for [role], who will not read the full document.

[paste the report]

Slide 1: the finding, with the single number that matters
Slide 2: what it means for [their specific decision]
Slide 3: what we recommend, and what we would need to be wrong about

Condense, do not rewrite. Keep every figure exactly as given, with its units.
Text: brief. Tone: neutral. No images.

Onboarding decks

Create a first-week onboarding deck for a new [role] joining [team].

10 slides:
1. What this team exists to do, in one sentence
2. What you personally will own by day 30
3. Who does what, with names and what to ask each of them
4. The three systems you need access to, and who grants them
5. How we work: meetings, docs, decisions, where things live
6. What good looks like here, with one real example
7. What we are currently bad at, honestly
8. Your first task, and what done looks like
9. The questions people are embarrassed to ask, answered
10. Who to talk to when something feels wrong

Audience: someone competent and completely without context.
Text: detailed. Tone: warm, direct, no company-values language.

Create a 6-slide customer onboarding deck for [customer], starting from what they bought.

1. What you bought, restated as the outcome you wanted
2. What happens in week 1, with dates and owners
3. What we need from you, and by when
4. What success looks like at 30, 60 and 90 days
5. Who to contact for what
6. The first thing to do after this call

Audience: [their team], mixed technical and non-technical.
Text: brief. Tone: clear, low-jargon.
Use the dates I have given exactly. Do not invent a timeline.

How do you keep real numbers intact in a generated deck?

By computing them somewhere else and handing Gamma finished figures. This is Gamma's advice rather than ours: its guide to driving decks from an LLM says to "Read the source fresh on every request", to pre-compute in a script, and, in the line worth pinning above your desk, "Never make Gamma do arithmetic - pass it finished figures only."

The same page tells you to restate every number with units and name the chart type you want, and gives a table technique: one pipe-delimited row per line, plus an explicit instruction not to edit. Its worked example ends "Preserve row order exactly. No edits, no additions, no aggregation", and explains why in one line: "The | delimiter keeps column boundaries unambiguous."

Two documented constraints change how you plan. Chart output is not deterministic: the docs state that "Generation is non-deterministic — results may vary across runs, even with identical inputs", and that no parameter controls chart type or styling directly. You steer charts with words, then check. And there is no editing pass through the API. The scope page is blunt: "The API creates gammas but does not edit existing ones." The Help Center repeats it, "There's no edit tool - to change a deck, regenerate it", so a wrong figure means regenerating rather than patching.

If you build the same deck repeatedly, there is a stored-instruction layer. Gamma's template instructions embed guidance inside a template so that, in Gamma's words, "Gamma reads all the instructions out of the template and includes them in the AI prompt." They never appear in the output. Gamma documents them on Pro and Ultra plans, and warns that "Instructions count toward the AI prompt's token budget", so they compete with your content for space.

What does the Gamma free plan actually allow?

Enough to evaluate it, and less than most write-ups suggest. Three limits matter for prompt planning, all verified on Gamma's own pages on 27 August 2026.

Slide count per generation is capped. Gamma's pricing page lists "Create up to 10 slides per prompt" on Free and "Create up to 75 slides per prompt" on Plus. The Help Center gives different figures for the same thing, "Free workspaces: up to 10 slides per generation" and "Paid workspaces: up to 100 slides per generation", while the API documents numCards as "1 to 75 cards" on paid tiers. The free number is consistent; the paid ceiling is not. Check gamma.app/pricing before planning a long deck. The cap applies only to the generator: the Help Center notes "There's no cap on total slides in a gamma — you can always keep growing a deck."

Free credits do not refresh. Gamma's credits article states that on the free plan "all AI actions use credits, and credits do not refresh", that "Each new free user receives 400 credits when initially signing up", and that generation is "metered per slide and per image". That is a fixed budget, not a monthly allowance, which makes the free tier a trial rather than an ongoing plan. Paid plans refill monthly and roll over up to double the plan size.

Exports carry a watermark. The export article says the Made with Gamma logo or watermark "appears on presentations exported from free accounts", and answers the direct question with "Only Plus and Pro users can export without the Gamma watermark." Formats are PDF, PNG and PowerPoint, with Google Slides reached by uploading the PPTX; Word is not supported on any plan.

Gamma's individual pricing page lists Free, Plus, Pro and Ultra, with a separate business tab; its developer docs additionally name Teams, Business and Enterprise. We are not quoting prices, because they change. Packaging shape is what decides whether a prompt you wrote is runnable on your plan at all.

Where does an AI-generated deck stop being enough?

At the point where someone will interrogate it. The hazard with deck generators is not bad output. It is output that looks finished.

A rough deck invites scrutiny; every reader knows to check a page of unformatted bullets. A generated Gamma deck arrives evenly paced, consistently styled and visually competent, and that finish borrows credibility the content has not earned. The polish arrives before the thinking does.

Three things stay human.

Narrative judgement. The generator produces a well-formed sequence. It cannot know that your board already rejected the framing on slide three, or that the number your CFO will fixate on is buried on slide nine. Ordering a deck for a specific room is politics as much as logic, and the model is not in the room.

Real data. Anything a stakeholder can check has to be checked by you. Charts vary between runs by Gamma's own admission, and a figure that reads plausibly is not a figure that is right.

Anything with consequences. Pricing, commitments, dates, legal claims, customer names, competitive comparisons. If being wrong costs someone something, a person reads it first.

Gamma gets you from nothing to a credible draft in minutes, which is genuinely valuable. The last 20%, the argument and the numbers and the room, is the part that was always the work.

Does a prompt library help with a deck generator?

For the repetition, yes. For the judgement, no. We make a prompt tool: we do not build decks, we do not design slides, and nothing we ship will tell you whether your Q3 narrative holds up. Anyone claiming a prompt library replaces the thinking in a board deck is selling something.

What it helps with is repetition. You will write the same six or seven deck briefs over and over, the weekly update and the QBR and the pitch refresh, each with the same six slots and different contents. Those are prompt templates with variables, and retyping them from memory is how the "do not invent numbers" line goes missing on the deck where it mattered. Saving them once is the whole benefit. Same argument as building a personal AI prompt library, applied to decks, and the same reason reusing prompts beats copy-pasting them.

The second help is upstream of Gamma entirely. Bad decks start from a prompt that names a topic and nothing else, and expanding that into a brief with an audience, an arc, a density and constraints is a different job from generating the deck. Prompt Architects includes built-in AI on every plan, so there is no separate API key to wire up. The pattern is the one we applied to prompting an app builder: the generator makes the artefact, and the prompt carries the decisions the generator would otherwise make for you.

The eight-check Gamma prompt checklist

Each one closes a decision Gamma would otherwise close for you.

1. Job. Name the artefact and what it is for, not the topic.
2. Audience. Who is in the room and what they already know.
3. Arc. The numbered slide list. If you cannot write it, the deck is not ready to generate.
4. Count. State it explicitly, and check it against your plan's cap.
5. Split. Decide whether Gamma divides your content or you do, using your own break markers.
6. Density. Brief, medium, detailed or extensive, plus any hard per-slide limit.
7. Data. Preserve mode, finished figures with units, no arithmetic asked of the generator.
8. Constraints. No invented numbers, visible placeholders for gaps, and what not to touch.

Skip any of them and you inherit a default. The defaults are reasonable. The problem is not noticing which one you got until someone in the audience does.

Sources and access date

Every Gamma claim here was read on 27 August 2026 at Gamma's own properties, not from a search summary. Gamma renames surfaces often, so verify before relying on a detail:

• Generation parameters and defaults: developers.gamma.app/guides/generate-api-parameters-explained
• Charts, scope and pricing: developers.gamma.app/guides/charts-and-structured-content, /reference/common-feature-requests, /get-started/access-and-pricing
• Slides, and the generator's slide cap: help.gamma.app/en/articles/11016396-what-are-slides-in-gamma-and-how-do-they-work
• Creation modes: help.gamma.app/en/articles/7838093-how-do-i-create-a-new-presentation-document-or-webpage-in-gamma
• Create with Agent and deck styles: help.gamma.app/en/articles/15002203-how-do-i-create-with-agent-in-gamma
• Credits: help.gamma.app/en/articles/7834324-how-do-credits-work-in-gamma
• Export and watermark: help.gamma.app/en/articles/8022861-what-s-the-easiest-way-to-export-my-gamma
• Template instructions: help.gamma.app/en/articles/16056626-what-are-template-instructions-and-how-can-i-use-them
• Driving decks from an LLM: help.gamma.app/en/articles/15715171-how-can-i-get-my-data-into-gamma-decks-using-an-llm
• Gamma's own prompt library: gamma.app/prompts · plans: gamma.app/pricing

Two disagreements inside Gamma's own documentation are worth knowing about. The generator's paid slide cap is 100 in the Help Center, 75 on the pricing page and 75 in the API reference. The number of creation modes is three on one Help Center page and five on another published the same day. Both are signs of a product moving faster than its documentation.