summer-engine 4.5.0 → 4.6.0

package/dist/mcp/ops-surface.d.ts

@@ -23,6 +23,13 @@ import type { HostedLocalHook } from "./hosted-mount.js";
  */
 export declare const SUMMER_SEARCH = "summer_search";
 export declare const SUMMER_CALL = "summer_call";
+/**
+ * The first-game look rule. It opens the engine instructions because clients
+ * keep only the start of long server instructions (Codex: the first 512
+ * characters), and a project's first frame decides whether the person keeps
+ * going. The same rule is in the AGENTS.md block (project-memory/agent-instructions.ts).
+ */
+export declare const FIRST_GAME_LOOK_RULE: string;
 export declare const OPS_MCP_INSTRUCTIONS: string;
 /** The assets profile's version: no engine tools, so it names none. */
 export declare const OPS_MCP_ASSETS_INSTRUCTIONS: string;

package/dist/mcp/ops-surface.js

@@ -29,7 +29,18 @@ import { FOOTER_SUFFIX } from "../core/library-read.js";
  */
 export const SUMMER_SEARCH = "summer_search";
 export const SUMMER_CALL = "summer_call";
-export const OPS_MCP_INSTRUCTIONS = "Summer Engine MCP, operation catalog. Call summer_get_project_context first when Summer Engine is open. " +
+/**
+ * The first-game look rule. It opens the engine instructions because clients
+ * keep only the start of long server instructions (Codex: the first 512
+ * characters), and a project's first frame decides whether the person keeps
+ * going. The same rule is in the AGENTS.md block (project-memory/agent-instructions.ts).
+ */
+export const FIRST_GAME_LOOK_RULE = "First game in a new project: make it look finished, even if they asked for a quick prototype, because the first frame decides if they keep going. " +
+    "Keep their features and raise the look: sky and sun with shadows, fog, a texture on every surface, real models for player, characters and props (starter project and summer_assets_search first, never capsules or boxes as final art), one palette, a styled UI font. " +
+    "Before you say it is ready, play it and check a screenshot of the running game.";
+export const OPS_MCP_INSTRUCTIONS = "Summer Engine MCP. " +
+    FIRST_GAME_LOOK_RULE +
+    " Write GDScript files directly; create scenes and import assets through Summer while the project is open. summer_get_project_context tells you which project you are connected to. " +
     "Listed tools are the common jobs; for anything else, summer_search describes the job in words and returns the operation and its exact input, then summer_call runs it. " +
     "More than 3 scene edits: one summer_run_script with scenePath. Each engine tool's full guide: summer_docs_read. Long work answers with a job: jobs.wait. " +
     "Going live: skill/release-checklist, then store.go_live with the person's yes; a game is live once Summer's automated checks pass, so never tell anyone to wait for a review. Prices and other live changes may answer needs_approval with a link: give it to the person. " +

package/dist/project-memory/agent-instructions.js

@@ -36,10 +36,18 @@ export function renderAgentsBlock(commands = projectCommands()) {
         "",
         "This is a game made with Summer Engine, the game engine built for AI. Game code is GDScript (`.gd`), scenes are `.tscn`, resources are `.tres`, and `project.godot` is the project file.",
         "",
+        "## First game: make it look finished",
+        "",
+        "People judge Summer by the first frame of their first game, so make it look finished even when they ask for a quick prototype. Keep the features they asked for and raise the look:",
+        "- sky and sun with shadows, tonemapping, a little fog;",
+        "- a texture on every surface, and real models for the player, characters and main props (the starter project and the Summer asset library first), never capsules or boxes as final art;",
+        "- one colour palette and a styled UI font.",
+        "Before you say it is ready, play it and look at a screenshot of the running game, not the editor: the editor shows a preview sky and sun that the game does not have.",
+        "",
         "## How to work on it",
         "",
-        "- Change scenes through Summer while Summer Engine has the project open. The editor rewrites `.tscn` files when it saves, so hand edits get lost.",
-        "- With Summer's MCP server, call the `summer_*` tools and start with `summer_get_project_context`. Without it, run the same operations as `summer` commands in the shell (the `summer-cli` skill). If `summer` is missing or older than 4.0, use `npx -y summer-engine@latest` in its place.",
+        "- Write GDScript (`.gd`) files directly. Create and change scenes and import assets through Summer while Summer Engine has the project open: it imports new files, and the editor rewrites `.tscn` files when it saves, so hand edits to an open scene get lost.",
+        "- With Summer's MCP server, use the `summer_*` tools; `summer_get_project_context` tells you which project you are connected to. Without it, run the same operations as `summer` commands in the shell (the `summer-cli` skill). If `summer` is missing or older than 4.0, use `npx -y summer-engine@latest` in its place.",
         "- Summer's skills teach each part of a game. `npx -y summer-engine@latest setup <agent> --yes` installs them for your agent (add `--cli` for no MCP server). Start with `using-summer`, and find the right one with `summer docs search --query \"<the task>\"`.",
         "- `.summer/` is the project's memory: `GameSoul.md` says what the game is, `memory/` holds the decisions to keep. Read them before you change the game's look, sound or story.",
         "- Check your own work: script errors, a screenshot, a play run. Ask the person to play only for feel and fun.",
@@ -50,7 +58,7 @@ export function renderAgentsBlock(commands = projectCommands()) {
         "",
         "## Publishing",
         "",
-        "The `publish-your-game` skill has the steps; `summer ops search \"publish my game\"` finds each operation. `summer store publish` sends the game to Summer's store review, and the game's owner approves it: give them the link it prints. Nothing goes live until they approve.",
+        "The `publish-your-game` skill has the steps; `summer ops search \"publish my game\"` finds each operation. Going live needs the game owner's yes. A game goes live as soon as Summer's automated checks pass; Summer's staff review it after it is live, so never tell anyone to wait for a review.",
         SUMMER_BLOCK_END,
     ].join("\n");
 }

package/gemini-extension.json

@@ -1,7 +1,7 @@
 {
   "_generated": "GENERATED from integrations/gemini — do not edit; npm run generate:registry",
   "name": "summer",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it. The Summer Engine MCP server, context primer and game-dev skills.",
   "contextFileName": "GEMINI.md",
   "mcpServers": {

package/library/skills/make-game/SKILL.md

@@ -48,7 +48,7 @@ These rules from the playbooks apply to every genre:
 
 - **2D scales to the viewport.** Set `display/window/stretch/mode = canvas_items` and `stretch/aspect = expand`; UI uses Control anchors; code-positioned nodes compute from `get_viewport_rect().size`. Never hardcode 1920x1080.
 - **Playable slice, not tech demo.** Name the core loop in one sentence; every input gets feedback (tween, sound, particle, flash, shake); progression is visible; a restart exists. The bar is "feels good for 30 seconds".
-- **Fast first draft when someone is waiting.** The first playable version uses shapes, the palette and any template art, plus at most one or two generated assets the person specifically asked for; generation takes minutes, so it never blocks the first play. Say plainly that it is a first draft to get a feel for the game, that the art is not final, and ask if this is the direction they want. Generate the rest of the art in later passes.
+- **The first playable already looks good.** People judge Summer by the first frame of their first game, so the first version looks finished even when they ask for a quick prototype: keep the features they asked for and raise the look. Sky and sun with shadows, tonemapping and a little fog; a texture on every surface; real models for the player, characters and main props from the starter project or the Summer asset library (`summer_assets_search`), never capsules or boxes as final art; one colour palette; a styled UI font. Generation takes minutes, so it never blocks the first play: use starter and library art first, plus at most one or two generated assets the person asked for, and generate the rest in later passes. Before you say it is ready, play it and look at a screenshot of the running game, not the editor (the editor shows a preview sky and sun that the game does not have).
 - **A way back to the title.** From inside play, a pause menu or a **Leave** button returns to the title screen without quitting the app.
 - **Text the default font can show.** No emoji or symbols (▲ ◀ ★ ♥ ✓) in UI text: they render as boxes with hex codes. Use words or icons; see `ui-basics`.
 
@@ -201,7 +201,7 @@ Repeat until every mechanic in the plan is implemented OR the user calls cut.
 
 ## Phase 5: Layer (look + sound)
 
-**Goal**: the game stops looking like a programmer art prototype.
+**Goal**: deepen the look and add sound. The first playable already looks good (see "The first playable already looks good" above); this phase writes the art bible, replaces the remaining stand-in art and adds audio.
 
 ```
 Skill: art-direction
@@ -276,7 +276,7 @@ If the brief said "jam" or "prototype", skip this phase. If the brief said "game
 |---|---|
 | Skip the brainstorm because the user said "FPS" | Even with the genre named, you need the scope cut list. Otherwise mechanic 4 quietly sneaks in and the game never ships. |
 | Let mechanic 2 start before mechanic 1 is verified clean | Compounding bugs. You'll spend the rest of the session debugging which mechanic broke what. |
-| Stack art direction on top of unfinished mechanics | Art changes are reversible only if the underlying scene structure is stable. Get mechanics done first. |
+| Change the art style while mechanics are unfinished | Art changes are reversible only if the underlying scene structure is stable. Get mechanics done before a new style; the first playable still starts good-looking. |
 | Treat "polish" as required | If the brief says "jam in 2 days", polish is a cut item. Respect the brief. |
 | Run all phases without confirming | The user owns scope. Stop at every checkpoint. |
 | Ship online play behind a setting nobody changes | Hosted join is never exercised, so it breaks without anyone noticing. Reachable by default, or the owner joins online before every release. |
@@ -313,7 +313,7 @@ No Summer MCP tools in this session? Run each one as a command; when `summer --v
 
 | In this skill | Command |
 |---|---|
-| `assets.search` | `summer assets search` |
+| `assets.search`, `summer_assets_search` | `summer assets search` |
 | `summer_docs_read` | `summer docs read` |
 | `summer_add_node` | `summer engine add-node` |
 | `summer_batch` | `summer engine batch` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "summer-engine",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "description": "MCP server, CLI and skills for Summer Engine, the game engine built for AI. Connect Claude Code, Cursor, Codex and other agents to build, test and publish full games to summer.games.",
   "mcpName": "io.github.SummerEngine/summer",
   "keywords": [

package/registry/generated/gemini-extension.json

@@ -1,7 +1,7 @@
 {
   "_generated": "GENERATED from integrations/gemini — do not edit; npm run generate:registry",
   "name": "summer",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it. The Summer Engine MCP server, context primer and game-dev skills.",
   "contextFileName": "GEMINI.md",
   "mcpServers": {

package/registry/generated/index.json

@@ -2284,7 +2284,7 @@
       "id": "skill/make-game",
       "kind": "skill",
       "version": "1.2.0",
-      "content_hash": "79eab1d1c84cdf321347a1952daaf4c4dd18e239f470adf775fba5e0f18116df",
+      "content_hash": "b6078a16547b4d8e14ccc75125b1f3be70543e30f3fb6bc2ab508f5ddae8e069",
       "summary": "Orchestrate 'make me a game': brainstorm, plan, scaffold, mechanics, art, audio, polish, verify, ship.",
       "use_when": [
         "the user says 'make me a game', 'build me a game', 'I want to make a [genre] game', or 'let's build something' — running the full game-dev pipeline",

package/registry/generated/marketplace.claude.json

@@ -10,7 +10,7 @@
     {
       "name": "summer",
       "source": "./",
-      "version": "4.5.0",
+      "version": "4.6.0",
       "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it. A first-run guide (/summer:start), game-dev skills, and two MCP servers: the bridge to the Summer Engine desktop app, and Summer's hosted cloud server for people without it.",
       "author": {
         "name": "Summer Engine",

package/registry/generated/plugin.claude-directory.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "summer",
   "displayName": "Summer Engine",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it. A first-run guide (/summer:start), game-dev skills, and two MCP servers: the bridge to the Summer Engine desktop app, and Summer's hosted cloud server for people without it.",
   "author": {
     "name": "Summer Engine",
@@ -158,7 +158,7 @@
       "command": "npx",
       "args": [
         "-y",
-        "summer-engine@4.5.0",
+        "summer-engine@4.6.0",
         "mcp"
       ]
     },

package/registry/generated/plugin.claude.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "summer",
   "displayName": "Summer Engine",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it. A first-run guide (/summer:start), game-dev skills, and two MCP servers: the bridge to the Summer Engine desktop app, and Summer's hosted cloud server for people without it.",
   "author": {
     "name": "Summer Engine",

package/registry/generated/plugin.codex.json

@@ -1,7 +1,7 @@
 {
   "_generated": "GENERATED from integrations/codex — do not edit; npm run generate:registry",
   "name": "summer",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it. Game-dev skills, lifecycle hooks, and a 125-tool MCP bridge to the Summer Engine desktop app.",
   "author": {
     "name": "Summer Engine",

package/registry/generated/plugin.cursor.json

@@ -3,7 +3,7 @@
   "_generated": "GENERATED from integrations/cursor — do not edit; npm run generate:registry",
   "name": "summer",
   "displayName": "Summer Engine",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it. Game-dev skills, lifecycle hooks, and a 125-tool MCP bridge to the Summer Engine desktop app.",
   "author": {
     "name": "Summer Engine",

package/registry/generated/plugin.factory.json

@@ -2,7 +2,7 @@
   "_generated": "GENERATED from integrations/factory — do not edit; npm run generate:registry",
   "name": "summer",
   "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it. Game-dev skills, lifecycle hooks, and a 125-tool MCP bridge to the Summer Engine desktop app.",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "author": {
     "name": "Summer Engine",
     "email": "founders@summerengine.com",

package/registry/generated/server.json

@@ -3,7 +3,7 @@
   "name": "io.github.SummerEngine/summer",
   "title": "Summer Engine",
   "description": "The game engine built for AI. Any agent makes a multiplayer game and publishes it.",
-  "version": "4.5.0",
+  "version": "4.6.0",
   "websiteUrl": "https://summerengine.com",
   "icons": [
     {
@@ -22,7 +22,7 @@
     {
       "registryType": "npm",
       "identifier": "summer-engine",
-      "version": "4.5.0",
+      "version": "4.6.0",
       "transport": {
         "type": "stdio"
       },