asciinema

原文涵盖的主题

• asciinema
• What this skill is - and isn't
• Hard rules
• Workflow
• Scripts
• Gotchas (asciinema 3.x, agg 1.9)

Script the session, drive it, gate the cast, prove every scene from the cast, then publish. Never record a live shell. | Situation | Owner | |---|---| | README or PR demo of a CLI or TUI, .cast + GIF, asciinema.org upload | this skill | | Recording a browser flow | agent-browser | | Produced video, motion graphics, voiceover | video | | Proving a TUI change frame by frame (no recording) | the project's own screen harness | 1. Sample data only. A public demo runs against a fixture server or sandbox account with generic content. The session script points the tool at an isolated config dir (XDGCONFIGHOME in a temp dir, fake auth) so it cannot read the real one. 2. Never record an interactive shell. A real prompt and rc files leak user, host, and paths. The session script prints a fake $ prompt and types each command. 3. The leak gate is not optional. record.sh rewrites the header command (asciinema stores the full command line, absolute paths included) and fails on home paths, loopback addresses, token names, and every --deny string. A failure means fix the script, never edit around the gate. 4. Prove scenes from the cast. Run cast-check.py --expect with one marker per scene before ca

这里只展示节选，请以完整原文和当前要求为准。