Skip to content

armgit / viz3d

Public Imported from GitHub
0

An AI agent skill that turns any subject into a 3D film or app

Default to a light UI with explanatory motion and themes

Nguyen Xuan An01a24e8ac460
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.md
index c8430c1..76cd4b1 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
@@ -71,11 +71,22 @@ Build a live 3D app in the browser that makes a complex place or system easy to
(read it first), using the GLB asset pack in {{FOLDER}}/app/public/assets (read blender/ASSETS.md). Render the
world, skin the UI and shape the film as the look named in the topic says (its section in
{{SKILL_DIR}}/references/looks.md, and its reference files). In every look: a
-world with things moving on their own; pins and selection rings over objects; a real dashboard around the
-scene (top bar with search, site switcher, live clock and user; KPI cards top left; a detail card on the right that
-opens for any clicked object with live fields and a progress bar; a timeline strip at the bottom; tabs of lists at
-the bottom right; zoom and camera buttons). Make your own name, logo and data; do not copy the reference's name,
-logo, text or exact layout. Never call it a game in the UI.
+world with things moving on their own; pins and selection rings over objects; and a light UI that keeps the world
+the main thing on screen. Start from the smallest UI the topic needs: a name, the few numbers that matter (two to four
+KPIs), a detail card that opens for a clicked object, the stage bar and the playback controls. Buttons are few, large
+enough to hit, plainly labelled and do one thing each. Do not add a default dashboard (search, site switcher, user
+menu, list tabs, extra panels) unless the topic needs it or the user asks; when the user asks for a specific panel or
+control, build that one to their need. Make your own name, logo and data; do not copy the reference's name, logo,
+text or exact layout. Never call it a game in the UI.
+
+Motion that explains. Animate what the viewer must understand: the parts move as the process does, flows (goods,
+power, fluid, people, data) travel along their real paths as moving particles or arrows, the part a stage is about
+glows while the rest dims, numbers count to their new value, cards and the stage bar slide in rather than pop, and the
+camera eases between stages. Every motion shows a fact of the process; nothing moves only for decoration.
+
+Themes. Ship three themes switched by one quiet button and remembered per viewer: the look's own palette, a dark
+one and one more that suits the topic (blueprint, paper, night shift). A theme changes the scene's lights, ground and
+materials as well as the UI colours, and every theme keeps text contrast readable.
Work only in {{FOLDER}}/app. Stack: Vite + React + React Three Fiber (+ drei, @react-three/postprocessing with N8AO for ambient occlusion), and
Playwright as a dev dependency for checks and the film, all pinned to exact versions, serve on port
diff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/references/live-embed.md b/plugins/visualize-in-3d/skills/visualize-in-3d/references/live-embed.md
index d1dfb16..68a2d0b 100644
--- a/plugins/visualize-in-3d/skills/visualize-in-3d/references/live-embed.md
+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/references/live-embed.md
@@ -24,9 +24,11 @@ Skip Pass 1 and do not ask about Blender. Build everything in one pass in `{{FOL
(`real-objects.md`): proportions and part count still matter.
3. **The look carries the quality.** Toy isometric from `looks.md`: soft shadows, N8AO, a warm key light, a ground
with real materials, flat colours from one palette. Clean primitives under good light read as a design choice.
-4. **Data the leaders recognise.** Ask for a sample export (CSV or JSON) and its field names. With a sample, map it
+4. **A light UI, motion that explains, three themes**, as the Pass 2 brief says: few plain buttons, no default
+ dashboard, flows and stages animated, and panels added only when the user asks for them.
+5. **Data the leaders recognise.** Ask for a sample export (CSV or JSON) and its field names. With a sample, map it
as in "Field mapping" below. Without one, seed a simulation with the real counts and rates from the topic research.
-5. **Done when** the overview, a clicked unit with its card and each stage preset look right in screenshots, it runs
+6. **Done when** the overview, a clicked unit with its card and each stage preset look right in screenshots, it runs
at 60 fps, and `npm run build` gives a static folder that opens from any web server.
Budget about 60 tool calls. Report the URL to run it, the screenshots, and what a full build adds (Blender models,