The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need the whole video watched from start to finish before we publish. Play the project from the…
Execute — do the immediate task
+I need the whole video watched from start to finish before we publish. Play the project from the first clip through the final transition on my phone so I can confirm pacing, check for jump cuts, and hear audio levels across every scene. If anything stutters or drops frames, pause and mark the exact timecode so I can fix the source clip before export.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I show this draft to the social lead, make watching it easy: surface the total runtime up…
Improve — make it easier to accept
+Before I show this draft to the social lead, make watching it easy: surface the total runtime up top, flag any abrupt audio level jumps, and show where transitions are longer than one second. Highlight any clips with different frame rates or resolutions that could cause playback hiccups so I can smooth pacing or replace assets quickly.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I played the project and video frames froze at 00:01:22 while audio kept going. The social lead…
Decide — diagnose the stuck moment
+I tapped play and the preview dropped frames halfway through.
I played the project and video frames froze at 00:01:22 while audio kept going. The social lead needs this polished by Friday and I can't rerender now. Do I inspect the clip at that timestamp for mismatched frame rates and large codecs first, or export a short test of the problematic section to confirm it's a device preview issue? Tell me the most likely cause and the single next check to run.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every time I review rough cuts on my phone I hit playback glitches—frames drop, audio slips, or…
Become — change the pattern
+I keep finding playback glitches only on my phone during reviews.
Every time I review rough cuts on my phone I hit playback glitches—frames drop, audio slips, or transitions stutter—and I lose time recreating fixes that don't matter after export. Which habit will cut this down: standardize incoming clip frame rates and codecs at import, or build a two-minute export test after edits before any stakeholder review? Recommend the one practice to adopt and how to make it stick.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other mobile video editing work people do in CapCut.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.