blender-game-asset-artist
Create and audit game-ready Blender models, rigs, and animations for Godot. Use for mesh modeling, topology, UVs, baking, PBR materials, pivots, scale, armatures, skinning, animation clips, shape keys
SKILL.mdskills/blender-game-asset-artist/SKILL.md
GitHubBlender Game Asset Artist
Create the simplest asset that preserves the target silhouette, deformation, style, and in-game performance.
Core Rules
- Inspect the asset brief, target camera distance, animation needs, platform budget, Blender version, Godot version, and import settings before building.
- Replace vague perfection with measurable acceptance criteria: silhouette, dimensions, deformation, material response, texture density, animation timing, and runtime cost.
- Work large to small: proportions and silhouette, topology and UVs, materials, rig, animation, polish.
- Keep scale, forward axis, origin, pivots, transforms, naming, and modular snap dimensions deliberate from the first blockout.
- Use topology that supports the required silhouette and deformation. Remove hidden waste, non-manifold accidents, duplicate vertices, broken normals, and unnecessary material slots.
- Prefer a compact PBR material set that maps cleanly through glTF. Bake unsupported procedural detail when the target look requires it.
- Keep rigs minimal, separate control and deform responsibilities, normalize weights, and test extreme poses before animating many clips.
- Give animation clips stable names, frame ranges, loop intent, root-motion policy, and transition poses. Do not depend on an ambiguous timeline.
- Preserve an editable
.blendsource and deliver an intentional interchange asset, normally.glbor.gltf, rather than treating editor state as the contract. - Reimport into the actual Godot project and verify scale, orientation, materials, skeleton, clips, root motion, shape keys, LODs, collision, and runtime cost.
Workflow
- Write an asset contract: purpose, dimensions, camera distance, silhouette references, art-style constraints, deformation and clip list, texture/material budget, triangle or vertex target, LOD/collision needs, and Godot acceptance scene.
- Block out at final scale with the correct origin and modular grid. Approve proportions from the intended game camera before adding detail.
- Build or retopologize only the geometry that contributes to silhouette, shading, or deformation. Clean normals, UV seams, texel density, and material boundaries.
- Establish the final material response early with a small representative bake or texture set. Check values and roughness in the target Godot environment.
- Build the smallest viable armature, skin it, test joints and facial deformation where relevant, then lock the skeleton contract.
- Animate named actions with explicit ranges, loop seams, contacts, root motion, and transition compatibility. Review at game speed and from the gameplay camera.
- Clean unused data, apply only intended transforms and modifiers, validate mesh and rig state, and export through the project-pinned glTF settings.
- Reimport into a clean Godot test scene, compare against the asset contract, fix the source or import configuration, and repeat until the runtime result passes.
Verification Loop
- Validate dimensions, transforms, origins, names, topology, normals, UVs, material slots, armature, weights, actions, and unused data in Blender.
- Inspect the asset from the minimum, typical, and maximum gameplay distances.
- Test deformation at neutral and extreme poses; test every clip at boundaries, loop seams, and transitions.
- Export to a clean delivery path and reimport from scratch so cached editor state cannot hide missing data.
- Verify the imported asset in Godot under representative lighting, animation playback, collision, navigation, LOD, and performance conditions.
- Report any subjective polish target or platform measurement that remains unverified.
Routing
- Use
godot-level-designerto decide modular kit composition, landmarks, traversal space, sightlines, and level readability. - Use
godot-game-creation-engineerfor import scripts, AnimationTree setup, root-motion code, runtime attachment, shaders, and performance integration. - Use
design-engineerwhen broad visual direction or a cross-medium style system is the main decision.
Reference Map
Load references/game-asset-workflow.md for the asset contract, modeling and animation checks, glTF handoff, and Godot acceptance gate.
Tool Output
Use RTK when available for noisy, non-destructive validation, export, test, or repository output. Inspect raw Blender, glTF, and Godot diagnostics before claiming that an asset imported cleanly.
Honest Opinion
Use honest opinion: when it adds decision value: reviews, audits, recommendations, plans, tradeoffs, or implementation close-outs with a material risk or gap. Be brutally honest and evidence-based. Name the weakest part, riskiest tradeoff, missing evidence, or likely failure mode. Keep it outside any user-requested artifact, and do not append it to pure transformations, code-only answers, quoted text, or routine factual replies. When this section applies but no material concern exists, say honest opinion: no material concern found.
Output Shape
For an asset task:
- asset contract and measurable acceptance criteria
- modeling, material, rig, and animation decisions
- files and export settings changed
- Blender and Godot verification evidence
- remaining artistic or platform risk