Aura3D turns a sentence into a polished browser 3D scene your team can actually own. Primitives, particles, physics, data worlds, cities, characters, materials, and real GLB assets all flow into clean TypeScript. It feels like magic. It ships like software.
A fictional tactical showcase built around poster-grade art direction, playable smoke checks, summit remix controls, accessibility settings, route health, and deploy evidence. It is designed to prove the SDK can carry a real marketing moment without hiding the engineering contract.
Aura3D gives AI coding assistants the nouns and verbs of browser 3D: scenes, models, lights, cameras, materials, effects, interactions, UI, and deployment-ready assets behind a compact TypeScript API. The result is fast to generate and simple to refine.
// Typed GLB path: register once, then compose the scene. import { createAuraApp, scene, model, camera, lights, effects } from "@aura3d/engine"; import { assets } from "./aura-assets"; createAuraApp("#app", { diagnostics: { overlay: true }, scene: scene({ background: "#05070a" }) .add(model(assets.boombox, { scale: 1.2 })) .add(lights.studio({ intensity: 1.2 })) .camera(camera.orbit({ distance: 4 })) .add(effects.bloom({ intensity: 0.35 })) }); // Typed assets keep the model path stable across builds.
Aura3D gives prompts structure: cinematic particles, physical playgrounds, data galaxies, material labs, city blocks, mini-games, humanoids, and product viewers. The assistant starts with a maintained scene system, then edits the TypeScript you own.
// Prompt + asset path: bring the GLB, then stage it. import { createAuraApp, sceneKits } from "@aura3d/engine"; import { assets } from "./aura-assets"; const kit = sceneKits.productViewer({ asset: assets.conceptCar, lighting: "cinematic", controls: "orbit", }); createAuraApp("#app", kit.toAppOptions());
Aura3D examples show the whole range: generated primitive systems, particles, materials, data scenes, interactions, and real GLB/glTF product assets. Click any card and open the actual app route.
The assistant starts with a scene kit, then shapes primitives, controls, labels, physics, and motion into something that feels finished.
When a real product or character arrives as GLB/glTF, Aura3D makes it typed, centered, lit, interactive, and ready for a product page.
Start with a template, add a real asset, and let the assistant shape the scene. Aura3D handles the browser 3D foundation so your team can focus on the moment users see.
Aura3D brings the production pieces together: engine API, prompt workflow, GLB/glTF asset CLI, React adapter, scene kits, diagnostics, static deploy checks, and lower-level packages for teams that want full control.
A 3D landing page has to feel effortless: fast first load, correct assets, clear controls, and no broken routes. Aura3D keeps those production details close to the code.
Aura3D starts with the dependable browser path and lets advanced examples opt into WebGPU when the browser supports it. The page remains clear, fast, and understandable.
The practical default for agent-written browser 3D: canvas setup, resize, render loop, camera, lights, interactions, and cleanup handled by the app API.
WebGPU examples depend on browser support. If the browser exposes navigator.gpu, routes can use it. If not, Aura3D keeps the route on the supported browser path.
The CLI fingerprints the file, writes the manifest, and generates typed asset references. From there, the assistant can compose a polished product scene without brittle paths.
# The file already exists on disk. npx @aura3d/cli@latest assets add \ ./assets/robot.glb \ --name robot \ --public-path /aura-assets/ # Generated files: ./aura.assets.json ./src/aura-assets.ts
import { assets } from "./aura-assets"; scene() .add(model(assets.robot)) .add(lights.studio()); // Stable path: model(assets.robot)
Describe the scene. Generate primitives, particles, physics, data, controls, and product viewers. Bring real GLB assets when you have them. Aura3D turns browser 3D into a product surface your team can design, edit, and ship.