---
name: demo-ai-build-film
description: >-
  The shot rules for a film of an AI building something in Adom Hydrogen (a PCB with adom-aiflow and
  KiCad, Fusion or Altium, a dashboard app, any long AI run): Hydrogen always full screen with the
  Windows taskbar showing, every other app (KiCad, a pup window, Adom Fields) at 90 percent floating
  over it, the AI panel filling the VS Code pane and visibly working, never a file explorer, never a
  blur, never a dialog, upright 3D, the board filling KiCad's canvas, real-time 3D field views, and
  an ending that shows the share of the plan used, not hours. Read before you set up the desktop, not
  after the take. Trigger words: AI build film, AI PCB video, film the AI building, demo video of a
  run, Hydrogen demo video, record the build, re-film a step, aiflow demo mode, 90 percent window,
  taskbar showing, upside down board, file explorer in the shot, blur, plan usage ending.
---

# Filming an AI build in Hydrogen

The viewer has never seen Hydrogen. Every shot has to tell them where they are: the Hydrogen desktop,
the AI on the left, the apps it drives floating on top. These rules came from one owner's review of a
four-minute film of Gemini 4 Argon building a buck converter; each one cost a re-shoot.

## Set the stage before the camera rolls

- **Hydrogen full screen, Windows taskbar visible, in every shot.** The taskbar icons are part of the
  story ("this is a whole desktop"). Never crop or blur it.
- **The AI panel fills the VS Code pane.** Move the AI's view into VS Code's panel (activity bar icon,
  right-click, Move To, Panel), close the sidebar (`workbench.action.closeSidebar`), hide the editor
  area (`workbench.action.toggleEditorVisibility`), and hide every other panel tab. A reload (sign-in,
  update) brings the sidebar back: re-check before every take.
- **Never the VS Code file explorer, never another AI's tab** in any shot.
- **The AI is visibly working in every Hydrogen shot.** A still panel next to a moving dashboard reads
  as fake. Give the AI real, read-only work about the step on screen and start the camera once its
  output has filled the panel.
- **Other apps float at 90 percent over Hydrogen**: KiCad's editors and 3D viewer, a pup window with a
  dashboard (Adom Fields), any desktop app. Same bounds every time (on 2560 x 1600: x 128, y 76,
  2304 x 1376) so the cuts don't jump.
- **Show dashboards in Hydrogen webviews or pup windows.** Adom apps in a webview (the AI Flow
  timeline, wiki part pages with their 3D viewer) teach the viewer that Hydrogen is more than a chat.
- **The usage widget fully visible** in Hydrogen shots; show the Hydrogen Widgets menu once so viewers
  learn where it comes from, and circle its value at the start and at the end.
- **Notifications off** for the take; check that no other thread is using the machine
  (`desktop_user_idle_ms`, the window list) and roll only after a quiet minute.

## Shots

- **The prompt**: push in toward the chat box while it types; about three seconds of typing.
- **Wiki part pages**: film each one after its 3D viewer has loaded (`adom-cli hydrogen webview drive
  --name <tab> ready --viewer 3d`), never the loading spinner sped up.
- **Prove the parts reached the EDA tool**: each part's symbol, footprint and 3D model in KiCad's own
  windows (`kicad_show_symbol`, `kicad_show_footprint`, `kicad_show_3d_chip`).
- **Schematic**: the whole sheet for a second or two, then a slow push in and pan.
- **Placement**: part by part, fast (about three seconds for the lot), every move a bridge call with no
  mouse. The board fills KiCad's canvas, never small and tucked at the top.
- **Silkscreen**: the board without it, then with it: the labels popping in.
- **Loop backs**: the AI Flow timeline full screen on the loop-back banner, then the fix itself.
- **Adom Fields**: real time (a sped-up slow rotation becomes dizzy rocking), about two seconds per
  view. For views whose field lives between the layers (energy, magnetic), pull the stack apart and
  hide the part bodies so the field is actually visible.
- **3D tour in KiCad's 3D viewer**: the top face reads like a board on a table (the near edge at the
  bottom of the frame); a view where the far edge looks wider reads as upside down. One slow orbit, a
  close pass, then the bottom face as its own shot (bottom view, tilted, labels upright). Never spin
  twice, never roll through edge-on.

## Never

- Blur anything. A clip that would need a blur (an email address, a name) is dropped.
- Show a dialog of any kind: confirmations, errors, update banners. File an issue on the tool that
  raised an error dialog.
- Repeat a clip. A second visit to a page must show something new, in one smooth eased scroll.
- Hold a static shot with nothing happening.
- Cover a window with a patched or faked widget.

## Re-filming a finished run

`adom-aiflow --run <run> demo at <step|step@n|ISO> --title "<board name>"` rebuilds the AI Flow
timeline as it stood at that moment into `<run>/demo/`; `demo serve --port <port>` serves it for a
Hydrogen tab of its own, and each later `demo at` updates the open page in place. The run's own state
is never written. Replay placement and silkscreen from the run's saved boards and move logs, in a
scratch copy of the project.

## The ending

No text-only summary card. The finished board turning in 3D beside the figures. Lead with the share
of the plan the build used, then the cost of that share; token counts are secondary. Never quote wall
clock hours: idle time between prompts makes them misleading.