arjun988/blender-skills / .claude/skills/collision-proxy
collision-proxy
VerifiedCollision proxy authoring for games including UCX/UHX naming, convex hulls, capsules, and simple collider meshes in Blender via MCP.
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 |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 468k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |