Prompting
Write prompts that give LittleDemo the right recording target and stopping point.
Prompting
Good prompts describe the viewer, the task, and the payoff. You do not need to write click-by-click instructions.
A useful prompt shape
textShow [who] doing [task] so they can see [payoff].
Examples:
textShow a support lead creating a saved view for urgent tickets.
textShow a founder comparing the three pricing plans and switching to annual billing.
textShow a developer adding the JavaScript SDK to a docs page and previewing the embed.
Add constraints when they matter
Use constraints for timing, section targeting, and output tone.
textKeep this to about 10 seconds. Focus on the pricing table and the annual billing toggle.
textUse a simple scroll. Do not click into the app.
textFeature the proof section with customer logos and testimonials.
Avoid these prompt patterns
| Prompt | Why it underperforms |
|---|---|
Make it cool | No target, no viewer, no finish line. |
Click everything | Produces wandering demos. |
Show the whole app | Usually too broad for a short video. |
Use our secret workflow | The recorder can only use what the target URL exposes. |
When to pick a template
Leave the template on auto until the output repeatedly misses the style.
Then pick a template:
bashlittledemo demos create \ --project proj_abc123 \ --prompt "Show the plan cards and annual toggle" \ --template pricing-focus
See choose a recording template for the full decision guide.