v1.5.0 — bulleted cards

build-deck: bulleted cards

The cards slide type now takes an optional bullets[] array per card, rendering a scannable bulleted list instead of a paragraph body.

type: cards
cards:
  - num: "01"
    title: Platform & systems at scale
    role: Amazon · AWS
    bullets:
      - Shipped storage virtualization at AWS to millions of users
      - Founding engineer on Kindle Fire Tablet and Echo / Alexa
      - Architect of Amazon's Common OS

• body stays optional — a bullet-only card emits no empty body.
• Bullet markers follow the card accent (primary/accent); dense mode shrinks the bullet font.
• Turns crowded multi-clause cards (intros, per-product challenge breakdowns) into clean, scannable bullets.

Issue #17 · PR #18

v1.4.0 — proscons grid subtype

build-deck: proscons grid subtype (multi-option comparison)

The proscons slide type now compares several options that each carry their own pros and cons.

Grid subtype

Add an options[] array and proscons renders N side-by-side split cards — each option a light PROS zone over a dark CONS zone, with a title / role header and an optional accent ring on the leading option:

type: proscons
title: Business model — options, with trade-offs
options:
  - title: B2C
    role: Direct to user
    pros: [Fastest feedback and brand, Viral reach in AI-native circles]
    cons: [High CAC, Fragile retention]
  - title: B2B2C
    role: Current hypothesis
    accent: true
    pros: [...]
    cons: [...]
footer: ...            # optional; footer_emphasis: true for the callout box

• Reuses the same --pc-* tonal variables; wired into the per-theme card overrides (Aurora glass, Brutalist sharp) and the Present-mode entrance cascade, so it adapts across all 8 themes.
• Absent options, the original single stacked pros/cons layout (v1.3.0) is unchanged.

Issue #15 · PR #16 · design note in build-deck/docs/

v1.3.0 — pros/cons slide type + type-scale refinements

build-deck: pros/cons slide type + type-scale refinements

New proscons slide type

Trade-offs render as two stacked, contrasting panels — pros in a light raised card (top), cons in an inverted dark card (bottom). Tonal contrast (no green/red) driven by theme-aware --pc-* CSS variables, with tuned overrides for Carbon, Dusk, Aurora (glass), and Brutalist so the split adapts natively across all 8 themes. Optional pros_label / cons_label / footer.

type: proscons
title: Build the renderer in-house?
pros: [Advantage one., Advantage two.]
cons: [Drawback one., Drawback two.]
footer: Optional recommendation.   # optional

The skill now mandates proscons for any trade-off (pros/cons, benefits/risks, for/against) rather than a plain bullet list.

Type-scale refinements (from deck review)

• Hero title smaller (clamp(96-152px) -> clamp(68-108px)).
• Vision line larger (18 -> 23px).
• Body text +1.5px across every slide type.
• Roadmap: renamed subnets / "SUBNETS / SCOPE" -> scope / "SCOPE".
• Fixed stale "4 themes" doc references (the renderer has 8).

Verification

Rendered the proscons sample full-bleed across Terracotta, Carbon, Brutalist, Aurora, and Dusk — the light/dark split reads clearly on every theme; footer and page numbers render in Review mode and PDF export.

Issue #13 · PR #14 · design note in build-deck/docs/

v1.2.0 — nano-banana image generation skill

nano-banana — new skill

Wraps Google's Gemini image-generation API (Nano Banana family) so Claude / Claude Code can generate or edit images programmatically from any session. Before this, the only path was pasting prompts into the Nano Banana UI by hand.

Highlights

• Stdlib-only Python CLI — no requests, no google-genai dependency. Single-file generate.py.
• Default model: gemini-3.1-flash-image-preview (newest flash-tier image model, 16:9 native).
• Pro tier: --model nano-banana-pro-preview for higher fidelity hero/deck images.
• Stable fallback: --model gemini-2.5-flash-image if the preview goes flaky.
• Image edit / image-to-image: pass --input ref.png (repeatable for multi-reference composition).
• Documented model catalog in SKILL.md, including the gemini-3.5-flash text-only gotcha (returns finishReason: NO_IMAGE).

Setup

export GEMINI_API_KEY="..."   # https://aistudio.google.com/apikey
python3 ~/.claude/skills/nano-banana/generate.py \
  --prompt "editorial photo of …" \
  --out output.png

Tracking

• Issue: #11
• PR: #12

Full diff: v1.1.0...v1.2.0

v1.1.0 — build-deck motion

A three-layer motion system for build-deck's Present mode. All CSS-only, no new dependencies, fully gated by prefers-reduced-motion.

What's new

Layer A — Slide transitions

When you advance to the next slide in Present mode, the swap is animated. Four variants:

• Fade — opacity in/out
• Slide — translateX in/out with cross-fade
• Zoom — scale + opacity, atmospheric
• Cut — no animation (deliberate, for Brutalist)

Each theme has a default; a new Motion dropdown in the topbar lets you override.

Theme	Default	Theme	Default
Terracotta	Fade	Mono	Slide
Carbon	Slide	Aurora	Zoom
Berry	Fade	Brutalist	Cut (deliberate)
Lab	Slide	Dusk	Fade

Selection persists to localStorage.deck-transition.

Layer B — Element entrance cascade

When a slide becomes current, its title, subtitle, and cards / pillars / nodes stagger in over ~500ms. Brutalist and Lab deliberately opt out.

Layer C — Per-theme background motion

Each theme has a distinct background-motion signature in Present mode:

• Aurora — gradient hue-drift, 20s loop
• Mono — dotted-grid pulse on each slide change
• Carbon — scanline drift, 8s loop
• Berry — vignette breathe, 8s loop
• Terracotta — paper grain texture (static — warmth, no motion)
• Brutalist + Lab — deliberately static
• Dusk — none in v1.1 (particle field deferred to v1.2, needs JS)

Reduced motion

All animations are gated by @media (prefers-reduced-motion: no-preference) and overridden by a blanket kill switch when the OS reports prefers-reduced-motion: reduce. Decks stay fully functional — transitions become instant, looping animations stop.

Design and plan

• Design doc
• Implementation plan

What's next

v1.2 — Publish & Share:

• make publish DECK=<name> → Cloudflare Pages
• Single-file HTML bundle (make bundle DECK=<name>)
• Speaker mode (BroadcastChannel)
• Password protection / signed URLs

Closes #5.

v1.0.0 — build-deck v2 + write-doc

First tagged release of claude-skills. Two skills, both production-ready.

Skills

build-deck — themed slide decks

• Dual-mode renderer. Review (scroll all slides) and Present (one slide fills viewport), toggle in the topbar, state persisted to localStorage.
• Present mode chrome. Top progress hairline (width = current/total), floating bottom nav bar (Prev · NN / MM · Next) that fades after 2s of mouse idle, on-slide page numbers (also visible in PDF export).
• Keyboard nav. ← / → / Space / Home / End / Esc.
• 8 themes, each with distinct typography and chrome (not just recolored):
  • Terracotta — warm cream + terracotta + serif. Strategic narrative.
  • Carbon — premium dark + electric lime + warm orange. Technical / fundraising.
  • Berry — cream + berry + italic serif. Editorial.
  • Lab — minimal off-white + magenta + mint, no slide borders. Product / clinical.
  • Mono — pure white + cyan, monospaced titles, dotted left bar. Modern tech.
  • Aurora — violet→teal gradient + glass cards + light-weight titles. Vision / future.
  • Brutalist — stark white + black + chartreuse, Archivo Black ALL CAPS, 3px frame. Manifesto.
  • Dusk — plum-dark + lavender + peach, italic serif hero. Premium dark.
• Theme dropdown replaces the chip row (scales to N themes).
• PDF export works from both modes; one slide per page, 16:9 (13.333in × 7.5in), page numbers survive print.
• Bug fix. A duplicated [data-theme=\"terracotta\"] CSS selector was silently applying Carbon's tokens. Fixed.

write-doc — markdown → themed PDF

Source is .md; rendering is pandoc + headless Chromium via `make pdf DOC=`. Themes: terracotta, carbon, berry, lab.

Design + plan docs

The v2 design doc and implementation plan are in build-deck/docs/:

• 2026-05-18-v2-design.md
• 2026-05-18-v2-plan.md

Closes #1.