siril9/presentation-skill / plugins/presentation-skill/skills/presentation-skill
presentation-skill
FlaggedBuild, edit, redesign, render, and verify content-led, structurally diverse, clean, editable, reproducible PowerPoint `.pptx` decks. Use for scientific, lab, clinical, consulting, board, investor, editorial, policy, and operational presentations where alignment, readability, contrast, and balanced density matter.
DESIGN.md
View on GitHub---
version: "alpha"
name: "presentation-skill Deck System"
description: "Agent-readable design contract for clean, aligned PowerPoint decks generated by presentation-skill."
colors:
primary: "#071E3A"
secondary: "#0B6B78"
tertiary: "#F59E0B"
neutral: "#F4F8FB"
surface: "#FFFFFF"
text: "#0F172A"
muted: "#475569"
line: "#D5DEE8"
typography:
title:
fontFamily: "Trebuchet MS"
fontSize: "53px"
fontWeight: 700
lineHeight: 1.05
letterSpacing: "0px"
body:
fontFamily: "Calibri"
fontSize: "22px"
fontWeight: 400
lineHeight: 1.22
letterSpacing: "0px"
caption:
fontFamily: "Calibri"
fontSize: "13px"
fontWeight: 400
lineHeight: 1.15
letterSpacing: "0px"
rounded:
sm: "4px"
md: "8px"
spacing:
xs: "4px"
sm: "8px"
md: "16px"
lg: "24px"
xl: "40px"
components:
title-slide:
backgroundColor: "{colors.primary}"
textColor: "#FFFFFF"
typography: "{typography.title}"
content-header:
backgroundColor: "{colors.primary}"
textColor: "#FFFFFF"
typography: "{typography.title}"
card:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.md}"
padding: "16px"
footer:
backgroundColor: "{colors.neutral}"
textColor: "{colors.muted}"
typography: "{typography.caption}"
generated-image-slide:
backgroundColor: "{colors.neutral}"
textColor: "{colors.text}"
rounded: "{rounded.md}"
padding: "18px"
section-divider:
backgroundColor: "{colors.secondary}"
textColor: "#FFFFFF"
typography: "{typography.title}"
callout:
backgroundColor: "{colors.tertiary}"
textColor: "{colors.primary}"
typography: "{typography.body}"
rounded: "{rounded.md}"
padding: "16px"
divider:
backgroundColor: "{colors.line}"
height: "1px"
---
## Overview
presentation-skill creates clean, editable, reproducible PowerPoint decks from structured outlines. Compose supported layouts around the content rather than following a fixed template sequence. Keep a coherent design system within each deck, with meaningful structural choices across decks. Alignment, readability, contrast, and balanced density win over decoration; palette or border changes alone are not diversity.
## Colors
Use one base preset per deck, with compatible treatments where the content benefits. Keep typography, spacing, and semantic color coherent. Avoid generic blue unless the topic calls for it. Dark title and section slides may contrast with light content slides, or the deck may use a consistent dark theme.
## Typography
Titles must visibly dominate body copy. For ordinary delivery, use at least 28pt for titles, 16pt for body text, 13pt for supporting subtitles, and 9pt for captions and source lines. Shorten or restructure content before shrinking type. Letter spacing is always zero; do not use negative tracking.
## Layout
Use a 16:9 canvas with disciplined side margins and repeatable gutters. Content starts only after wrapped titles and subtitles have reserved enough height. Body text is left aligned except for KPIs. Choose a focal structure suited to the content; a clean bullet list, table, or rectangular highlight can be sufficient without an added visual.
For reusable workspaces, capture the taste decision in `design_brief.json`
before writing `outline.json`: audience posture, cover archetype, grid policy,
container/card policy, evidence continuity, figure export rules, and the
rhythm-break plan. The outline should implement that brief rather than cycling
through every available variant.
For reproducible first-turn setup, use `scripts/emit_deck_start_packet.py`.
It emits the compact user-question payload, the design-contract scout prompt,
and staged handoff commands for style routing, data analysis, content research,
outline critique, and visual QA. Use it before outline authoring when the deck
needs to be rebuildable, sourced, or personalized.
When user preferences are underspecified and personalization matters, ask the
optional intake questions with `scripts/emit_deck_intake_prompt.py`. Store
answers or assumptions in `design_brief.user_intake`, then translate them into
the actual taste layer: `visual_system`, `design_modulation`,
`title_page_concept`, `deck_style`, `asset_plan`, and `notes.md`.
Before writing the outline, use `scripts/emit_design_contract_prompt.py` to
lock a reproducible design contract: base preset, palette, background system,
header/footer treatment, content-led slide order, asset posture, source policy,
continuity rules, analysis artifacts, readability thresholds, speed policy, and
QA gates.
## Design DNA
Before rendering, choose a deck DNA that controls motif, pacing, density, and
which treatments are appropriate. Good decks vary by argument, not by randomizing
slides:
For non-trivial decks, resolve `style_execution_plan_v1` and its
`renderer_role_contracts_v2` contract before outline authoring. Select one of the
eight composition grammars from audience, evidence shape, and argument. Keep
its reading path, grid, frame, and role systems coherent; adapt variants to the
actual evidence and borrow at most two bounded treatments from secondary
influences.
- Lab results dashboard: figure/table first, compact semantic fills,
restrained navy header, captions and interpretation strips. Icons are
usually wrong here unless they label workflow steps.
- Board risk memo: dark opener, status colors, risk matrix, timeline, owner
table, and direct decision language.
- Product/investor reveal: one cinematic KPI or hero moment, asymmetric
product/value cards, map or product visual, launch timeline, clear ask.
- Editorial report: masthead cover, warm paper/serif tone, artifact or concept
imagery, fewer larger text blocks, deliberate whitespace.
- Civic science policy: map/data anchor, policy tradeoff matrix, accessible
plain-language captions, source lines, and implementation table.
Use `deck_style.page_system`, `structural_motif`, `header_mode`, `title_layout`, `title_motif`,
`section_motif`, `timeline_mode`, `matrix_mode`, and `stats_mode` only to
reinforce the chosen DNA. Do not mix multiple DNA patterns in one short deck.
If the cover uses chips, tags, or stage labels, carry them forward as a small
system on later slides; a motif that appears only on slide 1 reads as a
template artifact.
`renderer_role_contracts_v2` is the structural contract. It assigns distinct,
normalized semantic slots to title, section, evidence, comparison, chart,
table, decision, and references while preserving editable PowerPoint objects.
The model can choose `primary`, `alternate`, or `dense` per slide, but cannot
inject arbitrary coordinates. Resolution order is explicit slide override,
v2 grammar contract, v1 role system, then legacy renderer. Flat treatment
fields remain compatible fallbacks; they must not override the role system
merely to create novelty.
Alternate layouts may change emphasis, but should not mirror numbered steps
out of their source reading order. Peer boxes in a row share aligned edges;
unequal sizes should signal a deliberate hierarchy, not incidental text length.
Keep labels, indices, and body copy clear of both panel edges and each other.
New workspaces use v2. A workspace with only `renderer_role_systems_v1` stays
on v1 until `scripts/upgrade_renderer_role_contracts_v2.py` is run; repeated
upgrades are no-ops.
## Elevation & Depth
Cards may use a light shadow or fine border, but the deck should not become a stack of floating panels. Use depth to separate functional content groups, not as decoration.
## Shapes
Cards may use modest radii only when they do not have edge-attached accents. If a top/side accent rail, header strip, or flush overlay touches the card edge, use a rectangular card body so the accent aligns cleanly. Avoid gratuitous accent lines around titles; a restrained report rule is valid when it serves hierarchy.
## Components
Title slides must not all share one house template. Pick a cover archetype that
matches the deck DNA: lab plate, command center, poster, masthead, light atlas,
broadsheet, or split hero. Content slides use a dark header bar, clean lab header, or
clearly reserved header stack. Generated-image slides must be standalone and
labeled as generated, with prompt/model/purpose metadata visible so the slide
can be deleted without affecting the deck narrative.
Do not use an empty translucent rectangle as a substitute for a missing hero
image or proof object. When no meaningful visual exists, let typography and
whitespace carry the cover.
Avoid repeating four equal cards as the default rhythm. Use feature-left stats,
policy bands, open quadrants, staggered timelines, or open editorial events
when the content is not truly modular.
Timelines should not always be rail-and-card diagrams. Use simple report bands
for academic/ops updates, a chapter-spread when one milestone anchors the
story, and open events only when the spacing itself carries meaning. If the
slide is really a process, figure, or comparison, do not force `timeline`.
Rhythm breaks are optional, not mandatory. Use `kpi-hero` only when one number
or date genuinely carries the decision. If the deck is an academic update,
methods summary, or lab-results readout, a plain table, figure, standard slide,
or bottom takeaway box is usually better than a forced hero slide.
## Academic, Lab, And Data Decks
Use the `lab-report` preset or another restrained light preset. Credibility
comes from evidence-led layouts and clean report slides, not decorative icons:
put plots, workflow screenshots, microscopy/gel/readout panels, tables, method
diagrams, or concise bullets in the main region. For simple academic decks,
a restrained white canvas with a black heading, simple bullets or tables,
rectangular highlights, footer rule, sources, and page number is fully valid.
Use a bottom takeaway box only when it
helps the presenter state the result without editing formatting manually. Use
9-11pt captions for assay/run/source metadata, optional navy headers, and semantic
red/green/blue/orange accents for genotype, control, pass/fail, or risk states.
For `lab-clean` report slides, `header_variant: "auto"` is optional; a fixed
plain heading can keep a report consistent. Auto rotates among restrained
left-accent, split-rule, title-rule, side-rail, top-bottom-rule, and plain
heading/rule combinations. Set a short deck-level `style_seed` in
`deck_style` or `style_system` when two similar lab reports should keep
different but reproducible treatment rhythm. When a `style_mix_matrix` is
present, the same seed resolves compatible title, footer, section, timeline,
matrix, stats, cards, chart, and callout pools before rendering. Use
`top-bottom-rule` for a light report-page chrome with a subtle shaded band
under the top rule, and `plain` when figures or tables need no header rule at
all.
Keep provenance compact with `footer_mode: "source-line"` so sources, refs, and
page numbers sit below the bottom rule without crowding the evidence region.
Use `variant: scientific-figure` for 2-4 figure-panel slides with subfigure
labels and compact captions. Use `variant: image-sidebar` for one large figure
plus interpretation, and `variant: lab-run-results` for compact
result dashboards with multiple editable tables, semantic green/red/yellow
cell fills, small footnotes, and a short interpretation strip. Then use
`table`, `flow`, `stats`, and `comparison-2col` before generic card grids.
Preflight errors on more than 4 scientific-figure panels because the renderer
lays out only the first 4.
Icons are optional; use them for conceptual cards or timelines, not as
substitutes for evidence figures or result tables.
Generated plots should be exported for the slide, not for a manuscript page.
The figure script should set aspect ratio for the target layout, use tight
Matplotlib bounding boxes, trim exterior whitespace, and keep the actual data
region large. If three or four detailed panels make plots tiny, use one large
`image-sidebar` figure or split the evidence across slides.
Flow diagrams are optional and should not be used as a generic rhythm break.
Use `flow` only when a method, architecture, assay path, or operating sequence
is itself the evidence. Keep visible rows to four boxes; if there are more
steps, split the process, summarize stages, or use a table/timeline. The
fallback Mermaid renderer caps rows at four boxes and balances long flows, but the
better design choice is often to avoid the diagram entirely.
## Do's and Don'ts
Do choose a topic-fit palette, give every content slide a clear reading path, keep source/provenance visible when useful, and run geometric plus visual QA before declaring a deck done.
Do not repeat a layout mechanically, center body text, mix incompatible presets inside one deck, use qualitative text as a giant KPI, force a hero slide when no single metric deserves it, or bury generated imagery inside evidence slides without disclosure. A consistent series of report pages may reuse the same structure when the evidence calls for it.
For public-topic decks, use source-backed imagery when it strengthens the
argument. A small number of Wikimedia/CC images with visible source metadata
is better than many decorative visuals. When external assets are staged, keep
`assets/attribution.csv` and let the renderer add an editable Image Sources
slide unless a custom credits slide already exists.
## Review Loop
The quality loop is source edit → build → QA → rendered review → source edit
again. Use `scripts/visual_review.py` after the normal QA gate to create a
contact sheet and flag orphan-word, title-wrap, safe-area, footer-clearance, and
variant-rhythm risks. Treat it as a punch list for source edits, not a reason to
patch the generated `.pptx` directly.
Also inspect for motif continuity and figure readability: evidence tags from
the opener should recur intentionally, and figure panels should not contain
small islands of plotted data inside large white fields.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |