explodedview
/explodedview — an object → a 3D exploded product viewer
The output is ONE self-contained HTML page (about 700 KB; the three.js bundle is inlined, no network requests): an eyebrow, a headline with a colour accent, a lede, chips, a 3D viewer, the parts list, the assembly steps (reading guide), 3 takeaways and a footnote. The agent writes data, not geometry code: a JSON spec describes every part as a few primitive shapes with material presets; the page's engine builds the model, lights it like a studio and gives it a professional viewer UI.
It must look like a manufacturer's product-viewer render and stay true: real proportions, correct part names, correct assembly order, nothing invented. The models are illustrative (primitives, not CAD) and the footnote says so.
Page theme: pages open in the Deep dark theme (a dark studio). A ☀/☾ button (built into the template, top right) switches to the light studio and remembers the choice; the device's own dark mode is ignored. The 3D scene repaints live. Don't remove the button or add your own theme CSS. Check both themes (the validator renders both). Printing is always light: a still image of the EXPLODED view plus the parts list; controls and sidebar are hidden.
Usage
/explodedview <object> — optional extras: level ("simple", "detailed"), version or size ("147 mm phone"), audience,
handwritten, language. Defaults: the common version of the object, 6–10 parts, English.
If the user gives only /explodedview with no object, ask for the object in one short line.