How to write Gamma prompts for a useful first draft

Useful Gamma AI prompts say who the presentation is for, what those people need to decide, which sources to use, and how to organize the answer. Put those requirements before decorative preferences. Gamma 5 starts with a creation conversation, while the classic generator remains available through Use classic generator. Keep the tested brief and accepted changes in fenbs so your next draft starts from what worked, even when another AI helps you prepare it.

Which creation route should your prompt use?

Gamma’s creation guide↗ (opens in a new tab) describes the current conversational starting point and the separate classic flow. In Classic, Create New AI offers Generate, Paste, and Import. Choose the route by the material you already have rather than rewriting approved copy simply to turn it into a short topic prompt.

1. If you are starting with an idea, write the audience, purpose, and proposed structure before beginning the creation conversation or using Generate in Classic.
2. If you already have approved wording, prepare that text and use the documented Paste route in Classic. Mark which facts and phrases need to stay exact.
3. If your starting point is an existing file or webpage, use the documented Import route in Classic, then inspect the resulting structure against the source.
4. Review the generated draft for meaning before spending time on visual polish. Keep missing evidence and unresolved questions visible.

These routes describe different starting materials, not different standards of truth. An imported number still needs the right label and scope. A pasted paragraph can still be too long for the audience. A generated outline still needs your judgment about what belongs in the meeting.

What should you put in the creation brief?

Think of the prompt as instructions to a colleague who has not attended the earlier conversations. Give the colleague enough information to build a useful first draft without guessing why the presentation exists. Be specific about the action you need from the audience.

• Audience: their role, what they know already, and what needs a short explanation.
• Purpose: the question to answer or decision to support.
• Source material: the approved notes, definitions, figures, and examples the draft may use.
• Structure: the order of ideas and the purpose of each section.
• Limits: unsupported claims to avoid, exact wording to preserve, and missing information to leave open.
• Review target: the questions a person will use to judge the first draft.

Create a presentation for a small operations team.
Purpose: choose which of two scheduling proposals to test.
Audience: knows the current process; does not know the proposals.
Structure: current problem, option A, option B, comparison, open questions, requested decision.
Use only the approved notes below.
Keep supplied figures and their labels exact.
If evidence is missing, list the question rather than inventing an answer.
Use short headings and one clear purpose per section.
Approved notes: [paste the checked source material here]

This example supplies a testable purpose without pretending that a particular wording guarantees a good result. Replace the example’s audience and structure with your actual job. A product introduction, classroom lesson, and budget review should not all inherit the same opening just because one prompt worked once.

How do you give sources without burying the task?

Put a short instruction before the source material: what may change, what must remain exact, and what the material is supposed to support. Then organize the evidence by section or question. Long unmarked notes make it harder for you to check whether a claim came from the source or from the draft.

For example, separate “approved product description” from “ideas we have not accepted.” Do not paste a brainstorm directly beneath confirmed facts without naming the distinction. When a source is incomplete, write the question that needs a person’s answer. Do not fill the gap with a plausible figure to make the deck look finished.

Keep the source link and the agreed interpretation in fenbs. That lets another assistant help with the next wording change while preserving why the accepted claim belongs in the presentation. For the broader process from notes to slides, read generate slides with AI.

How should you revise a weak first draft?

Identify the kind of failure before rewriting the whole prompt. Wrong facts need correction from the source. A confusing order needs a better sequence. Too much detail needs a clearer audience boundary. Asking for all three at once can hide whether the important correction actually survived.

Keep the accepted parts explicit when you request a revision. “Preserve the comparison and approved figures; simplify the introduction” gives you a smaller review surface than “try again.” Inspect the revised output anyway. An instruction is a request to check, not evidence that the result obeyed it.

Where can you find the original prompt?

For a gamma originally generated with AI, Gamma documents the upper-right three-dot menu (…) → View Source Prompt. Save the useful wording along with the material it depended on and your accepted revisions. Viewing the source prompt does not promise that rerunning it produces an identical deck.

Keep a short version label in your own record: audience, purpose, source set, and the change that improved the draft. “Operations comparison, approved notes, lead with the decision” tells you why a prompt worked. A folder of unnamed copied prompts does not explain which one to reuse.

Gamma also has template instructions↗ (opens in a new tab) for reusable guidance during AI generation from a template. Their availability differs from ordinary template access, and plain duplication ignores those instructions. Use the separate Gamma template guide when you need repeated content and layouts rather than just a creation brief.

How to keep a useful Gamma prompt with fenbs

Keep the prompt so you never lose the work behind it. You can return on any device and ask another connected AI to continue from the accepted audience, sources, and revisions.

1. Create a free account.
2. Save the prompt that worked. Give it a plain name that says what you use it for.
3. Keep the approved sources and the owner’s choices beside the work. Say which parts change for each new audience.
4. Before stopping, write what you checked and what needs another look. Ask the next connected assistant to read that record before preparing a new prompt.

fenbs keeps reusable prompts and the work around them; it does not generate the Gamma deck. If you only need to retrieve one source prompt inside Gamma, a second library may be unnecessary. It helps when your creation instructions need to survive different tools and repeated jobs.

Read the AI prompts hub for more ways to keep reusable instructions, or the Gamma saving guide when the deck is ready for delivery.