beam-ai-team/beam-ai-deck-templates

Beam AI Deck Templates

Use this skill when creating or adapting Beam-branded HTML decks and reports. It packages the portable parts of the Beam slide-library work so templates can live outside the Prism app while still being usable by Prism, Designer agents, or standalone HTML workflows.

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

Safety Contract

Require explicit user approval before sending, publishing, or externally sharing a generated customer deck/report. Keep customer-specific content, source references, and generated assets in the user-approved output folder, and do not commit private customer material into reusable templates.

Pack Contents

• ../../../design/beam-ai/decks/design-packs/beam-ai-decks/ - dark Beam sales deck design system for 16:9 HTML decks.
• ../../../design/beam-ai/decks/design-packs/beam-use-case-report/ - DIN A4 report design system for use-case proposal and operating diagnostic reports.
• ../../../design/beam-ai/decks/templates/beam-customer-intro-problem-fit/ - customer intro deck template focused on pain, platform fit, proof, pilot path, and next steps.
• ../../../design/beam-ai/decks/templates/beam-rpo-candidate-operations-intro/ - recruiting/RPO intro deck template.
• ../../../design/beam-ai/decks/templates/beam-use-case-proposal-report/ - A4 use-case proposal report template.
• ../../../design/beam-ai/decks/examples/hudson-talent-rpo-intro/ - curated RPO customer intro deck example with local assets and QA evidence.
• ../../../design/beam-ai/decks/examples/beam-use-case-proposal-report-html/ - curated A4 report example with Beam logo and content structure.

Individual slide-level HTML patterns live in the separate beam-ai-slide-library skill. Use that skill when the user asks for a slide library, specific slide patterns, or Prism slide-library/{slug}/slide.json items.

When To Use Which Asset

Use a design pack when the target system already knows how to compile design tokens, layouts, and template slots into a deck or report.

Use a template manifest when a Designer or deck-generation agent needs a semantic slide/report plan with editable content blocks, template roles, and expected slots.

Use an example when the user needs a high-fidelity HTML reference, wants to inspect the finished look, or asks for a custom artifact based on an existing Beam style.

Use beam-ai-slide-library when the unit of reuse is a single slide or slide section rather than a full deck/report template.

Use beam-figma-to-html-slides alongside this skill when the source is a Figma deck or when a template needs additional Figma-derived visual fidelity.

Design Rules

• Keep the Beam deck stage at 16:9 with 1920x1080 source logic or 1600x900 prototype logic.
• Use 100px source padding, or 80px on the 1600x900 prototype.
• Use the Beam dark background recipe from the design pack unless the source template intentionally supplies a different background.
• Preserve editable text for titles, labels, bullets, CTA bars, commercial terms, metrics, and most card content.
• Use image slots for photos, product screenshots, complex Figma-rendered visuals, logo strips, and decorative spheres.
• Do not use generic dark-card layouts when a template includes a stronger Figma-derived composition.
• Keep customer-facing copy above the design pack minimum font sizes. Do not solve crowded slides by shrinking below the minimum.
• Preserve the Beam font-weight mapping: Regular 400, Medium 500, Semibold 600, Bold 700, Black 900.

Output Guidance

For a new HTML deck, create:

artifact-name/
├── index.html
├── manifest.json
├── content.md
├── assets/
└── qa/

For a report, use DIN A4 page sizing and the beam-use-case-report design pack. Add the Beam logo on the cover and keep report body text readable, with 14px base copy and no text below 10px.

For Prism-compatible output, keep stable slide IDs, template names, editable slots, local asset paths, and source/provenance references in the manifest.

QA

Before handing off:

• Validate template and design-pack JSON.
• Open the HTML locally and inspect the first, densest, and last pages/slides.
• For decks, render a contact sheet when possible.
• Record any simplification or missing primitive in the artifact audit.