summer-engine 1.3.1 → 1.4.0

package/skills/rendering-and-lighting/art-direction/SKILL.md

@@ -0,0 +1,284 @@
+---
+name: art-direction
+description: Use when defining the visual style of the game — references, palette, mood, lighting plan, post-processing, do/don't list. Outputs an art bible at `.summer/art-bible.md`. Trigger on "art direction", "art bible", "visual style", "color palette", "what should it look like", "the look".
+license: MIT
+compatibility: [Cursor, Claude Code, Windsurf, Codex]
+category: rendering-and-lighting
+user-invocable: true
+allowed-tools: Read Grep Glob Write Edit summer_get_project_context summer_project_setting summer_inspect_node summer_set_prop
+paths: [".summer/**", "project.godot", "**/*.tscn"]
+---
+
+# /art-direction — Define the Visual Style
+
+## Overview
+
+A consistent art direction is what makes a low-budget game *look* like a finished game. Most solo devs lose this fight by mixing styles — a toon-shaded character on a photoreal terrain, a pixel UI over a smooth 3D world. This skill builds an art bible the rest of the project obeys: references, palette, mood, lighting plan, post-processing, and a do/don't list. It writes to `.summer/art-bible.md` — the file every rendering / shader / lighting / VFX skill reads later.
+
+**Core principle:** Constraint produces style. A game with **15 colors total** looks more intentional than a game with infinite-color textures. Pick the constraint, then defend it.
+
+## Steps
+
+### 1. Open with references
+
+Ask exactly this:
+
+> Two or three references — games, films, art books, anything visual. What's the vibe?
+
+Don't suggest. Listen. References are the single most reliable signal of what they actually want. If they say one game, ask for one more — single-reference art bibles converge into a clone of that game.
+
+If they freeze, offer 4 axes (not games):
+
+> Pick the one that feels right: a) painterly + warm + handcrafted (Sable, Tunic), b) crisp + saturated + toon (Hi-Fi Rush, Splatoon), c) dark + moody + grounded (Dishonored, Inside), d) lo-fi + nostalgic + crunchy (Dusk, Faith).
+
+### 2. Read the brief if it exists
+
+```
+Read .summer/GameSoul.md
+```
+
+Brief might say "horror" — that constrains palette and lighting. Brief might say "cozy" — that *forbids* harsh contrast. Quote it back:
+
+> Brief is "cozy farming sim". That rules out harsh shadows and saturated reds. Confirming.
+
+### 3. Pin the rendering technique
+
+This is the technique question, not the mood question. Force a choice:
+
+| Technique | When | Pro | Con |
+|---|---|---|---|
+| Toon / cel-shaded | Stylized 3D, expressive characters | Forgiving on textures, ages well | Can feel generic without strong palette |
+| PBR realistic | Grounded sim, horror, military | Lighting does the work | Asset cost is brutal solo |
+| Lo-fi PS1 | Nostalgia, horror, indie cred | Tiny assets, fast iteration | Niche audience appeal |
+| Flat / matte | Minimalist puzzle, casual | Cheapest to author | Limited mood range |
+| Painterly (textured-shaded) | Story-led, fantasy | Distinctive | Requires consistent texture authoring |
+| 2D pixel | Retro, platformer, RPG | Mature pipeline | Animation cost scales fast |
+| 2D hand-drawn | Narrative, indie | Distinctive, expressive | Animation cost extreme |
+
+Ask:
+
+> One technique. Which is it?
+
+If they pick more than one ("PBR characters in a toon world"), name the conflict and force a hierarchy:
+
+> Mixed techniques rarely cohere. If you mean "stylized PBR with toon outlines" — that's one technique (PBR + post-process outline). If you mean "toon characters in a PBR world" — that's two, and they'll fight. Pick one as primary.
+
+### 4. Build the palette
+
+A palette is **6-15 colors** total. Not a vibe, not "warm tones" — actual hex codes. Force it.
+
+Walk:
+
+```
+Primary background — what color does the screen mostly read as?
+Secondary background — second most common?
+Accent — what does the player's eye go to?
+Warning / damage — what reads as bad?
+Reward / pickup — what reads as good?
+UI base — text, frames
+UI emphasis — buttons, callouts
+Skin / character — if applicable
+```
+
+State candidates as hex. For a "cozy farming" game:
+
+```
+#3a4a3a   primary BG (deep moss green)
+#5e6f4f   secondary BG (sage)
+#e6c068   accent (golden wheat)
+#a83e3e   warning (warm red, not pure red)
+#c8a268   reward (warm tan)
+#1f1a16   UI base (warm near-black, NOT pure black)
+#f4ecdf   UI text (cream, NOT pure white)
+#e3b08a   skin warm
+#a8784f   skin cool
+```
+
+Pure white (#ffffff) and pure black (#000000) are almost always wrong — they break the palette. Flag it if the user pitches them.
+
+Ask:
+
+> Palette above. Adjust any, or lock it?
+
+### 5. Define the mood adjectives
+
+Three to five adjectives. Concrete, not vague.
+
+Bad: "cool, atmospheric, immersive."
+Good: "soft, hand-warmed, slightly melancholic, golden-hour."
+
+Ask:
+
+> Three to five adjectives that aren't 'cool' or 'atmospheric'. Pick from concrete sensory words.
+
+### 6. Write the lighting plan
+
+State the plan in one block. For Godot 4.5:
+
+```
+Sun: DirectionalLight3D, color #fff2d9, energy 0.9, angle ~30° (warm low-angle)
+Sky: ProceduralSkyMaterial, sky_top_color #6b88a3, sky_horizon_color #d8b88e
+Ambient: AmbientLight #4a5570, energy 0.15
+Indoor fills: OmniLight3D color #ffd9a8, energy 0.6, range 4m
+NEVER: pure-white DirectionalLight, no ambient, hard cube shadows
+```
+
+For 2D:
+
+```
+Base: CanvasModulate #f4ecdf, gentle warm wash
+Accent: PointLight2D for fireflies / lanterns, color from accent palette
+NEVER: full-bright modulation, no soft falloff
+```
+
+### 7. Define post-processing rules
+
+Godot 4.5 post stack: Glow, SDFGI, SSAO, SSR, Adjustments, Color Correction (LUT). State opinions, not options.
+
+```
+Glow: ON, threshold 0.9, intensity 0.5  (soft bloom on highlights only)
+SDFGI: OFF for vertical-slice scope (perf cost; bake light probes later)
+SSAO: ON, light_affect 0.3 (just enough for grounding)
+SSR: OFF unless we have wet/glass surfaces
+Color correction: Filmic tonemap, slight S-curve LUT toward warm
+Vignette (custom shader): ON, subtle, 0.15 strength
+Chromatic aberration: OFF (overused, looks cheap)
+Film grain: ON only if mood adjective is "lo-fi" or "vintage"
+```
+
+Make these calls. Don't enumerate options.
+
+### 8. Build the do / don't list
+
+This is the contract. Five do's, five don'ts. Specific, enforceable.
+
+```markdown
+## DO
+- All colors come from the palette. New asset? Pick the closest existing color, don't invent.
+- Outline shader on character + interactable props (no outline on environment).
+- Soft shadows (DirectionalLight3D shadow_blur 1.5).
+- Warm key + cool fill — never both warm or both cool.
+- Texture filter: Linear with mipmaps OFF for crunchy near-pixel feel.
+
+## DON'T
+- No pure white (#ffffff). Use #f4ecdf.
+- No pure black (#000000). Use #1f1a16.
+- No realistic photo-textures. All textures must read as "painted" at 1m distance.
+- No procedural sky shaders mid-day with full sun — too generic. Always angle the sun.
+- No chromatic aberration / lens flare / motion blur — they're cheap and date-fast.
+```
+
+### 9. Apply Godot project-level settings
+
+Some art-direction calls translate to `project.godot` settings. Apply them.
+
+**Preferred (Summer MCP):**
+
+```
+summer_project_setting(key="rendering/textures/canvas_textures/default_texture_filter", value="2")  # Linear no mipmaps if pixel-art-ish
+summer_project_setting(key="rendering/environment/defaults/default_clear_color", value="Color(0.227, 0.290, 0.227)")  # palette primary
+summer_project_setting(key="rendering/anti_aliasing/quality/msaa_3d", value="2")  # MSAA 2x for clean edges
+```
+
+If a `WorldEnvironment` node is in the main scene, set its environment defaults to match the lighting plan:
+
+```
+summer_inspect_node(path="./World/WorldEnvironment")
+summer_set_prop(path="./World/WorldEnvironment/...", key="...", value="...")
+```
+
+Ask before each:
+
+> May I update `project.godot`'s default clear color to the palette primary, and enable MSAA 2x?
+
+**Fallback (no MCP):** print the `project.godot` snippet for the user to paste.
+
+### 10. Save the art bible
+
+Always write the bible. Path: `.summer/art-bible.md`.
+
+```markdown
+# Art Bible — <Game Name>
+
+**References:** <2-3 specific games / films>
+**Technique:** <one of the 7 above>
+**Mood:** <3-5 concrete adjectives>
+
+## Palette
+| Hex | Role |
+|---|---|
+| #3a4a3a | Primary BG |
+| #5e6f4f | Secondary BG |
+| ... | ... |
+
+## Lighting plan
+- Sun: DirectionalLight3D, color #fff2d9, energy 0.9
+- Sky: ProceduralSkyMaterial top #6b88a3, horizon #d8b88e
+- Ambient: #4a5570 energy 0.15
+- Indoor fills: OmniLight3D color #ffd9a8 range 4m
+- NEVER: pure-white sun, no ambient
+
+## Post-processing
+- Glow: ON, threshold 0.9
+- SDFGI: OFF (vertical-slice scope)
+- SSAO: ON, 0.3
+- SSR: OFF
+- Tonemap: Filmic
+- Vignette: subtle 0.15
+- Chromatic aberration: OFF
+
+## DO
+- ...
+
+## DON'T
+- ...
+```
+
+Ask:
+
+> May I create `.summer/art-bible.md` with this bible?
+
+### 11. Route to the next step
+
+End with:
+
+> Bible saved. Next:
+> - `/summer:audio-direction` to define the sonic identity that pairs with this look.
+> - `/summer:vfx` to design particle / hit-feedback styles within the palette.
+> - Open the project's `WorldEnvironment` node and dial in the lighting plan.
+> - Or generate first-pass concept assets via `summer_generate_image` using the palette + mood as the prompt prefix.
+
+## Common mistakes
+
+| Mistake | Fix |
+|---|---|
+| Vague palette ("warm tones") | Hex codes only. 6-15 of them. Locked. |
+| Pure white / pure black | Off-white (#f4ecdf) and off-black (#1f1a16). Pure values blow out the palette. |
+| Single reference | At least two references. Single = clone. |
+| Mixing techniques | Toon characters in a PBR world fight. Pick one technique, stick to it. |
+| No "DON'T" list | The DON'T list is the actual contract. The DO is aspirational. |
+| Chromatic aberration / motion blur | Cheap, overused, date-fast. Off by default. |
+| Procedural skybox without angle | Mid-day sun + uniform fog reads generic. Always angle the sun. |
+| Skipping the lighting plan | Lighting *is* art direction in 3D. Without a plan, every level looks different. |
+| Adopting "AAA realism" at vertical-slice scope | Asset cost is brutal solo. Stylized always wins. |
+| Calling SetResourceProperty on inline sub_resources | Silent fail. See `_shared/mcp-tools-reference.md` § Trap. |
+
+## Collaborative protocol
+
+This skill writes one design doc (`.summer/art-bible.md`) and may modify `project.godot` settings + the main scene's `WorldEnvironment`. Always ask. See `_shared/collaborative-protocol.md`.
+
+## Want a working starter?
+
+No template — this is a workflow that produces the bible the rest of the project obeys. After the bible exists, every `summer:` rendering / lighting / shader / VFX skill reads it.
+
+## See also
+
+- `_shared/collaborative-protocol.md`
+- `_shared/godot-version.md` — Godot 4.5 rendering API notes (Compositor moved in 4.4 / 4.5)
+- `_shared/mcp-tools-reference.md`
+- `scene-and-project/brainstorm-game/SKILL.md` — produces the brief that anchors the bible
+- `audio/audio-direction/SKILL.md` — the sonic counterpart
+- `rendering-and-lighting/3d-lighting/SKILL.md` — implements the lighting plan
+- `shaders/shader-basics/SKILL.md` — for outline / toon shaders
+- `post-processing/bloom-and-glow/SKILL.md` — implements the glow rule
+- `post-processing/color-grading/SKILL.md` — implements the LUT and tonemap call

package/skills/scene-and-project/brainstorm-game/SKILL.md

@@ -0,0 +1,210 @@
+---
+name: brainstorm-game
+description: Use when the user wants help deciding what game to make, scoping a new project, or turning a vague idea into a buildable plan. Walks through genre, scope, core loop, mechanics, and art direction, then writes a 1-page brief to `.summer/GameSoul.md`. Trigger on "brainstorm a game", "what should I make", "I want to make a game", "help me scope", "new game idea".
+license: MIT
+compatibility: [Cursor, Claude Code, Windsurf, Codex]
+category: scene-and-project
+user-invocable: true
+allowed-tools: Read Grep Glob Write Edit summer_get_project_context summer_get_scene_tree
+paths: [".summer/**", "project.godot", "**/*.md"]
+---
+
+# /brainstorm-game — Decide What Game to Build
+
+## Overview
+
+Most game projects fail because they were never scoped. This skill turns "I want to make a game" into a 1-page brief that names the pitch, the core loop, three mechanics max, the art direction, and the scope (jam / vertical slice / full game). The brief lands at `.summer/GameSoul.md` — the file Summer's onboarding pipeline and every future `summer:` skill reads on first turn.
+
+**Core principle:** Constrain ruthlessly. A buildable bad idea beats an un-buildable great idea. Three mechanics, one art direction, one scope. Anything else gets parked in a "Later" list.
+
+## Steps
+
+### 1. Open with the one question
+
+Ask exactly this and wait:
+
+> One sentence — what kind of game do you want to make?
+
+Don't pre-pitch genres. Don't list options. Read what they say. The first sentence is signal.
+
+If they freeze ("I don't know"), offer 4 reference points only:
+
+> No worries. Pick the one that pulls you most: a) something cozy and exploratory (Stardew, A Short Hike), b) something tight and skill-based (Celeste, Hades), c) something story-led (Disco Elysium, Citizen Sleeper), d) something silly and short (Goat Sim, Untitled Goose). Or describe a different vibe.
+
+### 2. Branch on genre signal
+
+Read their answer for a genre anchor and pick **one** branch. Don't ask multiple questions in parallel.
+
+| Anchor word(s) | Branch |
+|---|---|
+| "shooter", "FPS", "TPS", "combat" | Action-Combat branch |
+| "platformer", "metroidvania", "souls-like" | Skill-Platforming branch |
+| "RPG", "story", "narrative", "dialogue" | Narrative branch |
+| "roguelike", "deckbuilder", "auto-battler" | Run-Based branch |
+| "sim", "cozy", "farming", "city-builder" | Sim branch |
+| "puzzle", "physics", "sandbox" | Puzzle branch |
+| "horror", "atmospheric" | Horror branch |
+| "multiplayer", "PvP", "co-op" | Multiplayer branch (forces the multiplayer-or-not call before scope) |
+
+If unclear, ask the smallest disambiguating question:
+
+> Tighter on this — is it more "tense and dangerous" or "calm and exploratory"?
+
+### 3. Pin the core loop
+
+A core loop is what the player does for 30 seconds, repeated. State a candidate and ask them to refine. Examples per branch:
+
+| Branch | Candidate core loop |
+|---|---|
+| Action-Combat | "Enter room, read enemy patterns, kill, loot, advance." |
+| Skill-Platforming | "See obstacle, attempt, fail, learn, retry, clear, next." |
+| Narrative | "Walk to character, choose dialogue, see consequence, walk to next." |
+| Run-Based | "Pick a card/weapon/build, fight, die, unlock, repeat with edge." |
+| Sim | "Plan day, execute, harvest reward, plan next day." |
+| Puzzle | "See state, form theory, test, observe, solve or rethink." |
+| Horror | "Hear cue, locate threat, hide or flee, advance space." |
+
+State your candidate. Ask:
+
+> The 30-second loop I'm hearing: <candidate>. Does that match what you have in your head, or is the actual moment-to-moment different?
+
+### 4. Constrain to three mechanics maximum
+
+Force the trade. State the rule:
+
+> Three mechanics, no more. What are the three things this game has that other games in this genre don't?
+
+If they pitch five, push back. Not "we'll add it later" — actually cut. Two examples for them to react to:
+
+> Hades has three: dash-attack-cast, room reward choice, and run-end conversation. Everything else (mirror upgrades, weapon variants, bosses) is content built on those three. What are yours?
+
+Common new-dev mistake: listing features ("inventory, crafting, quests") instead of mechanics ("a single resource that's both currency and ammo"). Push them toward verbs and decisions, not nouns and systems.
+
+### 5. Pick an art direction in one phrase
+
+Not a paragraph. Examples to anchor:
+
+- "Lo-fi PS1 polygons + dithered shader"
+- "Hand-drawn 2D, single bold outline, 4-color palette"
+- "Toon-shaded Nintendo-bright, no realistic lighting"
+- "Pixel art, 16x16 tiles, GameBoy 4-shade green"
+
+Ask:
+
+> One phrase for the look. If a stranger asked your screenshot's style in 6 words, what do you say?
+
+Don't go deeper here — `/summer:art-direction` is where the bible gets built. This is one phrase to seed it.
+
+### 6. Pin the scope
+
+State the choices flat:
+
+> Scope. Pick one: (a) a 4-hour jam-sized prototype — one mechanic, one level, one art direction, ships in a weekend. (b) a vertical slice — 30-60 minutes of polished play that proves the core loop, ships in 2-4 weeks. (c) a full game — 4-20 hours of content, ships in 6+ months.
+
+If they flinch at (c), recommend (b). New devs almost always overestimate scope. Default recommendation if they're unsure: **vertical slice**.
+
+### 7. Sanity-check the combination
+
+Do this in your head, not out loud unless something fails:
+
+- Is the core loop achievable with the three mechanics + the chosen art direction in the chosen scope? If not, name what has to flex (usually scope down or merge two mechanics into one).
+- Is there a hidden multiplayer requirement? ("4-player" or "co-op" anywhere = stop, multiplayer is its own scope explosion.)
+- Is the art direction generatable / sourceable for a solo dev? (Photoreal 3D for a 4-week vertical slice is a red flag.)
+
+If you spot a problem, raise it once, plainly:
+
+> One concern: <X>. Suggest <flex Y>. OK or do you want to push through anyway?
+
+### 8. Draft the brief
+
+Compose the 1-page brief. Format:
+
+```markdown
+# <Game Name or "Untitled">
+
+**Pitch:** <One sentence the player would tell a friend.>
+
+**Core loop (30s):** <What the player does, repeated.>
+
+**Three mechanics:**
+1. <Verb-led: "Parry to convert damage into mana"  not "Combat system">
+2. <…>
+3. <…>
+
+**Art direction (one phrase):** <…>
+
+**Scope:** <Jam | Vertical slice | Full game>
+
+**Win condition:** <How the player knows they succeeded — ending? Score? Unlock?>
+
+**One thing this is NOT:** <Define by negation. Cuts scope creep later.>
+
+**Inspirations:** <2-4 specific games, films, or images.>
+
+**Parked for later:** <Things they pitched that didn't make the three.>
+```
+
+### 9. Ask permission and write
+
+**Preferred (Summer MCP + host file write):**
+
+> May I create `.summer/GameSoul.md` with this brief?
+
+On yes, use `Write` (host file tool) — `.summer/GameSoul.md` is plain markdown, no engine import needed:
+
+```
+Write .summer/GameSoul.md
+```
+
+If `.summer/GameSoul.md` already exists, read it first, show what would change, ask:
+
+> `.summer/GameSoul.md` already exists. May I overwrite it, or merge into a "Revision 2" section below the existing brief?
+
+**Fallback (no host write tool — agent is read-only):**
+
+Print the full brief to the user with the explicit instruction:
+
+> Save this as `.summer/GameSoul.md` in your project root. Every Summer skill reads it.
+
+### 10. Route to the next step
+
+End every successful brainstorm with a routing question:
+
+> Brief saved. Next step:
+> - `/summer:design-mechanic` — design the core loop in detail (recommended for vertical slice).
+> - `/summer:design-level` — sketch level 1 / the tutorial.
+> - `/summer:art-direction` — turn the one-phrase look into an art bible.
+> - Or pick up `/summer:make-game` to start scaffolding the project.
+
+Don't auto-pick. Let them decide.
+
+## Anti-patterns (don't do these)
+
+| Anti-pattern | Why it fails |
+|---|---|
+| Asking 6 questions in a row before any branching | User feels interviewed, not collaborated with. Branch after each answer. |
+| Letting them list 5+ mechanics | Three is the constraint. Without the constraint, the brief is useless. |
+| Skipping the "one thing this is NOT" line | This is the single best scope-protection in the brief. Future "let's add X" gets compared against it. |
+| Writing the brief without showing it first | They have to react to it. They'll catch their own bad fits when they read it back. |
+| Defaulting to "full game" scope | New devs overestimate. Default to vertical slice; let them upgrade if they push. |
+| Pitching a genre they didn't ask for | The first sentence they typed is signal. Don't override it. |
+| Including art direction details | One phrase. Bible-building is `/summer:art-direction`. |
+| Saving without asking | Always ask "May I create `.summer/GameSoul.md`?" — see collaborative-protocol. |
+
+## Collaborative protocol
+
+This skill writes one file (`.summer/GameSoul.md`). Always ask before writing. Always show the brief inline before saving so the user can react. See `_shared/collaborative-protocol.md`.
+
+## Want a working starter?
+
+No template — this is a workflow that produces the brief that drives template selection later. Once `.summer/GameSoul.md` exists, `/summer:make-game` can match it against `_shared/template-registry.md`.
+
+## See also
+
+- `_shared/collaborative-protocol.md` — "May I write?" pattern
+- `_shared/template-registry.md` — templates the brief will be matched against later
+- `gameplay-mechanics/design-mechanic/SKILL.md` — design the core loop in detail
+- `level-design/design-level/SKILL.md` — sketch level 1
+- `rendering-and-lighting/art-direction/SKILL.md` — turn the one-phrase look into a full bible
+- `audio/audio-direction/SKILL.md` — sonic identity
+- `scene-and-project/make-game/SKILL.md` — scaffold the project once the brief is locked

package/skills/scene-and-project/make-game/SKILL.md

@@ -440,3 +440,13 @@ After first playable, ask the user what to improve. Common next steps:
 | Debug | `summer_get_console` | Read output |
 | Debug | `summer_get_script_errors` | Check .gd compile |
 | Debug | `summer_clear_console` | Clear output |
+
+---
+
+## Collaborative protocol
+
+This skill orchestrates a full game build — many writes across scenes, scripts, and project settings. Always ask before each phase: "May I bootstrap the project (scenes, project.godot, folders)?", "May I generate the assets (image + 3D) for X, Y, Z?", "May I scaffold the player scene + attach `player.gd`?". Group related writes into one ask per phase, never bulk-write across phases. See `../../_shared/collaborative-protocol.md`.
+
+## Fallback
+
+No fallback for this — Summer MCP required. The whole point of `make-game` is the orchestration layer over `summer_*` tools. If MCP isn't connected, fall back to running the individual sub-skills (`fps-controller`, `3d-lighting`, etc.) which each document their own MCP-or-`.tscn` fallback paths.

package/skills/scene-and-project/scene-composition/SKILL.md

@@ -107,3 +107,11 @@ Use `./` for paths relative to the scene root:
 2. **Unnamed scene:** Saving without a path fails if the scene was never saved. Use `path` for new scenes.
 3. **Duplicate names:** Godot auto-renames (Node, Node2, etc.). Use descriptive unique names.
 4. **Mixing 2D and 3D:** Don't put Node2D under Node3D or vice versa in the same hierarchy.
+
+## Fallback
+
+No fallback for this — Summer MCP required. Handwriting `.tscn` files for hierarchy mutations is error-prone (UID collisions, wrong format version, broken sub_resource refs). If MCP isn't connected, open the scene in the Godot editor and use the SceneTree dock.
+
+## Collaborative protocol
+
+This skill creates and mutates scene files. Always ask before applying: "May I create `res://scenes/player.tscn` and instantiate it under `./World`?". See `../../_shared/collaborative-protocol.md`.

package/skills/ui-and-ux/ui-basics/SKILL.md

@@ -120,3 +120,31 @@ For UI that scales with window size:
 3. MarginContainer with percentage-based margins (may need theme or script)
 
 For simple cases, CenterContainer + fixed-size children works. For complex layouts, a Theme resource or script may be needed.
+
+## Fallback (no MCP — edit `.tscn` directly)
+
+If Summer MCP isn't connected, write the menu hierarchy by hand:
+
+```
+[node name="MainMenu" type="Control" parent="."]
+anchors_preset = 15
+
+[node name="Margin" type="MarginContainer" parent="MainMenu"]
+anchors_preset = 15
+theme_override_constants/margin_left = 50
+theme_override_constants/margin_right = 50
+theme_override_constants/margin_top = 50
+theme_override_constants/margin_bottom = 50
+
+[node name="VBox" type="VBoxContainer" parent="MainMenu/Margin"]
+
+[node name="Title" type="Label" parent="MainMenu/Margin/VBox"]
+text = "My Game"
+
+[node name="StartButton" type="Button" parent="MainMenu/Margin/VBox"]
+text = "Start Game"
+```
+
+## Collaborative protocol
+
+This skill writes UI scene nodes and wires button signals. Always ask before applying: "May I add the MainMenu (Control + Margin + VBox + Title + Start/Quit buttons) and connect Start.pressed to `_on_start_pressed`?". See `../../_shared/collaborative-protocol.md`.