[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73EPR4NK6F89693GZ1MAP6B":3,"skill-same:01M73EPR4NK6F89693GZ1MAP6B":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M73EPR4NK6F89693GZ1MAP6B","arcade-physics",null,"Minimal Arcade-class 2D physics over the zero-dependency ECS core: velocity integration, gravity, damping, and AABB collision detection plus response. Use when: implementing movement, gravity, or collision response on the ECS core; wiring the game loop system order; or fixing tunneling\u002Fclamping bugs.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-game\u002F.gemini\u002Fskills\u002Farcade-physics\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: arcade-physics\ndescription: >\n  Minimal Arcade-class 2D physics over the zero-dependency ECS core: velocity integration,\n  gravity, damping, and AABB collision detection plus response. Use when: implementing\n  movement, gravity, or collision response on the ECS core; wiring the game loop system\n  order; or fixing tunneling\u002Fclamping bugs.\nversion: 1.0.0\nscope: co-game\nstatus: active\nowner: pm\nlast_reviewed: 2026-08-25\nprerequisites: none\nrelates_to:\n  - skill: research-analysis\n    type: composes_with\n  - skill: test-driven-development\n    type: composes_with\n  - skill: sound-synth\n    type: follows\n  - skill: documentation-writing\n    type: composes_with\n  - skill: code-review\n    type: composes_with\nmetadata:\n  type: implementation\n  triggers:\n    - arcade physics\n    - movement system\n    - gravity\n    - velocity integration\n    - collision response\n    - AABB resolution\n    - game loop order\n---\n\n# Skill: arcade-physics\n\n## Context\n\nPhaser ships two physics engines: Arcade and Matter. This skill provides the Arcade-class subset at the variant's 2D-casual scope: velocity integration, gravity, damping, AABB overlap detection, and collision response. Matter.js-class rigid-body dynamics (rotational dynamics, joints, stacking, continuous physics) are explicitly out of scope; the scope boundary in `docs\u002Fscene-management.md` already records that 3D or physics-heavy titles need a real engine.\n\nThe ECS template already provides the data model and the detection half:\n\n| Provided by `src\u002Fecs\u002Farcade-puzzle-template.ts` | What it does |\n|---|---|\n| `Transform` (x, y, rotation, scale), `Velocity` (vx, vy), `BoundingBox` (width, height) | Components |\n| `CollisionSystem` | O(n^2) AABB overlap detection; emits `CollisionEvent { entityA, entityB }` pairs into `activeCollisions`. Detection only; no resolution |\n| `GridSystem` | Grid-to-world position sync for `GridPosition` entities |\n\nThis skill adds the two missing pieces: a `MovementSystem` that integrates `Velocity` into `Transform`, and collision response patterns that consume `CollisionSystem.activeCollisions`.\n\n## When to Use\n\n- Implementing entity movement, gravity, or jumping on the ECS core.\n- Wiring system registration order in the fixed-timestep game loop.\n- Resolving AABB overlaps: solid-wall separation, one-way platforms, tile leading-edge blocking.\n- Debugging tunneling (entities passing through walls) or velocity clamping bugs.\n- Writing deterministic unit tests for movement and collision code.\n\nDo not use for rigid-body dynamics (rotation, joints, stacking). That is outside the 2D-casual scope recorded in `docs\u002Fscene-management.md`.\n\n## Execution Steps\n\n### Step 1: Add the MovementSystem\n\nCopy this reference implementation into the game's systems directory (for example `src\u002Fsystems\u002FMovementSystem.ts`) and adjust import paths. All quantities are pixels and seconds: velocities in px\u002Fs, gravity in px\u002Fs^2, `dt` in seconds.\n\n```typescript\nimport { World, type System } from \".\u002Fecs-core\";\nimport { Transform, Velocity } from \".\u002Farcade-puzzle-template\";\n\nexport interface MovementConfig {\n  gravity: number;   \u002F\u002F px\u002Fs^2 added to vy each step; 0 disables\n  damping: number;   \u002F\u002F per-second linear drag applied to both axes; 0 disables\n  maxSpeed: number;  \u002F\u002F px\u002Fs cap on velocity magnitude; Infinity disables\n  maxDt: number;     \u002F\u002F seconds; never integrate a dt larger than this\n}\n\nexport const DEFAULT_MOVEMENT_CONFIG: MovementConfig = {\n  gravity: 0,\n  damping: 0,\n  maxSpeed: Infinity,\n  maxDt: 1 \u002F 60,\n};\n\nexport class MovementSystem implements System {\n  public name = \"MovementSystem\";\n\n  constructor(private config: MovementConfig = DEFAULT_MOVEMENT_CONFIG) {}\n\n  public update(world: World, deltaTime: number): void {\n    \u002F\u002F Clamp dt: never integrate more than one fixed step's worth of time.\n    const dt = Math.min(deltaTime, this.config.maxDt);\n\n    for (const entity of world.query(Transform, Velocity)) {\n      const transform = world.getComponent(entity, Transform)!;\n      const velocity = world.getComponent(entity, Velocity)!;\n\n      \u002F\u002F Semi-implicit Euler: update velocity BEFORE position.\n      \u002F\u002F This keeps a gravity-accelerated entity resting on a resolved\n      \u002F\u002F surface stable instead of sinking one gravity step per frame.\n      velocity.vy += this.config.gravity * dt;\n\n      if (this.config.damping > 0) {\n        const drag = Math.max(0, 1 - this.config.damping * dt);\n        velocity.vx *= drag;\n        velocity.vy *= drag;\n      }\n\n      this.clampSpeed(velocity);\n\n      transform.x += velocity.vx * dt;\n      transform.y += velocity.vy * dt;\n    }\n  }\n\n  private clampSpeed(velocity: Velocity): void {\n    const speed = Math.hypot(velocity.vx, velocity.vy);\n    if (speed > this.config.maxSpeed && speed > 0) {\n      const scale = this.config.maxSpeed \u002F speed;\n      velocity.vx *= scale;\n      velocity.vy *= scale;\n    }\n  }\n}\n```\n\nThree rules from the implementation, restated because they are the common bug sources:\n\n1. **Semi-implicit Euler order**: `vy += gravity * dt` comes BEFORE `y += vy * dt`. Explicit Euler (position first) accumulates energy and makes grounded entities jitter.\n2. **dt clamp**: never integrate a `dt` larger than the fixed-timestep remainder. A single long frame after a tab stall must not teleport entities through walls (tunneling).\n3. **Max-speed clamp** normalizes the velocity vector, not a single axis, so diagonal movement is not faster than axial movement.\n\n### Step 2: Register systems in the fixed-timestep loop in this order\n\n```text\ninput -> MovementSystem -> CollisionSystem -> response consumers -> render\n```\n\n- `MovementSystem` runs BEFORE `CollisionSystem` so detection sees post-integration positions; response consumers run AFTER `CollisionSystem` so they read a fresh `activeCollisions` array.\n- Pass `dt` in SECONDS, not milliseconds. The house convention in `docs\u002Fco-game.context.md` (Game Development Specific Rules) uses `FIXED_DT = 1000\u002F60 ms` with an accumulator; convert once at the call site: `world.update(FIXED_DT \u002F 1000)`.\n- `world.update()` executes systems in registration order. Deterministic ordering is what makes fixed-dt unit tests reproducible; register systems in the same order in every scene (see `docs\u002Fscene-management.md`).\n\n### Step 3: Consume activeCollisions with the right response pattern\n\nAll four patterns read `CollisionSystem.activeCollisions` after the collision step.\n\n**(a) Separation resolution (solid walls).** Push entity A out of entity B along the smaller overlap axis:\n\n```typescript\nimport { World, type Entity } from \".\u002Fecs-core\";\nimport { Transform, BoundingBox } from \".\u002Farcade-puzzle-template\";\n\n\u002F** Push entityA out of entityB along the smaller overlap axis. *\u002F\nfunction resolveSeparation(world: World, entityA: Entity, entityB: Entity): void {\n  const tA = world.getComponent(entityA, Transform)!;\n  const bA = world.getComponent(entityA, BoundingBox)!;\n  const tB = world.getComponent(entityB, Transform)!;\n  const bB = world.getComponent(entityB, BoundingBox)!;\n\n  \u002F\u002F Penetration depth per axis (positive while intersecting).\n  const overlapX = Math.min(tA.x + bA.width - tB.x, tB.x + bB.width - tA.x);\n  const overlapY = Math.min(tA.y + bA.height - tB.y, tB.y + bB.height - tA.y);\n\n  if (overlapX \u003C overlapY) {\n    \u002F\u002F Shallower penetration on X: push A toward the side its center is on.\n    const aCenterX = tA.x + bA.width \u002F 2;\n    const bCenterX = tB.x + bB.width \u002F 2;\n    tA.x += aCenterX \u003C bCenterX ? -overlapX : overlapX;\n  } else {\n    const aCenterY = tA.y + bA.height \u002F 2;\n    const bCenterY = tB.y + bB.height \u002F 2;\n    tA.y += aCenterY \u003C bCenterY ? -overlapY : overlapY;\n  }\n}\n```\n\nAfter separating on an axis, zero the velocity component directed into the surface (for example `velocity.vx = 0` when A was pushed out horizontally while moving toward B).\n\nAxis-decision table:\n\n| Comparison | Resolution |\n|---|---|\n| `overlapX \u003C overlapY` | Push A out horizontally; zero `vx` if directed into B |\n| `overlapY \u003C overlapX` | Push A out vertically; zero `vy` if directed into B |\n| `overlapX == overlapY` (corner) | Resolve the axis of larger incoming velocity component; tie breaks to X by convention |\n\n**(b) Tile-grid leading-edge checks.** For grid-locked games, prefer blocking entry over pushing out: before moving an entity, test the tile at its leading edge (position plus half-entity-size in the movement direction) and deny the movement when that tile is solid. The house example in `docs\u002Fco-game.context.md` (Game Development Specific Rules: 28x31 grid, 16px tiles, `HALF_ENTITY_SIZE = 7` leading-edge checks) shows the convention. Grid conventions are per-game: the grid dimensions, tile size, and any `HALF_ENTITY_SIZE`-style constant belong to the game's own constants file, not to this skill.\n\n**(c) One-way platforms.** Apply vertical resolution only when the entity approaches from above:\n\n```typescript\nif (prevBottom \u003C= platformTop + epsilon && velocity.vy >= 0) {\n  transform.y = platformTop - boundingBox.height;\n  velocity.vy = 0;\n}\n```\n\n`prevBottom` is A's bottom edge in the previous fixed step. An entity jumping up from below passes through; an entity falling from above lands.\n\n**(d) Event-only handling (pickups, triggers).** Consume the `CollisionEvent` without changing position: flag or destroy entityB (for example set `ScoreValue.collected`), add score, and trigger a sound via the `sound-synth` patterns. No separation.\n\n### Step 4: Test with deterministic fixed-dt steps\n\n- Advance the world N fixed steps in a loop (`for (let i = 0; i \u003C N; i++) world.update(1 \u002F 60)`) and assert exact positions computed from the config, not approximate ranges. With gravity `g` and step `dt`, velocity gains exactly `g * dt` per step; cumulative position offsets follow closed-form values the test can state precisely.\n- Write pairwise resolution tests: two entities overlapping by a known offset, one fixed step, then assert the exact separated position and the zeroed velocity component.\n- Keep systems under test free of `Math.random()` and `Date.now()` so runs are reproducible.\n- Author these tests following the `test-driven-development` skill (red-green cycle, movement test written first).\n\n## Output Format\n\nEvery implementation using this skill reports two artifacts:\n\n1. The system registration order as a numbered list mirroring the loop order:\n\n```text\n1. InputSystem\n2. MovementSystem\n3. CollisionSystem\n4. \u003CResponse consumers by name>\n5. RenderSystem\n```\n\n2. The collision-response decision table filled in for the game's entity pairs:\n\n| Situation | Decision rule | Resolution action |\n|---|---|---|\n| Solid wall | `overlapX \u003C overlapY` | Push A out on X; zero `vx` directed into B |\n| Solid wall | `overlapY \u003C overlapX` | Push A out on Y; zero `vy` directed into B |\n| One-way platform | `prevBottom \u003C= platform top` and `vy >= 0` | Snap A on top, zero `vy`; otherwise pass through |\n| Pickup \u002F trigger | any overlap | No position change: flag or destroy B, add score, play SFX |\n| Tile boundary (grid games) | leading-edge tile is solid | Block entry before integration |\n\n## Related Skills\n\n- `test-driven-development`: red-green discipline for the deterministic fixed-dt tests in Step 4.\n- `code-review`: review checklist for system order and integration correctness.\n- Scene-level structure (one `World` per scene, system registration on enter): see `docs\u002Fscene-management.md`.\n","# Skill: arcade-physics\n\n## Context\n\nPhaser ships two physics engines: Arcade and Matter. This skill provides the Arcade-class subset at the variant's 2D-casual scope: velocity integration, gravity, damping, AABB overlap detection, and collision response. Matter.js-class rigid-body dynamics (rotational dynamics, joints, stacking, continuous physics) are explicitly out of scope; the scope boundary in `docs\u002Fscene-management.md` already records that 3D or physics-heavy titles need a real engine.\n\nThe ECS template already provides the data model and the detection half:\n\n| Provided by `src\u002Fecs\u002Farcade-puzzle-template.ts` | What it does |\n|---|---|\n| `Transform` (x, y, rotation, scale), `Velocity` (vx, vy), `BoundingBox` (width, height) | Components |\n| `CollisionSystem` | O(n^2) AABB overlap detection; emits `CollisionEvent { entityA, entityB }` pairs into `activeCollisions`. Detection only; no resolution |\n| `GridSystem` | Grid-to-world position sync for `GridPosition` entities |\n\nThis skill adds the two missing pieces: a `MovementSystem` that integrates `Velocity` into `Transform`, and collision response patterns that consume `CollisionSystem.activeCollisions`.\n\n## When to Use\n\n- Implementing entity movement, gravity, or jumping on the ECS core.\n- Wiring system registration order in the fixed-timestep game loop.\n- Resolving AABB overlaps: solid-wall separation, one-way platforms, tile leading-edge blocking.\n- Debugging tunneling (entities passing through walls) or velocity clamping bugs.\n- Writing deterministic unit tests for movement and collision code.\n\nDo not use for rigid-body dynamics (rotation, joints, stacking). That is outside the 2D-casual scope recorded in `docs\u002Fscene-management.md`.\n\n## Execution Steps\n\n### Step 1: Add the MovementSystem\n\nCopy this reference implementation into the game's systems directory (for example `src\u002Fsystems\u002FMovementSystem.ts`) and adjust import paths. All quantities are pixels and seconds: velocities in px\u002Fs, gravity in px\u002Fs^2, `dt` in seconds.\n\n```typescript\nimport { World, type System } from \".\u002Fecs-core\";\nimport { Transform, Velocity } from \".\u002Farcade-puzzle-template\";\n\nexport interface MovementConfig {\n  gravity: number;   \u002F\u002F px\u002Fs^2 added to vy each step; 0 disables\n  damping: number;   \u002F\u002F per-second linear drag applied to both axes; 0 disables\n  maxSpeed: number;  \u002F\u002F px\u002Fs cap on velocity magnitude; Infinity disables\n  maxDt: number;     \u002F\u002F seconds; never integrate a dt larger than this\n}\n\nexport const DEFAULT_MOVEMENT_CONFIG: MovementConfig = {\n  gravity: 0,\n  damping: 0,\n  maxSpeed: Infinity,\n  maxDt: 1 \u002F 60,\n};\n\nexport class MovementSystem implements System {\n  public name = \"MovementSystem\";\n\n  constructor(private config: MovementConfig = DEFAULT_MOVEMENT_CONFIG) {}\n\n  public update(world: World, deltaTime: number): void {\n    \u002F\u002F Clamp dt: never integrate more than one fixed step's worth of time.\n    const dt = Math.min(deltaTime, this.config.maxDt);\n\n    for (const entity of world.query(Transform, Velocity)) {\n      const transform = world.getComponent(entity, Transform)!;\n      const velocity = world.getComponent(entity, Velocity)!;\n\n      \u002F\u002F Semi-implicit Euler: update velocity BEFORE position.\n      \u002F\u002F This keeps a gravity-accelerated entity resting on a resolved\n      \u002F\u002F surface stable instead of sinking one gravity step per frame.\n      velocity.vy += this.config.gravity * dt;\n\n      if (this.config.damping > 0) {\n        const drag = Math.max(0, 1 - this.config.damping * dt);\n        velocity.vx *= drag;\n        velocity.vy *= drag;\n      }\n\n      this.clampSpeed(velocity);\n\n      transform.x += velocity.vx * dt;\n      transform.y += velocity.vy * dt;\n    }\n  }\n\n  private clampSpeed(velocity: Velocity): void {\n    const speed = Math.hypot(velocity.vx, velocity.vy);\n    if (speed > this.config.maxSpeed && speed > 0) {\n      const scale = this.config.maxSpeed \u002F speed;\n      velocity.vx *= scale;\n      velocity.vy *= scale;\n    }\n  }\n}\n```\n\nThree rules from the implementation, restated because they are the common bug sources:\n\n1. **Semi-implicit Euler order**: `vy += gravity * dt` comes BEFORE `y += vy * dt`. Explicit Euler (position first) accumulates energy and makes grounded entities jitter.\n2. **dt clamp**: never integrate a `dt` larger than the fixed-timestep remainder. A single long frame after a tab stall must not teleport entities through walls (tunneling).\n3. **Max-speed clamp** normalizes the velocity vector, not a single axis, so diagonal movement is not faster than axial movement.\n\n### Step 2: Register systems in the fixed-timestep loop in this order\n\n```text\ninput -> MovementSystem -> CollisionSystem -> response consumers -> render\n```\n\n- `MovementSystem` runs BEFORE `CollisionSystem` so detection sees post-integration positions; response consumers run AFTER `CollisionSystem` so they read a fresh `activeCollisions` array.\n- Pass `dt` in SECONDS, not milliseconds. The house convention in `docs\u002Fco-game.context.md` (Game Development Specific Rules) uses `FIXED_DT = 1000\u002F60 ms` with an accumulator; convert once at the call site: `world.update(FIXED_DT \u002F 1000)`.\n- `world.update()` executes systems in registration order. Deterministic ordering is what makes fixed-dt unit tests reproducible; register systems in the same order in every scene (see `docs\u002Fscene-management.md`).\n\n### Step 3: Consume activeCollisions with the right response pattern\n\nAll four patterns read `CollisionSystem.activeCollisions` after the collision step.\n\n**(a) Separation resolution (solid walls).** Push entity A out of entity B along the smaller overlap axis:\n\n```typescript\nimport { World, type Entity } from \".\u002Fecs-core\";\nimport { Transform, BoundingBox } from \".\u002Farcade-puzzle-template\";\n\n\u002F** Push entityA out of entityB along the smaller overlap axis. *\u002F\nfunction resolveSeparation(world: World, entityA: Entity, entityB: Entity): void {\n  const tA = world.getComponent(entityA, Transform)!;\n  const bA = world.getComponent(entityA, BoundingBox)!;\n  const tB = world.getComponent(entityB, Transform)!;\n  const bB = world.getComponent(entityB, BoundingBox)!;\n\n  \u002F\u002F Penetration depth per axis (positive while intersecting).\n  const overlapX = Math.min(tA.x + bA.width - tB.x, tB.x + bB.width - tA.x);\n  const overlapY = Math.min(tA.y + bA.height - tB.y, tB.y + bB.height - tA.y);\n\n  if (overlapX \u003C overlapY) {\n    \u002F\u002F Shallower penetration on X: push A toward the side its center is on.\n    const aCenterX = tA.x + bA.width \u002F 2;\n    const bCenterX = tB.x + bB.width \u002F 2;\n    tA.x += aCenterX \u003C bCenterX ? -overlapX : overlapX;\n  } else {\n    const aCenterY = tA.y + bA.height \u002F 2;\n    const bCenterY = tB.y + bB.height \u002F 2;\n    tA.y += aCenterY \u003C bCenterY ? -overlapY : overlapY;\n  }\n}\n```\n\nAfter separating on an axis, zero the velocity component directed into the surface (for example `velocity.vx = 0` when A was pushed out horizontally while moving toward B).\n\nAxis-decision table:\n\n| Comparison | Resolution |\n|---|---|\n| `overlapX \u003C overlapY` | Push A out horizontally; zero `vx` if directed into B |\n| `overlapY \u003C overlapX` | Push A out vertically; zero `vy` if directed into B |\n| `overlapX == overlapY` (corner) | Resolve the axis of larger incoming velocity component; tie breaks to X by convention |\n\n**(b) Tile-grid leading-edge checks.** For grid-locked games, prefer blocking entry over pushing out: before moving an entity, test the tile at its leading edge (position plus half-entity-size in the movement direction) and deny the movement when that tile is solid. The house example in `docs\u002Fco-game.context.md` (Game Development Specific Rules: 28x31 grid, 16px tiles, `HALF_ENTITY_SIZE = 7` leading-edge checks) shows the convention. Grid conventions are per-game: the grid dimensions, tile size, and any `HALF_ENTITY_SIZE`-style constant belong to the game's own constants file, not to this skill.\n\n**(c) One-way platforms.** Apply vertical resolution only when the entity approaches from above:\n\n```typescript\nif (prevBottom \u003C= platformTop + epsilon && velocity.vy >= 0) {\n  transform.y = platformTop - boundingBox.height;\n  velocity.vy = 0;\n}\n```\n\n`prevBottom` is A's bottom edge in the previous fixed step. An entity jumping up from below passes through; an entity falling from above lands.\n\n**(d) Event-only handling (pickups, triggers).** Consume the `CollisionEvent` without changing position: flag or destroy entityB (for example set `ScoreValue.collected`), add score, and trigger a sound via the `sound-synth` patterns. No separation.\n\n### Step 4: Test with deterministic fixed-dt steps\n\n- Advance the world N fixed steps in a loop (`for (let i = 0; i \u003C N; i++) world.update(1 \u002F 60)`) and assert exact positions computed from the config, not approximate ranges. With gravity `g` and step `dt`, velocity gains exactly `g * dt` per step; cumulative position offsets follow closed-form values the test can state precisely.\n- Write pairwise resolution tests: two entities overlapping by a known offset, one fixed step, then assert the exact separated position and the zeroed velocity component.\n- Keep systems under test free of `Math.random()` and `Date.now()` so runs are reproducible.\n- Author these tests following the `test-driven-development` skill (red-green cycle, movement test written first).\n\n## Output Format\n\nEvery implementation using this skill reports two artifacts:\n\n1. The system registration order as a numbered list mirroring the loop order:\n\n```text\n1. InputSystem\n2. MovementSystem\n3. CollisionSystem\n4. \u003CResponse consumers by name>\n5. RenderSystem\n```\n\n2. The collision-response decision table filled in for the game's entity pairs:\n\n| Situation | Decision rule | Resolution action |\n|---|---|---|\n| Solid wall | `overlapX \u003C overlapY` | Push A out on X; zero `vx` directed into B |\n| Solid wall | `overlapY \u003C overlapX` | Push A out on Y; zero `vy` directed into B |\n| One-way platform | `prevBottom \u003C= platform top` and `vy >= 0` | Snap A on top, zero `vy`; otherwise pass through |\n| Pickup \u002F trigger | any overlap | No position change: flag or destroy B, add score, play SFX |\n| Tile boundary (grid games) | leading-edge tile is solid | Block entry before integration |\n\n## Related Skills\n\n- `test-driven-development`: red-green discipline for the deterministic fixed-dt tests in Step 4.\n- `code-review`: review checklist for system order and integration correctness.\n- Scene-level structure (one `World` per scene, system registration on enter): see `docs\u002Fscene-management.md`.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":37,"description":50,"last_reviewed":51,"prerequisites":52},"pm","co-game","active","1.0.0",{"type":28,"triggers":29},"implementation",[30,31,32,33,34,35,36],"arcade physics","movement system","gravity","velocity integration","collision response","AABB resolution","game loop order",[38,41,43,46,48],{"type":39,"skill":40},"composes_with","research-analysis",{"type":39,"skill":42},"test-driven-development",{"type":44,"skill":45},"follows","sound-synth",{"type":39,"skill":47},"documentation-writing",{"type":39,"skill":49},"code-review","Minimal Arcade-class 2D physics over the zero-dependency ECS core: velocity integration, gravity, damping, and AABB collision detection plus response. Use when: implementing movement, gravity, or collision response on the ECS core; wiring the game loop system order; or fixing tunneling\u002Fclamping bugs.\n",1787616000000,"none","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-game\u002F.gemini\u002Fskills\u002Farcade-physics",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill arcade-physics",{"tool":67,"command":68},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill arcade-physics",{"tool":70,"command":71},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill arcade-physics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-game\u002F.gemini\u002Fskills\u002Farcade-physics\u002FSKILL.md",true,[],[76,84,89,94,99,104],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":85,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":83},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":90,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":83},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":95,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":83},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":100,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":83},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":105,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":83},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]