Terminal stories
A useful terminal demo has one protagonist, one everyday problem, and one visible payoff. Prefer a short happy path such as create → edit → run. Start at the product's value; omit installation, credentials, and provider setup unless setup itself is the feature being demonstrated.
Every command and product message must either exist in the product or be implemented before it appears. Shell prompts, typing, pauses, and editor chrome may be rendered deterministically. Model responses, run identifiers, and external state may be illustrative only when the accompanying documentation says so.
Keep the final frame readable without opening another artifact. A short real CLI summary can provide the payoff; retain the report path for deeper evidence. Aim for enough pause time to read each beat, and avoid rapid cuts or slide-show transitions when a continuous terminal session tells the story more clearly.