Route 3D production

Start with the intended deliverable: image reference, editable geometry, textured mesh, material maps, rigged character or engine-ready animation. Inspect the supplied assets and the target engine before selecting a route.

Need	Skill
Explore silhouettes or edit an accepted image	image-reference-workflow
Front sheet, parts and modeling references	character-sheet-pipeline
Generate images, meshes, material maps or video through fal.ai	fal-ai-generation
Work through an existing Higgsfield account	higgsfield-workflow
Editable procedural geometry in Three.js	img2threejs
Validate and deliver a PBR material	materials-to-game
Analyze motion timing	motion-reference-workflow or video-watch
Rig, skin, animate and export in Blender	blender-game-animation
Integrate clips and locomotion transitions in an engine	game-animation-integration
Plan and implement event-driven visual effects	game-vfx-workflow
Develop a HUD or menu from concept through live game state	game-ui-workflow
Design and validate a playable level	game-level-design
Select and integrate game sounds	game-audio-workflow
Verify the result in the actual game	gameplay-visual-review

Read the selected skill before execution. Its presence does not mean its MCP, CLI, account or editor is connected. Inspect live capabilities and exact model schemas; keep provider choices and accepted references from the current task.

For a game asset, separate concept acceptance from mesh acceptance. Verify topology, scale, materials, rig, root motion and engine import as applicable. A successful API request or attractive render is not an engine handoff. Record the chosen route and acceptance criteria in the current project card.