@jini-ai/agent-plugins 0.6.17 → 0.6.19

package/slide-design/skills/slide-design/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: slide-design
+version: 0.1.0
+last_updated: 2026-11-01
+description: Use when planning, writing, designing, reviewing or fixing slides or a presentation deck (pitch, talk, teaching, status update, report or decision deck), including the storyline, slide titles, charts, 16:9 layout, speaker notes, accessibility and HTML decks.
+---
+
+# Skill: Slide Design
+
+A good deck makes one point per slide, and the slides add up to one message.
+This skill covers the thinking and the design. It renders nothing itself.
+
+## Modes
+
+- **New deck** — run the workflow below.
+- **Fix my slide / fix my deck** — go to `references/review.md`, "Fix one slide".
+- **Review only** — run the checklist in `references/review.md` and report by severity.
+- **Outline only** — stop after step 3.
+
+## Workflow
+
+1. **Brief.** Get these. Ask only for what you can't infer; otherwise state your assumptions and go on.
+   - Audience: who they are, what they already know, what they care about.
+   - Goal: what they should think or do afterwards, in one sentence.
+   - Setting: presented live, read alone, or both. Room, video call or printed.
+   - Length: minutes available. Rough guide: 1 slide per 1–2 minutes when presented.
+   - Deck type: pitch, talk, teaching, update, report or decision (`references/storyline.md`).
+   - Brand: the host's theme, a brand the user gives, or the neutral default.
+   - Material: data, images, logos, quotes and anything that must appear.
+2. **Story shape.** Write the deck's message as one sentence. Pick the structure for the deck type
+   (`references/storyline.md`).
+3. **Titles-only outline.** List every slide as a takeaway title plus one line saying what evidence
+   it will show. Read the titles alone: they must tell the story. Show the outline before building
+   when the deck has more than 5 slides or the stakes are high. If the host runs without a user in
+   the loop, show it and continue.
+4. **Build.** For each slide: title, visual or text, speaker notes, source.
+   Charts: `references/charts-and-exhibits.md`. Layout, type, colour, images, accessibility:
+   `references/layout-and-style.md`. HTML output: `references/html-deck.md`.
+5. **Review.** Run `references/review.md`. Fix every blocker before you hand the deck over.
+   If the host can take screenshots, look at every slide.
+
+## Core rules
+
+1. One message per slide. Its title states that message by default; `references/storyline.md`
+   lists the exceptions.
+2. Read in order, the titles tell the whole story.
+3. Answer first in update, report and decision decks; detail follows.
+4. The body proves the title. Anything else goes to notes or the appendix.
+5. Show before you list: chart, diagram, image or big number before bullets.
+6. Text must read from the back of the room: body at least 18 pt (36 px at 1920×1080).
+7. Neutral colours plus one accent. The accent marks what to look at.
+8. Everything sits on one grid. Titles, sources and slide numbers never move.
+9. Every presented slide has speaker notes.
+10. Accessible by default: contrast, alt text, reading order, never colour alone.
+11. Never invent data, quotes or sources. Keep observations, estimates and causal evidence
+    distinct; a before/after trend shows timing, not cause.
+
+## Output
+
+Default: an outline and slide specs in chat, one block per slide:
+
+```
+### 4. Churn fell by a third after the onboarding rollout
+Visual: line chart, monthly churn Jan–Oct; months after rollout in accent; dashed line at the 6% target
+On slide: "Rollout, Mar" callout; y-axis "Monthly churn, %"
+Notes: The point: churn declined after rollout; attribution needs further evidence, such as a
+  cohort comparison. Look at March... (40–120 words)
+Alt: Line chart: churn fell from 8.1% to 5.4% after the March rollout.
+Source: Billing data, Jan–Oct 2026
+```
+
+All figures in this skill's examples are illustrative.
+
+Other outputs:
+- **HTML deck** — one HTML document, one section per slide (`references/html-deck.md`).
+- **PowerPoint, Keynote, Google Slides** — give the slide specs. Use a host export tool if one
+  exists; this skill doesn't produce those files.
+
+## Host tool use
+
+- Find the host's tools first (tool search or tool list). Use what fits:
+  - page or HTML tools to publish the deck;
+  - theme tools to read colour and font tokens;
+  - media tools to find or upload images;
+  - screenshot tools to check each slide;
+  - chart tools, if the host has them, to render charts.
+- With no such tools, answer with slide specs, or one self-contained HTML file, in chat.
+- Don't install packages or run shell commands to make a deck unless the host says you may.
+- Ask before overwriting an existing page or deck.
+- The host may add its own instructions. They win over this section.
+
+## References
+
+Load only what the task needs.
+
+- `references/storyline.md` — deck types and their structures, answer-first, the opening, titles,
+  summary slide, outline, closing slide, speaker notes.
+- `references/charts-and-exhibits.md` — choosing a chart from the question, finishing it,
+  tables, diagrams, numbers, icons.
+- `references/layout-and-style.md` — 16:9 canvas, grid and spacing numbers, type sizes, density,
+  colour roles, images, accessibility, slide types.
+- `references/review.md` — checklist by severity, fixing one slide, long decks.
+- `references/html-deck.md` — an HTML deck: structure, CSS, reading copy, notes, printing, checks.

package/slide-design/skills/slide-design/references/charts-and-exhibits.md

@@ -0,0 +1,100 @@
+# Charts and exhibits
+
+An exhibit is the proof for its slide's title. Write the title first, then pick the form.
+
+## Pick the form from the question
+
+| The title says… | Use | Avoid |
+|---|---|---|
+| A is bigger than B (compare items) | Horizontal bars, sorted | Pie, 3D, radar |
+| It went up or down (change over time) | Line for many points; columns for a few periods | Area stacks with many series |
+| X is most of the total (share) | One 100% bar, or a pie with ≤ 3 slices and one highlighted | Donut with many slices |
+| Values spread out or cluster (distribution) | Histogram, box plot, dot strip | An average alone |
+| X moves with Y (relationship) | Scatter, with a trend line if useful | Two lines on two y-axes |
+| We got from A to B because… (bridge) | Waterfall | Stacked columns |
+| Who leads (ranking) | Sorted bars or dot plot | Unsorted bars |
+| Where it happens (place) | Map, only if location matters; otherwise bars | Choropleth of raw counts |
+| One number matters | Big number with its comparison | Gauge, speedometer |
+| When things happen (plan) | Timeline or Gantt | Bulleted dates |
+
+Use several aligned charts on one slide when they support the same takeaway. Different takeaways
+get different slides.
+
+## Finish the chart
+
+Make the chart say the title, in this order. Steps 2, 4 and 5 are defaults, not laws:
+
+1. **Strip.** Remove borders, background fills, 3D, shadows and heavy gridlines. Keep light
+   gridlines only if people need to read values.
+2. **Mute.** Draw supporting data in a neutral grey. When series are categories people must tell
+   apart (products, regions), keep their colours from the deck's colour key instead.
+3. **Highlight.** Put the one bar, line or point that proves the title in the accent colour.
+4. **Label directly.** Name lines at their ends and put values on the bars that matter, then drop
+   the legend. If direct labels would collide, keep a compact legend. Drop the value axis if
+   every bar is labelled.
+5. **Add a reference** only when it means something here: target, average, last year or plan, as
+   a thin dashed labelled line.
+6. **Annotate.** One short callout where it matters ("Launch, Mar"), with a thin leader line if
+   needed. Two at most.
+7. **Round.** 2–3 significant figures. Units once, in the axis title or label. Same units across
+   the deck.
+8. **Source.** A small line at the bottom left: "Source: <who>, <date>".
+
+## Axes and honesty
+
+- Ordinary bars and columns that show magnitude start at zero. Lines may zoom in if the axis is
+  clearly labelled.
+- Waterfalls: the start and end bars rise from zero; each change bar floats from the previous
+  running total. Label the start, every change and the end.
+- Charts shown side by side share a scale.
+- No dual y-axes. Use two aligned charts instead.
+- Time runs left to right.
+- Rank bars largest to smallest, top to bottom. Leave built-in sequences as they are: periods,
+  age bands, rating scales from "disagree" to "agree".
+- Show uncertainty when it changes the decision: a range, error bars, "est.".
+- Don't cherry-pick the time window. If you crop it, say why in the notes.
+
+## Tables
+
+Use a table when people need exact values to look up.
+
+- Presented: at most about 6 rows and 5 columns. Bigger tables go to the appendix.
+- Right-align numbers and use the same decimals in a column.
+- Thin row separators only; no full grid.
+- Mark the row or cell that matters with weight or the accent.
+- Header row and first column in plain words, with units.
+
+## Diagrams
+
+- **Process:** 3–6 steps left to right. Use arrows only for a real sequence.
+- **2×2:** two axes that really are independent, each end labelled (low/high). Place items as
+  dots. Name the quadrants only if that helps.
+- **Breakdown tree:** whole on the left or top, parts after it. Parts don't overlap and add up to
+  the whole.
+- **Option comparison:** 2–4 options as columns, the same criteria as rows. Mark the chosen
+  option with the accent.
+- **Layers or pyramid:** only for a real hierarchy or stack.
+- **Overlap circles:** only for real overlap, with the shared part labelled.
+
+Rules for all diagrams: same shape for the same kind of thing, one line weight, text inside
+shapes at body size or larger, no decorative arrows or 3D.
+
+## Numbers on slides
+
+- A big-number slide: one figure, 160–240 px at 1920×1080, with what it measures and its
+  comparison ("+18% vs. plan").
+- Format the same way everywhere: 1.2M, 34%, $4.5k.
+- Don't rely on green and red to mean good and bad. Say "better" or "worse", or use arrows.
+- Check every total adds up and every number matches across slides.
+
+## Screenshots and photos as evidence
+
+- Crop to the part that matters, then enlarge it.
+- Point at the detail: an outline box, or dim everything else.
+- Screenshots must be current and readable at slide size. Blur personal or secret data.
+
+## Icons
+
+- One family, one style (line or filled), one colour (neutral or the accent).
+- Use an icon only when it adds meaning. Not one on every bullet.
+- Prefer the literal icon to the clever one, and still label it.

package/slide-design/skills/slide-design/references/html-deck.md

@@ -0,0 +1,175 @@
+# HTML deck
+
+Build the deck as one HTML document when the host can publish pages or HTML, or when the user
+wants a file. It works in any browser, presents full screen, and prints to PDF.
+
+## Structure
+
+- One document. One `<section class="slide">` per slide, in presenting order.
+- One unique heading per slide (`<h1>` on the title slide, `<h2>` after) in an `<hgroup>` with an
+  optional kicker. The `<hgroup>` is a fixed-height header zone, so bodies never shift.
+- Speaker notes go in `<aside class="notes">` as the slide's last child. Hidden when presenting.
+- Use real elements: lists, `<figure>` and `<figcaption>`, `<img alt>`, `<table>` with `<th>`.
+- Source order is the reading order: title, then content in speaking order, then source.
+- No script is needed. Scroll snap steps through slides with arrow and Page Down keys.
+- **Presentation copy:** design pixels at 1920×1080 (`layout-and-style.md`) scaled by one unit,
+  `--u`, so a slide fills the screen and prints as one page. Browser zoom can't enlarge it.
+- **Reading copy:** `class="reading"` on `<html>`. `rem` text that zoom enlarges, slides that
+  grow, no clipping, one column on narrow screens, notes shown. It doubles as the speaker copy.
+  Publish or send it alongside the presentation copy.
+
+## Template
+
+The figures in this template are illustrative.
+
+```html
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>Onboarding review</title>
+<style>
+  :root {
+    /* Set these from the host theme tokens or the user's brand. Fallbacks = neutral default. */
+    --deck-bg: #ffffff; --deck-text: #1a1a1a; --deck-muted: #6b6b6b;
+    --deck-line: #d4d4d4; --deck-accent: #2563eb; --deck-font: system-ui, sans-serif;
+    /* One design pixel of a 1920x1080 slide, fitted to the window. */
+    --u: calc(min(100vw, 100vh * 16 / 9) / 1920);
+  }
+  * { box-sizing: border-box; }
+  html { scroll-snap-type: y mandatory; }
+  body { margin: 0; background: #111; font-family: var(--deck-font); }
+  .slide {
+    position: relative; overflow: hidden; scroll-snap-align: center;
+    width: calc(1920 * var(--u)); height: calc(1080 * var(--u));
+    margin: 0 auto calc(16 * var(--u));
+    padding: calc(80 * var(--u)) calc(96 * var(--u)) calc(64 * var(--u));
+    background: var(--deck-bg); color: var(--deck-text);
+    font-size: calc(40 * var(--u)); line-height: 1.35;
+  }
+  /* Header zone: kicker + two 72px title lines, the same height on every slide. */
+  .slide hgroup { min-height: calc(220 * var(--u)); margin: 0 0 calc(32 * var(--u)); }
+  .slide h1, .slide h2 { margin: 0; line-height: 1.15; max-width: calc(1500 * var(--u)); }
+  .slide h1 { font-size: calc(104 * var(--u)); }
+  .slide h2 { font-size: calc(72 * var(--u)); }
+  .kicker { margin: 0 0 calc(16 * var(--u)); font-size: calc(28 * var(--u)); color: var(--deck-muted);
+    text-transform: uppercase; letter-spacing: .06em; }
+  .grid { display: grid; grid-template-columns: repeat(12, 1fr); column-gap: calc(24 * var(--u)); }
+  .span-4 { grid-column: span 4; } .span-6 { grid-column: span 6; }
+  .span-8 { grid-column: span 8; } .span-12 { grid-column: span 12; }
+  .big-number { font-size: calc(200 * var(--u)); font-weight: 700; line-height: 1; color: var(--deck-accent); }
+  .accent { color: var(--deck-accent); }
+  .slide figure { margin: 0; }
+  .slide img { display: block; max-width: 100%; height: auto; }
+  .source, .slide-number { position: absolute; bottom: calc(24 * var(--u)); margin: 0;
+    font-size: calc(22 * var(--u)); color: var(--deck-muted); }
+  .source { left: calc(96 * var(--u)); }
+  .slide-number { right: calc(96 * var(--u)); }
+  .notes { display: none; }
+  /* Reading and speaker copy: <html class="reading">. */
+  html.reading { scroll-snap-type: none; } .reading body { background: var(--deck-bg); }
+  .reading .slide { width: auto; max-width: 64rem; height: auto; overflow: visible; margin: 0 auto;
+    padding: 2rem 1.5rem; font-size: 1.25rem; border-bottom: 1px solid var(--deck-line); }
+  .reading .slide hgroup { min-height: 0; margin-bottom: 1rem; }
+  .reading .slide h1 { font-size: 2.5rem; } .reading .slide h2 { font-size: 1.75rem; }
+  .reading .kicker, .reading .source, .reading .slide-number { font-size: 1rem; }
+  .reading .source, .reading .slide-number { position: static; margin-top: 1rem; }
+  .reading .big-number { font-size: 4rem; } .reading .grid { column-gap: 1.5rem; row-gap: 1rem; }
+  .reading .notes { display: block; margin-top: 1.5rem; padding-top: 1rem;
+    border-top: 1px solid var(--deck-line); font-size: 1.125rem; color: var(--deck-muted); }
+  @media (max-width: 48rem) { .reading .grid { grid-template-columns: 1fr; } .reading .grid > * { grid-column: 1 / -1; } }
+  @page { size: 13.333in 7.5in; margin: 0; }
+  @page reading { size: auto; margin: 0.6in; }
+  @media print {
+    :root { --u: calc(13.333in / 1920); }
+    html { scroll-snap-type: none; }
+    body { background: none; }
+    .slide { margin: 0; break-after: page; -webkit-print-color-adjust: exact; print-color-adjust: exact; }
+    /* The reading copy flows across ordinary pages; long notes may span a page break. */
+    .reading main { page: reading; }
+    .reading .slide { break-after: auto; padding: 0 0 1.5rem; }
+  }
+</style>
+</head>
+<body>
+<main>
+  <section class="slide" aria-labelledby="s1">
+    <hgroup><h1 id="s1">Onboarding v2: three months of results</h1></hgroup>
+    <p>Product review · Ana Silva · 3 Nov 2026</p>
+    <aside class="notes">One-line point of the talk, then what you'll cover.</aside>
+  </section>
+
+  <section class="slide" aria-labelledby="s2">
+    <hgroup>
+      <p class="kicker">Retention</p>
+      <h2 id="s2">Churn fell by a third after the onboarding rollout</h2>
+    </hgroup>
+    <div class="grid">
+      <figure class="span-8">
+        <img src="churn.png" alt="Line chart: churn fell from 8.1% to 5.4% after the March rollout.">
+      </figure>
+      <p class="span-4">The biggest drop came in a customer's <strong class="accent">first 30 days</strong>.</p>
+    </div>
+    <p class="source">Source: billing data, Jan–Oct 2026</p>
+    <p class="slide-number">2</p>
+    <aside class="notes">The point: churn declined after rollout; attribution needs further
+      evidence, such as a cohort comparison. Look at March...</aside>
+  </section>
+
+  <section class="slide" aria-labelledby="s3">
+    <hgroup><h2 id="s3">Roll the new onboarding out to every plan by January</h2></hgroup>
+    <p>Ask: approve two engineers for six weeks.</p>
+    <p>Questions: ana@example.com</p>
+    <aside class="notes">Restate the ask, then take questions with this slide up.</aside>
+  </section>
+</main>
+</body>
+</html>
+```
+
+Adapt, don't copy blindly: change the variables, keep the unit, add slide types from
+`layout-and-style.md` as needed.
+
+## Brand and theme
+
+- If the host has a theme, read its colour and font tokens and set the `--deck-*` variables from
+  them, for example `--deck-accent: var(--theme-accent, #2563eb)` with the host's real token name. Don't hard-code colours
+  the theme already defines.
+- With a user brand, use its hex codes and fonts. Load web fonts only from sources the host allows.
+- Check contrast after mapping. Theme colours made for a website can fail on a projector.
+
+## Charts and images
+
+- Use the host's chart tool or plugin if it has one, or an image of the chart. Simple bars can be
+  inline SVG with `role="img"` and an `aria-label` that states the point.
+- Every chart needs a text alternative: alt text or a short caption with the key numbers.
+- Upload images through the host's media tools when it has them, and reference the stored URL.
+
+## Host limits
+
+- Some page tools accept only body content, strip `<style>` or `<script>`, or rewrite markup.
+  Keep the same structure and put the CSS where the host allows: a style block, theme custom CSS,
+  or inline styles. Then check a screenshot.
+- Ask before replacing an existing page. Publish as a draft or unlisted page if the host can.
+
+## Presenting and exporting
+
+- Present: open the page, go full screen (F11, or the browser's full-screen command), and use the
+  arrow or Page Down keys.
+- PDF: print, choose "Save as PDF". The presentation copy prints one 16:9 page per slide. Turn
+  on background graphics if the browser asks.
+- Speaker or reading copy: add `class="reading"` to `<html>` and print; it flows across ordinary
+  pages, notes included. Or list the notes in chat.
+- PowerPoint, Keynote or Google Slides: out of scope here. Hand over the slide specs, or use a
+  host export tool if one exists.
+
+## Checks
+
+- Screenshot each slide at a 1920×1080 viewport. Text must not run past the margins; overflow is
+  hidden, so look.
+- Print preview of the presentation copy shows one slide per page, nothing cut off.
+- Reading copy at 200% browser zoom and at a phone width: text grows, nothing is clipped, the grid
+  is one column, notes show.
+- Contrast passes; every image has alt text; headings are unique and in order.
+- The page still makes sense with CSS off: headings, then content, in speaking order.

package/slide-design/skills/slide-design/references/layout-and-style.md

@@ -0,0 +1,131 @@
+# Layout and style
+
+All sizes are for a 16:9 slide designed at 1920×1080 px. On a 13.33 × 7.5 in slide
+(PowerPoint's 16:9 default), 1 pt = 2 px.
+
+## Canvas and grid
+
+- **Margins (safe area):** 96 px left and right, 80 px top, 64 px bottom. All text stays inside.
+  Full-bleed images may run to the edge.
+- **Grid:** 12 columns inside the margins, 24 px gutters. Content width 1728 px, each column
+  122 px.
+- **Common splits:** 12 (full width), 6 + 6, 4 + 8 (text + visual), 8 + 4 (visual + text),
+  4 + 4 + 4, 3 + 3 + 3 + 3.
+- **Spacing scale:** 8, 16, 24, 32, 48, 64, 96 px. Use 16–24 inside a group and 48–64 between
+  groups. The same relationship always gets the same gap.
+- **Header zone:** starts at the top margin, same height on every slide: room for a kicker plus
+  2 title lines (about 220 px with a 72 px title). The body starts below it, whatever the title's
+  length.
+- **Footer zone (optional):** the bottom 48 px. Source on the left, slide number on the right.
+
+## Type
+
+| Role | Size at 1920×1080 | Points |
+|---|---|---|
+| Title | 64–88 px | 32–44 pt |
+| Statement or section title | 96–128 px | 48–64 pt |
+| Big number | 160–240 px | 80–120 pt |
+| Body, presented | 40–48 px, never below 36 px | 20–24 pt, never below 18 pt |
+| Body, read alone | 28–32 px, never below 24 px | 14–16 pt, never below 12 pt |
+| Chart labels needed to read the chart | the body minimum: 36 px presented, 24 px read alone | 18 pt / 12 pt |
+| Source, footnote, footer (supplementary only) | 20–24 px | 10–12 pt |
+
+- Lines up to about 60 characters. Line height 1.1–1.2 for titles, 1.3–1.4 for body.
+- At most 2 typefaces, or 1 family in 2 weights. Use the host theme's fonts when there are some.
+- Left-align text. Centre only title slides, statements and big numbers.
+- Emphasis by weight or the accent colour, not underline or long italics.
+- No all-caps sentences. Caps are fine for short labels with a little letter spacing.
+
+## Density
+
+- One message per slide, one focal point. The eye should land on the accent first.
+- Word budget, excluding chart labels: about 30 words presented, about 80 read alone.
+- Bullets: 3–5 per slide, at most 2 lines each, one level deep.
+- Too much? Split the slide, move detail to notes, or move it to the appendix.
+- Too little, or the same point as the slide before? Merge.
+
+## Alignment and grouping
+
+- **Gaps carry grouping:** use the 16–24 px step inside a group and 48–64 px between groups.
+  Never let a between-group gap shrink to an inside-group size.
+- **Parallel items share a style:** every option card, step or bullet in a set gets the same size,
+  fill and title weight. Change the style only to mark the highlighted item.
+- **Alignment:** every edge sits on a grid line. Title and body share one left edge.
+- **Repetition:** equal gaps between repeated items, equal sizes for parallel boxes.
+- **Consistency:** title, logo, source and slide number stay put across slides.
+- **Squint test:** view a thumbnail; structure and focal point should still show. A thumbnail
+  checks hierarchy; check legibility on the intended display.
+
+## Colour
+
+Where colours come from, in order:
+
+1. The host's theme tokens (primary or accent, text, background, fonts), read with its theme tools.
+2. A brand the user supplies: hex codes, logo, fonts.
+3. The neutral default: text #1A1A1A on #FFFFFF or #FAFAF7, grey #6B6B6B for secondary text and
+   muted data marks, #D4D4D4 for decorative separators and gridlines only, one accent #2563EB.
+
+Rules:
+
+- Give colours roles: background, text, muted text, neutral data, accent, and optionally
+  good and bad. Don't pick colours slide by slide.
+- One accent per slide for "look here". Use shades of one hue before adding a second hue.
+- Before building, write a colour key: each recurring category (product, region, segment) and its
+  hex. Every chart in the deck uses that key.
+- Light backgrounds suit read-alone decks and printing. Dark ones suit talks in dim rooms. Pick
+  one per deck.
+- At most about 5 colours in one chart. Group the rest as "Other".
+
+## Images
+
+- Show the real thing: the product, the people, the place. Skip generic stock.
+- Give images real space: full-bleed or a whole grid cell, not a small floating picture.
+- Text on an image only over a calm area or a dark overlay (at least 50% opacity), and the text
+  must still pass contrast.
+- Full-bleed images need at least 1920 px of width. Crop, never stretch.
+- Use only images the user owns, has a licence for, or generated with permission. Credit when
+  required.
+- Logos: official files, original colours, same visual height in a row.
+- Generated images: one style across the deck, no fake text inside them, check hands and faces,
+  show people inclusively.
+
+## Accessibility
+
+- **Contrast:** text at least 4.5:1 against its background. Large titles and chart marks at
+  least 3:1.
+- **Never colour alone:** add labels, patterns, icons or arrows. Avoid red and green pairs; blue
+  and orange read for most people.
+- **Alt text** for every meaningful image and chart. Say the point, not the look:
+  "Line chart: churn fell from 8.1% to 5.4% after the March launch." Decorative images get empty
+  alt text.
+- **Reading order:** title first, then content in the order you'd present it. In HTML that is the
+  source order; in slide apps, set the object order.
+- **Unique titles:** screen reader users jump between slides by title.
+- **Motion and media:** captions for video and audio, no flashing more than 3 times a second,
+  little motion.
+- **Plain words:** spell out an acronym the first time it appears.
+- Share the deck and notes as a file people can open on their own device (for HTML, the reading copy).
+
+## Builds and transitions
+
+- Use builds only to reveal points in the order you speak them.
+- One transition for the whole deck: a fade or none. No flying or spinning.
+
+## Slide types
+
+| Type | Layout |
+|---|---|
+| Title | Deck title, subtitle, presenter, date. Left-aligned or centred. |
+| Agenda | 3–5 items in the words the section dividers use. |
+| Section divider | Section name large, optional number. |
+| Statement | One sentence, 96–128 px, lots of space. |
+| Big number | The number, what it measures, its comparison. |
+| Chart | Takeaway title, chart over 8–12 columns, source in the footer. |
+| Text + visual | Text in 4 columns, visual in 8. |
+| Comparison | 2–4 equal columns with the same rows. |
+| Process | 3–6 steps across. |
+| Quote | The quote large, the person's name and role small. |
+| Full-bleed image | The image, plus at most one line of text. |
+| Summary | Message, 3–4 reasons, the ask. |
+| Closing | Message, ask or next step, contact. |
+| Appendix | Its own divider, then backup slides with full detail. |

package/slide-design/skills/slide-design/references/review.md

@@ -0,0 +1,93 @@
+# Review
+
+## How to review
+
+Work top-down and fix in that order. Don't polish a slide that will be cut.
+
+1. **Deck:** read the titles only. Is the message clear? Does the story flow? Do the type and
+   length fit the audience and the time?
+2. **Slide:** does the body prove the title? Is there one focal point?
+3. **Detail:** numbers, words, alignment, sizes.
+
+If the host can take screenshots, capture every slide at 1920×1080 and look at each one, then
+look at them small, side by side, for consistency. Ideally see it full screen on the real display.
+
+## Checklist by severity
+
+**Blocker** — fix before anyone sees the deck:
+
+- No clear deck message, or no ask in a pitch or decision deck.
+- A title claims something its slide doesn't show, or the data contradicts it.
+- Invented data, quotes or sources; a causal claim resting only on a before/after trend.
+- Wrong or inconsistent numbers: totals that don't add up, units that change.
+- Text below the minimum sizes, or contrast below 4.5:1 (3:1 for large titles).
+- Personal or confidential data on screen; images without the rights to use them.
+- Broken slides: text overflowing or cut off, missing images, placeholder text left in.
+- A typo in a title, a name, a number or a date. Check these letter by letter.
+
+**Major** — fix before presenting:
+
+- Titles are topic labels, or the title chain doesn't read. Image-only talk slides, dividers and
+  teaching questions are allowed exceptions (`storyline.md`).
+- More than one message on a slide; a wall of text.
+- The wrong chart for the question, no highlight, a legend where direct labels would fit, a
+  magnitude bar or column axis that doesn't start at zero (floating waterfall change bars are
+  fine, `charts-and-exhibits.md`).
+- Groups that overlap or leave gaps.
+- Fonts, colours or positions that change between slides; more than one accent on a slide.
+- Missing speaker notes on presented slides; missing alt text.
+- No closing slide with the next step.
+- Too many slides for the time.
+
+**Minor** — fix if there's time:
+
+- Elements off the grid by a few pixels; uneven gaps.
+- Number formats that differ; a chart without its source and date.
+- A title slide missing the deck title, presenter or date.
+- A single word alone on a title's last line.
+- Mixed icon styles.
+- Other typos.
+
+Report format:
+
+```
+Verdict: <one line: ready / ready after fixes / needs rework>
+Blockers
+1. Slide 4: title says churn fell, chart shows signups → chart monthly churn instead
+Major
+2. Slides 6–9: titles are labels ("Market") → rewrite as takeaways (proposed below)
+Minor
+3. Slide 11: source line missing → add "Source: CRM export, Oct 2026"
+```
+
+Give the fix with each problem, not just the problem.
+
+## Fix one slide
+
+1. **Find the message.** What is the slide trying to say? If its title doesn't say it, propose a
+   takeaway title and say it's your reading.
+2. **Give each element a destination** as you go: a text, figure, image or chart that proves the
+   message stays; context moves to the notes; detail someone may ask for goes to the appendix;
+   noise is cut. Write the destinations down; the user sees every cut.
+3. **Pick the form:** chart, diagram, comparison, big number or short text
+   (`charts-and-exhibits.md`).
+4. **Rebuild** on the grid, with the takeaway as the title (`layout-and-style.md`).
+5. **Check:** the message reads faster than before; sizes and contrast pass.
+6. Still two messages? Make two slides.
+
+Answer with: the new title, the new layout spec, where each moved or cut item went, and a short
+before → after.
+
+## Fix a whole deck
+
+Run the checklist, then fix in this order: message and outline, titles, one slide at a time,
+then consistency across slides. Show the new titles-only outline before rebuilding slides.
+
+## Long decks (15+ slides)
+
+- Section dividers whose words match the agenda.
+- Optionally a small section label at the top left so people know where they are.
+- Same header and footer and slide numbers throughout.
+- The appendix comes after the closing slide, under its own divider. Point to it from the body
+  ("see A3").
+- After every edit, check the summary slide still matches the body.