# Presentation Deck Branch

Use this branch for PowerPoint, Keynote, Google Slides, business presentations, investor decks, board/executive decks, sales or pitch decks, training decks, read-alone decks, slide redesigns, and PPTX/PDF deck delivery.

Read `design-okf/production/presentation-deck.md` for the source-of-truth commercial deck model: decision path, density modes, narrative structures, slide claim/evidence/action, page types, master/template rules, accessibility, and delivery checks.

Read `design-okf/systems/taste-engine.md` when the deck needs a memorable style, stronger executive polish, a pitch/campaign identity, slide-archetype variation, anti-template critique, or when the deck risks becoming the same title-plus-card slide repeated.

Read `design-okf/systems/type-personality.md` when deck typography is part of the visual memory, when choosing deliverable-safe fonts, when Chinese/English mixed slide text matters, or when the deck must travel across devices as PPTX/PDF.

Read `design-okf/systems/motion-language.md` when the deliverable is an animated HTML deck, live web deck, scroll/paged storytelling experience, or when transitions/sequence animation are explicitly requested. Read-alone, PDF, and portable PPTX decks default static; use motion only when the delivery mode supports it and it helps attention or continuity.

Read `design-okf/systems/motion-contract.md` when an HTML or live deck makes a specific animation promise, such as scroll-linked SVG drawing, progress-bound transitions, timeline sequencing, or no-flash reveal behavior.

## Brief

Clarify or infer:

- Audience: executive, customer, investor, board, team, trainees, or public.
- Mode: live presentation, read-alone email deck, decision memo deck, sales/pitch, training, or internal execution.
- Goal: inform, persuade, request approval, win a customer, raise funding, align execution, or teach.
- Duration and slide count when relevant.
- Output: editable PPTX, PDF, notes/script version, template, image exports, or HTML deck.
- Brand/template: logo, VI, slide master, fonts, colors, page footer, confidentiality labels.
- Risks: confidential data, financial numbers, client identity, legal claims, font/image/icon rights.

Ask only when missing audience, decision goal, or output format would point the deck at the wrong use case.

## Deck Strategy

- State the one-sentence deck conclusion before designing slides.
- Choose a narrative spine: pyramid, SCQA, What-So What-Now What, 5W1H, or AIDA.
- Build the slide list so title-only reading tells the story.
- Separate mainline slides from appendix, backup data, speaker notes, and data-source files.
- Match density to mode: live decks need fewer words and larger type; read-alone decks need enough annotation to stand without narration.
- Set taste dials for the deck. Executive decks usually need controlled variance; pitch, campaign, and brand decks can use stronger visual memory.
- Decide whether type should recede for distance readability or stand forward for cover/section memory. Do not make body slides expressive at the cost of reading.

## Slide Rule

Every slide needs:

- Claim: the conclusion or message the audience should retain.
- Evidence: data, example, comparison, visual, or quote that supports it.
- Action: decision, next step, implication, or reason the slide exists.

If a slide has no claim, merge, rewrite, move to appendix, or delete it.

## Visual System

- Use one strongest focal point per slide.
- Keep title, chart, annotation, footer, and source aligned to a grid.
- Repeat title position, type hierarchy, chart style, icon style, footer, and page number.
- Treat title, body, chart labels, data numbers, footers, and section dividers as different type roles.
- Use emphasis color sparingly for the decision-critical number, risk, or action.
- Prefer left alignment for dense business content.
- Use CRAP plus hierarchy: contrast, repetition, alignment, proximity, and reading order.
- Vary slide archetypes by narrative job: claim, evidence, comparison, process, decision, quote, data, appendix, and transition. Do not solve every slide as title plus cards.

## Data Slides

- Use conclusion titles, not generic chart titles.
- Choose chart type from the business question: compare, trend, composition, relationship, distribution, process, or funnel.
- Remove 3D, heavy gradients, heavy borders, and decorative chart effects.
- Direct-label important values when practical.
- Show unit, time period, source, assumptions, and methodology where credibility depends on them.
- Keep data meaning and measurement basis consistent across slides.

## Delivery

- Preserve or create slide master rules for recurring layouts.
- Confirm font embedding or choose deliverable-safe fonts when the deck travels across devices.
- Export a PDF for external review when layout stability matters.
- Include notes/script version, editable version, frozen version, data source files, and asset/license notes when the deck is business-critical.
- Use the Presentations capability for actual PPTX/Google Slides file creation or editing when available; this branch governs design judgment and QA.

## Done Criteria

A deck is ready when the title story is coherent, every core slide has claim/evidence/action, density matches delivery mode, visual system and brand rules are consistent, charts are trustworthy, accessibility/export checks are addressed, and unresolved legal/data/brand/font risks are named.
