@funpixel/tools 0.1.0 → 0.1.1

package/plugins/claude/skills/game-spine/references/replay.md

@@ -2,9 +2,9 @@
 
 Two options for a game whose rules already step from input (skill `fp:game-logic`: seeded,
 engine-free, a fixed step): keep a run as data and play it back frame by frame, and prove a
-refactor changed nothing a player sees. Both are lessons from one game, Held Note (a third-person
+refactor changed nothing a player sees. Both are lessons from one game (a third-person
 3D horror chapter in three.js, September 2026, hand-iterated over many agent sessions), gathered by
-the Held Note lane. No first-try action game has tested them yet; read them as options with the
+its lane. No first-try action game has tested them yet; read them as options with the
 reasons they earned, not as a procedure.
 
 ## What the kit already does
@@ -30,7 +30,7 @@ If the sim advances one fixed step per intent (what the hands asked for this ste
 dodge), a run is the list of intents plus the seed and any setting that changes the sim. Replaying
 it means feeding that list instead of live input.
 
-- **Held Note's shape.** Its chapter bots produce intents; a small script wrote a bot run's intents
+- **That game's shape.** Its chapter bots produce intents; a small script wrote a bot run's intents
   to JSON, and the game read them from a window global in place of the controls, through the real
   renderer, camera and sound. One test made the replay trustworthy:
   `same_seed_same_inputs_same_events` plays a bot's intents again on a fresh sim with the same seed
@@ -39,10 +39,10 @@ it means feeding that list instead of live input.
   what a step did; turning it on by default silently broke every recorded replay. The game now
   turns the assist off whenever a replay runs. Store such settings with the recording.
 - **Re-record after a sim change.** A recording holds intents, not positions: a tuned run speed
-  moves where she stands when the next intent arrives, and the replay drifts. The symptom Held
-  Note learned to read: a still of her staring at a wall is usually a stale recording.
+  moves where she stands when the next intent arrives, and the replay drifts. The symptom the
+  game learned to read: a still of her staring at a wall is usually a stale recording.
 - **A recorder in the game.** A key saves a person's run the same way, with its long frames,
-  camera jumps and errors marked. Held Note's note says a human run beats any bot for feel; when it
+  camera jumps and errors marked. The game's note says a human run beats any bot for feel; when it
   was written, no human run had been replayed yet.
 
 ## Film mode: the same frame every time
@@ -59,16 +59,16 @@ function loop(now: number) {
 }
 ```
 
-Held Note's stills script replayed an intent file, ticked 1/60 s at a time until the sim's clock
+Its stills script replayed an intent file, ticked 1/60 s at a time until the sim's clock
 reached each requested second, held the sim for about 20 frames so the camera settled, then shot.
 A still at 36.8 s was the same picture every run, so:
 
 - **A moment can be debugged a frame at a time.** Replay to just before it, tick, read
-  `__FPX_STATE__` and `funtools inspect --at x,y` on each frame. Held Note's "what is that white
+  `__FPX_STATE__` and `funtools inspect --at x,y` on each frame. Its "what is that white
   ball?" was found this way: at one fixed frame, hide one thing at a time (the torch light, the
   enemy, the particles, the beam) until it goes. It was an additive beam seen down its own axis
   (skill `fp:art`, `references/frames.md`).
-- **An A/B at a frame only means something if the frame keeps it.** Held Note's torch and emissive
+- **An A/B at a frame only means something if the frame keeps it.** The game's torch and emissive
   materials were re-posed every frame, so turning them off in a debug step did nothing, while the
   albedo, which nothing re-set, could be tested. Turn a thing off where the frame reads it from.
 - **Wall-clock work does not follow the film clock.** CSS transitions and timers ran in real time;
@@ -78,7 +78,7 @@ This is the spine's one loop and one clock with a second driver, not a second lo
 
 ## Proving a refactor or a split
 
-Held Note's `sim.ts`, `station.ts` and `game.ts` each grew past 800 to 1,100 lines and were split
+The game's `sim.ts`, `station.ts` and `game.ts` each grew past 800 to 1,100 lines and were split
 into small modules with typed seams. A split that should change nothing was accepted on four
 agreements, each an option:
 
@@ -94,7 +94,7 @@ wall clock, can differ between two captures of one build; capture the same build
 treat a later difference no larger than that as noise (the same idea as `journey replay --repeat 2`).
 With film mode the stills can be identical to the pixel, and then any difference is real.
 
-The case for it, from Held Note: after the game split, the capture hook reached the game through a
+The case for it, from that game: after the game split, the capture hook reached the game through a
 loose cast, the replay cursor and the intro timer had moved, and every capture view silently sat at
 t = 0 behind the opening shot. A blind panel scored that round 4.9 ("no enemy in any capture").
 Typing the seam (no cast) and logging an error when a view misses its beat fixed it; on real

package/plugins/claude/skills/game-spine/references/room-api.md

@@ -1,4 +1,4 @@
-# Room API (`@funpixel/sdk/multiplayer`, SDK 0.6.0)
+# Room API (`@funpixel/sdk/multiplayer`, SDK 0.7.0)
 
 ```ts
 import { Room, getGameKey, RoomError } from '@funpixel/sdk/multiplayer';

package/plugins/claude/skills/game-spine/references/sdk.md

@@ -18,7 +18,7 @@ and tweens).
 
 ## The surface
 
-1. Pin it exactly: `"@funpixel/sdk": "0.6.0"`, no caret. The root export is `setupGameResize`
+1. Pin it exactly: `"@funpixel/sdk": "0.7.0"`, no caret. The root export is `setupGameResize`
    only; everything else comes from a subpath (`/audio`, `/multiplayer`, `/save`, `/liveParams`,
    `/device`).
 2. **Resize.** `setupGameResize(cb: (width: number, height: number) => void, win?: Window): () => void`

package/plugins/claude/skills/gdd/SKILL.md

@@ -28,8 +28,8 @@ is an evidence gap, not a rebuild.
 
 ## Invent first, then fill the template
 
-A plan filled template-first lost 3 of 3 blind seats to one that spent its time on design (Gallery
-Heist, 1 Oct 2026). The order that won, in [references/invent-first.md](references/invent-first.md):
+A plan filled template-first lost 3 of 3 blind seats to one that spent its time on design (one
+game, 1 Oct 2026). The order that won, in [references/invent-first.md](references/invent-first.md):
 
 1. **Six forcing questions**, in `## The invention`: what the core object means, why the verb
    exists in this world, who wants what by name, what the twist costs in feeling and in play, the

package/plugins/claude/skills/gdd/references/as-built.md

@@ -28,9 +28,9 @@ team's robot game passed that test: its Unity port matched the web build exactly
 - Name what is not built yet as not built. A planned feature stays in Part 1 until a test or a
   recorded playthrough shows it running.
 - Write each value beside where it lives (`src/tuning.ts · FUSE_S = 3.0`), a shape a short script
-  can compare to the code on every build (The Hot Gates checked 213 numbers that way). Where a value
+  can compare to the code on every build (one game checked 213 numbers that way). Where a value
   moved from its target, "the reason was not recorded" is better than a guessed one.
-- Keep a list of the defects writing the spec found; writing Pocket Crew's found five.
+- Keep a list of the defects writing the spec found; writing one game's found five.
 - Say what nothing has observed yet (unheard, never played on a phone, fun unproven) and leave the
   person's own play as a question for them until it happens.
 

package/plugins/claude/skills/gdd/references/design-measures.md

@@ -1,7 +1,7 @@
 # The design measures
 
 `npx @funpixel/tools gdd` ends with six numbers read off the GDD, each with why and the peers' figures. They come
-from the Don't Die field report (10 Oct 2026), and its owner's rule holds them: "Advise, never gate." Each is advice.
+from one game's field report (10 Oct 2026), and its owner's rule holds them: "Advise, never gate." Each is advice.
 Read them, decide what to do, and leave the call on the game's size and scope to the owner. A dense, systemic game
 can be the choice; the lint then says "dense: is each element learned (used again after its teach)?", never "too
 many".
@@ -13,7 +13,7 @@ it.
 | Measure | What it reads | The line |
 |---|---|---|
 | Elements per hour | `design/spec/elements.json` (`[{id, kind, name, debut_place, debut_beat_t, uses}]`), else `## Elements`, else the tables under `## Content` (`### Roster` and its kin, the player's row left out) | new mechanics, enemies, tools and systems ÷ first-playthrough hours; good games sit at about 1.4–3 (Prey 1.4, Scorn 2.2, Superhot 2–3); warns above about 4; any element used fewer than twice after its teach is "check by hand" |
-| The spine | `## The spine`: a `Spine:` sentence, clauses split by `;`, and a table of system, the clause it serves (quoted or by number), genre beat | a system that serves no clause warns: Don't Die cut the systems that mapped to none |
+| The spine | `## The spine`: a `Spine:` sentence, clauses split by `;`, and a table of system, the clause it serves (quoted or by number), genre beat | a system that serves no clause warns: one game cut the systems that mapped to none |
 | Sources | every table with a Source column (the identity lock's and the asset script's are pictures, not claims), footnotes `[^n]` with their `[^n]: …` line, `[source?]` markers | a marked claim with no source line warns; "approx, from memory" is kept and listed as secondhand; `gdd --sources` lists them all |
 | Peers | `## Worth against the genre` or `## Peers` | each peer's length and elements per hour: the report's figures where it has them, the GDD's own figure when its row carries a link, else unknown, never guessed |
 | Length totals | the parts' minutes: `design/spec/places/*.json` `target_minutes.first_time`, else a Length column in `## Chapters`, `## Places` or `### Stages` | summed against `Play length:` (or `**Length:**`), the difference shown; warns past 10% (or 2 minutes); the owner's `target_minutes` is shown, never judged |

package/plugins/claude/skills/gdd/references/design-note.md

@@ -19,7 +19,7 @@ What each line is for:
 - **Depth** is where a finished level still loses to the genre hit: critics picked the hit for a
   longer, denser run and a reason to replay. Fill the `Depth:` line under the core loop from bot
   runs; the options and genre numbers are in the game-logic skill's depth reference.
-- **The first minute** puts the signature on screen early: Dead Letter's first cut showed it at
+- **The first minute** puts the signature on screen early: one game's first cut showed it at
   3:45, and the fix moved it under 30 s.
 - **Juice** maps actual events to visible responses and explicit audio choices, including silence.
   Remove inapplicable example rows: a loss or reward tier invented to fill the template is a

package/plugins/claude/skills/gdd/references/first-look.md

@@ -36,7 +36,7 @@ style words or the rule, redraw that frame once, and write what changed into the
 ## Identity lock first
 
 Make each recurring design's sheet from its best draft before anything else, then draw every picture
-to the sheets and one verbatim style block (Blue Freight: seven of seven redraws on-model). Drift
+to the sheets and one verbatim style block (one game: seven of seven redraws on-model). Drift
 check: frames side by side, each design part by part (hair, outfit, silhouette, colours, a vehicle's
 shape); `funtools judge identity <frames…> --concept ref-hero.png` asks a seat. Keep a before/after
 of each redraw, then list the honest breaks. Details: [world-and-identity.md](world-and-identity.md).

package/plugins/claude/skills/gdd/references/floors.md

@@ -14,8 +14,8 @@ game keeps the checks; a Stop with nothing open or deferred removes it. Delete i
 What the team's best shipped games had in common (research 08, 17, 20), each with why:
 - coherent art and readable actors, scenery and UI in the chosen medium;
 - every row of the juice table in the game, with its limits (skill `fp:game-feel`);
-- the signature on screen within about 30 seconds, and controls taught where first needed (Dead
-  Letter's first cut showed its signature at 3:45);
+- the signature on screen within about 30 seconds, and controls taught where first needed (one
+  game's first cut showed its signature at 3:45);
 - a signature-moment view (`moment: true`) that plays the payoff, since critics judge stills
   (skill `fp:verifying`);
 - the full screen set: a real title, how to play, settings (sound, motion), play, pause, and the

package/plugins/claude/skills/gdd/references/gameplay-contract.md

@@ -62,7 +62,7 @@ state and emitted events. A table and an existing test file prove neither execut
 Keep a seeded novice simulation beside the skilled balance bot. The novice receives only the
 observation a player could have, reacts at a declared interval, and sometimes misses or hesitates;
 it cannot inspect future spawns, exact hidden state or a solver's answer. Freeze its policy and
-seed list before tuning. A floor used on Gesundheit's first wave: 100
+seed list before tuning. A floor used on one game's first wave: 100
 fixed seeds, at least 80 runs that both survive the stage and earn score. Record both counts, elapsed time,
 deaths by cause, policy parameters and failing seeds. Other genres state the equivalent first
 success and deadline before the run. This is a regression floor, not a human success estimate.

package/plugins/claude/skills/gdd/references/genre-puzzle.md

@@ -62,7 +62,7 @@ What a player of the hit expects without being told. Keep them as defaults; brea
 Starting code with these as defaults, and the screen flow: [starters.md](starters.md), "Merge or drop".
 
 - Drop and merge (Suika): the piece hangs over a drop line that shows where it will fall, and the next piece is shown.
-- Aim and bounce (Peggle): the aim guide shows the first path, and the free-ball bucket moves along the bottom every shot; it never runs out. A capped helper read as a bug twice in Lantern Night.
+- Aim and bounce (Peggle): the aim guide shows the first path, and the free-ball bucket moves along the bottom every shot; it never runs out. A capped helper read as a bug twice in one of our games.
 - A wrong move is cheap: undo or an instant restart of the level, and a solved state that is unmistakable.
 - No clock on thinking in a pure puzzle (Monument Valley has no fail state); pressure comes from a board that fills, not a timer.
 
@@ -85,7 +85,7 @@ Pick one signature and up to three more before building (`npx @funpixel/tools wo
 Portal, Monument Valley and The Witness are puzzles you walk through. What differs from a board:
 
 - **The chamber is the unit.** Each debuts one element, then asks for it in a new combination; a
-  chapter spends itself on one trick. A chamber that tells you every step is a tutorial: Fold Room's
+  chapter spends itself on one trick. A chamber that tells you every step is a tutorial: one game's
   first version cleared in 1:11 with a hint per step, and critics called it "a tutorial, not a
   puzzle". The aha is a known tool used a new way: the exit seen through the portal, the cube
   carried through it, the switch reachable only from the far side.
@@ -94,7 +94,7 @@ Portal, Monument Valley and The Witness are puzzles you walk through. What diffe
 - **Readable space.** The player always knows which side of a portal they are on (a different light
   or colour per room), where a carried object will land (a ring on the floor before the drop) and
   when something is in reach (it answers before the tap). These were our blind players' three
-  medium findings on Fold Room.
+  medium findings on that game.
 - **Controls.** First person, or a fixed three-quarter view with tap-to-move (Monument Valley). Held
   sideways: move on the left thumb, look on the right, one action button of at least 44 px, and the
   two thumbs never share a zone.
@@ -123,7 +123,7 @@ Options with reasons; more in skill `fp:game-logic`, its depth reference.
   places its hard levels on a rhythm the player can feel; a daily seeded board gives a reason to
   return.
 - Pressure from the first drops: a small container or a partly filled seeded start, so the first
-  minute already asks where things go. Critics called Plush Pop's early basket "too sparse, no
+  minute already asks where things go. Critics called one game's early basket "too sparse, no
   packing pressure" beside Suika Game.
 - The best score per mode saved, the next piece shown, restart in one tap.
 

package/plugins/claude/skills/gdd/references/genre-racing.md

@@ -31,7 +31,7 @@ that catch this genre's quiet bugs. The creator's brief wins over anything here.
   time), a colour that owns it, and a body that leans, squats and bounces with the physics.
 - A driver visible in the seat, or a face on the kart, buys character for very little.
 - Rivals each keep one colour and one personality in how they drive (the bully, the careful one).
-- **Keep the pack in view** (Particle Rush, Oct 2026). Draw rivals at true scale out to about 60 m
+- **Keep the pack in view** (one racer, Oct 2026). Draw rivals at true scale out to about 60 m
   and compress the distance beyond it, so the pack stays on screen while contact up close reads
   exactly. A bunching rule tuned for the chase keeps it there: a racer more than 10 m from the
   pack's mean distance is pulled toward it, 0.05 m/s per metre beyond, at most 0.8 m/s, ahead or
@@ -76,7 +76,7 @@ What a player of the hit expects without being told. Keep them as defaults; brea
 Starting code with these as defaults, and the screen flow: [starters.md](starters.md), "Racing".
 
 - A fall or a wall is a short respawn on the track, never a restart of the race.
-- Position and lap are always on screen; the rivals' pace is beatable with a thumb, not only with frame-perfect input (Saltwake's Dusk Cup was won only at 60 decisions a second).
+- Position and lap are always on screen; the rivals' pace is beatable with a thumb, not only with frame-perfect input (one racer's last cup was won only at 60 decisions a second).
 - Help for the back of the pack: Mario Kart weights its items toward the players behind, so a race stays open.
 - A ghost or a best time to beat on the next attempt.
 

package/plugins/claude/skills/gdd/references/genre-rpg.md

@@ -86,8 +86,8 @@ Pick one signature and up to three more before building (`npx @funpixel/tools wo
 
 A design question for the GDD: for each weapon, ability or spell, the situation where it beats the
 others (reach, a crowd, a shield, a state it opens or finishes) and what it costs. A choice of three
-reads as a choice when the three answer different situations (our reading). Held Note, one of our
-hand-iterated games, answered it per weapon (a cutter for joints, a rivet driver that pins an enemy
+reads as a choice when the three answer different situations (our reading). One of our
+hand-iterated games answered it per weapon (a cutter for joints, a rivet driver that pins an enemy
 from range, a scattergun that clears a crowd at the cost of stealth, a knife that finishes a staggered
 enemy). A question, not a mandate; more in skill `fp:game-feel`, `references/contact.md`.
 

package/plugins/claude/skills/gdd/references/genre-shooter.md

@@ -87,8 +87,8 @@ Pick one signature and up to three more before building (`npx @funpixel/tools wo
 
 A design question for the GDD: for each gun, upgrade or panic button, the situation where it beats
 the others (range, a crowd, armour, a state it opens or finishes) and what it costs. Two guns that
-answer the same situation are one weapon wearing two looks (our reading). Held Note, one of our
-hand-iterated games, answered it per weapon (a cutter for joints, a rivet driver that pins an enemy
+answer the same situation are one weapon wearing two looks (our reading). One of our
+hand-iterated games answered it per weapon (a cutter for joints, a rivet driver that pins an enemy
 from range, a scattergun that clears a crowd at the cost of stealth, a knife that finishes a staggered
 enemy). A question, not a mandate; more in skill `fp:game-feel`, `references/contact.md`.
 

package/plugins/claude/skills/gdd/references/genre-survival.md

@@ -83,8 +83,8 @@ Pick one signature and up to three more before building (`npx @funpixel/tools wo
 
 A design question for the GDD: for each weapon, tool or upgrade, the situation where it beats the
 others (a crowd, range, the night, a resource it saves) and what it costs. An upgrade that answers
-no new situation is a bigger number rather than a choice (our reading). Held Note, one of our
-hand-iterated games, answered it per weapon (a cutter for joints, a rivet driver that pins an enemy
+no new situation is a bigger number rather than a choice (our reading). One of our
+hand-iterated games answered it per weapon (a cutter for joints, a rivet driver that pins an enemy
 from range, a scattergun that clears a crowd at the cost of stealth, a knife that finishes a staggered
 enemy). A question, not a mandate; more in skill `fp:game-feel`, `references/contact.md`.
 

package/plugins/claude/skills/gdd/references/invent-first.md

@@ -1,6 +1,6 @@
 # Invent first, then fill the template
 
-Two plans were written from one brief on 1 Oct 2026 (Gallery Heist, a first-person paint shooter in
+Two plans were written from one brief on 1 Oct 2026 (a first-person paint shooter in
 a museum at night). The plan that followed this skill's template was clearer (8.4 against 8.1) and
 more buildable (7.2 against 6.4), and lost 3 of 3 blind seats, 7.0 against 8.0. It trailed on level
 design by 1.8, story and world by 1.7, fun by 1.2 and phone controls by 1.0. It spent its extra
@@ -70,14 +70,14 @@ Canvas): genre and fidelity, depth (5 minutes, 30 minutes or chapters), the core
 clock, question, antagonist, frame), extras with their cost (voice per character, cutscenes, photo
 mode, multiplayer, and for a deep game two takes: two parallel builds of the locked plan, played
 side by side from the title by `npx @funpixel/tools compare-takes`, the mix keeping what each won;
-on Blue Freight one take won the environment and the other the dynamics). Propose a pick per card with its reason for this game
+on one game, one take won the environment and the other the dynamics). Propose a pick per card with its reason for this game
 (`pitch propose core world --why "…"`); the plan shows your picks and the owner approves them with it
 at the lock (`flow ask`). Under their autonomy "ask", each card is theirs instead: `pitch ask` posts each
 as a question in the chat, and `pitch lock` waits for their answers. From then on the core gets the art budget, the tests and the hardest checks, and
 what was not picked stays light. Autonomy is the OWNER's setting (funpixel.json `flow.autonomy`,
 from their brief), never a card you propose: under `ask` and `plan-then-go` every pitch card waits
 for their answer; only their `go` lets you pick, record each pick with its reason, and lock.
-(Wind Orchard, 4 Oct: under "ask" the agent proposed and locked all seven cards itself.)
+(One game, 4 Oct: under "ask" the agent proposed and locked all seven cards itself.)
 
 ## 4. Named behaviour tests, before code
 

package/plugins/claude/skills/gdd/references/level-and-fun.md

@@ -1,6 +1,6 @@
 # Levels, a world that plays, fun and the phone
 
-Where a plan made with the kit lost to the owner's own workflow (Gallery Heist, 1 Oct 2026: two
+Where a plan made with the kit lost to the owner's own workflow (one game, 1 Oct 2026: two
 GDDs from one brief, three blind judges, 7.0 against 8.0). The kit's plan led on clarity and
 feasibility and trailed on level design (−1.8), story and world (−1.7), fun (−1.2) and phone UX
 (−1.0). Every judge named the same four things, so this page is those four, with what our best
@@ -26,9 +26,9 @@ Write the place row before drawing its picture, and draw each picture from its r
 pictures to each other: if two could swap captions, one of them is not a place yet.
 
 **Shape of a level.** Teach the new thing alone, test it, twist it, then combine it with what came
-before (teach, develop, twist, test, celebrate). The Hot Gates gave each of its eight islands one
-rule; The Last Good Robot debuts each of its nine kinds alone at the head of its wave before it
-joins a crowd (41, 82, then 100 robots per floor). Dead Letter calmed its level after watching the
+before (teach, develop, twist, test, celebrate). One game gave each of its eight islands one
+rule; another debuts each of its nine kinds alone at the head of its wave before it
+joins a crowd (41, 82, then 100 robots per floor). A third calmed its level after watching the
 gray-box: a plan is allowed to lose to the game in front of you.
 
 **Layout laws as tests.** The winning plan wrote its rooms as data with laws a test can read: a
@@ -61,7 +61,7 @@ Ask of the world: **what does it do when you play?**
   one kind is a painting to the gun (auto-fire skips him), one sidesteps after 0.3 s of lock so your
   burst flies into the art, one always perches against a dark backdrop, one carries a canvas as a
   shield. Each asks a different question of the same verb. The kit's roster was one striped body
-  with five props: one enemy in five coats. The Last Good Robot's "one chassis, nine heads" works
+  with five props: one enemy in five coats. One game's "one chassis, nine heads" works
   because each head is a different idea, not because the chassis is shared.
 
 ## 3. Fun with depth
@@ -69,13 +69,13 @@ Ask of the world: **what does it do when you play?**
 | Ask | A strong answer | Where it showed |
 |---|---|---|
 | How many decisions a minute does the verb make? | every shot is a choice about where you stand | the winning plan: "the game rewards the step before the shot" |
-| What is the boring optimum, and what makes it lose? | named, with the rule that beats it | panic-firing pays nothing; Held Note's welding every door runs you out of gas |
-| Does risk pay? | a riskier line scores more, never only costs more | The Hot Gates' kill ladder (10 in 2 s up to 100 in 3 s, slow motion on the top rung) |
-| What does each verb cost? | a price in time, resource or the route | Held Note: hold 1.5 s, 25 gas, and the room beyond is gone |
-| Why play the next room? | it asks a new question of the same verb | each kind debuts alone (The Last Good Robot) |
+| What is the boring optimum, and what makes it lose? | named, with the rule that beats it | panic-firing pays nothing; in one horror game, welding every door runs you out of gas |
+| Does risk pay? | a riskier line scores more, never only costs more | one game's kill ladder (10 in 2 s up to 100 in 3 s, slow motion on the top rung) |
+| What does each verb cost? | a price in time, resource or the route | the horror game: hold 1.5 s, 25 gas, and the room beyond is gone |
+| Why play the next room? | it asks a new question of the same verb | each kind debuts alone (the nine-kind game above) |
 | Why play again? | a grade, a medal for clean play, a best to beat | the winning plan's results screen grades splashes, and only your own cost the clean-hand medal |
 
-Held Note added weapons only when each answered a different situation, all drawing on one canister;
+The horror game added weapons only when each answered a different situation, all drawing on one canister;
 two answers to the same situation are one tool wearing two looks.
 
 ## 4. Phone UX: two thumbs, 852 × 393
@@ -85,7 +85,7 @@ The phone is where a plan is cheapest to fix and most often lost.
 - **Controls off the play and off the held thing.** Both plans first put Fire and Cover on the gun;
   the kit's HUD v2 moved them to the right edge and shrank the gun to a sixth of the screen.
   Whatever the hero holds is part of the frame budget; a mockup that breaks its own cap breaks it in
-  the build. Held Note's HUD covered 41% of the phone screen until it was measured.
+  the build. One game's HUD covered 41% of the phone screen until it was measured.
 - **One gesture per thumb zone.** The winning plan put aim, tap-for-cover and hold-to-wipe all in
   the right thumb's zone: three gestures that collide. Give each zone one gesture, or make one a
   button.

package/plugins/claude/skills/gdd/references/pages.md

@@ -11,11 +11,8 @@ data gets none; a map drawn by hand is a page of its own.
 ## The bar: the studio's best GDD pages
 
 The owner judges a plan page against the studio's own bespoke design pages, not against the base
-`gdd page` writes. Name them when you show yours, and say where yours falls short:
-
-- **Knockout Lap v0.2**: kept locally by the owner, so ask for it by name.
-- **Particle Rush**'s GDD page: ask the owner for its link.
-- **Gallery Heist**'s GDD page.
+`gdd page` writes. Ask the owner for them (one is kept locally by the owner, the others by link),
+name them when you show yours, and say where yours falls short.
 
 What makes them strong, and how much of it `gdd page` draws:
 

package/plugins/claude/skills/gdd/references/plan-at-size.md

@@ -29,11 +29,11 @@ What play must reach, counted. It goes in the GDD's `## Content list`:
 - **Size it to play length:** a game is at least 15 minutes of real play by a first-time
   player, even with one level: escalation (a new idea per stage, not only speed), variety, a twist
   around the middle, and an ending worth reaching. Write the `Play length:` line and count the
-  content that fills it (Riad Rush and Fold Room: "at least 15 minutes play, to be a game", owner,
+  content that fills it (two of our games: "at least 15 minutes play, to be a game", owner,
   3 Oct); a 2-minute arcade round is a choice the line states "on purpose". `funtools sim` holds
   the skilled bot's run to that line and asks that it reaches the ending, and `playtest experience` fills `Reached in play` for areas,
   levels and waves from the long blind player and the bot (marked `(measured)`). Play reaching half
-  the claimed areas or less is a warn: Floe claimed 8 worlds and play reached 2.
+  the claimed areas or less is a warn: one game claimed 8 worlds and play reached 2.
 - **Size it to the game:** a one-screen toy can honestly say "Levels 1"; say that it is the choice
   in the list ("one screen on purpose") and the ambition read leaves it alone. A full game names
   its areas, kinds with a debut each (the `## Content` roster), a climax and at least one ending.
@@ -96,7 +96,7 @@ under `## AD rules` (the hooks and the fidelity seat read that heading):
 
 - **Offer them and explain why:** every playtest round, the fidelity seat judges each line held,
   partly held or broken beside the target frames. Without lines, "does it still look like the plan"
-  has no answer. Held Note's six lines caught a darker art pass that hid its threats.
+  has no answer. One game's six lines caught a darker art pass that hid its threats.
 - **They are the creator's words.** Offer drafts from the pitch and the first look; the creator
   rewrites, keeps or cuts them.
 - **Declining is fine, and kept:** `Declined: I will judge the look by eye (the creator, 30 Sep)`.
@@ -121,8 +121,8 @@ them once to PNGs.
 Moments that invite someone to look: after the plan is applied, after the first look, after the
 first slice. The someone can be a friend, the owner, a player, or the creator's next-morning self.
 Offer the pause, record who looked and what they said in the GDD's `## Pause points` table, and
-carry on either way. LGR waited four days for its owner's "go ahead"; Held Note built twenty
-minutes after its approval; Dawg Ball never paused and still reached its gate. The pause is there
+carry on either way. One game waited four days for its owner's "go ahead"; another built twenty
+minutes after its approval; a third never paused and still reached its gate. The pause is there
 because a second pair of eyes is cheapest before code, not because the path needs permission.
 
 ## 6 · The plan grows with the game

package/plugins/claude/skills/gdd/references/production-tiers.md

@@ -45,14 +45,14 @@ and that wins.
 
 | Setting | What it adds | Seen in |
 |---|---|---|
-| small | The GDD and one target frame of the moment that sells the game; the meta layer (stars, collection, a map of levels) planned with the mechanic, not after it. | Koi Out, Stitch Pop, Porcelain Panic, Dock Jam: a one-second mechanic, a meta layer, many levels. |
-| mid | A target frame per place or level, the story's beats as ids the game reports, progress saved per level or chapter, and a runbook of what proves each step. The plan is also a spec folder the game loads (`design/spec/`: every number in `tunables.json`, rooms and chapters as data with pars, slice first; `funtools spec init`, skill `fp:gdd`, references/spec-folder.md). | Dead Letter (`GAME.md`, `QUALITY_BAR.md`, design addenda per pass), The Last Good Robot (`RUNBOOK.md`, `runbook.json`), The Hot Gates. |
-| deep | A making-of log (`design/MAKING.md`: decision, numbers, lesson, one entry per lane). Show first: films or a proofs page the owner picks from, then build behind a flag, measure, merge. One lane per worktree. | Held Note (`design/MAKING.md`, `PERF.md`, frames at 0:10, 1:00, 2:00 as the definition of done), Pocket Crew, the Blue Freight plan. |
+| small | The GDD and one target frame of the moment that sells the game; the meta layer (stars, collection, a map of levels) planned with the mechanic, not after it. | Four casual puzzle games: a one-second mechanic, a meta layer, many levels. |
+| mid | A target frame per place or level, the story's beats as ids the game reports, progress saved per level or chapter, and a runbook of what proves each step. The plan is also a spec folder the game loads (`design/spec/`: every number in `tunables.json`, rooms and chapters as data with pars, slice first; `funtools spec init`, skill `fp:gdd`, references/spec-folder.md). | One game (`GAME.md`, `QUALITY_BAR.md`, design addenda per pass), another (`RUNBOOK.md`, `runbook.json`), a third. |
+| deep | A making-of log (`design/MAKING.md`: decision, numbers, lesson, one entry per lane). Show first: films or a proofs page the owner picks from, then build behind a flag, measure, merge. One lane per worktree. | One game (`design/MAKING.md`, `PERF.md`, frames at 0:10, 1:00, 2:00 as the definition of done), another, and one game's plan. |
 
 Lanes at deep: `npx @funpixel/tools lanes plan` splits a build stage into lanes, each with a brief,
 its own paths, a spend cap, a time-box and a merge gate; `lanes merge` lands one only after a seat
 that did not build it passes it and the owner has picked between any candidates (`/fp:lanes`).
-Lane hygiene, from Held Note's builder. Use one worktree per lane, never `git stash` (it is
+Lane hygiene, from one game's builder. Use one worktree per lane, never `git stash` (it is
 shared across worktrees), and never rewrite history. Never run two headless Blender jobs at once:
 their dialogs land on the owner's screen. A stale build fools a screenshot, so rebuild before every
 capture. The owner's screenshots become named before-frames.
@@ -61,17 +61,17 @@ capture. The owner's screenshots become named before-frames.
 
 | Setting | What it adds | Seen in |
 |---|---|---|
-| small | One palette in code (a `palette.ts` or the style tokens) and one verbatim style block every generation carries. | The Joydle slate's casual games. |
-| mid | Reference sheets before any art (`ref-*` in `assets/assets.json`). Several draws per item, the most on-palette one kept (`assets gen` scores each by hue against the palette and warns under 55%). Every provider original kept in `assets/raw/`, with a line per job in `assets/costs.jsonl`. Colour ownership: one colour, one meaning. | The Last Good Robot (`tools/luminance.mjs`, `contact-sheet.mjs`, `asset-coverage.mjs`), Dead Letter (`ASSETS.md`), the harness games' `forge.mjs` palette scoring. |
-| deep | Identity locks for every recurring design (GDD `## Identity lock`, skill `fp:gdd`). The 3D line: reference images, then the model, then the original kept with its request id and seed, then cleanup on the bench, then two tiers (phone and HD). Hard-surface pieces are rebuilt or baked from the high-poly onto clean geometry. A decimated AI mesh looks melted, and no shader fixes it. Materials are normalised in code and in the files. | Held Note (`sources/`, `design/assets.md`, models and models/hd), Pocket Crew (raw art kept with request ids and seeds), Blue Freight (seven redraws on-model at the first try once the sheets existed). |
+| small | One palette in code (a `palette.ts` or the style tokens) and one verbatim style block every generation carries. | The studio's casual games. |
+| mid | Reference sheets before any art (`ref-*` in `assets/assets.json`). Several draws per item, the most on-palette one kept (`assets gen` scores each by hue against the palette and warns under 55%). Every provider original kept in `assets/raw/`, with a line per job in `assets/costs.jsonl`. Colour ownership: one colour, one meaning. | One game (`tools/luminance.mjs`, `contact-sheet.mjs`, `asset-coverage.mjs`), another (`ASSETS.md`), the harness games' `forge.mjs` palette scoring. |
+| deep | Identity locks for every recurring design (GDD `## Identity lock`, skill `fp:gdd`). The 3D line: reference images, then the model, then the original kept with its request id and seed, then cleanup on the bench, then two tiers (phone and HD). Hard-surface pieces are rebuilt or baked from the high-poly onto clean geometry. A decimated AI mesh looks melted, and no shader fixes it. Materials are normalised in code and in the files. | One game (`sources/`, `design/assets.md`, models and models/hd), another (raw art kept with request ids and seeds), a third (seven redraws on-model at the first try once the sheets existed). |
 
 ## Verify, the QA loop
 
 | Setting | What it adds | Seen in |
 |---|---|---|
 | small | Rules tests with a seed (same seed and inputs, same round), `verify`, `look --hud` at phone size, `feel`, and one blind phone player. | Every funtools starter ships the seed test. |
-| mid | Bots on several seeds through every level (`sim`, per-level curves; `rooms` for a spec folder's rooms, each against its par), a replay test, a boot test where storage throws (the starter's `test/platform.test.ts`), and fixed-framing before and after on every visual change: `capture --all` then `compare` at desktop 1280x720 and phone 844x390, plus a short film (`clip`). | The Last Good Robot (`src/test/sim.test.ts`, `platform.test.ts`, `tools/release-check.mjs`, `bless-check.mjs`), Dead Letter (`scripts/screen-audit.mjs`, `smoke.mjs`, audio pause tests), The Hot Gates (`src/test/`). |
-| deep | Blind phone players from the title, with no view jumps, as the gate a panel cannot replace (a wrong kit fact sank one version that panels passed). An interleaved A/B phone profile: 844x390 at 3x, CPU slowed four times, a fixed seed, reading p95, long frames and mid-play shader compiles (`profile --viewport phone --throttle 4 --seed 7 --compare`). Evidence per lane in the making-of log. | Held Note (`design/PERF.md`, `tools/profile.mjs`, `tools/compare.mjs`), Pocket Crew (a 3.7 s splash fooled the captures; the fixes were level design: practice zones, camera volumes, a landing ring). |
+| mid | Bots on several seeds through every level (`sim`, per-level curves; `rooms` for a spec folder's rooms, each against its par), a replay test, a boot test where storage throws (the starter's `test/platform.test.ts`), and fixed-framing before and after on every visual change: `capture --all` then `compare` at desktop 1280x720 and phone 844x390, plus a short film (`clip`). | One game (`src/test/sim.test.ts`, `platform.test.ts`, `tools/release-check.mjs`, `bless-check.mjs`), another (`scripts/screen-audit.mjs`, `smoke.mjs`, audio pause tests), a third (`src/test/`). |
+| deep | Blind phone players from the title, with no view jumps, as the gate a panel cannot replace (a wrong kit fact sank one version that panels passed). An interleaved A/B phone profile: 844x390 at 3x, CPU slowed four times, a fixed seed, reading p95, long frames and mid-play shader compiles (`profile --viewport phone --throttle 4 --seed 7 --compare`). Evidence per lane in the making-of log. | One game (`design/PERF.md`, `tools/profile.mjs`, `tools/compare.mjs`), another (a 3.7 s splash fooled the captures; the fixes were level design: practice zones, camera volumes, a landing ring). |
 
 ## One structure that has worked
 
@@ -79,10 +79,10 @@ Not required; the outcome is what checks read. The owner's deeper games split an
 `src/sim/` (fixed step, seeded, cloneable, so a save is a `structuredClone` and bots play whole
 chapters) from `src/view/` (the engine draws the sim and decides nothing) and `src/ui/` (Preact
 screens and HUD). Tests drive the sim with bots on several seeds. Every view lane can then prove the
-sim untouched. See The Last Good Robot, The Hot Gates and Held Note. The funtools starters keep the
+sim untouched. The funtools starters keep the
 same split in small: `rules.ts` engine-free and seeded, `game.ts` drawing it.
 
-The 3D starter's quality tier follows the GPU, never `pointer: coarse` (Held Note
+The 3D starter's quality tier follows the GPU, never `pointer: coarse` (one game's
 `src/view/device.ts`). A desktop window in touch emulation reports a coarse pointer and would get the
 phone's budget; the touch layout still follows the pointer.
 

package/plugins/claude/skills/gdd/references/sections.md

@@ -1,7 +1,7 @@
 # What makes each section strong
 
-Distilled from the team's GDDs (The Last Good Robot, The Hot Gates) and five the owner wrote end
-to end on 28–29 September (Pocket Crew, a deep-sea horror, a kart racer, a frozen metroidvania, a
+Distilled from two of the team's GDDs and five the owner wrote end
+to end on 28–29 September (a crew platformer, a deep-sea horror, a kart racer, a frozen metroidvania, a
 marionette party game). Each row: what the strong version holds, what the thin version looks like,
 and the example that made the difference. `funtools gdd` looks for the evidence in the strong
 column; it cannot tell a good design from a long one, so use it as a checklist, not a grade.
@@ -18,7 +18,7 @@ The robot game's smile (a face flickers onto every defeated robot) and the Greek
 (the count over the army is health, weapon and story) are theses you can see. The owner's horror
 design adds a top-five table: the one reason each hit worked, and what a naive version of our game
 would lack. For each big choice, name the answer everyone reaches for first and the answer of someone
-merely avoiding it, then choose past both; write them down as "Ruled out: X · Y" (the Held Note: guns
+merely avoiding it, then choose past both; write them down as "Ruled out: X · Y" (the horror game: guns
 and gore, then no combat at all, then a welder that cuts the enemies' limbs). A pillar with its **risk** beside it ("horror on a phone:
 risky, since a lit room and a small screen flatten fear; answered by a brightness step and sound
 drawn as arcs") is a
@@ -33,7 +33,7 @@ optimum named, and the rule that makes it lose (panic-firing pays nothing; weldi
 you out of gas). Thin: numbers with no reasons, or a loop with "and also" in it, which is two games.
 The numbers are targets until a test pins them; say so. Give each verb its **price** (weld a door:
 hold 1.5 s, 25 gas, and the room beyond is gone for good): a verb that costs nothing stops being a
-choice. Play one level's economy on paper before code, as a middling player would (the Held Note's
+choice. Play one level's economy on paper before code, as a middling player would (the horror game's
 chapter 2 needed 187 gas across cuts, burns, a pin and a door, so it placed 1.3 × 187 = 243).
 
 ## Opening (the first minute)
@@ -57,7 +57,7 @@ in its tell at a time; never spawn in view; each kind debuts alone) are what mak
 Give each kind something it **takes** besides health (the resource, time, the route, a connection,
 your attention, your plan): a roster where every kind only takes health is one enemy in different
 coats. A tell stays honest when an enemy that chooses a target takes the nearest, never a random one,
-and online it adds the round trip (Break a Leg! uses 0.8 s against about 300 ms of phone lag).
+and online it adds the round trip (the marionette party game uses 0.8 s against about 300 ms of phone lag).
 
 ## Look
 
@@ -66,7 +66,7 @@ colour for "you", one for "hurts", one for "you can touch this"); a font chosen
 asset economy (what is generated, what is built in code, how many); **five AD rules**, each
 checkable in one frame (a colour count, a size at which a thing reads, where grime may and may
 not live); and **target frames**: the key art plus four whole frames of the ladder's moments, each
-saying which claim it pins. Held Note's were timed to its ladder (0:10, 1:00, 2:00, 3:00, 5:00), so
+saying which claim it pins. The horror game's were timed to its ladder (0:10, 1:00, 2:00, 3:00, 5:00), so
 captures of the same seconds could be laid beside them (skill `fp:art`).
 Thin: "stylised and colourful". The owner's docs keep the style words
 in one file and repeat them word for word in every prompt; reference sheets pin each recurring
@@ -113,7 +113,7 @@ controls) before any content; when time runs short, the dressing shrinks, never
 
 ## Requests against the pillars, and the pillar audit
 
-Held Note (the owner's deep-sea horror game, September 2026) was audited against its own GDD
+The owner's deep-sea horror game (September 2026) was audited against its own GDD
 mid-build: an agent graded every beat on both platforms, about 6.6 of 10 against the plan. The
 lesson was that requests made mid-build can quietly break a pillar. "Add guns" broke "you have no
 gun", "make her faster" broke the one-canister economy (its chapter bots could no longer afford the

package/plugins/claude/skills/gdd/references/spec-folder.md

@@ -9,11 +9,11 @@ loads at build time.
 
 Our real games were built this way, and the GDK's games were not.
 
-- **Gallery Heist** was built against `design/gdd/spec/`, written before code. Its README set the
+- **One heist game** was built against `design/gdd/spec/`, written before code. Its README set the
   order of reading. Its `tunables.json` held every number with an id, a default, a range, a unit,
   a why and the tests that pin it. It grew from 652 to 941 tunables while lanes built, because each
   lane wrote its numbers back. It had six rooms whose pars add up to an 18-minute night.
-- **Held Note** and **Pocket Crew** kept their levels as data with tested laws, and their bots
+- **Two others** kept their levels as data with tested laws, and their bots
   finished every level on several seeds.
 - The GDK games were one screen and one GDD, with the numbers in a markdown table that nothing loaded.
 
@@ -110,7 +110,7 @@ near its par.
 `funtools spec lint` checks the folder against itself and the code, and records `.funtools/spec.json`.
 The GDD stage reads that record past the small tier. It checks:
 
-- the sections the tier needs (Gallery Heist's names count: `crew.md`, `fun-and-difficulty.md`, `sfx.md`);
+- the sections the tier needs (the heist game's names count: `crew.md`, `fun-and-difficulty.md`, `sfx.md`);
 - every default inside its own range, ids used once, and the tests they name;
 - unknown ids in the code, the rooms or the spec files (a `P-TUNE-` proposal is a note);
 - tunables the code never reads, and a tunable's number still typed into `src/`;

package/plugins/claude/skills/gdd/references/the-path.md

@@ -1,9 +1,8 @@
 # The path, step by step
 
 The brief's path, step by step. This is the long form: what each step is for, the tool that helps,
-and the signal that says it is done. It is how the owner's best games were made (Held Note's
-`design/MAKING.md` writes it down end to end; Gallery Heist, Pocket Crew, The Last Good Robot and
-The Hot Gates ran the same way): a plan that is a contract, target frames that show what done
+and the signal that says it is done. It is how the owner's best games were made (one game's
+`design/MAKING.md` writes it down end to end; four others ran the same way): a plan that is a contract, target frames that show what done
 looks like, the sim first, assets generated and made to behave, and every round spent closing the
 gap between the game and its targets.
 
@@ -112,7 +111,7 @@ green throughout.
 game goes chapter by chapter (the GDD's `## Chapters`, the `chapters` stage): plan the chapter with
 the owner, make its target frames first, build it to them, show it, and open the next only on their
 yes (`note verdict chapter:<id> accept "<their words>"`). Fold a
-mid-build request back into the pillars before you build it: Held Note's "add guns", "make her
+mid-build request back into the pillars before you build it: one game's "add guns", "make her
 faster" and "make maneuvers easier" each broke a stated rule until they were folded back.
 **Done when:** the content list is reached in play.