Trigger when the user wants to learn, implement, debug, or extend "使用空间划分的广义阶段碰撞检测" or a 物理引擎 build-your-own project using JavaScript. Use this skill for staged Claude Code guidance, milestone planning, minimal implementation, and troubleshooting.
Pro scans all 5 files and shows the line behind each finding
Scanned 9/7/2026
Skills Directorynpx -y skills add linkxzhou/build-your-own-x-skills --skill physics-engine-buildnewgames-broad-phase-collision --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Physics Engine Buildnewgames Broad Phase Collision?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/linkxzhou-physics-engine-buildnewgames-broad-phase-collision)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: physics-engine-buildnewgames-broad-phase-collision
description: |
Trigger when the user wants to learn, implement, debug, or extend "使用空间划分的广义阶段碰撞检测" or a 物理引擎 build-your-own project using JavaScript. Use this skill for staged Claude Code guidance, milestone planning, minimal implementation, and troubleshooting.
---
# 使用空间划分的广义阶段碰撞检测
Use this skill as a project coach for the original build-your-own tutorial.
## Source
- **Category**: 物理引擎
- **Language / stack**: JavaScript
- **Original resource**: http://buildnewgames.com/broad-phase-collision-detection/
## Workflow
1. Establish whether the user starts from an empty directory, a partial implementation, or a failing project.
2. Default to `JavaScript` unless the user chooses another stack.
3. Read `references/tutorial-map.md` and convert the source into 4-8 implementation milestones.
4. Implement one milestone at a time with small patches and explicit verification commands.
5. Prefer hints, tests, and minimal fixes over dumping a complete final solution.
6. Preserve the user's existing files and style.
## Milestone template
1. Project skeleton and first runnable command.
2. Core data model and invariants.
3. Input/parser/protocol/UI boundary.
4. Main algorithm or runtime engine.
5. Integration and end-to-end behavior.
6. Diagnostics, tests, and extensions.
## Expected outputs
- A staged implementation plan.
- A minimal project scaffold.
- A focused code patch for the current milestone.
- A debugging explanation and regression test.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
