---
name: dev-tool-video
description: Job skill for a video about a developer tool: a CLI, API, library, SDK or editor plugin. Adds questions, terminal and code moves, ideas and pitfalls. Load once, before asking.
---

# Developer tool video

Developers trust what they can see running. Build it as the `motion` skill
describes; this page adds what is specific to developer tools.

## Ask (on the motion skill's single card)

Use the shared visual-approach question from `motion` when unsettled, ahead of
an optional idea pitch. Adapt its choices to this job; keep the card to four
questions total and skip choices the brief or requested reference already settles.

- "What's the one command or line of code that shows it best?" Offer the
  README's quick-start as recommended, plus "Let GG Motion choose".
- "Where will people mostly watch this?" (from the `motion` skill).
- "Should it have music?" (from the `motion` skill).
- "Which idea should we go with?" Pitches below, plus "Let GG Motion choose".

Read the repository or docs directly: the README, real commands, real output
and the real logo. Never run the repository's scripts.

## Ideas that suit developer tools

- **One command, the whole story.** The command types, the output streams, and
  the result it produced grows out of the last line.
- **The diff.** The code before, a few lines change, and the effect appears
  beside it.
- **The pipe.** Input flows through the tool as one shape and comes out
  transformed; the camera follows the shape.

## Beats that work

- Start typing in the first second. Developers skim.
- Type at a human but quick pace; let output arrive in real-looking chunks,
  not all at once.
- Close-up on the line that matters, then pull back to the result.
- End on the install command and the name, held still.

## Moves

`kit.typewrite` for commands and code; `kit.tick` for passing steps;
`kit.reshape` from the output line into the result; `kit.camera` for close-ups
on a line. Pieces: `request-to-result`, `scale-dive`, `morph-carry`,
`camera-rig`.

## Look

A terminal or editor look from the tool's own brand or the user's theme, with a
monospaced face from the bundled fonts; real syntax colours, readable at phone
size (zoom in on the relevant lines rather than showing the whole file).

## Pitfalls

- Fake commands, flags or output. Use the real ones from the docs.
- Code too small to read.
- Walls of text with no visible cause and effect.
- Matrix-style rain, glitch effects or hacker clichés.