Skip to content
SkillModel-led3,289 tokens in use

unity-physics

Unity 6.3 LTS physics for your coding agent: Rigidbody and Rigidbody2D movement, collision versus trigger callbacks, layer matrices, raycasts and joints.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/unity/unity-physics
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing unity-physics costs

95tokens idle
3,289tokens in use
5,430tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill teaches an agent how Unity 6.3 LTS physics works in both 3D (PhysX) and 2D. It covers moving bodies with forces and linearVelocity in FixedUpdate, choosing between collisions and triggers, pruning the layer collision matrix, and writing ground checks and line-of-sight rays.

It is written for the bugs that waste an afternoon: an object that falls through the floor, OnTriggerEnter that never fires, or a ground ray that hits the player itself. Each one is listed with its cause and the fix, and the skill ends with ways to verify the result.

What You Get

  • A step-by-step workflow from identifying 3D or 2D physics to verifying the result
  • C# patterns for force-based movement, ground checks and kinematic platforms
  • A table of 3D versus 2D differences, such as OnCollisionEnter2D, RaycastHit2D and angularVelocity units
  • A gotcha list covering silent callbacks, rays that stop on triggers, tunnelling and the Unity 6 renames
  • Two reference files on 2D movement with Slide and one-way platforms, and on cast variants, LayerMask bit math and joints

Common Use Cases

  • Fixing an object that falls through the floor or a trigger callback that never fires
  • Writing a Rigidbody2D platformer mover with a contact-filter ground check
  • Setting up layer collision pairs so bullets, enemies and pickups only touch what they should
  • Migrating code from velocity and drag to linearVelocity and linearDamping after the Unity 6 renames

What Makes It Unique

The skill is specific to Unity 6.3 LTS and keeps 3D and 2D physics apart, since they never interact and fail silently when mixed. It points out that a 3D-named callback on a 2D object never runs, and it carries the Unity 6 API renames. It defers engine-neutral feel tuning, tilemap colliders and NavMesh to sibling skills, so it stays on the Unity physics API.

Under The Hood

The agent reads the SKILL.md and loads the two reference files only when the task needs them. It is told to grep scene and prefab YAML and the ProjectSettings assets to find the physics settings, so it reads files in your project. To verify, it can run the Unity command line tool against an open Editor, evaluate scripts with it, start Play mode, or run PlayMode tests in batch mode and read the NUnit results. It does not fetch web pages or call outside services itself, and it asks you to change the layer matrix in Project Settings.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers