Show the terminal experience
before you build it.

Script a mock terminal you fully control and render it to a video or gif. Built for a coding agent to drive.

skill
$ npx skills add r3al1tym/termscene
Try it in the playground
what it's for

For the experience you haven't built yet.

Recording tools capture a CLI that already works. termscene is for the other moment — when the thing is still an idea, and you need to show it clearly.

01

Pitch a concept

Mock the CLI you're proposing so a room can see how it'd feel — before a line of it exists.

02

Explain an idea

Turn "imagine you just type what you want…" into a clip that shows it, idealized and clean.

03

Slides & social

Drop a crisp, looping terminal moment into a deck, a launch post, or a README hero.

04

Simplify the real thing

Show the five steps that matter, not the forty that happened. A stylized version of the truth.

You decide every line of output, so the demo is exactly the story you want to tell — calm, clear, and the same every time.

the loop

Intent in, finished clip out.

Describe

Tell the agent the terminal moment you want — or write a scene file by hand.

Preview

It generates a scrubber — drag the timeline, tune the pacing, reload on edit.

Render

One command to mp4, GIF, or WebM. Square, landscape, or portrait.

Re-edit

Change a line, render again. Identical pipeline, updated clip.

{
  "meta": {
    "theme": { "preset": "claude" },
    "aspect": "wide",
    "window": { "chrome": "mac" }
  },
  "steps": [
    { "cmd": "add a /health endpoint" },
    { "out": "● Edit(server.ts)  +9", "style": "accent" },
    { "out": "{ status: ok }", "style": "ok" }
  ]
}

A scene is just steps on a clock.

cmd types a command. out prints output — with a style and optional char-by-char streaming. progress animates a bar. wait pauses. You never write timecodes; the compiler lays them out.

Then one command renders it — deterministically, the same every time.

themes claude · gemini · codex · warp +4 aspects 16:9 · 1:1 · 9:16 out mp4 · gif · webm