Rust Bevy Collision Broadphase
Use this skill to make Bevy collision detection scale without mixing detection,
response, rendering, and gameplay rules into one system.
Core Workflow
- Identify the collision shapes, movement model, entity counts, and layers.
- Keep collider data small and independent from sprites, textures, and game
rules.
- Choose the cheapest broadphase that fits the scene: brute force for tiny
counts, spatial hash for uniform worlds, quad tree for clustered worlds.
- Emit candidate or collision events; let separate systems decide response.
- Test edge contacts, fast movement, layer filters, despawn cases, and
deterministic ordering.
- Benchmark before and after changing the broadphase.
Read Next
| Task |
Load |
| Pick or review a broadphase |
guidelines.md, references/broadphase-patterns.md |
| Optimize an existing collision system |
workflows/optimize-collision.md |
| Route a specific symptom |
guidelines.md |
Source Notes
Guidance is transformed and paraphrased from Herbert Wolverson,
Advanced Hands-On Rust, especially Chapter 8 on obstacles and collision
detection and Chapter 12 on optimization. The examples are original skeletons
intended to preserve the transferable technique, not the book's project code.
1---2name: rust-bevy-collision-broadphase3description: Design and review Bevy 2D collision broadphase systems with AABB bounds, spatial indexes, typed collision events, and benchmark-driven test beds. Use when replacing O(n^2) collision checks, adding spatial partitioning, diagnosing Bevy collision performance, or separating broadphase, narrowphase, and response systems in Rust games.4license: MIT5compatibility: Codex, Claude Code, and other Agent Skills-compatible clients.6metadata:7 version: "0.1.0"8 displayName: Rust Bevy Collision Broadphase9 category: Rust10 tags: rust,bevy,gamedev,collision,performance11---1213# Rust Bevy Collision Broadphase1415Use this skill to make Bevy collision detection scale without mixing detection,16response, rendering, and gameplay rules into one system.1718## Core Workflow19201. Identify the collision shapes, movement model, entity counts, and layers.212. Keep collider data small and independent from sprites, textures, and game22 rules.233. Choose the cheapest broadphase that fits the scene: brute force for tiny24 counts, spatial hash for uniform worlds, quad tree for clustered worlds.254. Emit candidate or collision events; let separate systems decide response.265. Test edge contacts, fast movement, layer filters, despawn cases, and27 deterministic ordering.286. Benchmark before and after changing the broadphase.2930## Read Next3132| Task | Load |33|------|------|34| Pick or review a broadphase | `guidelines.md`, `references/broadphase-patterns.md` |35| Optimize an existing collision system | `workflows/optimize-collision.md` |36| Route a specific symptom | `guidelines.md` |3738## Source Notes3940Guidance is transformed and paraphrased from Herbert Wolverson,41*Advanced Hands-On Rust*, especially Chapter 8 on obstacles and collision42detection and Chapter 12 on optimization. The examples are original skeletons43intended to preserve the transferable technique, not the book's project code.
ConcertoNotes