Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

7.1 KB
Raw Blame

third_party/

Complete third-party source trees, copied in byte-identical to their upstream repository and never edited in place.

We keep each tree in full rather than a curated excerpt, because the worked examples are the substance: a SKILL.md that points at a demo/ is worth nothing without the demo, and a component library without its assets cannot be run to see what it does.

This is not a bundle directory. public/vendor/ (and the vendor/ folders inside a surface, such as src/scene-studio/vendor/) hold third-party artifacts we actually ship. third_party/ holds whole repositories we read: source, assets, tests, licence and all, so a re-sync is a diff against upstream rather than a merge against our edits.

What is here

Directory Upstream Commit Licence Files
threeui/ MengTo/threeui 68802d5428071ada5c20db8094b1649e6bb770ed (2026-09-01) MIT, (c) 2026 Meng To 430
designcode-agent-skills/ MengTo/Skills 321c769739b823de5eb94eb3a52aa1974fe783a2 (2026-08-29) MIT, (c) 2026 Meng To 898
image-blaster/ neilsonnn/image-blaster 4acb43ba126a12358f71838d1b1a05e856b10eaf (2026-05-14) MIT, (c) 2026 Neilson Koerner-Safrata 140

All licences ship with their tree (threeui/LICENSE, designcode-agent-skills/LICENSE, image-blaster/LICENSE.md). MIT requires the copyright notice and permission notice to travel with the copy, so those files are load-bearing: never delete or rewrite them.

What each tree is for, with entry points and worked examples, is documented on our side in docs/vendored-design-libraries.md.

threeui

@designcodeio/threeui 1.2.0, the login-free Community edition of the ThreeUI catalog: 50 parent components across 111 routes, the React component library under threeui/src/, 48 shader and scene studies under threeui/src/shaders/, the publishable package under threeui/packages/, and the catalog application shell that renders each component with live controls, a variant picker and a source tab.

image-blaster

A Claude Code workspace that turns one image into a 3D environment: a Gaussian splat of the static scene (World Labs Marble), GLB/OBJ meshes of the dynamic objects (Hunyuan 3D via FAL) and ambient plus per-object SFX (ElevenLabs via FAL). The pipeline is eight skills under image-blaster/.claude/skills/, six stage subagents, Node scripts under image-blaster/.claude/scripts/ and a React viewer in image-blaster/app/. Needs WORLD_LABS_API_KEY and FAL_KEY; see its README to run it.

designcode-agent-skills

132 portable SKILL.md folders in five groups (web-design 88, game-development 20, codex 19, ui 3, media 2), each with its references, scripts and a runnable demo/. Same Agent Skills folder format as our own .agents/skills/.

Rules

  1. Never edit a file inside a vendored tree. A local fix becomes a permanent merge conflict on every future sync. Fix it upstream (issue or PR, per the open-source-first section of CLAUDE.md) and re-sync, or wrap it from our own code outside third_party/.
  2. Never import from third_party/ at runtime. Nothing in api/, src/, server/ or a worker resolves a path under third_party/, and nothing should: these trees are not in the Cloud Build upload (see below), so a runtime import would resolve locally and 500 with ERR_MODULE_NOT_FOUND in production, which is exactly how revision 00412 broke. Copy what you need into the surface that uses it, keeping the upstream attribution with it.
  3. A new tree lands with its licence and a row in the table above.

How it is wired into the repo

Deliberately inert. Vendoring a tree must not change what three.ws builds, tests, installs, or ships:

  • Not an npm workspace. workspaces in package.json is an explicit list, never a glob over this directory, so npm install never walks these trees or tries to resolve their dependencies. Run a vendored project's own npm install inside its directory when you want to boot it.
  • Not in the Cloud Build upload. .gcloudignore excludes the repository root (/*) and re-includes only what an image needs. third_party/ is never re-included, so these 189 MB never enter a build context. That is also why rule 2 above exists.
  • Not in the frontend build. Vite's Rollup input is an explicit map of pages/*.html, and third_party/ is outside both src/ and public/.
  • Not in the test run. vitest.config.js includes explicit path globs (tests/**, src/**, packages/*/tests/**), none of which reach here, so upstream's own test files never join our suite.
  • Skipped by the house guards, on purpose (all committed in cb1ec2680): scripts/check-rules.mjs skips it because the typography and comment rules apply to prose we write, not prose we transcribe (this drop carries 1625 em-dashes that are upstream's to fix); scripts/audit-docs.mjs skips it because upstream's relative links resolve against upstream's layout; eslint.config.js and .i18nrc.json skip it for the same reason.
  • Still scanned for credentials. scripts/check-secrets.mjs deliberately does NOT skip third_party/: a third party's leaked key is still a leaked key in our history. All trees pass clean.
  • demo/ needed an explicit re-include. .gitignore carries an unanchored demo/ rule for local NVIDIA TRELLIS output, which silently swallowed 578 demo files here. !third_party/**/demo/ re-includes them.

Re-syncing a tree

Upstream moves. A sync is a clean re-copy, not a merge:

git clone --depth 1 https://github.com/MengTo/threeui /tmp/threeui-sync
git -C /tmp/threeui-sync rev-parse HEAD          # record this in the table above
rm -rf third_party/threeui
rsync -a --exclude .git /tmp/threeui-sync/ third_party/threeui/
node scripts/check-secrets.mjs --paths third_party/threeui
git status --porcelain third_party/threeui       # review before staging

Then update the commit, date and file count in the table above in the same change, and add a data/changelog.json entry only if the sync changes something a three.ws user or developer would notice.

Verify a copy is complete by comparing against upstream's tracked file list rather than eyeballing it:

git -C /tmp/threeui-sync ls-files | wc -l        # must equal:
find third_party/threeui -type f | wc -l

Attribution

threeui and designcode-agent-skills are the work of Meng To and the Design+Code team; image-blaster is the work of Neilson Koerner-Safrata. All are used here under the MIT licence. Anything we ship that derives from them keeps that attribution with it.