summer-engine 2.2.0 → 2.5.0

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
     {
       "name": "summer",
       "source": "./",
-      "version": "2.2.0",
+      "version": "2.5.0",
       "description": "Superpowers for AI game dev. 60 auto-trigger skills under summer: namespace, MCP bridge to the local Summer Engine, session-start + pre-commit hooks.",
       "author": { "name": "Summer Engine", "email": "founders@summerengine.com" },
       "category": "game-development",

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "summer",
-  "version": "2.2.0",
+  "version": "2.5.0",
   "description": "Superpowers for AI game dev. 60 auto-trigger skills + lifecycle hooks + MCP bridge to the local Summer Engine — the AI-native game engine.",
   "author": {
     "name": "Summer Engine",
@@ -26,10 +26,20 @@
     "performance"
   ],
   "skills": [
-    "./skills/_meta/using-summer/",
-    "./skills/_meta/skill-create/",
-    "./skills/_meta/skill-improve/",
-    "./skills/_meta/skill-test/",
+    "./skills/workflow/using-summer/",
+    "./skills/workflow/skill-create/",
+    "./skills/workflow/skill-improve/",
+    "./skills/workflow/skill-test/",
+    "./skills/workflow/gameskill/",
+    "./skills/workflow/brainstorming/",
+    "./skills/workflow/investigating-bugs/",
+    "./skills/workflow/verification-before-completion/",
+    "./skills/workflow/writing-plans/",
+    "./skills/workflow/dispatching-parallel-agents/",
+    "./skills/workflow/writing-skills/",
+    "./skills/workflow/playtesting-a-feature/",
+    "./skills/workflow/debugging-game-feel/",
+    "./skills/workflow/diagnosing-perf-regressions/",
     "./skills/scene-and-project/brainstorm-game/",
     "./skills/scene-and-project/new-project/",
     "./skills/scene-and-project/browse-templates/",
@@ -38,7 +48,9 @@
     "./skills/scene-and-project/make-game/",
     "./skills/debugging/debug/",
     "./skills/gameplay-mechanics/design-mechanic/",
+    "./skills/gameplay-mechanics/auto-fire-targeting/",
     "./skills/level-design/design-level/",
+    "./skills/level-design/scene-to-level/",
     "./skills/rendering-and-lighting/art-direction/",
     "./skills/rendering-and-lighting/3d-lighting/",
     "./skills/audio/audio-direction/",
@@ -60,6 +72,9 @@
     "./skills/2d-assets/tileable-texture/",
     "./skills/2d-assets/sprite-sheet/",
     "./skills/2d-assets/skybox-panorama/",
+    "./skills/2d-assets/create-asset-sheet/",
+    "./skills/2d-assets/instantiate-asset-pack/",
+    "./skills/2d-assets/use-widget-asset/",
     "./skills/3d-assets/prop-model/",
     "./skills/3d-assets/character-model/",
     "./skills/3d-assets/environment-kit/",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "summer",
-  "version": "2.2.0",
+  "version": "2.5.0",
   "description": "Superpowers for AI game dev. 60 auto-trigger skills, MCP bridge to the local Summer Engine, lifecycle hooks. Build games by talking.",
   "author": {
     "name": "Summer Engine",
@@ -15,10 +15,20 @@
     "workflow", "level-design", "vfx", "multiplayer"
   ],
   "skills": [
-    "./skills/_meta/using-summer/",
-    "./skills/_meta/skill-create/",
-    "./skills/_meta/skill-improve/",
-    "./skills/_meta/skill-test/",
+    "./skills/workflow/using-summer/",
+    "./skills/workflow/skill-create/",
+    "./skills/workflow/skill-improve/",
+    "./skills/workflow/skill-test/",
+    "./skills/workflow/gameskill/",
+    "./skills/workflow/brainstorming/",
+    "./skills/workflow/investigating-bugs/",
+    "./skills/workflow/verification-before-completion/",
+    "./skills/workflow/writing-plans/",
+    "./skills/workflow/dispatching-parallel-agents/",
+    "./skills/workflow/writing-skills/",
+    "./skills/workflow/playtesting-a-feature/",
+    "./skills/workflow/debugging-game-feel/",
+    "./skills/workflow/diagnosing-perf-regressions/",
     "./skills/scene-and-project/brainstorm-game/",
     "./skills/scene-and-project/new-project/",
     "./skills/scene-and-project/browse-templates/",

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://cursor.com/schemas/cursor-plugin/plugin.json",
   "name": "summer",
   "displayName": "Summer",
-  "version": "2.2.0",
+  "version": "2.5.0",
   "description": "Superpowers for AI game dev. 60 auto-trigger skills + lifecycle hooks + MCP bridge to the local Summer Engine — the AI-native game engine.",
   "author": { "name": "Summer Engine", "email": "founders@summerengine.com" },
   "publisher": "summer-engine",
@@ -17,10 +17,20 @@
   ],
   "tags": ["game-dev", "ai", "godot", "creative", "design"],
   "skills": [
-    "./skills/_meta/using-summer/",
-    "./skills/_meta/skill-create/",
-    "./skills/_meta/skill-improve/",
-    "./skills/_meta/skill-test/",
+    "./skills/workflow/using-summer/",
+    "./skills/workflow/skill-create/",
+    "./skills/workflow/skill-improve/",
+    "./skills/workflow/skill-test/",
+    "./skills/workflow/gameskill/",
+    "./skills/workflow/brainstorming/",
+    "./skills/workflow/investigating-bugs/",
+    "./skills/workflow/verification-before-completion/",
+    "./skills/workflow/writing-plans/",
+    "./skills/workflow/dispatching-parallel-agents/",
+    "./skills/workflow/writing-skills/",
+    "./skills/workflow/playtesting-a-feature/",
+    "./skills/workflow/debugging-game-feel/",
+    "./skills/workflow/diagnosing-perf-regressions/",
     "./skills/scene-and-project/brainstorm-game/",
     "./skills/scene-and-project/new-project/",
     "./skills/scene-and-project/browse-templates/",

package/.factory-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "summer",
-  "description": "Superpowers for AI game dev. 24 auto-trigger skills + lifecycle hooks + MCP bridge to the local Summer Engine — the AI-native game engine.",
-  "version": "2.0.1",
+  "description": "Superpowers for AI game dev. 60 auto-trigger skills + lifecycle hooks + MCP bridge to the local Summer Engine — the AI-native game engine.",
+  "version": "2.5.0",
   "author": {
     "name": "Summer Engine",
     "email": "founders@summerengine.com",

package/.opencode/INSTALL.md

@@ -63,7 +63,7 @@ The model should auto-invoke the `summer:fps-controller` skill before writing an
 |---|---|
 | No orientation banner appears | Verify `plugin` array in `opencode.json` and that `summer-engine` is installed in `node_modules/`. |
 | MCP tools return "not connected" | Run `summer run` to launch the engine. The MCP server lazy-connects on the first tool call. |
-| `summer` command not found | `npm install -g summer-engine` for the global CLI. |
+| `summer` command not found | Use `npx -y summer-engine@latest <command>` or install the CLI globally only if you want a persistent `summer` command. |
 | Skills don't auto-trigger | The using-summer skill loads on first user message; if that message is empty (e.g. a startup probe), they'll trigger on the second. |
 
 ## Uninstall

package/CHANGELOG.md

@@ -2,13 +2,34 @@
 
 All notable changes to summer-engine will be documented here. Following [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and [Semantic Versioning](https://semver.org/).
 
+## [2.5.0] — 2026-05-27 — "Project Memory"
+
+Note: `2.1.0` through `2.4.0` were internal package/plugin snapshots in the engine repo. npm `latest` was still `2.3.0` before this release, so `2.5.0` is the public catch-up release for the memory, setup, and MCP reliability work.
+
+### Added
+- `summer memory` — read-only CLI view of `.summer` project memory, with `--json`, `show <file>`, and `path` subcommands.
+- `projectMemory` in `summer_get_project_context` — lightweight summary of `.summer` canonical files and structured memory for agents.
+- `.summer/memory/` convention for locked project facts such as voice IDs, world canon, provider bindings, and cross-session decisions.
+- Project-memory checks in `summer status` and `summer doctor`.
+- First-class `summer setup github-copilot` and `summer setup vscode-copilot` targets for Copilot CLI and GitHub Copilot in VS Code.
+- Copy-paste setup prompt docs: users can paste "Install Summer Engine and let's make a game." into their AI environment instead of starting with npm commands.
+
+### Changed
+- `/summer:voice-line` now writes locked cast assignments to `.summer/memory/casting/voices.md`, while still reading legacy `.summer/voice-cast.md`.
+- Agent playbook and `using-summer` now require agents to read relevant project memory before creative/audio/dialogue/level/character work.
+- CLI and docs now link directly to the public source repo: `https://github.com/SummerEngine/summer`.
+
+### Fixed
+- MCP project context now falls back to engine health fields for project path, project name, and current scene.
+- Mutating MCP tools now surface failure terminal states and no-results failure envelopes instead of masking them as success.
+
 ## [2.0.0] — 2026-05-09 — "Superpowers"
 
 The plugin rebrand. Summer is now positioned as superpowers for AI game dev — installable in Claude Code, Codex (CLI + App), Cursor, Factory Droid, Gemini CLI, OpenCode, GitHub Copilot CLI, and Windsurf with one canonical command per harness.
 
 ### Added
 - **`summer:using-summer`** meta-skill — establishes workflow priority, red-flag list, and skill-invocation discipline. Auto-loads on session start. Modeled on `superpowers:using-superpowers`.
-- **`summer:debug`** skill — the missing flagship skill. Disciplined script-errors → console → debugger → hypothesize → propose → fix → verify loop. Honors all 4 cases in `_tests/specs/debug.md`.
+- **`summer:debug`** skill — the missing flagship skill. Disciplined script-errors → console → debugger → hypothesize → propose → fix → verify loop. Honors all 4 cases in `tests/specs/debug.md`.
 - **Manifest validator** (`src/lib/plugin-manifests.test.ts`) — vitest test that walks every plugin manifest and verifies each referenced skill resolves to a real `SKILL.md` on disk. Also enforces the "Use when…" auto-trigger pattern in every skill's description.
 - **`AGENTS.md`** + **`GEMINI.md`** at repo root — context primer for harnesses that read AGENTS-style files (Codex, Factory) and the Gemini extension.
 - **`.opencode/INSTALL.md`** — explicit OpenCode setup guide.
@@ -36,10 +57,10 @@ The plugin rebrand. Summer is now positioned as superpowers for AI game dev —
 
 ### Fixed
 - `summer_input_map_bind` syntax aligned across `fps-controller` SKILL.md and its behavioral test spec.
-- `_meta/skill-test` static linter relaxed to allow forward-reference `See also` links to other SKILL.md files (warn instead of fail).
+- `workflow/skill-test` static linter relaxed to allow forward-reference `See also` links to other SKILL.md files (warn instead of fail).
 
 ### Added
-- `_shared/summer-folder.md` — canonical `.summer/` folder convention (documents files written by `/summer:brainstorm-game`, `/summer:art-direction`, etc.).
+- `references/summer-folder.md` — canonical `.summer/` folder convention (documents files written by `/summer:brainstorm-game`, `/summer:art-direction`, etc.).
 - `CHANGELOG.md` — retroactive v1.0.0 → v1.3.1 history.
 
 ## [1.3.1] — 2026-05-05
@@ -64,9 +85,9 @@ The plugin rebrand. Summer is now positioned as superpowers for AI game dev —
 
 ### Added
 - 20-category skill library scaffold with descriptive folder names (`character-controllers`, `gameplay-mechanics`, `scripting-patterns`, etc.).
-- `_shared/` directory with 5 canonical references (godot-version, mcp-tools-reference, collaborative-protocol, template-registry, gd-style).
-- `_meta/` directory with 3 meta-skills (skill-test linter, skill-create bootstrap, skill-improve eval harness).
-- `_tests/specs/` directory with per-skill behavioral test specs (fps-controller as canonical format).
+- `references/` directory with 5 canonical references (godot-version, mcp-tools-reference, collaborative-protocol, template-registry, gd-style).
+- `workflow/` directory with 3 meta-skills (skill-test linter, skill-create bootstrap, skill-improve eval harness).
+- `tests/specs/` directory with per-skill behavioral test specs (fps-controller as canonical format).
 - `catalog.yaml` — 85-skill roadmap with HAVE / NEXT / LATER status.
 
 ### Changed

package/CLAUDE.md

@@ -1,5 +1,5 @@
 # Summer — Claude context
 
-This file primes Claude Code on Summer when it loads from this repo. The full agent workflow lives in `skills/_meta/using-summer/SKILL.md`; activate that skill on every fresh session.
+This file primes Claude Code on Summer when it loads from this repo. The full agent workflow lives in `skills/workflow/using-summer/SKILL.md`; activate that skill on every fresh session.
 
-@./skills/_meta/using-summer/SKILL.md
+@./skills/workflow/using-summer/SKILL.md

package/GEMINI.md

@@ -51,6 +51,5 @@ Tools return "Summer Engine is not running." Tell the user to run `summer run` (
 
 If skills aren't loading or the MCP server fails:
 
-- `npm install -g summer-engine` — global CLI.
-- `summer setup gemini --yes` — writes the right MCP config.
-- `summer doctor` — reports auth, engine, port, skill state.
+- `npx -y summer-engine@latest setup gemini --yes --force` — writes the right MCP config.
+- `npx -y summer-engine@latest doctor` — reports auth, engine, port, project memory, and skill state.

package/README.md

@@ -2,7 +2,11 @@
 
 Build real 2D and 3D games through conversation. No coding required. Export to Steam, desktop, mobile, and web. Built on the Godot team's work, customized and honed so AI agents and humans can collaborate on great games.
 
-**Summer** is the open-source plugin that connects your AI coding agent to Summer Engine. MIT licensed. Works in Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Factory Droid, GitHub Copilot CLI, and Windsurf.
+**Summer** is the open-source plugin that connects your AI coding agent to Summer Engine. MIT licensed. First-class setup works in Claude Code, Cursor, Codex, Windsurf, Cline, Roo Code, Gemini CLI, GitHub Copilot CLI, GitHub Copilot in VS Code, and OpenCode. Factory Droid uses the plugin marketplace path.
+
+- **Source:** [github.com/SummerEngine/summer](https://github.com/SummerEngine/summer)
+- **Docs:** [summerengine.com/docs](https://summerengine.com/docs)
+- **MCP setup:** [summerengine.com/mcp](https://summerengine.com/mcp)
 
 It just works. Open your agent, say *"let's make an FPS in Summer Engine,"* and it does.
 
@@ -10,7 +14,7 @@ It just works. Open your agent, say *"let's make an FPS in Summer Engine,"* and
 
 ## Get started — one prompt
 
-Open Claude Code (or Cursor / Codex / Windsurf / etc.) and paste:
+Open your AI agent (Claude Code, Cursor, Codex, Copilot, Windsurf, etc.) and paste:
 
 > Install Summer Engine and let's make a game.
 
@@ -29,7 +33,7 @@ At that point the agent has the skills, the MCP server, and your engine running.
 
 ## AGENTS READING THIS — the install playbook
 
-You are an AI coding agent (Claude Code, Cursor, Codex, Windsurf). The user told you to install Summer Engine. **Run this playbook via your shell** — Bash on macOS/Linux or PowerShell on Windows; `npx -y` is shell-agnostic and works identically in both. Detection first, then only install what's missing — never double-install.
+You are an AI coding agent. The user told you to install Summer Engine. **Run this playbook via your shell** — Bash on macOS/Linux or PowerShell on Windows; `npx -y` is shell-agnostic and works identically in both. Detection first, then only install what's missing — never double-install.
 
 ### Step −1 — Verify Node.js is on PATH
 
@@ -42,7 +46,7 @@ If this fails or returns a version below 18, **stop**. Tell the user: "Summer ne
 ### Step 0 — Pre-detection (no commits to disk, just check state)
 
 ```bash
-npx -y summer-engine doctor --json
+npx -y summer-engine@latest doctor --json
 ```
 
 The first invocation downloads the npm package transparently to npx's cache (~3 MB, ~5 sec). Subsequent calls are fast. The `-y` flag auto-confirms npx's "ok to install summer-engine?" prompt so the call doesn't hang in a non-interactive shell.
@@ -53,12 +57,15 @@ Parse the JSON output. Top-level `ok: true` means everything is installed and yo
 {
   "ok": true | false,
   "checks": [
-    { "id": "node-version",   "status": "ok" | "warning" | "fail", ... },
-    { "id": "cli-version",    "status": "ok" | "warning" | "fail", ... },
-    { "id": "login",          "status": "ok" | "warning" | "fail", ... },
-    { "id": "engine-install", "status": "ok" | "warning" | "fail", ... },
-    { "id": "local-api",      "status": "ok" | "warning" | "fail", ... },
-    { "id": "mcp-server",     "status": "ok" | "warning" | "fail", ... }
+    { "id": "node-version",        "status": "ok" | "warning" | "fail", ... },
+    { "id": "cli-version",         "status": "ok" | "warning" | "fail", ... },
+    { "id": "cli-version-current", "status": "ok" | "warning" | "fail", ... },
+    { "id": "skills-version-stale","status": "ok" | "warning" | "fail", ... },
+    { "id": "login",               "status": "ok" | "warning" | "fail", ... },
+    { "id": "engine-install",      "status": "ok" | "warning" | "fail", ... },
+    { "id": "local-api",           "status": "ok" | "warning" | "fail", ... },
+    { "id": "project-memory",      "status": "ok" | "warning" | "fail", ... },
+    { "id": "mcp-server",          "status": "ok" | "warning" | "fail", ... }
   ]
 }
 ```
@@ -67,21 +74,23 @@ Parse the JSON output. Top-level `ok: true` means everything is installed and yo
 |---|---|---|
 | `node-version` | continue | (Step −1 already covered this) |
 | `cli-version` | (always ok via npx) | — |
+| `cli-version-current` | continue | run `npx clear-npx-cache && npx -y summer-engine@latest doctor --json` (forces a fresh resolve) |
+| `skills-version-stale` | skip Step 1 | run Step 1 with `--force` |
 | `engine-install` | skip Step 2 | run Step 2 |
 | `login` | skip Step 3 | run Step 3 |
 | `local-api` | skip Step 5b wait-loop | run wait-loop after `summer run` |
+| `project-memory` | continue | if a project is open, run `summer:brainstorm-game` before building |
 | `mcp-server` | skip Step 1 | run Step 1 |
-| (skills installed) | skip Step 1 | run Step 1 |
 
-(There's no doctor check for "skills installed" yet — run Step 1 unconditionally on first install. It's idempotent.)
+**On version drift:** if either `cli-version-current` or `skills-version-stale` returns `warning` or `fail`, you should refresh before proceeding. Tell the user once: "There's a newer Summer (X.Y.Z → A.B.C); updating before we start." Then run the recommended action from `details.recommendedAction` and re-run doctor. Don't ask the user to choose — they paste 'install' and want the latest.
 
 ### Step 1 — Install user-level skills (idempotent, fast)
 
 ```bash
-npx -y summer-engine setup claude-code --yes
+npx -y summer-engine@latest setup claude-code --yes --force
 ```
 
-Replace `claude-code` with the user's actual agent: `codex`, `cursor`, or `windsurf`. (Gemini, OpenCode, Factory Droid, Copilot CLI use different install paths — see [`docs/`](docs/) per harness.) This writes 60 skill files to `~/.claude/skills/<name>/SKILL.md` (or the agent's equivalent user-skill directory) AND writes the MCP server config so the agent can talk to the engine.
+Replace `claude-code` with the user's actual agent: `codex`, `cursor`, `windsurf`, `cline`, `roo-code`, `gemini`, `github-copilot`, `vscode-copilot`, or `opencode`. Use `github-copilot` for Copilot CLI and `vscode-copilot` for GitHub Copilot Chat/Agent in VS Code. Factory Droid still uses the plugin marketplace path in the install section below. This writes 60 skill files to `~/.claude/skills/<name>/SKILL.md` (or the agent's equivalent user-skill directory) AND writes the MCP server config so the agent can talk to the engine. The `--force` flag wipes any stale skill content first, so re-runs always end up with the latest copy.
 
 **First-install detection:** if `~/.claude/skills/` didn't exist before this command, Claude Code wasn't watching it and won't auto-detect the new files this session. Tell the user **once**: "Skills installed — restart your agent so they load." On subsequent installs (directory already existed), skills auto-detect mid-session and no restart is needed. **You can detect first-install vs upgrade by checking if `~/.claude/skills/` existed before Step 1; record the result before running setup.**
 
@@ -90,7 +99,7 @@ Replace `claude-code` with the user's actual agent: `codex`, `cursor`, or `winds
 ### Step 2 — Install the engine app (only if `engine-install` check failed)
 
 ```bash
-npx -y summer-engine install
+npx -y summer-engine@latest install
 ```
 
 ~1 GB. Downloads from Summer's signed releases. The bundle includes the engine binary plus Git and a handful of other runtime tools so users who don't already have them aren't blocked. The CLI prints the URL and size before touching disk. Tell the user **"downloading the engine app, ~1 GB — this takes a couple minutes"** so they don't bail thinking it stalled.
@@ -100,15 +109,15 @@ npx -y summer-engine install
 ### Step 3 — Sign in (only if `login` check failed)
 
 ```bash
-npx -y summer-engine login
+npx -y summer-engine@latest login
 ```
 
-This opens the user's default browser. **Tell the user**: "Your browser is opening now. Click sign-in once and come back to this terminal." The CLI waits up to 120 seconds for the auth callback, writes the token to `~/.summer/auth-token`, and returns. **If the user takes longer than 120s, the command exits with an error — just re-run `npx -y summer-engine login` and tell them to be quicker.** Don't loop indefinitely. The same token is shared with the engine — they sign in once, both surfaces accept it.
+This opens the user's default browser. **Tell the user**: "Your browser is opening now. Click sign-in once and come back to this terminal." The CLI waits up to 120 seconds for the auth callback, writes the token to `~/.summer/auth-token`, and returns. **If the user takes longer than 120s, the command exits with an error — just re-run `npx -y summer-engine@latest login` and tell them to be quicker.** Don't loop indefinitely. The same token is shared with the engine — they sign in once, both surfaces accept it.
 
 ### Step 4 — Re-run doctor to confirm
 
 ```bash
-npx -y summer-engine doctor --json
+npx -y summer-engine@latest doctor --json
 ```
 
 Should now return `ok: true` for `cli-version`, `login`, and `engine-install`. (`local-api` will still be `warning` — that's expected; the engine isn't running yet.) If a setup check still fails, surface the specific message to the user — don't loop or paper over it.
@@ -124,8 +133,8 @@ cd ~/Projects   # or wherever the user keeps code
 If the user said "let's make a game" without specifying a template, default to `3d-basic`. Pick a sensible project name from the user's request (e.g. "FPS" → `my-fps-game`). Avoid spaces in the name.
 
 ```bash
-npx -y summer-engine create 3d-basic my-fps-game
-npx -y summer-engine run my-fps-game
+npx -y summer-engine@latest create 3d-basic my-fps-game
+npx -y summer-engine@latest run my-fps-game
 ```
 
 `summer run` launches the engine app with the project loaded and polls the engine's local API for up to 20 seconds before returning.
@@ -137,13 +146,13 @@ If the engine takes longer than 20s to boot (cold start, slow disk, etc.), `summ
 ```bash
 # Poll doctor until local-api flips to ok (max ~30s):
 for i in 1 2 3 4 5 6; do
-  result=$(npx -y summer-engine doctor --json)
+  result=$(npx -y summer-engine@latest doctor --json)
   echo "$result" | grep -q '"id":"local-api","status":"ok"' && break
   sleep 5
 done
 ```
 
-(Equivalent PowerShell: `for ($i=0; $i -lt 6; $i++) { $r = npx -y summer-engine doctor --json; if ($r -match '"id":"local-api","status":"ok"') { break }; Start-Sleep 5 }`)
+(Equivalent PowerShell: `for ($i=0; $i -lt 6; $i++) { $r = npx -y summer-engine@latest doctor --json; if ($r -match '"id":"local-api","status":"ok"') { break }; Start-Sleep 5 }`)
 
 Once `local-api` is `ok`, MCP tools are safe to call.
 
@@ -151,26 +160,29 @@ Once `local-api` is `ok`, MCP tools are safe to call.
 
 Now you have skills + MCP. **Don't jump into `summer create` content from a vague prompt** — invoke the `summer:brainstorm-game` skill via the `Skill` tool first. It scopes mechanics, art direction, and the V1 cut list, and writes the result to `.summer/GameSoul.md`. Every other Summer skill reads from that file.
 
+Project memory lives in `.summer/` as readable Markdown. Use `.summer/memory/` for locked facts that should not drift across sessions, such as character voice IDs, world canon, and provider bindings. Users can inspect it with `summer memory`; agents should read relevant memory surfaced by `summer_get_project_context` before changing creative/audio/dialogue/level/character work.
+
 Only skip brainstorm if the user explicitly said "skip brainstorm" or "just build the X already." After brainstorm, the appropriate build skills (`fps-controller`, `design-mechanic`, `design-level`, `make-game`, etc.) auto-trigger from natural language.
 
 ### Anti-patterns (do NOT do these)
 
-- **Don't run `npm install -g summer-engine`.** Use `npx -y summer-engine ...` instead. `-g` requires `sudo` on most Mac/Linux setups — the user will get permission errors and you'll get stuck. `npx` works without root and the MCP config we ship already points at `npx summer-engine mcp`.
+- **Don't run `npm install -g summer-engine`.** Use `npx -y summer-engine@latest ...` instead. `-g` requires `sudo` on most Mac/Linux setups — the user will get permission errors and you'll get stuck. `npx` works without root and the MCP config we ship already points at `npx summer-engine mcp`.
 - **Don't try to install Node.js for the user.** If `node --version` fails, point them at https://nodejs.org and stop.
 - **Don't ask the user "do you want the engine too?" or "do you also want the CLI?"** — there is one product, three pieces, all installed by this playbook.
-- **Don't double-install.** Always run `npx -y summer-engine doctor --json` first. Skip steps that already returned `status: ok`.
+- **Don't double-install.** Always run `npx -y summer-engine@latest doctor --json` first. Skip steps that already returned `status: ok`.
 - **Don't tell the user to type `/plugin marketplace add` or `/plugin install`.** The CLI path is the canonical install — those slash commands are an alternative for the marketplace TUI, not the primary flow.
 - **Don't run `summer install` or `summer login` in the background.** They print user-facing output (engine download progress, browser-opening notice). Run them in the foreground so the user sees what's happening.
 - **Don't skip the `--json` flag on `summer doctor`** — text output is fragile to parse and changes per version.
 - **Don't skip the `-y` flag on `npx`** — without it, npx prompts "ok to install summer-engine?" interactively and the call hangs in a non-interactive shell.
+- **Don't drop `@latest` from the npx commands.** `npx -y summer-engine` (no version pin) serves whatever's in npx's local cache, which can be a stale older version. The `@latest` tag forces npm to re-resolve from the registry. If a user reports "unknown command 'doctor'" or sees a much smaller skill list than expected, they got cache-served — tell them to run `npx clear-npx-cache` then retry with `@latest`.
 - **Don't call MCP tools (`summer_get_scene_tree`, etc.) until `local-api` is `ok`.** The engine takes a few seconds to boot after `summer run`. Use Step 5b's wait-loop.
 - **Don't `summer create` without `cd`'ing to a stable parent directory first.** It writes into CWD; agents that start in a temp dir will leave the project there.
 - **Don't loop `summer login` if it times out at 120s.** Re-run it once and tell the user to be quicker; loop forever and the user is stuck.
 - **Don't jump straight into `summer create` from a vague prompt.** Invoke `summer:brainstorm-game` first (Step 6). The build skills assume `.summer/GameSoul.md` exists.
 
-**Using a different agent?** Replace `claude-code` with `codex`, `cursor`, or `windsurf` in Step 1. Skill targets vary per agent (Cursor uses `.cursor/rules/`, Windsurf uses `.windsurfrules`, etc.). The CLI handles the difference. For Gemini, OpenCode, Factory Droid, and Copilot CLI, see [`docs/`](docs/) — those agents have their own install paths that the CLI doesn't fully automate yet.
+**Using a different agent?** Replace `claude-code` with any supported agent in Step 1: `codex`, `cursor`, `windsurf`, `cline`, `roo-code`, `gemini`, `github-copilot`, `vscode-copilot`, or `opencode`. Skill targets vary per agent (Cursor uses `.cursor/rules/`, Windsurf uses `.windsurfrules`, Cline + Roo use `.clinerules/`, Copilot uses `~/.copilot/skills` or `.github/skills`, OpenCode uses agent definitions, etc.). The CLI handles the difference. After install, **Cline and Roo Code users should restart VS Code** so the extension reloads its MCP config. **Gemini users** may need to run `gemini extensions enable summer-engine` after the first install. **VS Code Copilot users** should start the `summer-engine` MCP server from Agent mode if VS Code does not autostart it. **Factory Droid** still has its own plugin path below.
 
-**Power-user note:** if the user specifically wants `summer` on their `PATH` for everyday terminal use (outside the AI agent), they can run `npm install -g summer-engine` themselves later. The agent flow doesn't need it.
+**Power-user note:** if the user specifically wants `summer` on their `PATH` for everyday terminal use outside the AI agent, a global npm install is still possible. The agent flow doesn't need it.
 
 ---
 
@@ -183,7 +195,7 @@ If you specifically prefer the official Claude Code plugin marketplace UI, you c
 /plugin install summer@summer-engine
 ```
 
-This is functionally equivalent to `summer setup claude-code --yes` for the skill install. You'll still need `summer install` and `summer login` to get the engine running. The agent-driven path above is faster and idempotent; this exists for users who want everything in the plugin TUI.
+This is functionally equivalent to `npx -y summer-engine@latest setup claude-code --yes` for the skill install. You'll still need `npx -y summer-engine@latest install` and `npx -y summer-engine@latest login` to get the engine running. The agent-driven path above is faster and idempotent; this exists for users who want everything in the plugin TUI.
 
 ---
 
@@ -191,9 +203,9 @@ This is functionally equivalent to `summer setup claude-code --yes` for the skil
 
 You installed one product. It has three parts. You don't have to think about them — Summer wires them up — but here's what each does:
 
-- **Summer Engine** — the game engine app. Where you see, play, and debug your game. Installed by `summer install`. Proprietary, free to use.
-- **Summer plugin** — what Claude Code (or your agent) uses to know what game-dev skills to apply and which tools to call. Installed via `/plugin install`. MIT, open source.
-- **Summer CLI** — the terminal command (`summer ...`) that installs the engine, scaffolds projects, runs them, signs you in. Installed via `npm install -g summer-engine`. MIT, open source.
+- **Summer Engine** — the game engine app. Where you see, play, and debug your game. Installed by the agent via `npx -y summer-engine@latest install`. Proprietary, free to use.
+- **Summer plugin** — what Claude Code (or your agent) uses to know what game-dev skills to apply and which tools to call. Installed by `summer setup` or the marketplace path. MIT, open source.
+- **Summer CLI** — the terminal command layer that installs the engine, scaffolds projects, runs them, signs you in, and starts MCP. Usually invoked through `npx -y summer-engine@latest ...`, so no global install is needed. MIT, open source.
 
 The plugin gives the agent the skills. The CLI gives it hands to install and launch the engine. The engine is where the game actually lives.
 
@@ -205,9 +217,9 @@ We tell you before we touch your disk.
 
 | What | Size | When | Source |
 |---|---|---|---|
-| `summer-engine` npm package (CLI + plugin source) | ~3 MB | `npm install -g summer-engine` | [npmjs.com/package/summer-engine](https://www.npmjs.com/package/summer-engine) |
-| Summer Engine app | ~1 GB (engine + bundled Git/runtime tools) | `summer install` | Summer's signed releases |
-| Auth token | ~1 KB | `summer login` | Browser → `~/.summer/auth-token` |
+| `summer-engine` npm package (CLI + plugin source) | ~3 MB | first `npx -y summer-engine@latest ...` call | [npmjs.com/package/summer-engine](https://www.npmjs.com/package/summer-engine) |
+| Summer Engine app | ~1 GB (engine + bundled Git/runtime tools) | `npx -y summer-engine@latest install` | Summer's signed releases |
+| Auth token | ~1 KB | `npx -y summer-engine@latest login` | Browser → `~/.summer/auth-token` |
 | Skill files | < 50 KB | bundled in the npm package | no extra network call |
 | Generated assets (3D / image / audio / video) | varies | only on explicit `summer_generate_*` calls | Summer Engine Studio |
 | URL imports | varies | only on explicit `summer_import_from_url` calls | the URL you provide |
@@ -298,7 +310,7 @@ Twenty-four skills replace "agent flailing through tutorials" with measurable cr
 
 C# is supported by the engine. A `summer:csharp-patterns` skill is on the roadmap; for now write C# from Godot 4.5 docs.
 
-Full catalog with HAVE / NEXT / LATER status: [`skills/catalog.yaml`](./skills/catalog.yaml).
+Full list of shipping skills: the `skills:` array in [`.claude-plugin/plugin.json`](./.claude-plugin/plugin.json).
 
 ## Philosophy
 
@@ -352,49 +364,59 @@ droid plugin marketplace add https://github.com/SummerEngine/summer
 droid plugin install summer@summer-engine
 ```
 
+### Cline (VS Code)
+
+```bash
+npx -y summer-engine@latest setup cline --yes
+```
+
+Writes the MCP server config to VS Code's globalStorage for the Cline extension and drops project rules into `.clinerules/`. **Restart VS Code** so Cline reloads its MCP config.
+
+### Roo Code (VS Code)
+
+```bash
+npx -y summer-engine@latest setup roo-code --yes
+```
+
+Same shape as Cline (Roo Code is a Cline fork) — writes globalStorage MCP config and `.clinerules/` files. **Restart VS Code** afterward.
+
 ### Gemini CLI
 
 ```bash
-gemini extensions install https://github.com/SummerEngine/summer
+npx -y summer-engine@latest setup gemini --yes
 ```
 
-Update later: `gemini extensions update summer`.
+Drops a Summer extension manifest at `~/.gemini/extensions/summer-engine/`. If the extension isn't auto-enabled on next launch, run `gemini extensions enable summer-engine`. The marketplace path (`gemini extensions install https://github.com/SummerEngine/summer`) still works for users who prefer it — both end up at the same place.
 
 ### GitHub Copilot CLI
 
 ```bash
-copilot plugin marketplace add SummerEngine/summer
-copilot plugin install summer@summer-engine
+npx -y summer-engine@latest setup github-copilot --yes
 ```
 
-### OpenCode
+Writes MCP config to `~/.copilot/mcp-config.json` and skills to `~/.copilot/skills/`. In an active Copilot CLI session, run `/mcp reload` and `/skills reload`; otherwise restart Copilot CLI.
+
+### GitHub Copilot in VS Code
 
 ```bash
-npm install --save-dev summer-engine
+npx -y summer-engine@latest setup vscode-copilot --yes
 ```
 
-Add to `opencode.json`:
+Writes MCP config to VS Code's user `mcp.json` and skills to `~/.copilot/skills/`. Restart VS Code or run **MCP: List Servers**, then use Copilot Agent mode.
 
-```json
-{
-  "plugin": ["summer-engine"],
-  "mcp": {
-    "summer-engine": {
-      "command": "npx",
-      "args": ["summer-engine", "mcp"]
-    }
-  }
-}
+### OpenCode
+
+```bash
+npx -y summer-engine@latest setup opencode --yes
 ```
 
-Restart. Full guide: [`.opencode/INSTALL.md`](./.opencode/INSTALL.md).
+Writes the MCP server entry into `opencode.json` (`~/.config/opencode/opencode.json` for user scope, `./opencode.json` for project) using the array-shaped `command: ["npx", "-y", "summer-engine@latest", "mcp"]` format. Restart OpenCode. Full guide: [`.opencode/INSTALL.md`](./.opencode/INSTALL.md).
 
 ### Windsurf and others
 
 ```bash
-npm install -g summer-engine
-summer setup <agent> --yes
-summer doctor
+npx -y summer-engine@latest setup <agent> --yes --force
+npx -y summer-engine@latest doctor
 ```
 
 ---
@@ -407,7 +429,9 @@ summer doctor
 | `summer login` | Browser-based sign-in. |
 | `summer logout` | Clear auth tokens. |
 | `summer status` | Engine state, port, auth. |
-| `summer doctor` | Diagnose Node, login, engine, MCP. |
+| `summer doctor` | Diagnose Node, login, engine, project memory, MCP. |
+| `summer memory` | Inspect project memory in `.summer`. |
+| `summer memory show <file>` | Print a project memory Markdown file. |
 | `summer run [path]` | Launch the engine. |
 | `summer open <path>` | Open a project in a running engine. |
 | `summer create <template> [name]` | Scaffold a project. |
@@ -419,7 +443,7 @@ summer doctor
 | `summer mcp setup <agent>` | Write MCP config for an agent. |
 | `summer setup <agent> [--yes]` | One shot: MCP config + recommended skills + doctor. |
 
-Agents: `claude-code`, `codex`, `cursor`, `gemini`, `opencode`, `windsurf`. Scopes: `--scope user` (default), `--scope project`.
+Agents: `claude-code`, `codex`, `cursor`, `windsurf`, `cline`, `roo-code`, `gemini`, `opencode`. Scopes: `--scope user` (default), `--scope project`.
 
 ---
 
@@ -449,7 +473,7 @@ More coming.
 Skills evolve fast. Two ways to help:
 
 1. **Open an issue** if a skill misfires. Quote the prompt and the response.
-2. **Submit a SKILL.md** for one of the `NEXT` entries in [`skills/catalog.yaml`](./skills/catalog.yaml). Run `summer:skill-test` against it before opening the PR.
+2. **Submit a new SKILL.md** under `skills/<category>/<name>/`. Register it in `.claude-plugin/plugin.json` and `src/lib/skills-registry.ts`. Run `summer:skill-test` against it before opening the PR.
 
 [`docs/DEVELOPMENT.md`](./docs/DEVELOPMENT.md) is the contributor guide.
 

package/_persona/summer/SKILL.md

@@ -50,7 +50,7 @@ When the user invokes `/summer`, you:
 | "/summer let me play it" | `summer:scene-and-project/play` |
 | "/summer I'm stuck" or "/summer what should I work on" | `summer:scene-and-project/brainstorm-game` (back to the playable cut) |
 
-If nothing on the table fits, fall back to `summer:_meta/using-summer` and read the catalog (`skills/catalog.yaml`) to find the closest skill. Never invent a skill name; verify in the `Skill` tool's index first.
+If nothing on the table fits, fall back to `summer:using-summer` and walk the `Skill` tool's index to find the closest skill. Never invent a skill name; verify in the index first.
 
 ## Tone rules
 
@@ -64,7 +64,7 @@ If nothing on the table fits, fall back to `summer:_meta/using-summer` and read
 ## What to avoid
 
 - Don't pretend to be a different model. You're the same model with a sharper voice.
-- Don't invent Summer skills that don't exist. Check the `Skill` index and `skills/catalog.yaml` first.
+- Don't invent Summer skills that don't exist. Check the `Skill` tool's index first.
 - Don't generate without confirming cost. Ever.
 - Don't ship a 30-second response when the user wants the build started. Invoke the right skill and start producing artifacts.
 - Don't redirect users to external docs. Solve the problem in-conversation.
@@ -107,7 +107,6 @@ If `.summer/GameSoul.md` exists, read it before any creative work. It's the sour
 
 ## See also
 
-- `summer:_meta/using-summer` — base context for the Summer skill family (auto-loaded; this persona builds on top).
-- `summer:scene-and-project/brainstorm-game` — when starting from scratch or stuck.
-- `summer:scene-and-project/play` — push the build into the player's hands.
-- `skills/catalog.yaml` — full skill index when the routing table doesn't cover the request.
+- `summer:using-summer` — base context for the Summer skill family (auto-loaded; this persona builds on top).
+- `summer:brainstorm-game` — when starting from scratch or stuck.
+- `summer:play` — push the build into the player's hands.