cli-forge-demo

Optimization: This skill uses on-demand loading. Heavy content lives in references/ and is loaded only when needed.

Language rule: Skill instructions are English. Detect the project's primary language (README, comments, docs, commits) and generate the demo kit in that language. If bilingual, ask the user.

Diacritics rule: When the chosen output language uses diacritics (French, Spanish, Portuguese, etc.), render them correctly — including on capitals (É, À, Ç, Ô…). Never strip accents to ASCII: write "sécurité" not "securite", "Rôle" not "Role". ASCII-flattened French is a defect, not a style.

Writing style: Favor clarity — short sentences, one idea per sentence, plain words. A metaphor only when it clarifies. Keep one consistent register (impersonal/infinitive for operational docs). Separate narrative prose, meant to make the reader understand, from telegraphic content (tables, commands, checklists) which stays terse for action.

No fabricated output: Never invent command output, console captures, API responses, metrics, or logs. When real output is needed, emit a clearly-marked placeholder (🚧 "replace with a real capture"), never plausible-but-fake text presented as real.

Demo Forge — Reproducible Live-Demo Kit

"A good production is identical every night — not because the actors are lucky, but because the show is scripted, the marks are taped to the floor, and the stage is reset between performances."

Generate everything needed to give the same demo, flawlessly, every time: a staged script, deterministic data, a one-command reset, a backup recording, and the delivery support that best fits the project.

Core Principle — The Theatre

A live demo is a staged performance, not an improvisation. Eight mappings carry the whole skill (full model in references/staging.md):

Stage craft	What it means for the demo
The script & blocking	DEMO.md — exact lines (what you say) and exact marks (the precise commands). No improvisation on stage.
Same show every night	Fixed seed: state, data, clock, and environment are pinned so the run is deterministic. Reality is seeded like a PRNG. The canonical reproducibility toolkit is ../shared/determinism.md (consumed by cli-forge-pipeline, cli-forge-resilience, cli-forge-perf, cli-audit-wizard, cli-forge-oci-rootless) — demo is the visible twin of that contract.
Reset the stage	Returning to s0 is idempotent and fast (reset ∘ reset = reset) so you can run the demo back-to-back.
Open with the showstopper	Do the last thing first — front-load the payoff (Great Demo!'s "Do It"), then peel back how.
Hit your marks	Golden path / vertical slice only. Every beat earns its place; deviation is where demos die. The golden path is the T2-T3 rung of ../shared/gate-ladder.md made visible — what a demo shows is exactly what a fresh deploy + first operation proves.
No scene runs long	No uninterrupted segment over ~76 seconds (Gong data). Segment, checkpoint, interact.
The understudy	A pre-recorded backup (GIF / asciinema cast) and an offline mode. Never debug live > 45 s.
The matinée	The self-guided version the audience can re-run alone (interactive walkthrough).