Receipt Stack P06
0.0s
Previews are illustrative demonstrations of the technique — not your footage. Your real edit is produced later by Claude Code.
P06 · Proof · intermediate · 3–10s
Several real proof captures deal onto the frame one by one, each fully readable before the next lands, building a tidy stack of receipts.
Instead of flashing a collage, authentic proof cards — messages, payment confirmations, reviews, emails — arrive one at a time with a slight rotation and settle onto a growing stack. Each card gets its own readable hold before the next covers it, and a small counter shows how many there are. Quantity reads as weight of evidence while every item stays individually legible.
Try the parameters
Local path Claude Code can read. Never uploaded.
Blur names, emails, order numbers and card digits.
Best used for
- — Client results and messages
- — Sales or payout confirmations
- — Review roundups
- — Proving a pattern with several examples
Assets
- ● Screenshots required
- ○ Social comment optional
- ○ Document / PDF optional
- ○ Source video optional
- ○ Sound effects optional
Pairs well with
If assets are missing
With only one real capture, use P01 Screenshot Punch instead. If captures contain data the user cannot share, redact it or drop that card — never replace it with a recreated or 'example' receipt.
Accessibility
Each card needs its own readable hold (≥ 0.8s, plus 1/3s per word that matters); do not deal cards faster than the viewer can read them. Narrate or caption what the stack demonstrates.
Individual prompt
updates with the parameters above# CES style instruction — P06 Receipt Stack
You are an experienced motion designer and video editor working in Claude Code. Apply the **P06 Receipt Stack** 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** — Instead of flashing a collage, authentic proof cards — messages, payment confirmations, reviews, emails — arrive one at a time with a slight rotation and settle onto a growing stack. Each card gets its own readable hold before the next covers it, and a small counter shows how many there are. Quantity reads as weight of evidence while every item stays individually legible.
### P06 Receipt Stack
- **When:** ≈ 00:00.00 → 00:05.00 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V2+ (overlay above the picture)
- **What it does:** Several real proof captures deal onto the frame one by one, each fully readable before the next lands, building a tidy stack of receipts.
- **Parameters:** Proof captures folder: (not set); Cards in stack: 3 cards; Minimum hold per card: 1.4 s; Arrangement: Fanned stack (rotated); Rotation spread: 6 deg; Show count (e.g. 3 / 5): on; Auto-redact personal data: on; Accent colour: #D7FF5F
- **Steps:**
1. Take the 3 real captures from the project assets (the user's supplied proof captures; if none is present, stop and ask for it — do not substitute a mock-up) (in the user's order) and build a stack overlay from 00:00.00 to 00:05.00. If fewer than 3 are supplied, use only what exists — never pad the stack with duplicates or mock-ups. 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.
2. Before animating, redact personal data on every card (names of private individuals, emails, phone numbers, order IDs, card digits, addresses) with visible frosted blocks; leave amounts, dates and the platform context untouched.
3. Each card: scaled to 799px width (max 58% of frame height), 2.5% corner radius, white 1px inner stroke and soft drop shadow. Cards deal in from below-right, travelling ≈ 30% of frame height with a back-out curve with slight overshoot (cubic-bezier(0.34, 1.56, 0.64, 1)) over 12 frames.
4. Fan them: alternate rest rotations within ±6° and offset each by 1.5% of frame width so earlier cards peek out underneath.
5. Stagger: the next card may only arrive after the current one has been fully visible for ≥ 1.4s, or longer when it contains more text (≈ 3 words/second + 0.8s). Total ≈ 6.4s for 3 cards. Dim older cards to 70% brightness as new ones land.
6. Show a small counter ("1 / 3" → "3 / 3") in #D7FF5F mono type at the stack's top-left corner, incrementing on each landing.
7. After the last card's hold, sweep the whole stack out together (translateY −8%, opacity → 0 over 9 frames).
- **Assets:** Screenshots (⚠ MISSING) · optional: Social comment, Document / PDF, Source video, Sound effects
- **Fallback:** With only one real capture, use P01 Screenshot Punch instead. If captures contain data the user cannot share, redact it or drop that card — never replace it with a recreated or 'example' receipt.
**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.
- P05Search-to-ResultA search bar types the exact query character by character, a short loading beat follows, and it resolves into the real captured result card.
- 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.