@codyswann/lisa 2.179.0 → 2.180.0

package/package.json

@@ -93,7 +93,7 @@
     "ws": ">=8.20.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

package/phaser/merge/.claude/settings.json

@@ -30,5 +30,6 @@
   "permissions": {
     "deny": ["Read(./.entire/metadata/**)"]
   },
+  "disabledMcpjsonServers": ["phaser-editor"],
   "plansDirectory": "./plans"
 }

package/phaser/merge/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "phaser-editor": {
+      "command": "npx",
+      "args": ["-y", "@phaserjs/editor-mcp-server"]
+    }
+  }
+}

package/plugins/lisa/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/rules/phaser.md

@@ -5,6 +5,29 @@ on the official `template-vite-ts` layout (Vite + TypeScript 6). Phaser 4 is the
 only supported target — never introduce Phaser 3 idioms. These decisions are
 **locked** and most are **lint-enforced**; do not disable a rule, fix the code.
 
+## Official Phaser skills — use these for API knowledge
+
+Phaser ships **28 official, authoritative agent skills** inside the installed
+package at **`node_modules/phaser/skills/<topic>/SKILL.md`** — e.g. `scenes`,
+`sprites-and-images`, `physics-arcade`, `physics-matter`, `tweens`, `particles`,
+`filters-and-postfx`, `loading-assets`, `animations`, `tilemaps`, `cameras`,
+`input-keyboard-mouse-touch`, `audio-and-sound`, `game-object-components`,
+`v3-to-v4-migration`, `v4-new-features`, and more. The Phaser team maintains them
+in lockstep with the engine, and they cite exact `src/...` source paths.
+
+**For any Phaser API or subsystem question, read the matching official skill
+first.** Do not rely on memory, and do not expect Lisa to duplicate that
+knowledge — the `lisa-phaser` skills intentionally cover only the opinionated,
+project-specific, and lint-enforced layer (project structure, services, asset
+pipeline, i18n, accessibility, build/deploy, testing gates) that the official
+skills do not. When this file points at a Phaser subsystem (physics, rendering,
+scenes, …) the authority is the official skill of that name.
+
+An optional **Phaser Editor MCP server** (`@phaserjs/editor-mcp-server`, 40+
+tools for scenes/assets/tilemaps) is defined for this project type but
+**disabled by default** — enable it only when working with Phaser Editor v5. See
+`.mcp.json` and `disabledMcpjsonServers` in `.claude/settings.json`.
+
 ## Locked architecture decisions
 
 1. **Thin scenes over a pure-logic core.** Scenes and GameObjects are thin
@@ -18,7 +41,7 @@ only supported target — never introduce Phaser 3 idioms. These decisions are
    as an upgrade path — it is not the default and is not added unless required.
 3. **Arcade physics by default; Matter is opt-in.** Matter is heavier and does
    not interop with Arcade. Switching is a one-line config swap. See
-   `phaser-physics`.
+   the official `physics-arcade` skill.
 4. **Determinism.** No `Math.random()`, `Date.now()`, or `performance.now()` in
    game code. Use the seeded `Phaser.Math.RandomDataGenerator` (`Phaser.Math.RND`
    or a local instance seeded from one place) so replays and tests reproduce.
@@ -31,7 +54,7 @@ only supported target — never introduce Phaser 3 idioms. These decisions are
 6. **Performance.** Pool transient objects via `Group`s; make **no allocations
    and create no objects/tweens/timers inside `update()`**; atlas everything; use
    `BitmapText` for high-churn text; use `SpriteGPULayer` / `TilemapGPULayer` for
-   mass rendering. See `phaser-gameobjects`.
+   mass rendering. See the official `game-object-components` skill.
 7. **Baked-in asset pipeline.** Raw art in `assets/src` is packed at build time
    (free-tex-packer-core atlases, audiosprite, BMFont) into `public/assets`, and
    a codegen step emits typed keys to `src/assets.ts` so a missing or renamed key

package/plugins/lisa-phaser/skills/phaser-accessibility/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: phaser-accessibility
-description: This skill should be used when making a Phaser 4 game accessible — honoring prefers-reduced-motion, pausing on window/tab blur, keyboard navigation and visible focus for menus, colorblind-safe palettes, and a screen-reader live region that announces game state through the DOM. Use it when building menus, settings, HUD, or any player-facing UI, or when an accessibility requirement comes up. Pairs with phaser-services, phaser-i18n, and phaser-scenes.
+description: This skill should be used when making a Phaser 4 game accessible — honoring prefers-reduced-motion, pausing on window/tab blur, keyboard navigation and visible focus for menus, colorblind-safe palettes, and a screen-reader live region that announces game state through the DOM. Use it when building menus, settings, HUD, or any player-facing UI, or when an accessibility requirement comes up. Pairs with phaser-services, phaser-i18n, and the official scenes skill.
 ---
 
 # Phaser 4 Accessibility

package/plugins/lisa-phaser/skills/phaser-asset-pipeline/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: phaser-asset-pipeline
-description: This skill should be used when setting up or changing the build-time asset pipeline of a Phaser 4 game — packing raw art in assets/src into public/assets (free-tex-packer-core texture atlases, audiosprite audio sprites, BMFont bitmap fonts) and the codegen step that emits typed keys to src/assets.ts so a missing or renamed key is a compile error. Use it when adding source art, wiring packing into the build, regenerating typed keys, or eliminating raw string asset keys. Pairs with phaser-assets, phaser-build-deploy, and phaser-services.
+description: This skill should be used when setting up or changing the build-time asset pipeline of a Phaser 4 game — packing raw art in assets/src into public/assets (free-tex-packer-core texture atlases, audiosprite audio sprites, BMFont bitmap fonts) and the codegen step that emits typed keys to src/assets.ts so a missing or renamed key is a compile error. Use it when adding source art, wiring packing into the build, regenerating typed keys, or eliminating raw string asset keys. Pairs with the official loading-assets skill, phaser-build-deploy, and phaser-services.
 ---
 
 # Phaser 4 Asset Pipeline
@@ -13,7 +13,7 @@ Runtime assets are **generated, not hand-placed**. Raw source art lives in
 key constants into `src/assets.ts`**. The payoff: a missing or renamed asset is a
 **compile error**, not a green square or silent-missing audio at runtime. No raw
 string asset / scene / event keys anywhere — they all come from the generated
-module ([[phaser-assets]] covers loading those keys at runtime).
+module (the official `loading-assets` skill covers loading those keys at runtime).
 
 ## Layout
 
@@ -52,7 +52,7 @@ for (const f of files) await writeFile(`public/assets/atlases/${f.name}`, f.buff
 
 The frame names in the manifest become the atlas frame keys you reference as
 generated constants. Atlas everything that renders together — loose images break
-sprite batching ([[phaser-assets]]).
+sprite batching (the official `loading-assets` skill).
 
 ## Step 2: audio sprites with audiosprite
 
@@ -70,7 +70,7 @@ with `this.load.audioSprite(Audio.Sfx, "audio/sfx.json")` and play by sprite key
 ## Step 3: bitmap fonts with BMFont
 
 `BitmapText` is the performant choice for high-churn text (scores, timers) —
-[[phaser-assets]] / [[phaser-i18n]]. Generate the `.fnt` (XML/JSON) + PNG page
+the official `loading-assets` skill / [[phaser-i18n]]. Generate the `.fnt` (XML/JSON) + PNG page
 from a font source with a BMFont tool (`msdf-bmfont-xml` or the `bmfont` CLI) in
 the same script:
 

package/plugins/lisa-phaser/skills/phaser-i18n/SKILL.md

@@ -86,7 +86,7 @@ Persist the chosen locale via SaveService and apply it on boot; default from
 
 ## BitmapText vs Text — the localization trade-off
 
-The performance advice "use BitmapText for hot text" ([[phaser-gameobjects]])
+The performance advice "use BitmapText for hot text" (the official `game-object-components` skill)
 collides with i18n: a bitmap font only contains the glyphs it was generated with.
 
 - **BitmapText** — fastest, but the BMFont must include every glyph the locale

package/plugins/lisa-phaser/skills/phaser-project-structure/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: phaser-project-structure
-description: This skill should be used when creating, restructuring, or reasoning about a Phaser 4 game project — the game config, the Vite + TypeScript layout, the Boot → Preloader → MainMenu → Game scene flow, scale/resolution setup for desktop and mobile, and where code and assets belong. Use it before scaffolding a project, adding a major subsystem, or deciding where a file should live. Pairs with phaser-scenes, phaser-assets, phaser-rendering, and phaser-testing.
+description: This skill should be used when creating, restructuring, or reasoning about a Phaser 4 game project — the game config, the Vite + TypeScript layout, the Boot → Preloader → MainMenu → Game scene flow, scale/resolution setup for desktop and mobile, and where code and assets belong. Use it before scaffolding a project, adding a major subsystem, or deciding where a file should live. Pairs with the official scenes skill, the official loading-assets skill, the official filters-and-postfx skill, and phaser-testing.
 ---
 
 # Phaser 4 Project Structure
 
 ## Overview
 
-This stack targets **Phaser 4** (v4.1+ "Salusa", npm package `phaser`), built
+This stack targets **Phaser 4** (v4.2+, npm package `phaser@^4.2.0`), built
 with **Vite + TypeScript** — the layout the official `phaserjs/template-vite-ts`
 template and `npm create @phaserjs/game@latest` scaffold. Phaser 4 ships its own
 type definitions (`types/phaser.d.ts`); do not add `@types/phaser`.
@@ -55,17 +55,17 @@ v4-specific config facts:
 - Pixel-art games: `pixelArt: true` (nearest-neighbor + roundPixels), or the new
   **`render.smoothPixelArt: true`** (WebGL-only) for pixel art that rotates or
   scales smoothly. Pick one per project and record the choice.
-- Custom render nodes register under `render.renderNodes` — see [[phaser-rendering]].
+- Custom render nodes register under `render.renderNodes` — see the official `filters-and-postfx` skill.
 - `Phaser.HEADLESS` exists for logic-only boots (tests) — see [[phaser-testing]].
 
 ## Scene flow
 
-Four-stage boot, in order (see [[phaser-scenes]] for lifecycle detail):
+Four-stage boot, in order (see the official `scenes` skill for lifecycle detail):
 
 1. **Boot** — loads only the handful of assets the Preloader's loading screen
    needs (logo, progress-bar art). No game assets here.
 2. **Preloader** — renders the loading UI and loads everything else, preferably
-   via a single asset-pack manifest (see [[phaser-assets]]), then starts MainMenu.
+   via a single asset-pack manifest (see the official `loading-assets` skill), then starts MainMenu.
 3. **MainMenu** — entry UI; starts Game.
 4. **Game** (+ overlay scenes like `HUD`, `Pause` run in parallel) — gameplay.
 

package/plugins/lisa-phaser/skills/phaser-services/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: phaser-services
-description: This skill should be used when wiring cross-cutting services and shared state in a Phaser 4 game — the typed registry wrapper for global state, a single dedicated EventsCenter bus (never game.events), the .on()/.off() listener discipline enforced in scene shutdown, SoundService (mobile audio unlock on first gesture), InputService (semantic actions instead of raw keys), and SaveService (versioned localStorage with a migration chain). Use it when adding global state, an event bus, audio/input/save plumbing, or fixing listener leaks and lost saves. Pairs with phaser-scenes, phaser-testing, and phaser-i18n.
+description: This skill should be used when wiring cross-cutting services and shared state in a Phaser 4 game — the typed registry wrapper for global state, a single dedicated EventsCenter bus (never game.events), the .on()/.off() listener discipline enforced in scene shutdown, SoundService (mobile audio unlock on first gesture), InputService (semantic actions instead of raw keys), and SaveService (versioned localStorage with a migration chain). Use it when adding global state, an event bus, audio/input/save plumbing, or fixing listener leaks and lost saves. Pairs with the official scenes skill, phaser-testing, and phaser-i18n.
 ---
 
 # Phaser 4 Services and Shared State

package/plugins/lisa-phaser/skills/phaser-testing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: phaser-testing
-description: This skill should be used when writing or designing tests for a Phaser 4 game — unit-testing pure game logic with Vitest, keeping logic Phaser-free so it tests without a browser, the Phaser.HEADLESS renderer for logic-only boots, asset-manifest coverage tests, and the CI runtime gates (boot smoke, allocation/perf budget, leak gate, determinism gate, deterministic Playwright visual regression, bundle-size budget) that verify scenes and entities that are excluded from unit coverage. Use it when adding tests, setting up CI verification, or deciding what is testable at which level. Pairs with phaser-project-structure, phaser-assets, and phaser-services.
+description: This skill should be used when writing or designing tests for a Phaser 4 game — unit-testing pure game logic with Vitest, keeping logic Phaser-free so it tests without a browser, the Phaser.HEADLESS renderer for logic-only boots, asset-manifest coverage tests, and the CI runtime gates (boot smoke, allocation/perf budget, leak gate, determinism gate, deterministic Playwright visual regression, bundle-size budget) that verify scenes and entities that are excluded from unit coverage. Use it when adding tests, setting up CI verification, or deciding what is testable at which level. Pairs with phaser-project-structure, the official loading-assets skill, and phaser-services.
 ---
 
 # Phaser 4 Testing
@@ -56,7 +56,7 @@ Cheap tests that catch the silent runtime failures Phaser is famous for:
 
 - **Asset coverage**: every key constant in `src/assets.ts` appears in
   `public/assets/pack.json` (and optionally vice versa). A missing pack entry
-  otherwise ships as a green-square texture ([[phaser-assets]]).
+  otherwise ships as a green-square texture (the official `loading-assets` skill).
 - **Scene registry**: every `SceneKeys` constant has a scene class registered in
   the game config's `scene` array.
 - These are plain Vitest tests reading JSON/TS — no Phaser instance needed.

package/plugins/lisa-phaser-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.179.0",
+  "version": "2.180.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-agy/skills/phaser-accessibility/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: phaser-accessibility
-description: This skill should be used when making a Phaser 4 game accessible — honoring prefers-reduced-motion, pausing on window/tab blur, keyboard navigation and visible focus for menus, colorblind-safe palettes, and a screen-reader live region that announces game state through the DOM. Use it when building menus, settings, HUD, or any player-facing UI, or when an accessibility requirement comes up. Pairs with phaser-services, phaser-i18n, and phaser-scenes.
+description: This skill should be used when making a Phaser 4 game accessible — honoring prefers-reduced-motion, pausing on window/tab blur, keyboard navigation and visible focus for menus, colorblind-safe palettes, and a screen-reader live region that announces game state through the DOM. Use it when building menus, settings, HUD, or any player-facing UI, or when an accessibility requirement comes up. Pairs with phaser-services, phaser-i18n, and the official scenes skill.
 ---
 
 # Phaser 4 Accessibility

package/plugins/lisa-phaser-agy/skills/phaser-asset-pipeline/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: phaser-asset-pipeline
-description: This skill should be used when setting up or changing the build-time asset pipeline of a Phaser 4 game — packing raw art in assets/src into public/assets (free-tex-packer-core texture atlases, audiosprite audio sprites, BMFont bitmap fonts) and the codegen step that emits typed keys to src/assets.ts so a missing or renamed key is a compile error. Use it when adding source art, wiring packing into the build, regenerating typed keys, or eliminating raw string asset keys. Pairs with phaser-assets, phaser-build-deploy, and phaser-services.
+description: This skill should be used when setting up or changing the build-time asset pipeline of a Phaser 4 game — packing raw art in assets/src into public/assets (free-tex-packer-core texture atlases, audiosprite audio sprites, BMFont bitmap fonts) and the codegen step that emits typed keys to src/assets.ts so a missing or renamed key is a compile error. Use it when adding source art, wiring packing into the build, regenerating typed keys, or eliminating raw string asset keys. Pairs with the official loading-assets skill, phaser-build-deploy, and phaser-services.
 ---
 
 # Phaser 4 Asset Pipeline
@@ -13,7 +13,7 @@ Runtime assets are **generated, not hand-placed**. Raw source art lives in
 key constants into `src/assets.ts`**. The payoff: a missing or renamed asset is a
 **compile error**, not a green square or silent-missing audio at runtime. No raw
 string asset / scene / event keys anywhere — they all come from the generated
-module ([[phaser-assets]] covers loading those keys at runtime).
+module (the official `loading-assets` skill covers loading those keys at runtime).
 
 ## Layout
 
@@ -52,7 +52,7 @@ for (const f of files) await writeFile(`public/assets/atlases/${f.name}`, f.buff
 
 The frame names in the manifest become the atlas frame keys you reference as
 generated constants. Atlas everything that renders together — loose images break
-sprite batching ([[phaser-assets]]).
+sprite batching (the official `loading-assets` skill).
 
 ## Step 2: audio sprites with audiosprite
 
@@ -70,7 +70,7 @@ with `this.load.audioSprite(Audio.Sfx, "audio/sfx.json")` and play by sprite key
 ## Step 3: bitmap fonts with BMFont
 
 `BitmapText` is the performant choice for high-churn text (scores, timers) —
-[[phaser-assets]] / [[phaser-i18n]]. Generate the `.fnt` (XML/JSON) + PNG page
+the official `loading-assets` skill / [[phaser-i18n]]. Generate the `.fnt` (XML/JSON) + PNG page
 from a font source with a BMFont tool (`msdf-bmfont-xml` or the `bmfont` CLI) in
 the same script:
 

package/plugins/lisa-phaser-agy/skills/phaser-i18n/SKILL.md

@@ -86,7 +86,7 @@ Persist the chosen locale via SaveService and apply it on boot; default from
 
 ## BitmapText vs Text — the localization trade-off
 
-The performance advice "use BitmapText for hot text" ([[phaser-gameobjects]])
+The performance advice "use BitmapText for hot text" (the official `game-object-components` skill)
 collides with i18n: a bitmap font only contains the glyphs it was generated with.
 
 - **BitmapText** — fastest, but the BMFont must include every glyph the locale

package/plugins/lisa-phaser-agy/skills/phaser-project-structure/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: phaser-project-structure
-description: This skill should be used when creating, restructuring, or reasoning about a Phaser 4 game project — the game config, the Vite + TypeScript layout, the Boot → Preloader → MainMenu → Game scene flow, scale/resolution setup for desktop and mobile, and where code and assets belong. Use it before scaffolding a project, adding a major subsystem, or deciding where a file should live. Pairs with phaser-scenes, phaser-assets, phaser-rendering, and phaser-testing.
+description: This skill should be used when creating, restructuring, or reasoning about a Phaser 4 game project — the game config, the Vite + TypeScript layout, the Boot → Preloader → MainMenu → Game scene flow, scale/resolution setup for desktop and mobile, and where code and assets belong. Use it before scaffolding a project, adding a major subsystem, or deciding where a file should live. Pairs with the official scenes skill, the official loading-assets skill, the official filters-and-postfx skill, and phaser-testing.
 ---
 
 # Phaser 4 Project Structure
 
 ## Overview
 
-This stack targets **Phaser 4** (v4.1+ "Salusa", npm package `phaser`), built
+This stack targets **Phaser 4** (v4.2+, npm package `phaser@^4.2.0`), built
 with **Vite + TypeScript** — the layout the official `phaserjs/template-vite-ts`
 template and `npm create @phaserjs/game@latest` scaffold. Phaser 4 ships its own
 type definitions (`types/phaser.d.ts`); do not add `@types/phaser`.
@@ -55,17 +55,17 @@ v4-specific config facts:
 - Pixel-art games: `pixelArt: true` (nearest-neighbor + roundPixels), or the new
   **`render.smoothPixelArt: true`** (WebGL-only) for pixel art that rotates or
   scales smoothly. Pick one per project and record the choice.
-- Custom render nodes register under `render.renderNodes` — see [[phaser-rendering]].
+- Custom render nodes register under `render.renderNodes` — see the official `filters-and-postfx` skill.
 - `Phaser.HEADLESS` exists for logic-only boots (tests) — see [[phaser-testing]].
 
 ## Scene flow
 
-Four-stage boot, in order (see [[phaser-scenes]] for lifecycle detail):
+Four-stage boot, in order (see the official `scenes` skill for lifecycle detail):
 
 1. **Boot** — loads only the handful of assets the Preloader's loading screen
    needs (logo, progress-bar art). No game assets here.
 2. **Preloader** — renders the loading UI and loads everything else, preferably
-   via a single asset-pack manifest (see [[phaser-assets]]), then starts MainMenu.
+   via a single asset-pack manifest (see the official `loading-assets` skill), then starts MainMenu.
 3. **MainMenu** — entry UI; starts Game.
 4. **Game** (+ overlay scenes like `HUD`, `Pause` run in parallel) — gameplay.
 

package/plugins/lisa-phaser-agy/skills/phaser-services/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: phaser-services
-description: This skill should be used when wiring cross-cutting services and shared state in a Phaser 4 game — the typed registry wrapper for global state, a single dedicated EventsCenter bus (never game.events), the .on()/.off() listener discipline enforced in scene shutdown, SoundService (mobile audio unlock on first gesture), InputService (semantic actions instead of raw keys), and SaveService (versioned localStorage with a migration chain). Use it when adding global state, an event bus, audio/input/save plumbing, or fixing listener leaks and lost saves. Pairs with phaser-scenes, phaser-testing, and phaser-i18n.
+description: This skill should be used when wiring cross-cutting services and shared state in a Phaser 4 game — the typed registry wrapper for global state, a single dedicated EventsCenter bus (never game.events), the .on()/.off() listener discipline enforced in scene shutdown, SoundService (mobile audio unlock on first gesture), InputService (semantic actions instead of raw keys), and SaveService (versioned localStorage with a migration chain). Use it when adding global state, an event bus, audio/input/save plumbing, or fixing listener leaks and lost saves. Pairs with the official scenes skill, phaser-testing, and phaser-i18n.
 ---
 
 # Phaser 4 Services and Shared State