Create a new deck with slides from scratch. Use before creating a deck or standalone visual; resolve source fidelity, creative context, and the active design system before using the fallback HTML patterns in this skill.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Create a new deck with slides from scratch. Use before creating a deck or standalone visual; resolve source fidelity, creative context, and the active design system before using the fallback HTML patterns in this skill.
Creating a Deck
Do not explore the codebase for routine deck creation. Use the app actions
and linked skills. This does not override the active design system, Creative
Context, reference deck, or source material that the app already provides.
Workflow
Read the creative-context skill and retrieve factual evidence separately
from presentation structure. Respect contextMode: "off".
Unless the user named a reference deck or design system, call
get-workspace-defaults and use what it returns. See "Workspace Defaults".
Plan the slides (deck title, title slide, section dividers, content slides).
Call create-deck --title "..." --slides '[]' with a concise, specific
title derived from the user's request and source material. Never use
Untitled Deck or another placeholder title for a generated deck.
Navigate to the new deck.
Call add-slide once per slide in slide order, waiting for each result.
When the UI has already created the empty deck, keep its id and rename it before
adding the first slide. Call patch-deck with a patch-deck-fields operation
whose fields.title is the generated title. Do not leave the pre-created deck's
placeholder title in place. Include only title in that operation's fields;
omit all other optional fields.
Follow the creative-context reuse ladder before inventing a slide language:
reuse an approved native template unchanged, compose approved pieces, lightly
adapt a real approved example, generate from narrowly retrieved references,
then go net-new only when the relevant corpus is empty. Retrieval is a separate
step from generation. Persist the immutable and concise reuse
labels with the deck's generation provenance; never infer provenance later from
rendered slide HTML.
contextPackId
Direction and source checkpoint
Before authoring slide HTML, make a compact deck brief with the audience, job,
narrative thesis, one-sentence visual direction, active design-system tokens,
reference-deck composition pattern, image treatment, and known fit risks. The
linked Agent-Native design system controls tokens, typography, spacing, imagery,
and slide chrome. Impeccable-inspired advice about hierarchy, subtraction,
contrast, and polish is a review lens, not a competing theme. If the request is
open-ended and no approved direction exists, ask one targeted guided question
or present a bounded choice before writing; do not silently pick a new brand
language.
When the source is a transcript or meeting notes, extract the audience's
terminology, goals, objections, decisions, owners, dates, metrics, and open
questions before outlining. Preserve exact names, numbers, dates, and requested
quotes; retain speaker/source attribution; distinguish quotation, paraphrase,
inference, and unresolved claim. Do not invent connective claims to make the
story smoother. Keep factual evidence separate from visual references and
record the source/version identifiers in provenance when available.
When creative context is available, pass the pre-generation search result's
contextPackId to create-deck, pass deck-wide reuseLabels, and add
creativeContextReuseLabels to each slide that reused a specific item/version.
Do not omit these fields and let the final write action search after the HTML
has already been authored; that would fabricate influence. With an empty
library, omit them. With Library mode Off, omit them and create normally.
before adding the next slide
Do not create multiple slides in parallel for the same deck. Do not spawn
sub-agents to write into the same deck at the same time. Sub-agents may research
or draft slide copy, but one writer should call add-slide sequentially so the
editor stays stable and the user can watch progress.
Reference Decks
The user can pick an existing deck as a style reference when starting a new one.
When they do, a ## Reference Deck block is already in your context holding one
worked HTML example per layout.
Treat it as a pattern library, not an outline. The most common failure here is
walking the reference deck slide by slide and swapping in new copy, which
produces a deck with the wrong shape for its own content. Instead:
Plan the new deck from the user's request alone — story, slide count, order.
For each slide you decided to write, pick the pattern that fits that content.
Reuse a pattern as often as the content warrants, or never.
When nothing fits, compose a new slide from the same type scale, spacing,
color, and markup conventions rather than bending content to a near-miss.
The block deliberately omits the reference deck's slide sequence. Call
get-deck --id <reference deck id> --compact false only if you need full slide
HTML to see how that deck handled a case the patterns do not cover.
A reference deck and a design system are independent: the design system wins on
tokens (color, type, spacing, imagery, and slide defaults), the reference deck
wins on slide-level composition and markup idiom. Apply both when both are
present. Generic templates in this skill are fallback patterns only. Never let
a reference screenshot or deck silently transfer its brand tokens.
Decks the user has starred are their intended reference decks. list-decks
reports starred so you can offer them when the user asks for something "like
our usual deck".
Workspace Defaults
A workspace admin can flag one deck and one design system as the workspace
default, so a bare "make a deck about X" still comes out on brand. When the user
did not name a reference deck or design system, call get-workspace-defaults
before planning slides.
referenceDeck — call get-deck-reference-context --id <id> and treat the
result exactly like a user-picked reference deck.
designSystem — pass its id as designSystemId to create-deck, unless the
caller already has a personal default, which create-deck applies on its own.
Either field can come back { unavailable: true }. That means the default
exists but this user cannot open it, which is a misconfiguration, not an
absent default. Generate without it and tell the user their workspace default
is not shared with them, rather than silently producing an off-brand deck.
An explicit request always wins over the workspace default. Do not re-apply a
workspace default to an existing deck the user is editing.
If the user provides a Google Docs URL as source material, call
import-google-doc --url <url> first and build from the returned text. If the
action cannot read a private document, the user can connect Google Docs and
choose the file through the picker, or share the Doc with the configured service
account. Relay the action's exact access instructions instead of generating from
the URL alone.
pnpm action create-deck --title "My Deck" --slides '[]'
Then navigate:
pnpm action navigate --deckId=<id from create-deck output>
The literal values in the examples below are fallback values for a deck with no
linked system. When a system is linked, use its hydrated values or the renderer
variables (--ds-accent, --ds-bg, --ds-text, --ds-text-muted,
--ds-heading-font, --ds-body-font, --ds-radius) instead of copying
Poppins, cyan, white, black, or a stock radius into new markup.
Fit budget
The canvas is fixed at its aspect-ratio dimensions. With the standard 16:9
canvas (960x540) and padding: 80px 110px, the usable content area is only
740x380px. Treat that as a hard budget for the main flow: use at most two title
lines, three short bullets or cards, and two or three short items per column.
Split dense source material across slides instead of shrinking it into a dense
stack. Keep body text at or above 16px. Never hide overflow with zoom,
transform: scale(), clipping, or scroll overflow. A later structural repair
may reduce the slide's explicit padding, and that padding must remain intact
when the saved HTML is rendered.
Background is pure black (bg-[#000000]) — set by the renderer, not the slide HTML.
When no reference deck or hydrated design system is available, use a restrained,
content-first visual language. Do not invent colorful cards, boxes, or
decorative rectangles behind or over text. Add a colored shape only when it has
a clear semantic role and leaves the text unobscured; prefer typography,
spacing, alignment, and one restrained accent.
Bounded visual QA
Before calling the deck complete, render every changed slide at its canonical
aspect-ratio dimensions and make one batched review pass. Check hierarchy and
source fidelity, overflow or clipping, contrast, minimum readable text,
placeholder remnants, broken or missing images, asset fit, and preserved
data-slide-object-id values. Fix the findings in one correction pass and
recheck. Do not claim full-deck or pixel-perfect fidelity unless the whole deck
was rendered and compared.
Ready-to-Use Templates
Copy and fill in the bracketed values. Use \ to escape quotes inside the JSON string.
Use a non-empty create-deck --slides '[...]' payload only for imports or an
intentional atomic bulk replacement. For normal AI-generated decks, use the
empty-deck plus sequential add-slide workflow above.
