terminal-replica

1# Terminal replica
2 
3Terminal-like graphics must match the real tool and the real setup of the person who ships the asset. A generic green-on-black "hacker terminal" reads as fake. This skill is a method for capturing your own setup, plus a render recipe and a worked example.
4 
5## Method
6 
71. Capture the ground truth. Take a fresh screenshot of your real terminal running the tool. Sample background, foreground and accent colors from it with an eyedropper or `PIL.Image.getpixel`. A live screenshot beats any spec in this file.
82. Record these five facts about your setup:
9   - Emulator (Terminal.app, iTerm2, Warp, the VS Code integrated terminal, Ghostty).
10   - Font family and size. Check the emulator's settings. VS Code on macOS defaults to Menlo 12.
11   - Theme: background, default foreground, and the 16 ANSI colors.
12   - Shell prompt shape (for example `user@host ~ %` for default macOS zsh, or your powerline or starship layout).
13   - Statusline format, if your agent has a custom one.
143. Use your own session logs for transcript shapes. Claude Code stores them at `~/.claude/projects/<project-slug>/*.jsonl`. The assistant and tool-use turns show exactly what text appears.
154. Draw from those facts, then verify by placing the render next to a real screenshot before you publish.
16 
17Keep a small config in your own project (a JSON or Python dict) holding the five facts, and read it from your render scripts. Do not hardcode them in shared code.
18 
19## Claude Code TUI
20…