beam-ai-team/beam-ai-slide-library

Beam AI Slide Library

Use this skill when the task is slide-level: choosing, reusing, adapting, or exporting individual Beam slide patterns. This is separate from beam-ai-deck-templates, which owns full deck/report templates and design packs.

Asset root: ../../../design/beam-ai/slides from this skill directory.

Safety Contract

Require explicit user approval before promoting a draft slide into a shared library or shipping it in a customer-facing deck. Keep proprietary source screenshots, customer examples, and generated media tied to their approved asset folders and provenance notes.

Library Shape

• ../../../design/beam-ai/slides/README.md - human overview of the promoted slide library and Figma audit.
• ../../../design/beam-ai/slides/library.json - catalog of collections and individual slide entries.
• ../../../design/beam-ai/slides/figma-slides-library-audit.md - broader source Figma inventory, taxonomy, rename map, duplicate groups, and cleanup plan.
• ../../../design/beam-ai/slides/collections/ - full HTML reference decks that preserve runtime CSS, assets, manifests, audits, and compact QA evidence.
• ../../../design/beam-ai/slides/slide-library/ - Prism-shaped individual slide templates.
  • each slide folder contains slide.json
  • each HTML slide variant lives at variants/html-slide.html

The individual slide items are not themes. They are reusable content/layout patterns that should be paired with a Beam design pack, customer theme, or target deck runtime.

Current Collections

• beam-figma-test-page-editable-20 - 20-slide editable Beam Figma rebuild covering cover, about, thesis, platform, use cases, security, commercial, delivery, engagement, and closing patterns.
• beam-figma-skill-dogfood-7 - 7 high-fidelity slides rebuilt with the beam-figma-to-html-slides workflow and Figma-exported assets.
• beam-figma-new-library-9 - 9 additional library slides for case studies, ontology, discovery-to-ROI, production proof, and booth/activation patterns.

How To Use

1. Read library.json and shortlist slide patterns by role, category, or source collection.
2. Read README.md for the promoted slide inventory and counts.
3. Read figma-slides-library-audit.md when deciding which Figma slides should be promoted next.
4. Inspect the collection contact sheet before choosing a slide.
5. Use the individual slide-library/{slug}/slide.json entry when a Prism-compatible slide-library shape is needed.
6. Use the full collection index.html when you need the source runtime CSS or want to visually compare the slide in context.
7. When moving an individual HTML fragment into another deck, copy or rewrite its asset paths and apply the destination theme tokens.

Prism Notes

Prism already has an individual slide-library model:

• workspace path: slide-library/{slug}/slide.json
• HTML variant path: variants/html-slide.html
• API shape: DesignerSlideTemplate

These Beam Next slide-library items intentionally mirror that shape. Prism can create and use individual slides inside a workspace, but a polished one-click exporter from Prism to Beam Next is still a follow-up. Until then, keep using the manual export pattern in this skill: preserve the reference collection, generate individual slide.json items, and keep QA/contact-sheet evidence beside the source collection.

QA

Before promoting a slide to a production template:

• validate library.json and every slide.json
• inspect the source collection contact sheet
• confirm the HTML fragment has a single <section data-slide-id="...">
• check that referenced assets resolve after path rewriting
• record remaining fidelity gaps in the source collection audit