🎯 Design
Slide Deck Visual System: Type, Color, Layout, and Chart Rules
Define a slide visual system: type roles, layout grid, color for charts, and bans so a 12-slide deck looks like one product, not 12 templates.
0Reviews
Prompt
Act as a presentation designer creating a visual system for slides, not a full UI design system and not a speech. The output is rules a teammate can apply in Google Slides or Keynote. Inputs: - Deck job: [Job] - Audience: [Audience] - Slide count target: [Count] - Brand colors and type they have: [Brand] - Room: [Room] - Must include slide types: [Types] - Data I can chart: [Data] - Forbidden: [Forbidden] - Aspect: [16:9 / 4:3] Generate: 1. Principles (5): one line each (one idea per slide, big type, data before decoration). 2. Grid and layout: margins, 12-column or simple 2/3+1/3, title safe area, footer (page n / n, confidential or not). Aspect from Inputs. 3. Type roles: Title, deck, label, source. Sizes in px for 16:9 1920 or in points. One type family from Brand, plus a mono if Data needs it. Line length max. 4. Color: map Brand to background, title, body, accent, data series (max 4). What never uses accent (body text). 5. Slide types: For each Types item, a wireframe in words (title 6-8 words, body rules, image slot). Include title, agenda, statement, 3-up, comparison, chart, quote, close. Skip types not needed. 6. Chart rules: When to use bar vs line vs table. No pie unless Data has 2-3 parts. Always label the point, not a legend hunt. Source line from Data only. If a number is not in Data, do not chart it. 7. Don'ts: 12 (stock handshake, drop shadows, 6 fonts, bullet novels, animation as content, 3D pie, logo watermark every corner, fake screenshots). 8. 12-slide skeleton: titles only, mapped to types, using Job. Not the speech. Constraints: - Honor Forbidden and Brand. - Do not invent metrics. - This is slides, not a website design system. - No emojis unless Brand demands them. - Room: if TV at the back, bump title size and avoid thin lines.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Deck job: 12-minute product update to an internal ops audience on why BatchNotes will not auto-post to X Audience: 20 people, ops + one founder, already customers of our own tool Slide count target: 10-12 Brand colors and type they have: navy #1B2A4A, paper #F6F1E8, ink #121212, Inter Room: conference room TV, 16:9, people 4 meters away Must include slide types: title, problem, decision, before/after, one chart, FAQ, close Data I can chart: 16 weeks of Friday posts; waitlist-to-paid 4% then 7%; support "what's new" tickets dropped (no exact count, so no fake axis) Forbidden: AI purple, rocket clipart, 3D pie, fake Twitter engagement charts, "synergy" Aspect: 16:9
Example Output
1. Principles One idea per slide. Type big enough at 4 meters. Data only if we have it. Decision slide is the point. Decoration loses. 2. Grid 16:9. Margins 64px. Title in top 20%. Footer: "BatchNotes internal" + n/12, 14px, navy 40%. Content in a 2/3 + 1/3 or single column. No edge-to-edge photos. 3. Type (1920 wide) Title 56-64pt Inter semibold, max 6-8 words. Deck 28-32pt Inter regular, max 2 lines. Labels 18pt. Source 14pt. Mono Inter for the 4% / 7% pair. Dark navy or ink on paper. No thin 12pt body. 4. Color bg paper. title navy. body ink. accent navy only for the decision bar or the 7% number. Chart: one series navy, comparison ink. Never accent as paragraph color. No extra greens. 5. Slide types Title: product name, 12-min update, date, no subtitle novel. Problem: "what's new" tickets. 3 short lines. Decision: one sentence: we will not auto-post to X. Before/after: left auto-tweet on, right Zap-optional. Labels, not screenshots we do not have. Chart: two bars 4% and 7%, titled waitlist-to-paid, 16 weeks, team of 3. No fake ticket-count chart. FAQ: 3 questions, 1 line each. Close: decision repeated + owner. 6. Chart rules Two bars, values on the bars, no legend. Source: "one 3-person team, 16 Friday posts." Do not chart "tickets dropped" (no count). No pie. No X impressions. 7. Don'ts Rocket. 3D pie. Fake engagement. Handshake stock. Drop shadows. Six fonts. Bullet novels. Logo in every corner. Animation as content. Synergy. AI purple. Thin gridlines. 8. Skeleton 1 Title: Friday changelog, not a feed 2 Problem: "what's new" tickets 3 What we tried: 16 Fridays 4 Chart: 4% to 7% 5 What we will not do: auto-post to X 6 Zap is optional 7 Before/after motion 8 Risk: looking like a social product 9 FAQ 10 Decision + owner 11 (optional) office hours 12 Close: same decision line