Skip to content

Blueprint Universe X10

0.0s

Previews are illustrative demonstrations of the technique — not your footage. Your real edit is produced later by Claude Code.

X10 · Signature Effects · advanced · 3–12s

A plain visual transforms into a blueprint world: grid lines spread, outlines trace each part and animated paths connect the labelled components.

The explanation moves from a normal image into a technical-drawing environment: the background floods to blueprint blue with a fine grid, outlines trace the parts of the visual, and connecting paths draw between labelled components with dimension marks and callouts. A slow camera drift across the drawing makes it feel like a vast, engineered system. Labels come only from the speaker's own terms or the user's list.

Try the parameters

Begin on the supplied visual, then morph it into the blueprint.

Best used for

  • — System architecture explainers
  • — How-it's-made stories
  • — Engineering content
  • — Strategy frameworks

Assets

  • ● Transcript with timing required
  • ○ Screenshots optional
  • ○ Photos optional
  • ○ Document / PDF optional
  • ○ Brand fonts optional

Pairs well with

If assets are missing

If no source visual is supplied, start directly on the blueprint field. If the transcript doesn't describe a clear system, ask for the component list rather than inventing an architecture.

Accessibility

Ensure labels have ≥ 4.5:1 contrast on the blueprint colour and stay on screen ≥ 1.5s. Keep line pulses slow and the camera drift gentle.

Individual prompt

updates with the parameters above
# CES style instruction — X10 Blueprint Universe

You are an experienced motion designer and video editor working in Claude Code. Apply the **X10 Blueprint Universe** 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

**Signature Effects** — The explanation moves from a normal image into a technical-drawing environment: the background floods to blueprint blue with a fine grid, outlines trace the parts of the visual, and connecting paths draw between labelled components with dimension marks and callouts. A slow camera drift across the drawing makes it feel like a vast, engineered system. Labels come only from the speaker's own terms or the user's list.

### X10 Blueprint Universe

- **When:** ≈ 00:00.00 → 00:06.00 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V1 (main picture)
- **What it does:** A plain visual transforms into a blueprint world: grid lines spread, outlines trace each part and animated paths connect the labelled components.
- **Parameters:** Component labels: (not set); Blueprint colour: #0F2C5C; Line colour: #BFD8FF; Annotation density: Technical (dimensions + callouts); Path draw time: 1.2 s; Camera drift: on; Transform from source visual: on
- **Steps:**
  1. Open from 00:00.00 to 00:06.00 on the supplied visual (screenshot, photo or diagram) full-frame, then over 24 frames flood the background to #0F2C5C, desaturate the visual and trace its main shapes as #BFD8FF outlines (stroke-dashoffset), crossfading the image away to leave the line drawing.
  2. Grid: a fine grid (2.5% of frame width, #BFD8FF at 10% opacity) and a major grid every 5 cells (20% opacity), spreading outward from the centre over 15 frames.
  3. Components: take the parts and their relationships strictly from what the speaker explains in the transcript; if the structure is unclear, ask the user for the component list. Never add parts the speaker doesn't mention.
  4. Connections: SVG paths with right-angle routing between related components, drawn via stroke-dashoffset over 1.2s (36 frames) each, in the order the speaker explains them; then send a small #BFD8FF pulse along each path to show direction of flow.
  5. Annotations (technical): add dimension lines with arrowheads, a few numbered callouts and corner registration marks. Dimension marks are decorative — never print measurements or figures that weren't supplied.
  6. Camera: drift slowly across the drawing (≈ 4% of frame width per second) with a 1.0 → 1.1× push, landing centred on the component being discussed at the end.
- **Assets:** Transcript with timing (⚠ MISSING) · optional: Screenshots, Photos, Document / PDF, Brand fonts
- **Fallback:** If no source visual is supplied, start directly on the blueprint field. If the transcript doesn't describe a clear system, ask for the component list rather than inventing an architecture.

**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 signature effects styles

Reserve for the moment you most want shared or remembered. Check prerequisites: some need masks or prepared assets.

Your recipe starts here.

Add a style to begin building.