An AI agent skill that turns any subject into a 3D film or app
Add stage cameras, simulation speed and a stage tour
Nguyen Xuan An55ccd55d6d5f
diff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/SKILL.md b/plugins/visualize-in-3d/skills/visualize-in-3d/SKILL.mdindex 4a8a21f..e1c91bb 100644--- a/plugins/visualize-in-3d/skills/visualize-in-3d/SKILL.md+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/SKILL.md@@ -39,7 +39,8 @@ Paths use `{{WORK_DIR}}` for the folder where projects live (the current directo1. **Write the topic file** `{{WORK_DIR}}/TOPIC-<slug>.md` in the shape of the files in `examples/` (airport ramp,AI data center, agent office, wildfire valley): folder and port, sites, the world (real parts of the place and what- moves), data (units, tasks, fields), four KPIs, what the bottom timeline follows, made-up names, and the look (toy isometric when the user names none).+ moves), data (units, tasks, fields), four KPIs, the key stages of the process in order (each with where it happens+ and the event that marks it), what the bottom timeline follows, made-up names, and the look (toy isometric when the user names none).Research the real operation first and list the real object types the main assets stand for.2. **Pass 1, assets** with the Pass 1 brief (`references/brief.md`), or `references/no-blender.md` without Blender.3. **Pass 2, app and film** with the Pass 2 brief, once pass 1 is checked.diff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/examples/agent-office.md b/plugins/visualize-in-3d/skills/visualize-in-3d/examples/agent-office.mdindex 57e4813..4738905 100644--- a/plugins/visualize-in-3d/skills/visualize-in-3d/examples/agent-office.md+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/examples/agent-office.md@@ -1,2 +1,2 @@Your folder: {{WORK_DIR}}/viz-agent-office (create it). Port 5422.-Subject: an AI agents office, the "workers" of a desktop app called Orglet (by CodePawl), shown as a little isometric office where each AI agent is a character. Before designing, read what Orglet really does from its public repository, https://github.com/codepawl/orglet (read only: its README files and docs), and show only real features and concepts from it (for example agents, tasks, tools, approvals, if that is what the docs say). Sites are teams or workspaces. The world: desks, rooms such as a research corner, a coding room, a review room and a mailroom; agent characters walk between rooms carrying task cards; a manager desk where tasks arrive; approval stations where a human signs off. Data: agents (name, role, current task, tool in use, tokens spent), tasks with stages, approvals waiting. KPIs that fit the real product. Characters are original simple chunky low-poly figures, not any existing character. If something you would like to show is not in Orglet's docs, leave it out and list it in your report.+Subject: an AI agents office, the "workers" of a desktop app called Orglet (by CodePawl), shown as a little isometric office where each AI agent is a character. Before designing, read what Orglet really does from its public repository, https://github.com/codepawl/orglet (read only: its README files and docs), and show only real features and concepts from it (for example agents, tasks, tools, approvals, if that is what the docs say). Sites are teams or workspaces. The world: desks, rooms such as a research corner, a coding room, a review room and a mailroom; agent characters walk between rooms carrying task cards; a manager desk where tasks arrive; approval stations where a human signs off. Data: agents (name, role, current task, tool in use, tokens spent), tasks with stages, approvals waiting. Stages, each with its own camera: task arrives at the manager desk, an agent picks it up, research, coding, review, approval signed by a human. KPIs that fit the real product. Characters are original simple chunky low-poly figures, not any existing character. If something you would like to show is not in Orglet's docs, leave it out and list it in your report.diff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/examples/ai-datacenter.md b/plugins/visualize-in-3d/skills/visualize-in-3d/examples/ai-datacenter.mdindex cd64c83..d68b845 100644--- a/plugins/visualize-in-3d/skills/visualize-in-3d/examples/ai-datacenter.md+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/examples/ai-datacenter.md@@ -1,2 +1,2 @@Your folder: {{WORK_DIR}}/viz-datacenter (create it). Port 5421.-Subject: an AI data center operations app. Sites are data halls on a campus. The world: rows of server racks with glowing GPU trays whose colour follows temperature, hot and cold aisles, overhead cable trays, cooling units and chillers outside, power substations and battery rooms, robot carts that swap failed drives and GPUs, technicians walking. Data: training and inference jobs (progress, GPUs used, tokens per second), rack temperature and power draw, alerts (a GPU failing, a cooling unit degrading), maintenance tickets. KPIs: tokens per second, GPUs busy, PUE, power in megawatts. The bottom timeline follows one training run's stages. Use plausible, clearly made-up numbers and names; no real company or model names.+Subject: an AI data center operations app. Sites are data halls on a campus. The world: rows of server racks with glowing GPU trays whose colour follows temperature, hot and cold aisles, overhead cable trays, cooling units and chillers outside, power substations and battery rooms, robot carts that swap failed drives and GPUs, technicians walking. Data: training and inference jobs (progress, GPUs used, tokens per second), rack temperature and power draw, alerts (a GPU failing, a cooling unit degrading), maintenance tickets. KPIs: tokens per second, GPUs busy, PUE, power in megawatts. The bottom timeline follows one training run's stages. Stages, each with its own camera: job queued at the scheduler, GPUs allocated (rack lights change), training (power and heat rise), checkpoint written to storage, cooling responds (chiller ramps), done. Use plausible, clearly made-up numbers and names; no real company or model names.diff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/examples/airport-ramp.md b/plugins/visualize-in-3d/skills/visualize-in-3d/examples/airport-ramp.mdindex 1a1fe69..01e0697 100644--- a/plugins/visualize-in-3d/skills/visualize-in-3d/examples/airport-ramp.md+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/examples/airport-ramp.md@@ -1,2 +1,2 @@Your folder: {{WORK_DIR}}/viz-airport (create it). Port 5423.-Subject: an airport ground operations app. Sites are terminals. The world: terminal buildings with gates and jet bridges, aircraft taxiing, parking and pushing back, baggage tugs with carts, fuel trucks, catering trucks, a control tower, runways with lights. Data: flights (gate, status, delay, turnaround progress), ground vehicles (task, battery or fuel), baggage loads, gate availability. KPIs: on-time departures, turnaround time, gates in use, bags handled. The bottom timeline follows one aircraft's turnaround stages (arrive, deboard, clean, refuel, board, push back). Use made-up airline names and logos, no real airlines.+Subject: an airport ground operations app. Sites are terminals. The world: terminal buildings with gates and jet bridges, aircraft taxiing, parking and pushing back, baggage tugs with carts, fuel trucks, catering trucks, a control tower, runways with lights. Data: flights (gate, status, delay, turnaround progress), ground vehicles (task, battery or fuel), baggage loads, gate availability. KPIs: on-time departures, turnaround time, gates in use, bags handled. The bottom timeline follows one aircraft's turnaround stages (arrive, deboard, clean, refuel, board, push back). Stages, each with its own camera: arrive at the stand (chocks on), deboard (bridge docked), bags off (belt loader running), refuel (hose connected), board, push back (tug moving). Use made-up airline names and logos, no real airlines.diff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/examples/wildfire-valley.md b/plugins/visualize-in-3d/skills/visualize-in-3d/examples/wildfire-valley.mdindex 0e923cf..34d0520 100644--- a/plugins/visualize-in-3d/skills/visualize-in-3d/examples/wildfire-valley.md+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/examples/wildfire-valley.md@@ -1,2 +1,2 @@Your folder: {{WORK_DIR}}/viz-wildfire (create it). Port 5424.-Subject: a wildfire analysis tool over real terrain (photoreal terrain look). Pick one well-documented fire with public perimeter data (agency incident reports and published fire-perimeter files by date); get the user's OK before downloading elevation and perimeter data, and record the sources. Sites are the fire's divisions or the valleys it crossed. The world: real elevation with a painted ground texture (dry grass, rock, burned ground), instanced trees, roads and the towns the fire threatened, long mountain shadows and haze. What moves: the fire front as a glowing line advancing perimeter by perimeter, smoke plumes, air tankers and helicopters flying drop runs, engines on roads. Data: perimeters by date and time, acres burned, containment percent, resources assigned, evacuation zones and their status, weather (wind speed and direction, humidity). KPIs: acres burned, containment, structures threatened, resources on scene. The bottom timeline scrubs the fire from ignition to containment; every overlay, chart and the key-events list follow it. Clicking an aircraft opens its camera feed in a thermal palette. Use the real fire's public facts for the timeline and made-up names for crews and aircraft; no agency logos.+Subject: a wildfire analysis tool over real terrain (photoreal terrain look). Pick one well-documented fire with public perimeter data (agency incident reports and published fire-perimeter files by date); get the user's OK before downloading elevation and perimeter data, and record the sources. Sites are the fire's divisions or the valleys it crossed. The world: real elevation with a painted ground texture (dry grass, rock, burned ground), instanced trees, roads and the towns the fire threatened, long mountain shadows and haze. What moves: the fire front as a glowing line advancing perimeter by perimeter, smoke plumes, air tankers and helicopters flying drop runs, engines on roads. Data: perimeters by date and time, acres burned, containment percent, resources assigned, evacuation zones and their status, weather (wind speed and direction, humidity). KPIs: acres burned, containment, structures threatened, resources on scene. The bottom timeline scrubs the fire from ignition to containment; every overlay, chart and the key-events list follow it. Stages, each with its own camera: ignition, first run uphill, evacuation of the town, air drop on the flank, line holds, containment. Clicking an aircraft opens its camera feed in a thermal palette. Use the real fire's public facts for the timeline and made-up names for crews and aircraft; no agency logos.diff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/references/brief.md b/plugins/visualize-in-3d/skills/visualize-in-3d/references/brief.mdindex 26a59e0..fe7efab 100644--- a/plugins/visualize-in-3d/skills/visualize-in-3d/references/brief.md+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/references/brief.md@@ -94,12 +94,29 @@ and opens its card; clicking a list row flies the camera to it (and follows it ithe world. Soft shadows, ambient occlusion, gentle bloom on lights, smooth camera moves. 60 fps at 1920x1080 on amid-range GPU such as an RTX 3060.+Stages and playback. The topic lists the key stages of the process (for a toll: queue, booth or reader, class set,+paid, posted). Each stage gets a named camera preset framed on where that stage happens, close enough that the unit+doing it fills about a quarter of the frame, from the side that shows the moving part (the boom, the tray, the hold+door), never through a wall or roof. A stage bar lists them in process order with a number key each (1 to 9); picking+one flies the camera there in about a second, and "Next stage" and "Previous stage" step through them. A "Tour"+button plays the stages in order, holding each until its event has happened once, then moves on; any click or drag+stops it. Per selected unit, "Follow" keeps the camera on it with three distances (close, mid, wide), and the card+shows which stage it is in, and how long it has been in it. Playback controls sit in the timeline strip: pause and+play (Space), speed 0.25x, 1x, 2x, 5x and 10x (keys - and +), and "Step" that advances one fixed step while+paused. Speed changes how many fixed steps run per frame (fractional speeds accumulate), never the step length, so the+simulation stays deterministic and the same seed gives the same result at every speed; the clock and every rate on+the KPI cards follow simulation time. "Slow down at events" (on by default in the tour) eases to 0.25x for the+second around a stage's key event and back. Store the camera presets in one data file, and expose them and the speed on+window.__app for the checks and the film.+UI rules: no small uppercase eyebrow labels above headings, no coloured left-border callouts, no divider linesbetween rows (spacing and subtle fills instead), every status starts with an icon whose shape differs per state, tabsare quiet text buttons, a card closes by clicking empty ground or Esc (no X on side panels).Verify with Playwright (Chromium with --enable-gpu --ignore-gpu-blocklist, plus --use-angle=d3d11 on Windows) at 1920x1080: the overview, a selected object with its card, a second site, a-close-up, plus close-ups of each main asset type. Look at every one and fix clipping, overlapping UI, unreadable+close-up, close-ups of each main asset type, and one per stage camera preset. Check that pause freezes every+moving part, that 5x and 0.25x keep the same order of events as 1x for the same seed, and that the tour runs+through every stage once. Look at every one and fix clipping, overlapping UI, unreadabletext, z-fighting, floating or sunken objects, broken picking, anything that looks like programmer art. Measure fps.Film: 30 s 1920x1080 30 fps at shots/film.mp4 with a deterministic virtual clock (override requestAnimationFrame,@@ -114,7 +131,8 @@ enough that dozens of moving units read); a beat that waits on the simulation anvirtual clock so the followed event lands 2-3 s into its beat); a follow camera that ends inside a structure (keep aminimum distance and a height above the tallest model); selection rings far wider than the object (fit thefootprint, an ellipse for long things, at most about 1.3x); bare white or grey ground (give every surface a real-material: asphalt, lane paint, verges, floors); a last shot where the site is small in a sea of empty ground.+material: asphalt, lane paint, verges, floors); a last shot where the site is small in a sea of empty ground. Use the stage presets for the film's beats instead of+free camera moves when a beat shows one stage, and show a speed change (2x or 5x) once with the control on screen.Record the film as {{SKILL_DIR}}/references/film.md "Live app films" says. Run the dev server as a backgroundjob and stop it when done. Write README.md, pass2_started_at.txt and pass2_finished_at.txt (UTC). Budget about 100 tool calls. Report: what wasdiff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/references/film.md b/plugins/visualize-in-3d/skills/visualize-in-3d/references/film.mdindex faf816e..cf203bd 100644--- a/plugins/visualize-in-3d/skills/visualize-in-3d/references/film.md+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/references/film.md@@ -82,6 +82,9 @@ leans on them most. Reading map: Pacing and text, Camera, Figures and places, Ma- A plain-words strip carries one short line at a time, on the caption timer above.- A roof or canopy that hides the action from the camera angle goes semi-transparent (about 30% opacity).- Fly-to moves own the camera until they finish; a drag during a fly makes the camera jump.+- A beat that shows one stage starts from that stage's camera preset (press its number key or click it in the+ stage bar), so the framing matches the app. Show one speed change on screen (2x or 5x, then back to 1x); the+ virtual clock still advances 1/30 s per frame and the app runs more simulation steps in it.## Checks