@codyswann/lisa 2.179.0 → 2.180.1

package/plugins/lisa-phaser-cursor/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-cursor/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-cursor/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-rails/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.179.0",
+  "version": "2.180.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/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/src/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/src/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/src/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/src/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/src/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/src/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/skills/phaser-assets/SKILL.md

@@ -1,96 +0,0 @@
----
-name: phaser-assets
-description: This skill should be used when loading or organizing assets in a Phaser 4 game — the Loader (images, texture atlases, spritesheets, audio, fonts), asset-pack manifests via this.load.pack, the new PCT compact atlas format (load.atlasPCT), typed asset keys, and where files live in the Vite project. Use it when adding any asset, restructuring loading, fixing a missing-texture/green-square bug, or optimizing load size. Pairs with phaser-project-structure, phaser-scenes, and phaser-gameobjects.
----
-
-# Phaser 4 Assets and Loading
-
-## Overview
-
-All runtime assets live under `public/assets/` (served verbatim by Vite — never
-`import` game assets through the bundler) and are loaded by Phaser's Loader in a
-scene's `preload()`. The opinionated pattern: **one asset-pack manifest, loaded
-by the Preloader, with every key defined as a typed constant.**
-
-## Asset packs (the default loading strategy)
-
-A pack is a JSON manifest the Loader consumes wholesale:
-
-```json
-{
-  "main": {
-    "files": [
-      { "type": "atlasPCT", "key": "game-atlas", "url": "atlases/game.pct" },
-      { "type": "image", "key": "background", "url": "images/background.png" },
-      { "type": "audio", "key": "sfx-jump", "url": ["audio/jump.ogg", "audio/jump.m4a"] },
-      { "type": "spritesheet", "key": "explosion", "url": "sheets/explosion.png",
-        "frameConfig": { "frameWidth": 64, "frameHeight": 64 } }
-    ]
-  }
-}
-```
-
-```ts
-// Preloader.preload()
-this.load.pack("game-pack", "assets/pack.json");
-```
-
-Why packs: loading is declared in one reviewable file instead of scattered
-`load.*` calls; adding an asset never touches scene code beyond using the key.
-
-## Texture atlases — the rule, not the suggestion
-
-Individual images break sprite batching. Everything that renders together ships
-in an atlas:
-
-- **PCT (Phaser Compact Texture)** is the preferred v4 atlas format —
-  `this.load.atlasPCT(key, url)` — its manifests are 90–95% smaller than the
-  JSON-hash equivalent. JSON/XML/Unity/multi-atlas loaders still exist for
-  third-party toolchains.
-- Spritesheets (`load.spritesheet`) are acceptable only for uniform-grid
-  animation strips; anything else is an atlas.
-
-## Audio
-
-- Provide at least two encodings (`.ogg` + `.m4a`) in the url array; Phaser
-  picks the first the browser can play.
-- Web Audio is the default manager; it unlocks on first user gesture — never
-  autoplay sound before input (it will silently fail and "work on my machine").
-- Use audio sprites (`load.audioSprite`) for large sets of short SFX.
-
-## Typed keys
-
-Every key lives in `src/assets.ts`:
-
-```ts
-export const Tex = { GameAtlas: "game-atlas", Background: "background" } as const;
-export const Sfx = { Jump: "sfx-jump" } as const;
-export const SceneKeys = { Boot: "Boot", Preloader: "Preloader", Game: "Game" } as const;
-```
-
-Scenes use `Tex.GameAtlas`, never `"game-atlas"` inline. A bad inline key fails
-at runtime as a green square or silent missing audio; a bad constant fails in
-review and in tests that assert the pack manifest covers every constant.
-
-## Loading UX and failure handling
-
-- The Preloader binds `this.load.on("progress", …)` to a progress bar built from
-  Boot-loaded art ([[phaser-project-structure]]).
-- Handle `loaderror`: `this.load.on(Phaser.Loader.Events.FILE_LOAD_ERROR, …)` —
-  log the key and URL; a missing asset must fail loudly in dev, not render as a
-  placeholder in production.
-
-## Project conventions
-
-- `public/assets/` subdirs: `atlases/`, `images/`, `audio/`, `sheets/`, `fonts/`,
-  plus `pack.json` at the root of `assets/`.
-- Generated atlas files (PCT/JSON + PNG pages) are build inputs, committed to the
-  repo; their source art lives wherever the art pipeline keeps it.
-- A test should assert that every key constant in `src/assets.ts` appears in
-  `pack.json` (cheap manifest-coverage check; see [[phaser-testing]]).
-
-## Verification
-
-Asset changes are verified by booting the game and watching the network panel /
-console: every file 200s, no `FILE_LOAD_ERROR`, and the new asset visibly renders
-or audibly plays in the scene that uses it.

package/plugins/lisa-phaser/skills/phaser-assets/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "Phaser Assets"
-short_description: "loading or organizing assets in a Phaser 4 game — the Loader (images, texture atlases, spritesheets, audio, fonts), asset-pack manifests…"
-default_prompt:
-  - "Use $phaser-assets: loading or organizing assets in a Phaser 4 game — the Loader (images, texture atlases, spritesheets, audio, fonts), asset-pack manifests…."

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

@@ -1,94 +0,0 @@
----
-name: phaser-gameobjects
-description: This skill should be used when creating or managing Phaser 4 GameObjects — sprites, images, text, containers, groups and object pooling, animations (anims), tweens, particles, and the v4 GPU layers (SpriteGPULayer, TilemapGPULayer) for massive object counts. Use it when adding entities, fixing per-frame allocation/GC issues, pooling projectiles, or choosing between a Container and a Group. Pairs with phaser-scenes, phaser-physics, phaser-rendering, and phaser-assets.
----
-
-# Phaser 4 GameObjects
-
-## Overview
-
-GameObjects carry over from Phaser 3 largely unchanged: `Sprite`, `Image`,
-`Text`, `BitmapText`, `Container`, `Group`, `Graphics`, the Shape objects, and
-the particle system. v4 adds `Gradient`, `Stamp`, `CaptureFrame`, the Noise
-objects, NineSlice tiling (`tileX`/`tileY`), and — the headline — the GPU
-layers. Removed: `Mesh`, `Plane`, the OBJ loader, `Camera3D`/`Layer3D`
-([[phaser-v3-migration]]).
-
-## Choosing the right object
-
-- **Image** for static visuals (cheaper than Sprite — no animation component).
-- **Sprite** only when it animates.
-- **Container** for transform-grouping a small, fixed set of children (a unit +
-  its health bar). Containers are not free — don't nest deeply or use them as
-  ad-hoc layers. In v4.1+, `Layer` is a true GameObject and is the right tool
-  for z-grouping with filters.
-- **Group** for managing many homogeneous objects — and for pooling (below).
-- **Text** uses Canvas rasterization per change; for score counters and other
-  hot text use `BitmapText`.
-
-## Object pooling (mandatory for spawn-heavy entities)
-
-Bullets, enemies, particles, pickups: never `new`/`destroy` per spawn — pool
-through a Group:
-
-```ts
-this.bullets = this.add.group({ classType: Bullet, maxSize: 64, runChildUpdate: true });
-// spawn
-const b = this.bullets.get(x, y, Tex.GameAtlas, "bullet") as Bullet | null;
-if (b) { b.setActive(true).setVisible(true); b.fire(dir); }
-// despawn (inside Bullet when off-screen/expired)
-this.bullets.killAndHide(this); this.body.enable = false;
-```
-
-`maxSize` caps the pool; `get()` returns `null` when exhausted — handle it
-(drop the spawn) rather than growing unbounded.
-
-## Per-frame discipline
-
-In `update()` paths: no object literals, no array spreads, no `.map/.filter`
-chains, no closures. Hoist scratch `Vector2`s and reuse them. The GC pause from
-per-frame garbage is the most common cause of stutter that profilers get blamed
-for.
-
-## Animations and tweens
-
-- Define animations once (Preloader `create` or a dedicated module) on the
-  global `this.anims`; play by key constant: `sprite.play(Anim.Run)`.
-- Tweens (`this.tweens.add`) and Timelines carry over from v3 unchanged. Kill
-  tweens that target objects you pool/despawn — a tween holding a pooled object
-  alive is a classic leak.
-
-## Massive counts: the GPU layers
-
-New in v4 — reach for these instead of "thousands of sprites":
-
-- **SpriteGPULayer** — on the order of a million static-ish sprites in a single
-  draw call, with per-member GPU-driven animation, easing, and parallax. Use for
-  starfields, crowds, debris, background fauna.
-- **TilemapGPULayer** — renders a whole tile layer as one quad with per-pixel
-  cost, up to 4096×4096 tiles. Use for large maps, especially on mobile.
-
-Regular Sprites + Groups remain correct for interactive entities (things with
-bodies, input, per-entity logic).
-
-## Particles
-
-The particle API is the v3.60-style `this.add.particles(x, y, texture, config)`
-emitter manager. v4 additions: particles respect the lighting system. Pool
-explosion-style one-shot emitters or use `emitter.explode()` rather than
-creating emitters per event.
-
-## Project conventions
-
-- Entity classes (`Bullet extends Phaser.Physics.Arcade.Sprite`) live in
-  `src/entities/`, take their tunables from `src/logic/` config objects, and use
-  asset-key constants ([[phaser-assets]]).
-- Depth management: named depth constants (`Depth.World`, `Depth.FX`,
-  `Depth.UI`), not scattered magic numbers.
-
-## Verification
-
-Object-lifecycle changes are verified in the running game: spawn/despawn the
-entity repeatedly and watch the object count (`this.children.length`,
-`group.getLength()`) stay bounded, and the FPS meter stay flat — an unbounded
-count or sawtooth memory profile means the pool or tween cleanup is wrong.

package/plugins/lisa-phaser/skills/phaser-gameobjects/agents/openai.yaml

@@ -1,4 +0,0 @@
-display_name: "Phaser Gameobjects"
-short_description: "creating or managing Phaser 4 GameObjects — sprites, images, text, containers, groups and object pooling, animations (anims), tweens…"
-default_prompt:
-  - "Use $phaser-gameobjects: creating or managing Phaser 4 GameObjects — sprites, images, text, containers, groups and object pooling, animations (anims), tweens…."