← ClaudeAtlas

live-demolisted

Turn a working robium app into a public, interactive web demo: a mission-control demo page (start/stop instance buttons, live boot terminal, fleet budget), per-visitor simulator instances on Cloud Run (scale-to-zero), and a visualizer handoff (Foxglove deep link or self-hosted viewer). Use when: 'live demo', 'demo page', 'let visitors drive the robot', 'try it live on the website', 'demo instance start/stop', 'host the sim for the demo', choosing the demo visualizer, or budgeting/deploying demo backends. Load after an app passes its smoke test (testing) — a demo hosts a finished app. Pairs with foxglove (bridge/viewer mechanics) and integration (container patterns). Not for: developer-facing visualization during a build (foxglove/rviz2) or general website building.
robium-ai/robium-plugin · ★ 0 · DevOps & Infrastructure · score 73
Install: claude install-skill robium-ai/robium-plugin
# live-demo Everything between "the app's smoke test is green" and "a stranger on the website is driving the robot." This skill owns the demo architecture that robium.org/demos/nav-trial runs in production: a control page whose Start/Stop buttons manage private, per-visitor simulator instances on Cloud Run, a session gateway inside the app container, and a viewer handoff. Every command, flag, and gotcha here was verified live (2026-07-13, nav-trial demo) — this is a distillation of a real deployment, not a design sketch. ## When to use this skill - Publishing any robium app as an interactive web demo, and every design choice inside that: flow shape, page anatomy, instance lifecycle, visualizer, budget, and the Cloud Run deployment. - Debugging a deployed demo (instance won't boot, viewer can't connect, status endpoint misroutes). - Cross-references — go to the sibling skill instead when the question is: - foxglove_bridge setup, layouts, or MCAP for *development* use → `foxglove` (this skill consumes its bridge; the demo-specific parts — session gateway, deep-link handoff — live here). - Container/compose patterns for the app itself → `integration`. - Whether the app is *done* enough to demo → `testing` (smoke test green is this skill's entry bar). - Env reproducibility of the app → `environments`. ## Key directives - **Delegation posture: embed.** The demo architecture (gateway contract, Cloud Run tuning for sims, viewer decision table) exists