Skip to content

Playbook and Three.js code kit for detailed dioramas: classic pixel art, stroked toon or pixel + stroke; two intake gates for look and model sourcing; free orbit, palette snap and ink; animated toy-scale cast; per-entity frame QA.

2.2 KB
Raw Blame

Construction-first pipeline

This is the operational order for all profiles/presets. The former palette-first sequence is retained only in the 3.18 backup, not as an alternate workflow.

  1. Resolve scope, profile and render preset. Read only routed recipes. Fill the compact DESIGN inventory from whole-object references.
  2. Dimension the site/object: units, top-surface datums, hierarchy, lots and full envelopes, access paths and interfaces.
  3. Build a neutral representative complete assembly with native-axis-safe helpers. Inspect grey front/side/rear views and measure contacts, openings and neighbour clearance.
  4. Replicate from shared data/frame tables. Validate every instance and required member, including rear/exterior/attachments.
  5. Evaluate mechanism or narrative motion from one driver. Test extrema, contacts, transitions, seam and closest-approach intervals; constrain full geometry, not centres.
  6. Add meaningful structural/functional detail, then signature narrative/educational detail. Recompute envelopes and contacts after canopies, trim, fittings and moving pieces are added.
  7. Apply one selected presentation recipe. Pixel uses palette/post; toon uses native smooth contours and four-tone materials; hybrid composes toon with one nearest-upscale low-res pass. Fit the real complete/swept subject to the measured UI-safe stage.
  8. Bind semantic selection ownership, live local callouts, constrained FX and profile UI. Materials must restore exactly; labels/ports/emitters follow their source transforms.
  9. Run geometry tests with required negative injections; render hero/reverse/high/critical-interface and selected/restored phone views; test pointer/keyboard/control lifecycles, deterministic freeze and standalone loading.
  10. Build the final artifact, identify its loaded hash, rerun affected checks and reconcile DESIGN/readme/evidence. FAIL/UNVERIFIED never becomes PASS through a screenshot or a confidence statement.

Narrative cast, locomotion, queues, combat, exits and five-layer acting apply only to implemented narrative features. Educational scenes require complete causal construction and lessons, not fictional actors or attack quotas. Presentation recipes cannot waive physical checks.