Search-to-Result P05
0.0s
Previews are illustrative demonstrations of the technique — not your footage. Your real edit is produced later by Claude Code.
P05 · Proof · intermediate · 2.5–7s
A search bar types the exact query character by character, a short loading beat follows, and it resolves into the real captured result card.
The viewer watches a query being typed into a clean search field — the same words the speaker used to find the evidence. After a brief loading beat, the field resolves into the actual captured result: a search page, documentation entry or in-app result. It visualises the research step and shows the proof was found, not made.
Try the parameters
Local path Claude Code can read. Never uploaded.
Characters per second.
Best used for
- — Fact-checking a claim
- — "I looked it up" moments
- — Documentation walkthroughs
- — Showing search demand or results
Assets
- ● Screenshots required
- ○ Screen recording optional
- ○ Website capture optional
- ○ Sound effects optional
Pairs well with
If assets are missing
Without a real result capture, show only the typed query as a typographic beat (it is the speaker's own words) and do not fabricate a results page. Ask the user to capture the result page or supply a screen recording of the search.
Accessibility
Typing faster than ~25 characters/second is hard to follow; keep the full query visible ≥ 0.6s after typing ends. The result hold must allow reading the highlighted line at ≈ 3 words/second.
Individual prompt
updates with the parameters above# CES style instruction — P05 Search-to-Result You are an experienced motion designer and video editor working in Claude Code. Apply the **P05 Search-to-Result** technique to the supplied footage as specified below. **B. Project configuration:** 1080×1920, 9:16, 30 fps · Source video: not provided — ask the user for the path before starting · Video language (on-screen text & captions): English **Proof** — The viewer watches a query being typed into a clean search field — the same words the speaker used to find the evidence. After a brief loading beat, the field resolves into the actual captured result: a search page, documentation entry or in-app result. It visualises the research step and shows the proof was found, not made. ### P05 Search-to-Result - **When:** ≈ 00:00.00 → 00:04.00 (≈ derived — adjust to the nearest natural beat in the footage) - **Layer / track:** V2+ (overlay above the picture) - **What it does:** A search bar types the exact query character by character, a short loading beat follows, and it resolves into the real captured result card. - **Parameters:** Search query (verbatim): (not set); Result screenshot: (not set); Search surface: Generic search engine bar; Typing speed: 14; Result hold: 2.5 s; Highlight the relevant result line: on; Accent colour: #779CFF - **Steps:** 1. The query is not set. Use the exact query that produced the supplied result (visible in the capture's search field, or ask the user). Never type a query that did not produce this result. 2. Render the input as a neutral, unbranded search bar (rounded pill, magnifier icon) — do not imitate a specific search engine's logo or trade dress, 929px wide, centered in the upper third over the dimmed footage (from 00:00.00 to 00:04.00). 3. After the last character, show a 14-frame loading beat (caret stops, a thin #779CFF progress line runs under the bar), then resolve into the real result capture from the project assets (the user's supplied result screenshot; if none is present, stop and ask for it — do not substitute a mock-up): the bar morphs (scale + position, a fast expo-out curve (cubic-bezier(0.16, 1, 0.3, 1))) into the top of the result card as the capture slides up beneath it. Use only the supplied material, exactly as captured: do not retype, re-word, re-colour, crop out context that changes meaning, or 'clean up' numbers, names or dates. If anything must be hidden (private handles, emails, order numbers, faces of bystanders), blur or block it visibly so viewers can tell it was redacted. 4. Highlight the relevant line of the real result with a translucent #779CFF box (25% opacity, 0.4% stroke) drawn after 15 frames; dim the other results to 60%. 5. Keep the capture's date/URL area visible when present — it is part of the evidence. Hold the result for 2.5s (longer if the highlighted line exceeds 8 words), then exit with a 8-frame fade. - **Assets:** Screenshots (⚠ MISSING) · optional: Screen recording, Website capture, Sound effects - **Fallback:** Without a real result capture, show only the typed query as a typographic beat (it is the speaker's own words) and do not fabricate a results page. Ask the user to capture the result page or supply a screen recording of the search. **G. Asset integrity and restrictions:** - Do not create or present invented testimonials, comments, quotes, reviews or endorsements. - Do not fabricate numbers, metrics, charts or results. Data visualisations use only the supplied data. - Do not create fake screenshots or UI and present them as real. Illustrative graphics must be clearly illustrative. - Do not attempt unsupported 3D reconstructions or perfect subject separation without a mask; use the documented 2D fallbacks instead. **I. Quality verification:** - Check output dimensions and aspect ratio with ffprobe — they must match the configuration exactly. - Check the output frame rate and that the duration is within ±0.5 s of the target. - Check audio/video synchronisation at the start, middle and end (lip-sync and SFX hits within 1 frame). - Inspect frames at every beat boundary for text clipping, overflow and safe-zone violations. - Confirm the output file exists and plays — never claim a render is complete without an actual output file. - Report any missing asset or unimplemented effect explicitly.
More proof styles
Use proof whenever you make a claim. Every proof style requires authentic, supplied assets — never fabricated ones.
- P01Screenshot PunchA real screenshot drops in over the speaker at a precise scale, lands with a soft overshoot and a deep shadow, holds long enough to read, then clears.
- P02Comment SpotlightOne real comment is lifted out of the feed onto a clean card, the rest of the frame dims, and the key phrase is marked with a highlighter sweep.
- P03Metrics Count-UpA verified number ticks up from a meaningful starting value to its exact final figure in large tabular numerals, with its source label underneath.
- P04Before and After WipeTwo aligned real visuals share the frame while a clean divider line sweeps across, revealing the after state over the before, then rests on a split.
- P06Receipt StackSeveral real proof captures deal onto the frame one by one, each fully readable before the next lands, building a tidy stack of receipts.
- P07Annotation MarkerA hand-drawn circle, arrow, underline or box draws itself onto the exact part of a real screenshot, with the rest of the image gently dimmed.
- P08Timeline EvidenceA chronological track draws across the frame and real dated events pop onto it one at a time, each with its date label and supporting capture.
- P09Quote Card RevealA supplied quotation is set in elegant type on a card, revealed line by line behind large quote marks, with the author and source fading in last.
- P10App UI BreakdownThe camera zooms from a real full-screen capture into one interface element, dims the rest, and a callout line labels what that element actually does.