Skip to content

AlexAnsart/demo-studio / skills/demo-setup

demo-setup

Verified

One-time setup that analyzes the current project and configures it to use the film-demo / narrate / sync-narration / produce-video skills — detects the dev server and framework, asks only when necessary, generates demo.config.json and .env entries, vendors the recording engine and project helpers, and scaffolds a first demo from reference patterns. Use when the user asks to set up, configure, or install demo-studio / video-recording skills for this project, or before running produce-video for the first time in a new codebase.

references/beat-plan.md

View on GitHub
# Beat plan (narrated videos)

After Whisper alignment (`align-narration.py`), build this table **before**
recording. Paste it as a comment block at the top of `run.mjs`:

```
// BEAT PLAN (from aligned.json)
// #  sentence (first words…)           dur    Show beat              min hold
// 1  "Here's the task board…"          2.4s   app settled, wide      3.5s
// 2  "Type what you need…"             5.1s   type + add             6.5s
// 3  "No reload — the list…"           3.8s   focus new row + wide   5.0s
```

## Min hold formula

**min hold = sentence duration + ~1.2s**

The sync stage can insert silence *between* sentences. It cannot extend a beat
that already left the screen — if the hold is too short, narration spills into
the next visual.

## Implementation in `run.mjs`

```javascript
async function holdMin(sec, label) {
  await pause(Math.max(0, Math.round(sec * 1000)))
  logRun(`Hold "${label}" ${sec}s`)
}

// After the "type + add" beat settles:
await holdMin(6.5, 'sentence-2')
```

During planned holds, `inactivity` / `zoom-too-long` guardrails are **expected**
— justify them against the beat plan row, don't "fix" by compressing idle time
(see `narrated-compose.md`).

## 1:1 mapping rule

Every on-screen action illustrates a clause. Cut unmotivated clicks. Every clause
needs something visible — if Say mentions a loading state, the Show beat must
include `appear`/`done` or a wide hold on the spinner/result.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall