Build 3D models in code

Two commands

Runs in Node. No modelling app, no DOM, nothing to log into. What comes out is a plain .glb, so it drops into Godot, Unity, Unreal or a web page the same as any other asset, and nothing from the kit ships with your game.

npm i antics-modelkit three
npx modelkit build models.mjs

A file that returns parts

One function per model, using the kit's own verbs. You don't implement these, they come with the package. Every part gets a name, so a page can open the lid, spin the wheel or light the sign without touching geometry.

import { box, sit } from "antics-modelkit";

export function crate(w = 0.6) {
  return { category: "prop", parts: [
    { name: "body", geometry: sit(box(w, w, w)), color: 0x8a6b45 },
  ] };
}

The checks are the point

A surface built inside out does not look wrong — it vanishes, and gets debugged as a lighting bug. The build refuses that, and refuses anything a glTF reader would reject, so what builds opens anywhere. Stray triangles it strips; holes you can see into it warns you about. It will also render the thing at play size and tell you when it is unreadable.

A pocket watch, from a photograph

Modelled from a single reference photo. The lid opens onto a movement that turns, and the recipe that generates it ships on the page — change the case size and build your own.

It already knows how

Point a coding agent at the docs and it can build, check and publish a model on its own. Our MCP server also lets it search the catalogue by part name — ask for something with a shutter and it finds the shophouse.

Read https://antics.gg/modelkit/llms.txt, then build me a 3D model with antics-modelkit and export it as a .glb

The source ships with it

The package carries its own source, unminified and commented — read it on npm without installing anything. MIT, so you can change it, build on it and use it commercially. The recipes on every model page are MIT too.