Cool Technology F03

Pairs well with

# CES style instruction — F03 Cool Technology

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

**Colour & Finish** — Cool Technology moves the white balance a few hundred Kelvin toward daylight-blue, refines blues and cyans, and adds crisp contrast so edges and interfaces feel precise. Electronic accents — monitors, LED strips, neon — are kept saturated but below clipping, and can be reinforced with a subtle rim glow. Skin is qualified out of the cool shift so faces stay human instead of turning grey-blue.

### F03 Cool Technology

- **When:** Applies to the whole video
- **Layer / track:** Whole composition
- **What it does:** Shifts whites neutral-to-cool, deepens blues, tightens contrast and keeps screen glows and LED accents controlled — a precise, modern tech finish with natural skin.
- **Parameters:** Grade strength (mix): 90%; Cool shift (K): -500; Tint (− green / + magenta): -2; Contrast: 14%; Saturation: 92%; Electronic accent colour: #38D6FF; Accent rim glow: on; Protect skin tones: on
- **Steps:**
  1. Apply the Cool Technology grade as one global adjustment across the entire 1080×1920 @ 30fps timeline — every camera shot and b-roll clip gets identical settings; no shot is graded in isolation. Pipeline order: source footage → primary balance → this grade → captions, titles, logos and UI graphics composited on top. Do not run brand graphics through the grade; #D7FF5F and the caption whites must render exactly as specified. Screen recordings and supplied screenshots get at most 30% of the grade strength so text and interface colours stay faithful.
  2. Balance each shot neutral, then cool the image by ≈500 K (colortemperature=temperature=7000:mix=0.9:pl=1) and apply tint -2 (colorbalance midtones gm=0.02). Lift −2% with a slight blue offset in shadows (colorbalance bs=0.05:rs=-0.03), gamma 0, gain held so whites read neutral-cool (#F2F6FF) at ≤ 96 IRE.
  3. Contrast +13% (curves=master='0/0.01 0.25/0.21 0.5/0.5 0.75/0.79 1/0.96'), overall saturation 93%, then boost only blues/cyans: huesaturation=saturation=0.11:colors=c+b. FFmpeg chain: -vf "colortemperature=temperature=7000:mix=0.9:pl=1,colorbalance=rs=-0.03:bs=0.05:gm=0.02:pl=1,eq=contrast=1.126:saturation=0.928,curves=master='0/0.01 0.25/0.21 0.5/0.5 0.75/0.79 1/0.96',huesaturation=saturation=0.11:colors=c+b".
  4. Electronic accents: keep screens, LEDs and neon in the #38D6FF family saturated but below 98% on every channel. Reinforce existing accent light with an edge glow only where it already exists in the shot — a soft #38D6FF rim (blurred subject-edge mask or a screen-blended radial at 15–25% opacity) on the side facing the light source. Never add glow to shots without a visible source.
  5. Protect skin: sample the median skin colour from a well-exposed cheek/forehead area (hex, e.g. 0xC08A6E — use the real sample) and build a hue-qualified matte around the ~20–30° skin hue range: [pre]colorkey=color=<skinHex>:similarity=0.16:blend=0.10,alphaextract,negate,gblur=sigma=4[skinMatte]; [balanced][skinMatte]alphamerge,colorchannelmixer=aa=0.85[skin]; [graded][skin]overlay=format=auto. This keeps faces on the vectorscope skin line (≈123°) while the look shifts everything else. Check the matte is soft-edged and does not catch wood, sand or orange props; tighten similarity if it does.
  6. Remotion approximation (motion-graphics plates, previews, or when FFmpeg is not in the pipeline): wrap each footage <OffthreadVideo> in an <AbsoluteFill style={{ filter: "contrast(1.126) saturate(0.928) hue-rotate(-1deg)" }}>, then add <AbsoluteFill style={{ background: "#3D6DFF", mixBlendMode: "soft-light", opacity: 0.18 }} /> (with a CSS mask-image radial hole over faces when skin protection is on). CSS filters run in 8-bit display space, so for the final master prefer rendering the FFmpeg-graded footage and using that file in Remotion.
  7. Verify before export: grab one frame per shot (ffmpeg -ss <t> -i graded.mp4 -frames:v 1 shotN.png) and inspect ffmpeg -i shotN.png -vf "split[a][b];[a]waveform=mode=column:graticule=green:flags=numbers[w];[b]vectorscope=mode=color3:graticule=green[v];[w][v]hstack" scope.png. RGB parade: highlights with blue ≥ green ≥ red by 2–4%; no channel flat-topping on screens or LEDs; skin trace still on the skin line. Shots must match each other within ±2 IRE in skin exposure and ±3° in skin hue; fix outliers with a per-shot exposure/white-balance trim before the look, never by changing the look itself. Export at 1080×1920, 30fps, 10-bit or high-bitrate 8-bit with -pix_fmt yuv420p to avoid banding in gradients and skies.
- **Assets:** Source video (⚠ MISSING) · optional: LUT file, Screen recording
- **Fallback:** If the footage was shot under warm tungsten light and the cool shift turns skin grey even with protection, halve the Kelvin shift and push the coolness into the shadows only (colorbalance shadows) instead of the whole image.

**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.