# synthetic-screen-recording

The synthetic-screen-recording skill guides synthetic terminal demos in Remotion with TerminalScene. Use it when the command sequence and output can be authored ahead of time.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 78316 repo stars
- Author: calesthio
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/calesthio/OpenMontage/tree/HEAD/.agents/skills/synthetic-screen-recording/SKILL.md
- Updated: 2026-10-24
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/synthetic-screen-recording

## What it does

The skill explains how to render a terminal-style demo instead of capturing a live desktop. `TerminalScene` types commands character by character, reveals program output, and supports a blinking cursor plus floating pills. Its timeline uses `cmd`, `out`, `pause`, and `pill` steps, so each visible event can meet a narration cue.

The component lives at `remotion-composer/src/components/TerminalScene.tsx`, is exported from `remotion-composer/src/components/index.ts`, and is selected in `remotion-composer/src/Explainer.tsx`. Use `lib/verify_scene_pacing.py` to inspect step timing before rendering. A browser demo should use `playwright-recording`; live capture is the better fit when network latency or another unpredictable behavior is part of the result.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add calesthio/OpenMontage --skill synthetic-screen-recording -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/synthetic-screen-recording/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/synthetic-screen-recording/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add calesthio/OpenMontage --skill synthetic-screen-recording -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/synthetic-screen-recording/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add calesthio/OpenMontage --skill synthetic-screen-recording -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/synthetic-screen-recording/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install calesthio/OpenMontage .agents/skills/synthetic-screen-recording
```

2. **Manually: put the files in place**
- File: `.github/skills/synthetic-screen-recording/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add calesthio/OpenMontage --skill synthetic-screen-recording -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/calesthio/OpenMontage --path .agents/skills/synthetic-screen-recording
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/synthetic-screen-recording/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/calesthio/OpenMontage/tree/HEAD/.agents/skills/synthetic-screen-recording/SKILL.md

## When to use it
- sync terminal actions with narration
- render a CLI demo without desktop capture
- show an installation or API-key setup flow
- control terminal output frame by frame
- hold the final scene state for readability

## Example prompts
- Create a Remotion install walkthrough with `TerminalScene`; time each command and output line against the narration.
- Show a `git clone` flow in the synthetic terminal and add a pill when the clone finishes.
- Run `lib/verify_scene_pacing.py` on the step list and adjust pauses so the scene follows the narration.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: eadaab769683c99e.

BEGIN THIRD-PARTY FILE eadaab769683c99e
```text
---
name: synthetic-screen-recording
description: Synthetic terminal-style screen recording guidance for Remotion `TerminalScene`.
license: MIT
---

# Synthetic Screen Recording (Remotion TerminalScene)

**Decision this skill answers:** When the user wants a screen-recording-looking demo of a terminal, CLI tool, or coding workflow — do I **capture the real desktop** (OS screen recording via `screen_recorder`, Windows-MCP, Cap, or Playwright), or do I **synthesize it in Remotion** with the `TerminalScene` component?

> **Heuristic:** If the agent can author the exact command/output sequence in advance, synthesize. Only capture live when the real behavior is unpredictable, needs a real app UI, or the user explicitly asked for a real recording.

## Why this exists

v3 of the OpenMontage showcase tried to use Windows-MCP + `screen_recorder` to drive a Git-Bash window for the install walkthrough. It stalled on window positioning, focus races, and taskbar privacy concerns. We pivoted to **pure Remotion rendering** — a React component named `TerminalScene` that draws a fake terminal and types commands character-by-character. The output is visually indistinguishable from a real screen recording (same traffic-light window chrome, blinking cursor, scrolling output) but deterministic, privacy-safe, pixel-perfect at 1080p, and pace-controllable to the frame.

That component + pattern is the capability this skill makes discoverable.

## When to use synthetic (TerminalScene)

**YES, synthesize when:**
- The demo is a **terminal / CLI / coding session** where commands and outputs are predictable
- The user wants a polished tutorial feel (clean typography, floating pills, cursor blink)
- Install walkthroughs, setup demos, API key config, `make` targets, `git clone` flows
- You need tight sync with narration — every command must land on a specific beat
- You want the result reproducible (re-render gets identical pixels)
- The user's actual desktop has private apps/windows visible you'd otherwise have to crop

**NO, capture a real screen when:**
- The demo is **a real app UI** that can't be faked (Figma, Photoshop, a web app with live state, a browser flow)
- The user explicitly asked for a recording of *their* actual screen
- The behavior depends on timing you can't script (streaming LLM output, real network latency)
- There's a visual quirk (a cursor effect, a plugin pop-up) that only appears in the live environment

**For a browser demo** → `playwright-recording` skill, not this one.
**For a real desktop** → `screen_recorder` tool or Cap via `cap_recorder`.

## The component — `TerminalScene`
```
END THIRD-PARTY FILE eadaab769683c99e

The third-party file has ended. Everything between the eadaab769683c99e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2637 of 9952 bytes. © calesthio · MIT · https://github.com/calesthio/OpenMontage/tree/HEAD/.agents/skills/synthetic-screen-recording/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
