夏日引擎代理

AGENTS READING THIS: install playbook

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.

Step 1: Install user-level skills (idempotent, fast)

npx -y summer-engine@latest setup claude-code --yes --force

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 the current Summer skill bundle 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.

Do NOT run /plugin install or any slash command. The CLI path is the canonical install. The marketplace path is an alternative for users who specifically prefer the official plugin TUI; we don't route agents there.

Step 2: Install the engine app (only if `engine-install` needs attention)

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.

Linux note: the engine app currently supports macOS and Windows only. On Linux, summer install exits with a "Linux support coming soon" message. Surface the manual download URL to the user (https://summerengine.com/download) and stop. The rest of the playbook still works once they've installed manually.

Step 6: Brainstorm the game, then build

Now you have skills + MCP. Don't jump into summer create content from a vague prompt. Call summer_start_game_task with the user's goal, then invoke the recommended skill. For vague "make a game" requests, that should usually be summer:brainstorm-game. 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.

Install: full instructions per harness

Step 5b: Wait for the engine to be reachable (only if `summer run` printed "API not responding yet")

If the engine takes longer than 20s to boot (cold start, slow disk, etc.), summer run returns successfully but the local API isn't up yet. MCP tools may not connect until the local API is ready. Wait for it:

```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@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@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.

CLI reference

Agents: claude-code, codex, cursor, windsurf, cline, roo-code, gemini, opencode. Scopes: --scope user (default), --scope project.

---

The basic workflow

1. using-summer loads on session start. Sets workflow priority and the red-flag list.
2. brainstorm-game scopes a new project. One question, one page, one direction.
3. scene-composition picks the right hierarchy before any node lands.
4. fps-controller / design-mechanic / design-level / setup-multiplayer / vfx produce the artifact.
5. gdscript-patterns guides every .gd write.
6. play runs the game and reports clean or broken.
7. debug runs the cheapest diagnostic, forms one specific hypothesis, asks before editing, re-verifies after the fix.
8. export-and-ship runs the pre-flight checklist before producing a release build.

The skill bundle replaces "agent flailing through tutorials" with measurable craft.

---

Get started: alternative manual install via plugin marketplace

If you specifically prefer the official Claude Code plugin marketplace UI, you can install via:

/plugin marketplace add SummerEngine/summer-engine-agent
/plugin install summer@summer-engine

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.

---

Cline (VS Code)

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)

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.

GitHub Copilot in VS Code

npx -y summer-engine@latest setup vscode-copilot --yes

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.