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.

examples/assistant-panel/script.md

View on GitHub
# AI assistant panel flow

## Say
1. "Open the assistant from anywhere in the app."
2. "Ask a question in plain language — the panel streams the answer as it thinks."
3. "When a tool runs, you see progress inline, then the result lands in the thread."

## Show
1. Preload app off-camera; close any open side panels for a clean opening frame.
2. Wide — main workspace visible.
3. Click the assistant launcher FAB — expect the side panel.
4. Focus the prompt textarea.
5. Type a short, realistic prompt (read from a fixture file if needed — never paste secrets).
6. Submit — `appear` immediately after click (no await on spinner box first).
7. Wide on the panel while the tool runs; `done` when the result block is visible.
8. Scroll the thread slowly so the answer and citation/tool block are readable.
9. Wide, hold ~3s on the final message (payoff), stop.

## Prep
- Use a dev account with assistant access enabled.
- Tool labels vary by product — locate the running/done state in DOM once, reuse selectors in `run.mjs`.
- **Never `focus()` during a tool wait** — stay wide on the panel; spinners flash under zoom.
- Default tool-wait compression: ≤ 2.5s on screen after compose.

## Clause markers
- (¢ "Open the assistant") — steps 2–3
- (¢ "Ask a question") — steps 4–5
- (¢ "When a tool runs") — steps 6–8
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: 471kUpdated 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