Building presentations when your AI already knows your context

Generic prompts produce generic decks: blue gradients, three bullet pillars, a stock “thank you” slide. The fix is not a cleverer opener—it is giving the model the same context a good freelancer would ask for on day one.

Context worth attaching

Audience & decision — “Seed investors, 20 minutes, need a second meeting” beats “make a pitch deck.”
Proof — metrics CSV, customer quotes, roadmap excerpt, competitive table. Cite sources in prompts so the model does not invent ARR.
Brand — hex colors, font names, logo SVG, “never use gradients.” Paste a link to your marketing site if files are heavy.
Product — Figma frame exports, API docs, README, screenshot folder. Interactive slides need real UI copy, not lorem ipsum buttons.
Constraints — slide count, no video, must work offline, must include pricing simulator on slide 9.

Where to put context by tool

Cursor / Claude Code: put assets in the repo (/docs, /data, /assets) and point the agent at paths. Skills and rules files keep packaging conventions consistent.

ChatGPT / Claude web: attach PDFs, CSVs, or zip the brief. For HTML output, ask for a single downloadable folder structure, then move it into a repo for real testing.

Superprez in-app AI: context lives in the repo Superprez provisions—messages reference the deck slug and branch. External edits still flow through Git: pull zip, edit with your preferred agent, upload or push back.

A brief that actually works

Audience: enterprise security buyers, 45 min workshop Decision: book a pilot in Q3 Slides: 14, linear, 1280×720 HTML deck Brand: #0F172A text, #2E5BEA accent, Inter, no stock photos Proof: attach metrics-q2.csv and 2 customer quotes in brief.md Interactive: slide 8 = ROI calculator (seats × plan); slide 11 = architecture diagram with clickable layers Delivery: static files, package for Superprez upload Do not invent revenue numbers—use CSV only.

More patterns in prompt templates.

Keep context alive after v1

Decks rot when context lives only in chat logs. Store the brief in the repo (BRIEF.md), version data files, and host on Superprez so collaborators inherit Git history—not a forwarded ChatGPT thread. When metrics change, update the CSV, ask your agent to refresh slide 6, push, and the live link updates for everyone.