Collision proxy
Skill arjun988/blender-skills/.claude/skills/collision-proxy
94 specialist Blender skills for Cursor, Claude Code, Kiro & Codex -> MCP-powered production pipeline from blockout to engine export.
npx -y skills add arjun988/blender-skills --skill collision-proxyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Collision proxy authoring for games including UCX/UHX naming, convex hulls, capsules, and simple collider meshes in Blender via MCP.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.2 KB, as published. Nobody here has run it
Collision Proxy
Simple, stable colliders. Prefer primitives and convex pieces over render mesh.
When to Use
- Game physics / blocking volumes
- Unreal UCX export
- Unity mesh or primitive colliders
- Hitboxes for interactables
Workflow
Identify collision needs → Build proxies → Name correctly
→ Test overlaps → Export with render mesh
Collider Types
| Type | Use |
|---|---|
| Box | Crates, walls, simple props |
| Capsule | Characters, poles |
| Sphere | Balls, soft approximates |
| Convex hull | Organic / irregular single body |
| Multiple convex (UCX) | Vehicles, complex props |
Unreal Naming
UCX_SM_Asset_01
UCX_SM_Asset_02
- Must match associated mesh naming rules for auto-association
- Convex only for UCX
Unity Notes
- Prefer engine primitives when possible
- Mesh colliders: convex toggle for dynamic rigidbodies
- Keep proxy collection exportable
Authoring Rules
- Slightly smaller than visual mesh to reduce snagging (project-dependent)
- No holes; watertight convex pieces
- Apply scale
- Origin aligned with render mesh
- Collection:
COL_Collision_[Asset]
Validation
- Player cannot fall through intended blockers
- No huge invisible walls beyond mesh
- Wheel/character capsules oriented correctly
- Named for target engine
Constraints
MUST DO
- Prefer few simple shapes over one complex mesh
- Match engine naming conventions
- Keep proxies in dedicated collection
MUST NOT DO
- Use render LOD0 as physics mesh by default
- Non-convex UCX for Unreal auto-convex workflows
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Collider Recipes | references/collider-recipes.md | When needed |
| Engine Naming | references/engine-naming.md | When needed |