ai3d-gen
Skill0 starsChanged 3 months agoMITView on GitHub
Use when the user asks for generative 3D assets (text-to-3D, image-to-3D, mesh synthesis) via self-hosted open models. Routes to extensions/comfyui-operator/wrapper.py against a local ComfyUI server, with direct-model fallbacks (TRELLIS, TripoSG, InstantMesh, Hunyuan3D). All free/open weights, no paid SaaS.
- Installs packages
In this repository110 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/project-bootstrap/templates/agents.mdAGENTS.md
- a11y-auditSkill
- agentic-ragSkill
- agent-reachSkill
- ai-coding-dictionarySkill
- ai-toolsSkill
- animation-directionSkill
- api-specSkill
- architecture-diagramsSkill
- architectureSkill
- ascii-artSkill
- ask-bundleSkill
- binary-triageSkill
- bragSkill
- brag-slimSkill
- career-opsSkill
- code-reviewSkill
- computer-useSkill
- context7Skill
- context-hygieneSkill
- creative-engineeringSkill
- cu-realtimeSkill
- data-analystSkill
- databaseSkill
- dead-wireSkill
- debuggingSkill
- deploySkill
- devin-configSkill
- dispatching-parallel-agentsSkill
- dmaSkill
- dockerSkill
- drift-reportSkill
- e2e-testingSkill
- edge-casesSkill
- executionSkill
- fact-checkSkill
- finishing-a-development-branchSkill
- firmware-probeSkill
- frontend-designSkill
- gatesSkill
- ghidraSkill
- ghSkill
- github-actionsSkill
- git-workflowsSkill
- grillingSkill
- handoffSkill
- humanizerSkill
- hyperframesSkill
- i18nSkill
- image-forensicsSkill
- impeccableSkill
- implement-layaSkill
- intakeSkill
- jiraSkill
- knowledge-modelingSkill
- laya-orchestratorSkill
- learn-modeSkill
- mcp-governanceSkill
- media-toolsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 62
Prefer TRELLIS/TripoSG for permissive licensing.
- Distinctive: line 67
Before spending a reconstruction/splat run on user photos:
- Very specific: line 73
Photometric QC: run extensions/ppisp-prep/photo_qc.py on the set.
- Very specific: line 86
Import into Blender via operate-blender for retopo/material work.
- Distinctive: line 95
Never send user assets to hosted APIs (Meshy, Tripo cloud, etc.) unless explicitly asked.
- Very specific: line 99
Check VRAM in status before queueing large models (>=8GB typical).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI 3D Generation (self-hosted)
Generate 3D assets locally via open-weight models. Two paths:
- ComfyUI-3D-Pack (primary): visual workflow server.
Wrapper:
extensions/comfyui-operator/wrapper.py(stdlib HTTP, no deps). - Direct model CLIs (fallback / batch): run the model repos' own Python entrypoints, no ComfyUI needed.
Output of both paths: meshes (GLB/OBJ/PLY) that feed operate-blender
for cleanup, retopo, texturing, render, or mesh-utils for inspection.
Prerequisites
- ComfyUI installed locally (user step):
git clone https://github.com/comfyanonymous/ComfyUI && pip install -r requirements.txt, thenpython main.py --port 8188. ComfyUI-3D-Packcustom node pack for full 3D graph coverage:git clone https://github.com/MrForExample/ComfyUI-3D-Pack ComfyUI/custom_nodes/ComfyUI-3D-Pack && pip install -r ComfyUI/custom_nodes/ComfyUI-3D-Pack/requirements.txt- 3D-Pack requires NVIDIA GPU + CUDA toolkit (nvcc). It eagerly
imports
nvdiffrast,spconv-cu126,nerfacc,slangtorch; no CPU wheels exist. On CPU-only machines the whole pack fails import (ComfyUI core still runs). Use the direct-model fallback path there. - GPU strongly recommended for generation speed regardless (models are diffusion transformers; CPU inference works but is very slow).
Wrapper commands
python extensions/comfyui-operator/wrapper.py status # health + VRAM
python extensions/comfyui-operator/wrapper.py submit wf.json # queue job
python extensions/comfyui-operator/wrapper.py history <pid> # poll status + outputs
python extensions/comfyui-operator/wrapper.py download <pid> --out dir/
python extensions/comfyui-operator/wrapper.py upload img.png # input assetsubmit requires API-format JSON (node-id -> {class_type, inputs}),
the shape produced by ComfyUI's "Save (API Format)". Build it
programmatically or export from the UI once.
history returns files: flattened output descriptors (filename,
subfolder, type) regardless of which node emitted them. download
fetches each via /view.
Model choices (open weights, license-verified in research)
| Model | Input | Quality | License | Where |
| TRELLIS | text/img | high, GLB+texture | MIT | microsoft/TRELLIS |
| TripoSG | img | high mesh quality | MIT | VAST-AI/TripoSG |
| InstantMesh | img | fast | Apache-2.0 | TencentARC/InstantMesh |
| Hunyuan3D-2 | text/img | high + PBR | Tencent permissive | Tencent/Hunyuan3D-2 |
| Stable Fast 3D | img | fastest UV+mat | Stability Community | stabilityai/stable-fast-3d |
Prefer TRELLIS/TripoSG for permissive licensing; Hunyuan3D-2 when PBR texture quality matters; Stable Fast 3D for speed.
Intake preflight (photo-sourced pipelines)
Before spending a reconstruction/splat run on user photos:
- Provenance: source images should verify as real captures — run
extensions/image-forensics/verdict.pyper image when a camera reference exists; synthetic inputs break PRNU assumptions and usually produce bad splats. - Photometric QC: run
extensions/ppisp-prep/photo_qc.pyon the set;correct/recaptureverdicts route through the PPISP correction pass or a re-shoot before generation.
Recipes
image -> textured GLB (ComfyUI path)
wrapper.py upload photo.png- Build/submit a workflow JSON wiring
LoadImage-> model node ->SaveMesh/Preview3D(node names per ComfyUI-3D-Pack version; queryGET /object_infofor exact class_type names on the live server). wrapper.py submit wf.json, pollhistory,downloadoutputs.python extensions/mesh-utils/meshops.py info out.glbto verify.- Import into Blender via
operate-blenderfor retopo/material work.
text -> 3D without ComfyUI (direct)
- Clone the model repo,
pip install -r requirements.txt, run its inference script. E.g. TRELLIS example script produces GLB directly. Thenmesh-utils/operate-blenderdownstream.
Boundaries
- Never send user assets to hosted APIs (Meshy, Tripo cloud, etc.) unless explicitly asked. The point of this stack is self-hosted.
- ComfyUI not running -> wrapper exits 1 with a start hint. Don't spawn the server silently; tell the user.
- Check VRAM in
statusbefore queueing large models (>=8GB typical).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

