vela-live-render

Render and validate Vela slide decks offline without external CDNs.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/migletto/slides --skill vela-live-render
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vela-live-render
Source: https://github.com/migletto/slides/tree/main/.claude/skills/vela-live-render
Command: npx skills add https://github.com/migletto/slides --skill vela-live-render

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of validating Vela slide decks in a blocked or offline container by providing a repeatable render harness that does not depend on external CDNs.

Core Features & Use Cases

  • Offline deck rendering: Builds a self-contained render of a Vela presentation with vendored React, ReactDOM, lucide-react, and Babel.
  • Deterministic UI automation: Runs headless UI test batteries, scripted screenshots, and recorded demo videos for repeatable QA.
  • AI feature verification: Exercises Vera and other AI integrations against the local Claude CLI to confirm real end-to-end behavior.
  • Use case: Validate a slide change in CI, capture a benchmark screenshot, or record a demo video without relying on the public web.

Quick Start

Use this skill to render the local Vela deck offline and run the headless UI test battery against the generated output.

Frequently Asked Questions about vela-live-render

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I render slide decks offline in a blocked CI container without CDN access?

You can validate slide changes in CI by running a headless UI test battery against the offline rendered output. This deterministic approach ensures reliable screenshot benchmarks and demo video capture.

How do I automate screenshot benchmarks and demo video capture for UI presentations?

Automated screenshot benchmarks and demo video capture are handled by running headless UI tests against the offline rendered output. This deterministic process provides repeatable QA without public web access.

Can I verify AI integration features against a local Claude CLI during headless UI testing?

You need an offline harness, vendored browser assets like React and Babel, and local Claude CLI access for opt-in AI integration checks. These prerequisites ensure the offline rendering and verification process functions correctly.

Do I need vendored browser assets and a local Claude CLI to run offline UI verification?

Yes, you need an offline harness, vendored browser assets, and local Claude CLI access for AI integration checks. These components ensure deterministic offline rendering and headless UI verification.

Why does offline presentation rendering require vendored React and Babel dependencies?

Offline presentation rendering requires vendored React, ReactDOM, and Babel to build a self-contained render environment. This removes external CDN dependencies and enables consistent rendering in blocked containers.