Presentation Generator

View saved version →

---
name: presentation-generator
description: Build a complete slide deck — pitch decks, sales decks, quarterly business reviews, board and all-hands updates, training decks, conference talks — delivered as a .pptx, or a self-contained HTML deck when PowerPoint files cannot be written, with an argument running through it, one idea per slide, speaker notes, and marked placeholders instead of invented numbers. Use when someone wants slides, a deck, a presentation, or a PowerPoint, Keynote, or Google Slides file made, restructured, tightened, or cut to a time limit, including asks like "turn these notes into a deck" or "I'm presenting to the board on Thursday". Do NOT use for prose that is not slides — an email, a post, web copy, a report or one-pager — that is a separate writing skill. Do NOT use for designing a web page or mockup, generating a photo or hero image, drawing a logo or favicon, writing source code, or building a website; those are separate skills. "Design my slides" is still this skill; "make an image for slide 3" is the image skill.
---

# Presentation Generator

## Goal

Build the deck a room can actually be presented from — a real file, with an argument running
through it, at the length the slot allows.

Writing slide text is the easy half and the host already does it. What does not happen on its
own is a headline that states a point instead of naming a topic, a number left as `[ARR]`
instead of quietly invented, forty words on a slide instead of a hundred and ten, and a
PowerPoint file that opens at 16:9 with the text still inside its boxes. **Those constraints
are the product.**

The characteristic failure is a deck that lists topics instead of making an argument:
Introduction, The Problem, Our Solution, Market, Team, Ask. Every slide looks like a slide,
the deck says nothing, and the meeting is wasted. Step 3 exists to prevent exactly that.

## Instructions

### 1. Get the subject and the room

Two things are required, and they arrive in one question:

- **What the deck is about** — the actual subject, not a title. **Required.**
- **Who is in the room** — investors, a customer, your own team, a class, a conference audience.
  **Required**, because it picks the deck type in step 2.
- **How long the slot is** — optional. Default to about ten minutes, and say you assumed it.

**A name is not a subject.** *"Make a deck for CoffeeCat"* gives you nothing to argue — a coffee
shop, a cat rescue, and a software company called CoffeeCat produce three unrelated decks. A
subject implies a plausible name; a name implies nothing. So the subject gates the work, and the
name is decoration on top of it.

**The subject is not always a business.** A training deck on pivot tables, a conference talk on
Kubernetes, and a student's deck on climate policy are all valid asks, and none of them has a
trade. So ask what the deck is **about**, not what the business does — and notice which one you
got, because step 8 needs to know whether the user's **own** business is in play.

Ask in **one short message**, folding everything in. Never a sequence of questions. If the user
already said *"a pitch deck for my bakery, going to seed investors"*, you have all three — go to
step 2. One example of the whole ask:

> What's the deck about, and who's in the room? A couple of lines is plenty — and tell me how
> long you've got if it isn't about ten minutes.

**IMPORTANT:** Absolutely NEVER ask about colors, fonts, layout, slide count, or structure.
Deciding those is the whole skill, and asking hands the work back. If the user volunteers any of
it, use it and say you did. Never ask for an email address, phone number, or location.

**If they actively decline** — *"just make something"*, *"doesn't matter"* — do not keep asking
and do not stall. Build against the most likely deck type, fill every factual slot with a marked
placeholder, say plainly what you assumed, and use **register B** in step 8. **Never invent a
business** to fill the gap — a deck br

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.