Overview
This section covers the technical requirements for building a three.js 3D preview into a creative tool / generator on the Atomm platform — architecture, interaction, render quality, and performance and stability — and closes with a pre-submission acceptance checklist.
Applies to: every generator app that ships a 3D preview view.
The same requirements are also written as a single-file skill for coding agents (Download 3D Preview Skill, top right). Hand it straight to yours.
The demo below is what an agent built after reading that skill: drag to orbit, scroll to zoom, and every parameter on the right feeds one geometry IR that the 2D preview, the 3D view and the exported SVG all read from.
How to read the requirement levels
| Term | Meaning |
|---|---|
| Must | Mandatory. Checked item by item at review. |
| Should | The default. Deviate only with a good reason. |
| Optional | Implement it if your product needs it. |
Do you need a 3D preview at all?
A 3D preview is optional. Build one only when thickness, stacked depth or how parts fit together is core to what your tool has to show. If the output is essentially flat, use a 2D SVG with a procedural material texture instead (a feTurbulence wood-grain filter, for example) — you get the material read at a fraction of the cost.
Once you decide to build one, it has to meet every acceptance criterion below. A 3D preview that falls short of the interaction and rendering baseline makes the product feel worse than no 3D at all, and will not pass review.