3dviz-pro-max Checked

artistic quality:

   python3 scripts/host-probe.py --out host.json
   python3 scripts/design-context.py "<objective>" --blueprints --host host.json \
     --delivery web-desktop --hero <blueprint-id>

T0–T4 describe the existing kit pipelines and their declared proof status. The legacy

quality_ceiling field is a shipped-kit pipeline recommendation, not a limit on custom geometry,

external assets, procedural materials or the agent's creativity. A missing kit tier does not

prohibit another construction method. Blender availability does not make an object high quality;

Three.js-only construction does not make it low quality.

6. **Build a convincing first view.** Keep the user's stack. Reuse shared scripts, renderer setup,

rigs and scaffold (templates/README.md), material utilities and geometry operations where they

help. For a large scene or collection, inspect one representative demanding object or scene before

multiplying the approach. A kit-shaped prototype should not silently become the finished hero.

Author custom geometry, shaders, materials, textures, lighting and interactions as needed. Use

Blender for suitable modeling, sculpting, rigging, UV or baking work; use Three.js for suitable

procedural geometry, interactive state and rendering. Choose their handoff deliberately.

For a distinctive finish, develop palette and material direction (references/object-craft.md#develop-a-material-direction)

from useful references: translate them into part assignments, surface scale and light response.

Material refinement can strengthen a good form; keep evaluating shape and attachments separately.

When adding or changing directional, practical, day/night or rescaled lighting, read

lighting direction and scale (references/lighting-direction-and-scale.md) before implementing the

rig. Identify emitter/receiver ownership and final world scale; choose the artistic treatment freely.

7. **Make behavior belong to the model.** Keep transforms, joints, contacts and controls tied to

their authoritative state. Inspect surrounding objects too: a stand needs support, a light ray

must stop at an opaque obstacle in its modeled scene, a creature needs clearance. An illustration

may simplify physics, but should not accidentally imply a simulation it does not perform.

Allocate reusable geometry once where practical; update transforms, uniforms or buffers during

motion. Park static scenes and respect reduced-motion preferences. Do not remove identity-defining

detail merely to meet an unmeasured budget; optimize what actually costs work.

Use subject clarity and meaningful motion (references/subject-clarity-and-motion.md) when

identity, mechanism or control effects are unclear. Explain what changes and stays fixed; keep

landmarks, color meanings and readouts synchronized with the visible state. Check local deformation

and attachments through relevant extremes, not just the resting silhouette.

8. **Run and inspect the real output.** Build through the project's existing commands, then view

the artifact in an available authorized browser. Inspect overview, meaningful close-ups and the

important interactions. If automated capture is allowed, the optional shared command is:

   pnpm build
   python3 scripts/capture.py --dir dist --all-views --click "#control" --out captures

Add --motion-check 2000 --expect-motion only when the tested state should visibly move.

--expect-usable can flag gross visibility failures; it does not judge art. A visible-browser

inspection is valid when headless execution is excluded. Never describe an unobserved frame.

For lighting changes, inspect source isolation at fixed exposure, an informative direction change,

and any output/reset controls. Check affected receivers and occluders, not just glowing bulbs.

Preserve the user's motion and camera choices across lighting modes unless a control promises reset.

9. **Refine by subject and evidence.** Use visual review (templates/checklists/visual-anti-slop.md)

and interaction/frame inspection (templates/checklists/inspection-per-frame.md) as conditional

prompts. Correct factual errors, broken controls and misleading relationships, then improve the

most consequential visual weakness. A failed shape may require a different construction method,

not more texture or a higher kit tier. For pinching, detached attachments or repeated pose fixes,

use regional deformation diagnosis (references/object-craft.md#diagnose-deformation-at-the-region-that-fails):

solver accuracy, surface deformation and visual quality need separate evidence. Revisit ownership

and rig assumptions after changing geometry. Continue useful refinement; reassess an approach that keeps

failing rather than applying a fixed number of cosmetic passes.

10. **Report honestly.** Separate what was built, observed, numerically checked and still limited.

Build success and collection completion do not establish artistic approval or subject clarity.

When describing skill use, distinguish guidance read, records actually retrieved and adap