anyCreature README

The project's README from github.com/Ariescar/anyCreature. As one markdown file: README.md.

anyCreature

Text → a game-ready 3D creature, in one session.

An AI session takes an order like "make me a menacing mountain giant", asks at most two questions, and delivers a skinned, animated, vertex-coloured, AO-baked GLB plus an offline showroom viewer.

License: MIT Version Engine Output Tooling

anyCreature — a winged creature compiled from a one-line order

Every creature is compiled from one JSON spec. No mesh files, no downloaded art packs, no photogrammetry. The worked example that ships with this repo, example/wolf.json, is 2,211 vertices and 31 joints written out by the engine from plain text.

Quick start

bash setup.sh                              # deps + red/green ruler calibration
node engine/cli.js example/wolf.json out/wolf.glb

setup.sh must print calibrate OK before you trust anything else: it builds one spec that has to pass and two that have to be blocked, so you know the rulers separate good from bad on your machine.

To run the full text-to-creature session, give your agent (Claude Code, Cursor, a VM agent — anything that runs shell commands) EXACTLY this:

Read MANUAL.md in this folder and follow it exactly — the cards in cards/ are the pipeline, do not improvise around them. First run bash setup.sh and confirm it prints "calibrate OK". Then make me: <describe your creature>. Real-world height: <e.g. 1.8 m>. Ask me exactly one question — card 01's — and nothing else. Not cost, not token budget, not how long, not whether to publish. Decide the rest and tell me what you chose when you deliver.

Three things that make or break the result:

Driving it harder

Knob Where What it changes
smooth_angle spec root, or per volume/part Crease threshold in degrees, default 50. Higher = smoother body, lower = more facets.
shading spec root Whole-body vertical colour ramp and grain — {gradient:{top,bottom}, noise:{size,amount}}.
build: "rigid" spec root The only way to get a fully faceted body past the checker. For robots and crystals, not for animals.
ao spec root Per-vertex ambient occlusion; false to skip the bake.
embed_spec spec root Every GLB embeds its own authored spec (asset.extras.source_spec) + a parts manifest — any agent can extract, edit, recompile, or graft parts between creatures (harness/graft.py). false opts out.
harness/claims.json QC The one claims sheet — signature presence, 6:3:1 hierarchy, focal contrast, saturated area, rig/animations, triangle budget. Everything is judged at boss standard; adjust tri_budget for cheap creatures.

What is actually in here

Folder What it holds
engine/ The ACS engine. One JSON spec in, one skinned GLB out. Zero runtime dependencies — node engine/cli.js spec.json out.glb is the whole interface.
cards/ The five stage cards the executing session reads, plus the spec syntax on one page.
harness/ Measuring tools (silhouettes, mask metrics, claims judge), the delivery packer and the publisher.
example/ A bred, approved light quadruped to read and copy from.
calibration/ One sample that must build and two that must be blocked — proof the rulers separate good from bad.

How it works

flowchart LR
    A[Order<br/>one sentence] --> B[Interview<br/>≤ 2 questions] --> C[Silhouette<br/>brief] --> D[LOW<br/>design free]
    D --> E{Gate 1<br/>RECOGNISED}
    E -->|fail| D
    E -->|pass| F{Gate 2<br/>PUNCHIER}
    F -->|reverted| D
    F -->|pass| G[MID<br/>all parts] --> H[HIGH<br/>colour + anims] --> I[SHIP<br/>stamp · deliver]

The two gates

Neither gate is self-graded. The session that designed the creature is the worst possible judge of whether it reads, because it already knows what it drew. So the silhouettes go to a context-free reader agent that has never seen the order, and the only question is "what is this?"

Gate 1 is RECOGNISED: all four views have to land. Gate 2 is PUNCHIER: a new round may only make the silhouette bolder than the last one — a round that tames the shape is reverted, even if it is "more correct". LOW's deliverable is an exaggerated silhouette, not an accurate one.

The engine floors

The compiler talks in three registers, and they mean different things:

Prefix Meaning
BLOCK: The build stops. A hard floor was crossed — faceted body, part floating off its host, a mirrored twin distorted past 30%, an attack that never reaches.
warn: It built, but something is probably wrong. Read it.
info: A number you asked for, or an assumption the compiler made on your behalf — like which way an anchored fin ended up facing.

Floors are not style opinions. They are the failures that survive review and ship broken: a body that renders in hard facets, a horn that hovers a centimetre off the skull, a right thigh collapsed to 40% depth by mirrored skinning.

What gets measured

four silhouette views the blind reader is shown

Every round renders these four views, reduces them to masks, and computes the numbers the design card declared a target for — width over height, mass thirds, torso depth contrast, leg fraction, silhouette turn count, zigzag alignment, and IoU against the previous round as a regression guard. The 24px thumbnail is what the blind reader actually sees; if it does not read at 24px, it does not read.

The doctrine in one paragraph

Head-to-head experiments showed the model designs BOLDLY when left free, and every attempt to teach it design upfront made the output tamer — so this harness ships a clean painter and a strict inspector. The creation side gets only the order, the engine syntax, and a short pit-map of engine-local traps; ALL quality control lives in gates read by context-free reader agents, never self-graded. Form beats obedience, everywhere.

Honesty about limits

Scripts

Script Role
engine/cli.js Spec → GLB. The whole engine interface.
harness/silmetrics.mjs Renders the four silhouettes and the 24px thumbnail; emits the layout metrics.
harness/maskmetrics.py Per-view mask measures and dullness flags (sq_fill, mirror_sym, straight_max).
harness/judge.mjs Claims judge — part shares, focal contrast, saturated area, rig/anim/triangle budgets.
harness/hero.mjs hero.png (1024² transparent, 45°) and hero.jpg over studio grey.
harness/deliver.py Stamps identity into the GLB, writes the offline showroom viewer, builds the upload pack.
harness/publish.mjs Gobkit publisher. Only runs after an explicit yes, and always tries the upload before offering the manual page.
harness/calibrate.py The red/green self-check setup.sh runs.

Requirements

Node 18+ and Python 3.9+. Windows: run setup.ps1 in PowerShell (or setup.sh in Git Bash/WSL). setup.sh installs three, playwright, numpy, pillow and scipy, then runs the calibration self-check. The engine alone needs nothing but Node; the dependencies are for the measuring and render tools.

Output contract

Every GLB this harness writes satisfies docs/OUTPUT_CONTRACT.md — two chunks, no trailing bytes, no external URIs, no textures (colour is baked into vertex colours), semantic material names, convention bone names. Verify any file with node harness/glbcheck.mjs <file.glb>; the same module runs as a dependency-free import inside a server or Worker.

Security

Short-lived local servers used by the render tools bind to 127.0.0.1 only, and Chromium runs with its OS sandbox enabled. The Gobkit submission key in harness/gobkit.json is public by design — it authorises posting to the community wall and nothing else. Details and reporting: SECURITY.md.

Licence

MIT — see LICENSE. One third-party component is bundled (harness/assets/three-bundle.js, three.js, MIT); attributions for it and for everything setup.sh installs are in THIRD-PARTY-NOTICES.md.

About

Gobkit: AI-native 3D infrastructure for agents and vibe coders. Stream game-ready 3D assets straight into your workflows via API. Agent-friendly. Studio-quality. Built by a team of artists and engineers.

Author: Ariescar | Alsomindtech

👹 gobkit.com · 📖 Devlog

anyCreature (Ariescar/anyCreature)

Searching Database…

467 ·GitHub
AnyCreature
Что это такое?anyCreature превращает описание обычным языком вроде 'a menacing mountain giant' в готового для игры 3D-персонажа — файл GLB со скелетом, анимацией и вершинными цветами плюс офлайн-просмотрщик — и всё это создаётся за одну сессию ИИ-агента.
Это отдельное приложение или то, что мой кодинг-агент запускает для меня?Это CLI-конвейер (движок плюс набор пошаговых «карт» и харнесс), рассчитанный на управление ИИ-кодинг-агентом вроде Claude Code или Cursor — GUI нет, только `node engine/cli.js spec.json out.glb`.
Как начать генерировать существо?Выполняйте `bash setup.sh` (или `setup.ps1` на Windows), пока он не выведет 'calibrate OK', затем укажите своему агенту на MANUAL.md и поручите ему следовать конвейеру карт для описанного вами существа.
Что нужно установить перед запуском?Node 18+ и Python 3.9+. setup.sh дополнительно устанавливает инструменты three.js, playwright, numpy, pillow и scipy для рендеринга и обмеров — самому движку нужен только Node.
Есть ли известные режимы сбоев, за которыми стоит следить?Слепое чтение отдельных частей может неверно распознать некоторые головы, показанные отдельно (слоны/птицы), спецификации, написанные до версии движка 1.2.0, теперь могут не пройти новые проверки, а запуск отдельных короткоживущих субагентов на каждый этап конвейера медленнее и дороже, чем один агент, ведущий работу от начала до конца.
Это работает на Windows или только на Mac/Linux?На всех трёх — Windows поддерживается через setup.ps1 в PowerShell (или setup.sh под Git Bash/WSL) наравне с нативной поддержкой macOS и Linux.
Обращается ли что-то из этого к удалённому серверу?Инструменты рендеринга и обмеров поднимают только короткоживущие локальные серверы, привязанные к 127.0.0.1; единственное внешнее действие — опциональный явный шаг публикации готового существа на стену сообщества Gobkit.
Что такое Gobkit?Gobkit — AI-нативная инфраструктура/API 3D-ассетов автора для потоковой доставки game-ready моделей агентам и «вайб-кодерам». anyCreature — открытый движок за ним, а готовые существа при желании можно публиковать на его стену сообщества.
Что фактически даёт опция embedspec?Она заставляет экспортируемый GLB нести внутри файла собственную авторскую JSON-спецификацию и манифест частей, так что любой агент впоследствии может извлечь, отредактировать, перекомпилировать или пересадить части между существами.
Почему два отдельных шлюза качества вместо одного?Сессия, спроектировавшая существо, хуже всех судит о его собственном силуэте. Шлюз 1 (RECOGNISED) проверяет, сможет ли читающий агент без контекста опознать существо по четырём видам; шлюз 2 (PUNCHIER) блокирует любую правку, делающую силуэт менее выразительным, чем в предыдущем раунде, даже если она более «правильная».
Что именно показывает входящий в комплект пример волка?example/wolf.json — четвероногое с 2 211 вершинами и 31 суставом, используемое чисто как справочник по синтаксису — оно содержит только анимации idle и move, без attack, а движок активно блокирует сборки, которые являются просто этим волком с едва изменёнными числами.
What are similar projects?img2threejs, procedural-film, genex-desktop, Procedura, mcp-for-blender, flutter_scene, blender-production-skills, image-to-3dlab
Which topics is it in?gltf, 3d-modeling, 3d-generation, procedural-generation, computer-graphics, game-development, 3d, cursor, animation, generative-ai, agent, claude-code
Creator
Ariescar
Size
1.1 MB
Stars
467
Updated
CommitSep 21Releasev1.3.2Sep 21
Age
2mo
Commits · 90 Days