Screenshot + GIF Capture Playbook

Yes, screenshot and GIF capture can be automated enough to keep docs current.

Output directories

• Screenshots: docs/user-guide/assets/screenshots/
• GIFs: docs/user-guide/assets/gifs/

1) Launch app

open dist/liltype.app

Or from source:

swift run liltype

2) Capture still screenshots

Use full-screen captures first, then crop if needed.

/usr/sbin/screencapture -x docs/user-guide/assets/screenshots/01-home.png
/usr/sbin/screencapture -x docs/user-guide/assets/screenshots/02-settings-general.png
/usr/sbin/screencapture -x docs/user-guide/assets/screenshots/03-settings-model.png
/usr/sbin/screencapture -x docs/user-guide/assets/screenshots/04-dictionary.png
/usr/sbin/screencapture -x docs/user-guide/assets/screenshots/05-sessions.png

3) Capture short motion clips and convert to GIF

Record a .mov clip:

/usr/sbin/screencapture -V 8 docs/user-guide/assets/gifs/hotkey-flow.mov

Convert to GIF (optimized two-pass palette):

ffmpeg -y -i docs/user-guide/assets/gifs/hotkey-flow.mov \
  -vf "fps=10,scale=1280:-1:flags=lanczos,palettegen" \
  docs/user-guide/assets/gifs/palette.png

ffmpeg -y -i docs/user-guide/assets/gifs/hotkey-flow.mov -i docs/user-guide/assets/gifs/palette.png \
  -lavfi "fps=10,scale=1280:-1:flags=lanczos[x];[x][1:v]paletteuse" \
  docs/user-guide/assets/gifs/hotkey-flow.gif

Recommended capture list

• first-launch permission wizard
• model download flow
• hotkey setup + conflict warning
• first dictation flow (record → transcribe → paste)
• dictionary term add/remove
• clipboard history search/reuse
• session start/stop/summarize

Capture hygiene

• Use one macOS theme consistently (Light or Dark)
• Hide personal/sensitive content before recording
• Keep file names stable so docs links don’t break