Phaser Arcade Physics

À propos de ce Skill

Add physics bodies, movement, gravity, world bounds, collisions, overlaps, and groups to browser games.

Pourquoi ce choix

Provides a focused workflow, implementation patterns, and common failure checks for phaser arcade physics. Pair it with the detected engine and any related systems required by the task.

À quoi il sert

• Use when your game task needs phaser arcade physics.

What this skill helps you build

Add physics bodies, movement, gravity, world bounds, collisions, overlaps, and groups to browser games.

Original phaser-arcade-physics instructions

Patterns in the upstream playbook

The entrypoint covers: Enable Arcade Physics (game config); Top-down movement (velocity from input); Platformer jump (gravity + ground check); Colliders vs overlaps (separate vs detect); A group of moving objects.

Original phaser-arcade-physics instructions

Use it in your project

1. Inspect the existing project

   Describe the desired behavior and share the relevant project files, engine version, and current failure or target result.

2. Apply the focused playbook

   Add physics bodies, movement, gravity, world bounds, collisions, overlaps, and groups to browser games.

3. Verify in the matching runtime

   Run the project or workflow with its actual dependencies and check the changed behavior before accepting the result.

Original phaser-arcade-physics instructionsEngine versions and upgrade policy

Shared collection installation

Install the complete upstream collection with its router and keep each skill’s bundled references, scripts, and assets. The dispatcher selects an engine and the smallest relevant task set; a member listing is a focused entry into that shared package.

Upstream installation guide

Avant de l’utiliser

• A browser project with the matching Phaser, PixiJS, or three.js dependency and a local HTTP server or existing build setup.

Agents compatibles