tesseract-3d

Design editable 3D scenes with Tesseract

The CLI may send basic usage telemetry for some commands. You can provide optional attribution via TESSERACT_SKILL=tesseract-3d and the other attribution variables. Respect the CLI's telemetry opt-out setting; never enable telemetry on the user's behalf.

1. Resolve this skill's root from the directory containing this SKILL.md. Read CLI installation and check the required Tesseract version once per session. Use the resolved executable path throughout the task. Scene3D requires a 3D-enabled CLI build: save tsrct project schema to a file and search it for createFxScene3DLayer (never print the whole schema). If it is absent, stop and tell the user that this CLI cannot author 3D scenes; do not substitute 2D layers or retry the actions. Read local operation and native authoring.
2. Read Scene3D basics, including its validator rules. Start from the matching recipes. When the user describes the work in Blender terms, use Scene3D for Blender users to pick the closest control and to name what has no equivalent. Establish the canvas, intended camera view, scale (pixelsPerMeter) and timing. For --hdr, an HDR delivery, hdrGraphicsWhiteNits, RGB above 1, or HDR stills, read HDR; a Radiance .hdr environment map needs only Scene3D basics. Preserve existing identities, animation and packaged resources when revising a scene.
3. Choose the renderer: prefer the path tracer for realistic lighting, reflections and refraction; use raster for stylized graphics and fast layout or motion checks.
4. Build native editable items rather than a prerendered image. Look up each action's exact fields in tsrct project schema before writing it; do not invent property names, enum spellings or commands. Apply in small batches and stop at a rejected batch before rendering. For imported models, read the conversion diagnostics and list clips, morphs and node overrides in poseStack (see imported models).
5. Use filmstrip review at feature-critical times. Animation is verified only when the sampled frames visibly differ; a stored keyframe or binding is not proof. Inspect saved JSON after structural edits and reload the document before delivery. Check representative frames with the final renderer and settings and estimate the cost before a long export. Before step 6, follow review and delivery and run the relevant tsrct evaluate --checks recipes in Scene3D basics, fix actionable findings, and rerun them. Use scene3d.items only when you also need per-item measurements; it does not run checks by itself.
6. Read and follow the critic review: two independent critics, an art director and a specialist for the scene's purpose, such as a product visualization lead for a product shot, score the rendered preview, and you revise between rounds until both rate it at least 8.5/10, for at most three review rounds. For a path-traced scene, render the views you give the critics with the final renderer flags, and give those flags on their Renderer line. Tell the user the review plan, each round's scores and feedback, and the final score.
7. Deliver the editable .tsrct and a rendered preview. Say which renders used the path tracer and with which flags. Explain unsupported controls, import losses, approximations and unverified output rather than silently replacing the design. Keep checkpoints, dumps and review renders lean as described in storage; detailed scenes make every full copy large.