
Physics 3d Collision
by unity-technologiescb1dccb8f5adNo license1K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
Diagnoses 3D PhysX collision and trigger problems. Use when OnCollisionEnter or OnTriggerEnter doesn't fire, objects pass through each other, raycasts miss, or a MeshCollider misbehaves. Also answers 2D and DOTS physics best-effort if no dedicated skill is available.
Add to a SourceWeft workspace
- Open the skill in your dashboard and add it to a workspace.
- Enable it for the chats that should use it.
This skill is instructions only: it ships no scripts to execute.
Add to SourceWeftYou will be asked to sign in first, then taken straight to this skill.
Ask your agent to install it
Paste this prompt into Claude Code, Codex, Cursor or another agent that can run commands — or into SourceWeft chat. The agent reads this skill's install guide, shows you its source, license and scripts, and installs it with the SourceWeft CLI once you agree.
Read https://sourceweft.com/skills/gh-unity-technologies-skills-physics-3d-collision/install.md and install the skill it describes. Before installing, show me its source, license and whether it ships scripts, and wait for my OK. Ask me before changing anything else on my machine.Install it yourself from a terminal
For Claude Code, Codex, Cursor and other local agents. The SourceWeft CLI fetches the skill from its source repository at the commit scanned here, and verifies every file against the hashes recorded when the skill was scanned. If anything differs, nothing is written.
npx @sourceweft/cli skills install gh-unity-technologies-skills-physics-3d-collisionAdd --agent claude-code, codex, cursor or universal to choose which agent gets it (Claude Code by default).
Upstream installer — not verified by SourceWeft
The open-source skills installer fetches the same pinned commit, but does not check the files against the hashes SourceWeft recorded.
npx skills add https://github.com/unity-technologies/skills/tree/cb1dccb8f5adffcca43a5a26993fdeb8eae59433/skills/physics-3d-collisionSource and attribution
Source:unity-technologies/skillsinskills/physics-3d-collisionat commitcb1dccb
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from unity-technologies/skills

Validate Urp Render Graph Renderer Feature
unity-technologies
Reviews Unity 6 URP Render Graph ScriptableRendererFeature code for wiring, binding and API issues.

Urp Postprocessing
unity-technologies
Sets up, configures, and debugs Unity URP post-processing effects through the Volume framework.

Ui Uitk
unity-technologies
Understands, edits and generates Unity UI Toolkit UXML and USS files with flex layouts.

Ui Ugui
unity-technologies
Guides understanding, editing, and generating Unity uGUI Canvas hierarchies, RectTransforms, Layout Groups, and prefab UI.

Ui Imgui
unity-technologies
Generates and modifies legacy Unity IMGUI editor code such as EditorWindows, custom Inspectors, PropertyDrawers and OnGUI scripts.

Ui
unity-technologies
Routes Unity UI requests to the right framework skill (UI Toolkit, uGUI, or IMGUI) and answers UI comparison questions.
More in Software Development

Playground
anthropics
Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.

M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.

Cardputer Buddy
anthropics
Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.

Web Design Guidelines
vercel-labs
Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.

Vercel React Native Skills
vercel-labs
React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.

Vercel React Best Practices
vercel-labs
Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.