@funpixel/tools 0.1.0 → 0.1.1

package/plugins/kiro/AGENTS.md

@@ -87,7 +87,7 @@ the demo with your game (`rules.ts`, `session.ts`, `game.ts`, `feel.ts`, `hud.ts
   paths, an environment map (they render flat grey without one), and `mixer.update(dt)` every frame.
 - Pixi: every display object gets a `.label`; `window.__PIXI_APP__ = app` after `app.init()`.
 - Room codes, share codes and seeds carry `data-funpixel-selectable` (else they cannot be copied).
-- `@funpixel/sdk` is pinned exactly (`"0.6.0"`). Import the root only for `setupGameResize`;
+- `@funpixel/sdk` is pinned exactly (`"0.7.0"`). Import the root only for `setupGameResize`;
   everything else from a subpath. Multiplayer is `Room.autoJoin(getGameKey(), …)`, never a raw
   WebSocket (skill `funpixel-game-spine`).
 - A performance fix changes how a frame is made (pooling, atlases, instancing), never what it shows.

package/plugins/kiro/README.md

@@ -14,4 +14,4 @@ Funpixel MCP is written disabled and the skills fall back to `npx @funpixel/tool
 Kiro shows hook output to the model only at the start of a turn, so the Stop gate cannot hold a turn open: it warns the person
 and hands its open items to the agent with the next message. See `hooks/host.md`.
 
-Generated by `funpixel-mono/gdk` (`npm run build`); edit the source there, never this copy.
+This folder is built from Funpixel's source and published as is: changes made here are replaced by the next release.

package/plugins/kiro/hooks/brief.md

@@ -87,7 +87,7 @@ the demo with your game (`rules.ts`, `session.ts`, `game.ts`, `feel.ts`, `hud.ts
   paths, an environment map (they render flat grey without one), and `mixer.update(dt)` every frame.
 - Pixi: every display object gets a `.label`; `window.__PIXI_APP__ = app` after `app.init()`.
 - Room codes, share codes and seeds carry `data-funpixel-selectable` (else they cannot be copied).
-- `@funpixel/sdk` is pinned exactly (`"0.6.0"`). Import the root only for `setupGameResize`;
+- `@funpixel/sdk` is pinned exactly (`"0.7.0"`). Import the root only for `setupGameResize`;
   everything else from a subpath. Multiplayer is `Room.autoJoin(getGameKey(), …)`, never a raw
   WebSocket (skill `funpixel-game-spine`).
 - A performance fix changes how a frame is made (pooling, atlases, instancing), never what it shows.

package/plugins/kiro/hooks/guidance.json

@@ -1,3 +1,3 @@
 {
-  "hash": "ec92c635aaac1cab"
+  "hash": "47443d9a284e95f9"
 }

package/plugins/kiro/hooks/vendor/pipeline/pipeline.mjs

@@ -16,7 +16,7 @@ export const PANEL_DEFAULT = 7.3;
 export const CATALOGUE = {
     pitch: {
         title: 'Invent and pitch',
-        why: 'a game whose answers are generic loses to one that invented something (Gallery Heist A/B, 3 of 3 seats)',
+        why: 'a game whose answers are generic loses to one that invented something (an A/B, 3 of 3 seats)',
         gates: [{ kind: 'gdd', headings: ['The invention'] }, { kind: 'studio' }, { kind: 'worth' }],
         rules: [
             'Answer the six forcing questions for THIS game in the GDD\'s `## The invention`: what the core object means, why the verb exists in this world, who wants what (names), what the twist costs, the one system that lives, what only this game has. A generic answer means the idea is not there yet.',
@@ -71,20 +71,20 @@ export const CATALOGUE = {
     },
     'first-look': {
         title: 'First look',
-        why: 'identity drifts between frames unless it is locked first (Blue Freight: 7 of 7 redraws on-model with reference sheets)',
+        why: 'identity drifts between frames unless it is locked first (one game: 7 of 7 redraws on-model with reference sheets)',
         gates: [{ kind: 'refs', min: 1 }, { kind: 'targets', min: 4 }, { kind: 'kit' }, { kind: 'set' }],
         rules: [
             `The whole game, not a few frames (owner, 4 Oct, asked twice): key art; every screen (the title as the play world, pause, the end; past small settings, results, a level select); the HUD on the phone and the desktop; a frame per place, each tied to a story beat; a living-world sheet; an animation board; a juice board; the sound list; the fun page. \`${T} firstlook\` lists what is missing; places and the living world only for a world game.`,
             'Reference sheets (identity lock) BEFORE moment frames; every recurring design drawn with its references and one verbatim style block.',
             'A target frame per hook moment at the play framing (desktop 1280x720, phone held sideways 852x393).',
-            `The world's kit beside the hero: sheets of its made parts (structures, ground, props, the living cast), cut into pieces before the slice (\`${T} cut\`); the slice is built from them, never from plain shapes (a fresh Blue Freight build shipped code-drawn primitives until the owner's note).`,
+            `The world's kit beside the hero: sheets of its made parts (structures, ground, props, the living cast), cut into pieces before the slice (\`${T} cut\`); the slice is built from them, never from plain shapes (a fresh build shipped code-drawn primitives until the owner's note).`,
             'A picture of every place; no two places alike in shape, material, era and light.',
             'The HUD mockup drawn over a target frame.',
         ],
     },
     'core-test': {
         title: 'Core test (A1): the game bites',
-        why: 'both Blue Freight builds spent their rounds on looks and the challenge never bit ("no challenges at all")',
+        why: 'both builds of one game spent their rounds on looks and the challenge never bit ("no challenges at all")',
         gates: [{ kind: 'tests' }, { kind: 'sim' }],
         rules: [
             `The GDD's named bots play the REAL level (\`${T} sim\`): an engine-free, fixed-step, seeded sim, plus a replay test.`,
@@ -119,7 +119,7 @@ export const CATALOGUE = {
     },
     expand: {
         title: 'Expand, room by room',
-        why: 'our real games are 10 to 18 minutes of designed play, grown room by room from a slice that passed (Gallery Heist: "nothing in Rooms 2-6 starts until the slice passes its gates")',
+        why: 'our real games are 10 to 18 minutes of designed play, grown room by room from a slice that passed (one plan: "nothing in Rooms 2-6 starts until the slice passes its gates")',
         gates: [{ kind: 'rooms' }],
         rules: [
             `Slice first: a room is opened for building only once the room before it passes (\`${T} rooms open <id>\`); the owner alone releases one early (\`--by owner\`).`,
@@ -162,7 +162,7 @@ export const CATALOGUE = {
     },
     'blind-play': {
         title: 'Blind play from the title',
-        why: 'blind players from the title found the blockers no panel could (Held Note)',
+        why: 'blind players from the title found the blockers no panel could',
         gates: [{ kind: 'play' }, { kind: 'sim' }],
         rules: [
             `A blind player from the title, no instructions (\`${T} play\`): a stall counts as blocking.`,

package/plugins/kiro/hooks/vendor/studio/pitch.mjs

@@ -51,7 +51,7 @@ export const CATALOGUE = [
             { id: 'cutscenes', label: 'Cutscenes', why: 'one earned cinematic (the ending, a reveal), skippable', cost: '$1–3 each, plus a scene to stage' },
             { id: 'photo', label: 'Photo mode', why: 'players share the wow moments; the share card carries the game', cost: 'a free camera, a frame and a share sheet: about a day' },
             { id: 'multiplayer', label: 'Multiplayer', why: 'friends in one room through the relay', cost: 'doubles the test work; the host owns the world state' },
-            { id: 'two-takes', label: 'Two takes', why: 'for a deep game: two parallel builds of the same locked plan, each winning different areas (one the environment, one the dynamics); `funtools compare-takes` plays both from the title and writes a best-of-both table, and the mix beats both (Blue Freight, 3 rounds)', cost: 'twice the build sessions, plus a merge round' },
+            { id: 'two-takes', label: 'Two takes', why: 'for a deep game: two parallel builds of the same locked plan, each winning different areas (one the environment, one the dynamics); `funtools compare-takes` plays both from the title and writes a best-of-both table, and the mix beats both (one game, 3 rounds)', cost: 'twice the build sessions, plus a merge round' },
             { id: 'none', label: 'None', why: 'everything goes into the core' },
         ],
     },

package/plugins/kiro/skills/fp-art-director/SKILL.md

@@ -22,8 +22,8 @@ whole-game target creation belongs to an unresolved or new-game direction.
    comfort (match the targets' quality, not their density), and framing numbers left to the owner
    (`funpixel-art`, references/judging-frames.md).
 3. **Generated assets.** The words live in `assets/style.json`: the medium sentence, the palette
-   roles, one isolation clause per asset family. Sets drift when each prompt is free text (The Last
-   Good Robot shipped a whole family at 0% chroma), so a new asset changes the subject or the
+   roles, one isolation clause per asset family. Sets drift when each prompt is free text (one game
+   shipped a whole family at 0% chroma), so a new asset changes the subject or the
    repair and keeps the rest of the words.
 4. **Asset specs.** Before generation, list the assets this task needs and settle the choices that
    change the result. For each: family, role size, the reference it uses, the one-line prompt

package/plugins/kiro/skills/fp-playtest/SKILL.md

@@ -21,7 +21,7 @@ person: it changes nothing in the game, and its steps are suggestions they pick
    seat. Each prompt carries those numbers as facts F1, F2, … to read before the frames (Scenario's
    numbers first, then eyes); the report says which facts each seat cited.
 4. Run every seat now, in parallel in the foreground (a background seat answered after a session
-   had already ended, Lantern Night S3), each as a fresh agent given only the contents of its prompt
+   had already ended, in one game's third session), each as a fresh agent given only the contents of its prompt
    file: one per `seats/<name>.md`, per `versus/<name>.md` and `fidelity/fidelity.md` when printed (and `fidelity/ui.md` from step 5), each a general-purpose
    agent (the `critic` agent's own format would override the prompt's), and the `player` agent with
    `player.md` at phone size. The Mobile QA seat (`mobile/mobile-qa.md`, the `mobile-qa` agent: is
@@ -45,7 +45,7 @@ person: it changes nothing in the game, and its steps are suggestions they pick
    (`.funtools/playtest/history.json`: panel axes, the experience bar, the blind player, minutes of
    real play, fidelity per moment and the AD lines, every round), with each drop marked. When it
    opens with "Look at the captures first", open those frames before trusting any score: a view
-   that never reached its beat is scored as the wrong game (Held Note scored 4.9 on views stuck at
+   that never reached its beat is scored as the wrong game (one game scored 4.9 on views stuck at
    the opening shot, 6.55 once they reached their beats). A thing on the list that is lost is a
    regression: the report leads with it and exits 1, the flow makes putting it back the round's first
    step, and only the owner takes an item off (`playtest keep --drop K<n> --by owner "<their words>"`).

package/plugins/kiro/skills/funpixel-3d/references/bake-off.md

@@ -1,7 +1,7 @@
 # The model bake-off: several candidates, one judged against the master
 
-Held Note tried its hero three ways (three providers' takes of the same front picture) and picked
-from turntable sheets; Gallery Heist made two to four models of each crew member before one held.
+One game tried its hero three ways (three providers' takes of the same front picture) and picked
+from turntable sheets; another made two to four models of each crew member before one held.
 A model is the most expensive asset a game makes, and the first one is rarely the keeper. The
 bake-off makes the choice cheap to see and puts it on record.
 
@@ -41,7 +41,7 @@ never before (step 5 of the skill).
 
 ## What it showed on real files
 
-On Held Note's own models, rendered by the bench: each prop's model was ranked first against its own
+On the first game's own models, rendered by the bench: each prop's model was ranked first against its own
 reference picture, by 0.03 to 0.13 over the next (crate, door, lockers, canister, bell); the three
 providers' takes of the hero scored within 0.03 of each other, and well above any prop. The team
 kept the Rodin take for reasons a silhouette cannot see (triangle budget, separable limbs). That is

package/plugins/kiro/skills/funpixel-3d/references/characters.md

@@ -44,7 +44,7 @@ pins up to 8 colours. It changes the paint, not the shape: a knight is not a res
 
 ## When the game poses its own skeleton
 
-Held Note (a three.js horror game, 29 Sep 2026) posed a code skeleton from its sim every frame, and
+A three.js horror game (29 Sep 2026) posed a code skeleton from its sim every frame, and
 its enemies lose limbs, so neither the library nor an auto-rig fit: their bones carry their own
 names, rolls and rest rotations, and none splits a body for severing. What it did instead, run in
 local Blender:

package/plugins/kiro/skills/funpixel-3d/references/hero-route.md

@@ -4,10 +4,10 @@ The default path for every hero of a 3D game: the player, the rivals, the bosses
 prop the player stares at. A choice the person locked (a code-built toy style, a budget of zero
 credits, a library character) overrides it. Environment and background may stay procedural.
 
-Why it exists: Saltwake, a phone racer, was offered `generate_3d_model` in three creator rounds
+Why it exists: a phone racer was offered `generate_3d_model` in three creator rounds
 and never called it. Its boats and world were boxes, cones and extrusions; stills of tidy
 primitives read as a style, and the blind panel scored the look above 7 while the owner saw "a
-shapes game". Fold Room, rooms of code geometry, reached 7.28 against Monument Valley 2's 8.60.
+shapes game". Another game, rooms of code geometry, reached 7.28 against Monument Valley 2's 8.60.
 
 ## Declared, proven, or named
 
@@ -40,7 +40,7 @@ numbered fact. Three honest states for a code-built hero:
    ([levels.md](levels.md)): 300K triangles on Meshy 7.1 (the default engine, 2048 px maps,
    about 160 credits), 500K faces and 4096 px PNG maps with `engine: "hunyuan"` (about 135), or
    500K triangles and 4096 px PBR maps with `engine: "rodin"` (about 240; the hard-surface take:
-   Held Note kept Rodin's crate, door, lockers and bell). A rigged hero stays `standard`, and
+   one game kept Rodin's crate, door, lockers and bell). A rigged hero stays `standard`, and
    never Rodin (it has no rig).
 
    Rodin 2.5 (`engine: "rodin"`) runs only when named and never falls back: static only (with
@@ -51,12 +51,12 @@ numbered fact. Three honest states for a code-built hero:
    `raw: true`: the engine's file untouched (the optimized copy clamps maps to 1024 px), then
    cut it to the device yourself. `npx @funpixel/tools gen model3d --image-asset front.png
    --back-asset back.png --style hero --engine hunyuan --raw` does all of it from the CLI.
-   **Fidelity against the views** (dont-die's Corer, 10 Oct 2026, `npx @funpixel/tools fidelity`):
+   **Fidelity against the views** (one game's hero, 10 Oct 2026, `npx @funpixel/tools fidelity`):
    from one view the model is a slab whose end views score ~46%; four views (front, back, both
    ends) fix the depth. Projecting the views onto the mesh was the largest single gain (a profile
    84 → 91%), and generation plus projection plateaued near 73% (Hunyuan from four views 72.8%,
    Meshy hero 73.3%: Meshy keeps profiles sharper, Hunyuan the ends). Check the views agree
-   first: `fidelity` names views no one object can match (the Corer's drawings drew the drum two
+   first: `fidelity` names views no one object can match (the hero's drawings drew the drum two
    sizes, which capped even a hand-built mesh at ~74%). For 95% (reached, 95.0% mean), the studio
    order: block the shape in Blender from primitives measured off the views (6.4K faces); render
    the plain mesh in four orthographic views; `gen edit` each render into a paintover in the house

package/plugins/kiro/skills/funpixel-3d/references/level-spec.md

@@ -93,7 +93,7 @@ A heist in a two-room cottage with a garden:
 ## Common mistakes
 
 - Colliding against the art: a character snags on every table leg and falls through foliage.
-- Colliders for the hero but not the camera: Held Note's shoulder camera entered walls six
+- Colliders for the hero but not the camera: one game's shoulder camera entered walls six
   times in one blind phone run and lost her; cast it against the walls and planes at the kit's faces.
 - Dressing before walking the blockout: every prop moved twice.
 - A marker the code asks for that the spec never declared.

package/plugins/kiro/skills/funpixel-3d/references/levels.md

@@ -1,6 +1,6 @@
 # Quality levels: one source, a cut per device
 
-Held Note decimated every model once for every device (the station kit 150,000 → 4,000
+One game decimated every model once for every device (the station kit 150,000 → 4,000
 triangles, characters → 13,000, props → 1,200–3,000, textures 4096² → 512–1024²). Next to its
 target frames it read flat and melted on a desktop that had headroom to spare, and the untouched
 generations survived only in a git-ignored temporary folder. Levels are the other way to do it:
@@ -40,7 +40,7 @@ failure: the level is the most the source allows at that quality.
 Where the source lives is your call. A generation made with `gen model3d` keeps the provider's
 untouched GLB in `.funtools/sources/models/` (never published); the platform keeps its own copy
 beside the shipped one. Cut from that, never from a file you already decimated: a level cut from
-Held Note's shipped walker (18K triangles) reached only 16K on phone, because the detail it needed
+its shipped walker (18K triangles) reached only 16K on phone, because the detail it needed
 to trade was already gone.
 
 A `hero` generation (`style: "hero"`) is the source this is built for, cut down per device
@@ -67,7 +67,7 @@ saver or a low GPU gets `phone`; `high` needs a GPU known to be high
 (`levelSignals(renderer.getContext())` reads it) and 8 GB; everything else `desktop`. A phone never
 downloads the desktop set. No manifest (a model never cut) loads the plain file, as before.
 
-## Measured on Held Note's sources (29 Sep 2026)
+## Measured on that game's sources (29 Sep 2026)
 
 Release build of the engine on a shared M-series laptop; the time is mostly KTX2 texture encoding.
 

package/plugins/kiro/skills/funpixel-3d/references/light-and-places.md

@@ -1,7 +1,7 @@
 # Light, dressing and places: directing the world
 
-A world reads as shapes when it is evenly lit, sparsely dressed and the same everywhere. Gallery
-Heist's plan was dark and moonlit, with spot-lit art and deep shadow, and its first build came back
+A world reads as shapes when it is evenly lit, sparsely dressed and the same everywhere. One heist
+game's plan was dark and moonlit, with spot-lit art and deep shadow, and its first build came back
 bright and evenly lit. Silt & Signal, by contrast, puts 42k instanced flowers along a clear road and
 gives each of its seven places its own light. The 3D starter (`funtools init --framework three-world`)
 directs all three from data, so you change values instead of writing a renderer:
@@ -116,7 +116,7 @@ palette (`sky-top`, `sky-horizon`, `ground`, `ground-2`, `stone`, `accent`, `glo
 (`grass`, `sand`, `cobble`, `flagstone`, `snow` or `moss`); its kit; its landmark; its road; its
 `density` target; and its `target` picture when the plan has one.
 
-Gallery Heist's spec is the model for a row: each room has a size and shape, a material, an era, a
+One heist game's spec is the model for a row: each room has a size and shape, a material, an era, a
 light and a colour, and differs from the others in all five. For example:
 
 - "Long Gallery, oxblood velvet, cool moonlight from the lunette against warm gold picture lights"

package/plugins/kiro/skills/funpixel-3d/references/painted-target.md

@@ -1,19 +1,19 @@
 # From a painted target to a 3D scene that holds up
 
-Why this exists: Blue Freight was built twice from one plan (1 Oct). In both builds the title and
+Why this exists: one game was built twice from one plan (1 Oct). In both builds the title and
 menus reached their painted targets, and the 3D walk stayed a flat, empty plane under a plain
 sky: a tech demo. In one build the cut-out hero's legs and arms drifted off the body as she
 walked. The walk is the first minutes of play, the stretch that decides whether people stay (the
-hook). Held Note shows the way that worked: every look pass ended in fidelity strips at fixed
-framings, today beside the target, and the next pass worked on the largest gap. Saltwake (boats of
-boxes and cones handed back as finished) and Fold Room (57 code primitives) show what happens
+hook). Another game shows the way that worked: every look pass ended in fidelity strips at fixed
+framings, today beside the target, and the next pass worked on the largest gap. A racer (boats of
+boxes and cones handed back as finished) and a puzzle game (57 code primitives) show what happens
 when nobody puts the game beside the picture.
 
 ## Read the target first (five minutes, written down)
 
 Before any code, measure the target frame and write the answers beside it in the GDD's place row:
 
-| Read | Example (Blue Freight, f3_walk) |
+| Read | Example (one game, f3_walk) |
 |---|---|
 | Horizon height, share of frame from the top | 0.42 |
 | Hero height, share of frame | 0.22, standing left of centre |
@@ -93,7 +93,7 @@ point at a closed gap in its strip did not close it.
 
 # A walk that reads as a person, in one piece
 
-The owner, after Blue Freight: "better walking animations, not like a robot; smooth movement like
+The owner, after that game: "better walking animations, not like a robot; smooth movement like
 us humans." A robot walk is limbs swinging at a constant speed about fixed points while the body
 glides. A person's walk is the body falling forward and catching itself.
 
@@ -150,7 +150,7 @@ size on screen wins, whichever took less work.
 ## Many painted cut-outs, one draw call
 
 A painted world of props, creatures and folk drawn as one `THREE.Sprite` each costs a draw call
-each: the Blue Freight build reached 164 against its budget of 150 with about 200 cut-outs. The 3D
+each: one build reached 164 against its budget of 150 with about 200 cut-outs. The 3D
 world starter's `src/cutouts.ts` draws every cut-out that shares an atlas as one instanced mesh, so
 300 cut-outs are one draw call. Cut the figures with `npx @funpixel/tools cut sheet.jpg` (clean
 alpha, no paper or floor patches), build the atlas in the page with `atlasFrom([...pngs])` (or use

package/plugins/kiro/skills/funpixel-3d/references/three-loading.md

@@ -48,8 +48,8 @@ root.traverse((o) => { const m = (o as THREE.Mesh).material as THREE.MeshStandar
 
 A free HDRI, when the game has one, replaces `RoomEnvironment` as both lighting and sky.
 
-Judge the result in the game's own light, not the generator's preview. Held Note (a dark three.js
-horror game, 29 Sep 2026) tuned every material in its loader rather than in the files: the hero's
+Judge the result in the game's own light, not the generator's preview. A dark three.js
+horror game (29 Sep 2026) tuned every material in its loader rather than in the files: the hero's
 suit to metalness 0.3 (it read as chrome under the torch), the crew's cloth to metalness 0 and 72%
 albedo (it burnt white in the beam). Its generated textures read near-black, and lifting the
 enemy's albedo ×1.9 made it go pure white a few metres into a spotlight: a colour above 1 has
@@ -169,13 +169,13 @@ function floorOffset(mixer: THREE.AnimationMixer, clip: THREE.AnimationClip) {
 
 Optimized GLBs are often quantized: positions stored as normalized int16, the real scale carried in
 the node. Baking a node transform into that geometry (`geometry.applyMatrix4`) clamps every vertex
-to ±1; Held Note's 3 m wall modules stood 1 m tall for a whole pass. Keep transforms in the object
+to ±1; one game's 3 m wall modules stood 1 m tall for a whole pass. Keep transforms in the object
 or instance matrix. The same quantization moves each mesh's scale into its node, so a part scaled
 at runtime (a gauge's fill) has that scale baked back first, or `scale.y = fraction` is not literal.
 
 A skinned mesh keeps `frustumCulled = false` (its bind-pose bounds lie), so nothing culls a crowd
 of them: every one animates and casts shadows everywhere. Cull them by distance and screen yourself
-(skill `funpixel-art`, its frames reference, has Held Note's numbers).
+(skill `funpixel-art`, its frames reference, has one game's numbers).
 
 Generated models usually face +Z, but not always. Wrap each in a group; yaw the inner model once
 at load (a vehicle whose posed size has x greater than z was authored sideways), and keep steering

package/plugins/kiro/skills/funpixel-3d/references/unity.md

@@ -1,17 +1,17 @@
 # 3D models from generator to Unity
 
-A 3D model can fail in Unity without an error. glTFast (the glTF importer, package `com.unity.cloud.gltfast`) decodes textures embedded in a GLB to raw RGBA32, 4–16 MB each, and imports a web GLB packed with meshopt or WebP as nothing. That made the 3D games 3–5× bigger than the 2D ones: Noodle Nights was 386 MB before this pipeline and 106 MB after. This skill takes a model from the generator to a compressed, collidable asset.
+A 3D model can fail in Unity without an error. glTFast (the glTF importer, package `com.unity.cloud.gltfast`) decodes textures embedded in a GLB to raw RGBA32, 4–16 MB each, and imports a web GLB packed with meshopt or WebP as nothing. That made the 3D games 3–5× bigger than the 2D ones: one idle game was 386 MB before this pipeline and 106 MB after. This skill takes a model from the generator to a compressed, collidable asset.
 
 ## Tools
 
-The studio's `com.joydle.core` package carries the texture import rule, `TextureBudget` (funpixel-unity-game, `references/studio-packages.md`): a texture named `model__basecolor.png` (or `__normal`, `__mr`, `__emissive`) under an `Art/` or `Models/` folder imports as ASTC 6×6 with mipmaps, sRGB only for base colour and emissive, at most 512 under `Food/`, `Props/` or `Characters/` and 1024 elsewhere. Not shipped by the kit or the package: the Unity starter, its checks and the studio scripts (`blender_prep.py`, `render_glb.py`, a collision audit, a size audit). `TextureBudget` imports `__normal` maps as Default (field report, 10 Oct). Do the rest with what exists:
+Not shipped by the kit: the Unity starter, its checks and the studio scripts (`blender_prep.py`, `render_glb.py`, a collision audit, a size audit). Do the rest with what exists:
 
-- Generate into the project: `npx @funpixel/tools gen model3d "<subject>" --image-asset concept.png --unity .` (after `npx @funpixel/tools login`) asks for the engine's own GLB (`--raw`: glTFast reads no Draco, meshopt or KTX2 without three more packages), splits it into `.gltf` + `.bin` + `model__basecolor`/`__normal`/`__mr` textures in `Assets/_Game/Generated/Models/<name>/` (the studio's `glb_split.py`, ported), and writes an import rule that sets those textures once, ASTC 6×6 at most 1024, sRGB only for colour, and keeps `__normal` a NormalMap over `TextureBudget`. Checked on 6000.6 with a Meshy and a Hunyuan model: meshes and textures import. The studio's `gen_3d.py` calls fal with a `.env` key: no metering, no cost log.
+- Generate into the project: `npx @funpixel/tools gen model3d "<subject>" --image-asset concept.png --unity .` (after `npx @funpixel/tools login`) asks for the engine's own GLB (`--raw`: glTFast reads no Draco, meshopt or KTX2 without three more packages), splits it into `.gltf` + `.bin` + `model__basecolor`/`__normal`/`__mr` textures in `Assets/_Game/Generated/Models/<name>/` (the studio's `glb_split.py`, ported), and writes an import rule that sets those textures once, ASTC 6×6 at most 1024, sRGB only for colour, and keeps `__normal` a NormalMap. Checked on 6000.6 with a Meshy and a Hunyuan model: meshes and textures import. The studio's `gen_3d.py` calls fal with a `.env` key: no metering, no cost log.
 
 - Prepare in Blender through the kit's bench: `npx @funpixel/tools model --local normalize hero.glb --height-m 1` (unit height), `model --local decimate hero.glb --target-triangles 3000`, `model --local inspect hero.glb` (triangle count). The hosted `inspect_model`, `optimize_model` and `fracture_model` do the same on a model a job made. Joining meshes and moving the origin to the base centre are not in the bench; do them in Blender by hand or in your own script.
 - Proof render: the hosted `render_model`, or `npx @funpixel/tools model --local render hero.glb --frames 3`, gives the three angles.
 - Split a GLB for Unity with gltf-transform (`gltf-transform copy model.glb model.gltf` writes `.gltf` + `.bin` + texture files); name the textures by role (`model__basecolor`, `model__normal`, `model__mr`) so the import rule can find them. gltf-transform also decodes web GLBs (meshopt + WebP).
-- Name split textures by role and keep them under `Art/` or `Models/`, so `TextureBudget` finds them; a game without the package writes the same rule as an `AssetPostprocessor` in `Assets/Editor/`, or uses the one `gen --unity` writes.
+- Name split textures by role and keep them under `Art/` or `Models/`, so the import rule finds them: write it as an `AssetPostprocessor` in `Assets/Editor/`, or use the one `gen --unity` writes.
 - Collision and size audits are your own Edit Mode tests until the checks ship: compare each prop's `Renderer.bounds` with its `Collider.bounds`, and read the Editor's build report for texture formats.
 
 Checks: `texture_audit`, `drawn_vs_solid`, `glb_import`, `tri_budget` and `lfs_audit` are proposed, not built (partial versions exist in single games). Until then `model --local inspect` gives the triangle count.
@@ -45,7 +45,7 @@ Checks: `texture_audit`, `drawn_vs_solid`, `glb_import`, `tri_budget` and `lfs_a
    | Kind | Setting |
    |---|---|
    | Model textures | ASTC 6×6, mipmaps, sRGB only for basecolor and emissive, max 512 (props) or 1024 (stalls) |
-   | 3D models | default glTFast import of the split `.gltf`; no LODs except The Hot Gates' mid LOD |
+   | 3D models | default glTFast import of the split `.gltf`; no LODs except one game's mid LOD |
    | Rigged characters (FBX) | Generic rig, root `Hips`, Loop Time on, Apply Root Motion off, in-place clips at 30 fps |
 
 8. Confirm the import (`glb_import`): every GLB yields at least 1 mesh with more than 0 vertices, and no `.webp` or `.woff2` sits under Assets.
@@ -55,24 +55,24 @@ Checks: `texture_audit`, `drawn_vs_solid`, `glb_import`, `tri_budget` and `lfs_a
 12. Audit the build (`texture_audit`): 0 unwhitelisted RGBA32 textures, RGBA32 total under 1 MB. Mipmapped textures must be power of two; Unity 6000.6 ships a mipmapped non-power-of-two texture as RGBA32 even with an ASTC override.
 13. Store baked binary data as `.bytes` in LFS (`lfs_audit`: 0 tracked binaries over 500 KB outside LFS, no untracked paid art).
 
-Rigs: one shared skeleton gives one Animator for the whole cast. Large crowds use no rigs at runtime: The Hot Gates bakes rigged GLBs to vertex-animation textures.
+Rigs: one shared skeleton gives one Animator for the whole cast. Large crowds use no rigs at runtime: one game bakes rigged GLBs to vertex-animation textures.
 
 ## Worked example
 
-Noodle Nights (a new 3D idle game), done with the studio's own scripts (proposed for the kit). Steps 2–4 are the report's general pipeline; it does not log them per game.
+A new 3D idle game, done with the studio's own scripts (proposed for the kit). Steps 2–4 are the report's general pipeline; it does not log them per game.
 
 1. Props and stalls as generated GLB; characters as Meshy-rigged FBX (the auto-rig survived import 7 of 7).
 2. Blender prep at 3,000 triangles: joined, unit height, origin at base centre.
 3. A 3-angle proof render and the triangle count.
 4. Split: `.gltf` + `.bin` + `model__basecolor`, `model__normal`, `model__mr` PNGs.
 5. The texture import rule: ASTC 6×6, max 512 for props and 1024 for stalls.
-6. Result: data 315 → 61 MB; the app 386 → 106 MB with the build size settings also on. Porcelain Panic went 229 → 75 MB.
+6. Result: data 315 → 61 MB; the app 386 → 106 MB with the build size settings also on. Another game went 229 → 75 MB.
 
 ## Common mistakes
 
-- Importing a web GLB as it is. Dawg Ball's 12 heads "did not import at all", with no error.
-- A prop with no collider, or art bigger than its collider. 42 Pocket Crew props could be walked through; Dead Letter's Paperweight art was 54 px taller than its collider; a Dawg Ball head drawn 1.15× its hitbox was removed.
-- `shader_feature` on a runtime-created material. Pocket Crew's instanced sets drew at the origin on device.
-- Baked data as serialised YAML in git. The Hot Gates' vertex-animation crowd assets are about 70 MB of YAML (minotaur 13.0 MB, cyclops 11.8 MB), and every re-bake adds about 70 MB to history.
+- Importing a web GLB as it is. One game's 12 heads "did not import at all", with no error.
+- A prop with no collider, or art bigger than its collider. 42 props in one game could be walked through; another's paperweight art was 54 px taller than its collider; a head drawn 1.15× its hitbox was removed.
+- `shader_feature` on a runtime-created material. One game's instanced sets drew at the origin on device.
+- Baked data as serialised YAML in git. One game's vertex-animation crowd assets are about 70 MB of YAML (minotaur 13.0 MB, cyclops 11.8 MB), and every re-bake adds about 70 MB to history.
 - Paid generations outside LFS: about 840 MB lived on one Mac.
-- Trusting Meshy's Idle preset. It bowed the head to the chest (Noodle Nights) and was re-keyed in Blender.
+- Trusting Meshy's Idle preset. It bowed the head to the chest and was re-keyed in Blender.

package/plugins/kiro/skills/funpixel-art/references/animation.md

@@ -38,7 +38,7 @@ is edited from, so the frames stay that character.
   the distinct poses per cycle.
 - The frames share one scale and one ground line; the feet are each frame's anchor.
 - The sheet draws every frame from the side or the front. An actor seen from above (a maze
-  chase, a twin-stick arena) has no ground line, and a Riad Rush run got a side-view gecko back
+  chase, a twin-stick arena) has no ground line, and one run got a side-view gecko back
   for a top-down maze (57 credits, discarded). Give such an actor its two to four key poses as
   `edit_image` pose edits of the top-down sprite (below), stepped at the stride rate.
 - Measured (the studio's animation evals): the character holds across frames, but each

package/plugins/kiro/skills/funpixel-art/references/cast.md

@@ -1,7 +1,7 @@
 # The cast: lock first, check second
 
-A game with a cast draws each member dozens of times: Gallery Heist drew its keepers 6 to 13 times
-each and its crew in rest, brace and cover poses; Held Note kept front, back and left pictures of
+A game with a cast draws each member dozens of times: one heist game drew its keepers 6 to 13 times
+each and its crew in rest, brace and cover poses; another kept front, back and left pictures of
 every character. What kept them on model was never a better sentence. It was the same picture
 attached to every call, and a look at each result against that picture before it was kept.
 
@@ -68,6 +68,6 @@ measure on any picture.
 ## What the numbers cannot see
 
 They catch a recolour, a lost signature colour, the wrong subject and a changed build. Two crew
-members in one uniform read close by numbers (Gallery Heist's Smudger and Carrier: 58% outline
+members in one uniform read close by numbers (one heist game's two crew members: 58% outline
 overlap, the same colours). Named features (the face, the earring, what the hand holds) are the
 identity seat's: `npx @funpixel/tools judge identity --concept design/cast/ren/master.png <views…>`.

package/plugins/kiro/skills/funpixel-art/references/effects.md

@@ -57,7 +57,7 @@ what each one measured. Pick what serves the look the game chose; a clean flat s
 9. **In a whole 3D game, read the slow frames.** Averages hide hitches: read p95/p99 at a named
    beat (the first fight, not the whole run), and name what appeared on each slow frame (a shader
    compile, a texture upload) before fixing it. Warm-up, culling skinned actors, a pixel budget,
-   pacing to the refresh, and the leaks Held Note met: [frames.md](frames.md).
+   pacing to the refresh, and the leaks one game met: [frames.md](frames.md).
 
 ## Worked example
 
@@ -76,7 +76,7 @@ textures; at resolution 1 it held 4.1 MB, and on the software renderer its frame
 - A custom Pixi filter that redeclares `uInputSize` in the fragment shader: the precisions differ
   from the vertex stage and the program fails to link (a black screen). Pass a varying instead.
 - `EffectComposer` without `OutputPass`: colours come out dark and tone mapping is skipped.
-- A white starburst or full-screen flash on contact: Particle Rush's (Oct 2026) read as glare, one 38% clipped.
+- A white starburst or full-screen flash on contact: one racer's (Oct 2026) read as glare, one 38% clipped.
   A small warm glow at the contact point, about 0.16 s, answers the hit.
 - Dither or halftone transparency in a shader: at phone size it reads as a glitch. Fade in broad, slow bands or
   real alpha. To find which module owns a fault, capture with one module off

package/plugins/kiro/skills/funpixel-art/references/frames.md

@@ -2,13 +2,13 @@
 
 The recipe lab ([cost](cost.md)) measures one effect in a small scene. A whole game adds things a
 lab never meets: first-use compiles, a crowd of skinned actors, level rebuilds, big retina windows
-and displays faster than 60 Hz. This is what Held Note (a three.js third-person horror game, 29 Sep
+and displays faster than 60 Hz. This is what one game (a three.js third-person horror game, 29 Sep
 2026, `design/PERF.md` in its repo) measured, and what each fix bought. The numbers are that game's
 on that machine; the causes recur.
 
 ## Smooth is a distribution, not an average
 
-At 78 fps average Held Note still stuttered. Read p95, p99 and the worst frame, and where the slow
+At 78 fps average that game still stuttered. Read p95, p99 and the worst frame, and where the slow
 frames land. Then name each slow frame's cause before changing anything: on a hitch frame, read
 `renderer.info` for what appeared (new shader programs, textures, geometries). Every hitch it
 found had a cause that showed there.
@@ -21,7 +21,7 @@ Profile vsync-capped, as a player sees it. An uncapped run (`--disable-frame-rat
 the game's own refresh detection into cutting resolution at 2.5 ms frames. And profile on a machine
 nobody is playing on: films and profilers share the GPU and read as lag to the player.
 
-## What Held Note found, and what each fix bought
+## What that game found, and what each fix bought
 
 | Symptom | Cause (measured) | Fix |
 |---|---|---|
@@ -44,13 +44,13 @@ Results on the same recorded run: desktop 1600×900 @2x worst frame 87 → 29 ms
 A 1950×1090 window at pixel ratio 1.5 is 4.8 M pixels through AO, depth of field and bloom:
 GPU-bound (p99 26 ms). On a 120 Hz display, 9 ms frames flip between 8 and 16 ms and judder.
 
-- **A pixel budget** caps the ratio by pixel count (Held Note: 2.6 M on desktop, 1.3 M on a phone);
+- **A pixel budget** caps the ratio by pixel count (that game: 2.6 M on desktop, 1.3 M on a phone);
   the DOM HUD stays at full retina.
 - **Pace to the refresh.** Detect the refresh from the fastest frames, judge each second's p90
   against that slot, and when 120 cannot hold, lock to 60 (render every other refresh) before
   lowering resolution.
 - **Hysteresis.** Each resolution change rebuilds the post-processing targets (41 textures, a 70–100
-  ms frame), so an oscillating scaler stutters every few seconds. Held Note's rule: no step up within
+  ms frame), so an oscillating scaler stutters every few seconds. Its rule: no step up within
   12 s of a step down, five fast seconds to earn one, none after two downs.
 
 Result: 119.2 fps on a 120 Hz display at 1950×1090 @2x, p99 9.4 ms, worst 17.5 ms, zero hitches.
@@ -74,7 +74,7 @@ with its animations paused, removed it.
 
 ## When something glows that should not
 
-"Anything that looks like a white ball is a light" held four times in Held Note: the torch's
+"Anything that looks like a white ball is a light" held four times in that game: the torch's
 hotspot on a close surface, the beam cone seen end-on, coral pushed past the bloom's white point,
 and the worst one, an additive ray-marched beam seen down its own axis. From the camera behind her,
 the view ray ran down the whole lit cone and eight summed samples bloomed into a white disc that

package/plugins/kiro/skills/funpixel-art/references/judging-frames.md

@@ -1,6 +1,6 @@
 # Judging frames against the targets: a fixed rubric, fixes by module, eye comfort
 
-From Particle Rush (Oct 2026), a Unity 6 3D racer built by several module agents (world, racers, levels) and one
+From a Unity 6 3D racer (Oct 2026) built by several module agents (world, racers, levels) and one
 integrator. An independent judge scored real captures against the painted targets every round; what follows is
 what held up, with its numbers. `funtools score` measures the same frames (layout, palette and light, density,
 comfort); this is the judge that reads what numbers cannot.
@@ -16,7 +16,7 @@ comfort); this is the judge that reads what numbers cannot.
 
 - **The same rubric every round**, written before seeing the frames, so a score moves only when a frame changed.
 - **Full-resolution phone captures from the real build** (the player on the target device size, not the editor, not
-  a web stand-in): Particle Rush judged 1172×2532 frames; half-size shots hid the material detail being scored.
+  a web stand-in): the racer judged 1172×2532 frames; half-size shots hid the material detail being scored.
 - **Per frame:** a total, the four category scores, the change since last round, and one eye-comfort word
   (yes, mild, glare, busy, no): could a person look at it for a minute without strain?
 
@@ -26,7 +26,7 @@ Every fix names the module that owns it, `[WORLD]`, `[RACERS]`, `[LEVELS]` (or t
 frame, the pixel region and the number: "[WORLD] the sun bloom washes out the upper right (11% clipped): bloom
 intensity −50%, exposure −0.4 EV". The integrator routes each tag to that module's agent (its lane, where
 `funtools lanes` runs them), so no agent reads another's list. End with the five changes that would raise the average most,
-each with its expected gain; Particle Rush's round-2 list predicted 76–80 from 64.
+each with its expected gain; the racer's round-2 list predicted 76–80 from 64.
 
 **Find the owner before assigning a fault.** Capture the same frame with one module turned off (a launch flag
 per module: no world dressing, no racer effects). The fault that disappears belongs to the module that was off;
@@ -34,7 +34,7 @@ a stripe under the racer that stays with the effects off is not the effects agen
 
 ## Read the categories, not only the total
 
-Particle Rush's round 2 rose 55.6 → 64.2, but composition gave +5.1 and effects +2.2 while light gave +0.7 and
+The racer's round 2 rose 55.6 → 64.2, but composition gave +5.1 and effects +2.2 while light gave +0.7 and
 detail +0.6: the gain came from removing noise (a white halo, crossing speed lines, a fourth trail), not from
 adding quality. Calm is not finished. When light and detail stall, give materials and lighting a round of their
 own (per place: a key light, a rim, a regrade, authored hero surfaces, a bake-off of each hero asset against
@@ -48,17 +48,17 @@ frames than the targets are the goal, as long as the quality matches.
 - `funtools score` prints each frame's **busyness** (the mean brightness step between neighbouring pixels on a grey
   copy 360 px on its short side) and **clipped share** (pixels at luma ≤ 2 or ≥ 253) beside its target's, and
   stamps the zero board's `comfort` counter. It warns, never fails: over 14, over 1.25× the targets' busiest, or
-  over 6% clipped. Particle Rush's painted targets read 9.2–15.4 there and its web frames 6.9–8.5; our liked
-  games' frames 2.0–11.9; Gallery Heist's room read 7.8% clipped before its light round and 0 after.
+  over 6% clipped. The racer's painted targets read 9.2–15.4 there and its web frames 6.9–8.5; our liked
+  games' frames 2.0–11.9; one heist game's room read 7.8% clipped before its light round and 0 after.
 - A calm frame has room for detail: add mid-ground surface detail at about half the target's density, low
-  contrast and slow (Particle Rush's near road, on its judge's own scale: a bottom-quarter gradient of about 3,
+  contrast and slow (the racer's near road, on its judge's own scale: a bottom-quarter gradient of about 3,
   against 1–2 then and 5–6 in the targets).
 - Clip sources are fixes, not taste: blown bloom, a white flash, an emissive that clips to white instead of
   keeping its colour (clamp it).
 
 ## Framing calls are the owner's
 
-A rubric's framing numbers are a judge's proposal. Particle Rush's rubric asked for the racer at 80% of the frame
+A rubric's framing numbers are a judge's proposal. The racer's rubric asked for the racer at 80% of the frame
 width; the owner settled on about 40%. Record the owner's number as a rule in the GDD (a tuning row), tell the
 judge it is fixed and not to mark it down, and judge what fills the space the smaller hero leaves instead. Ask
 the owner before a judge's hero size, camera height or crop becomes a fix.

package/plugins/kiro/skills/funpixel-art/references/look.md

@@ -23,7 +23,7 @@ game, the moves below are what held our bar games' looks together.
    procedural proven by a rendered study; "primitives for now" is a stand-in, not a route).
    At the first look the world's kit stands beside the hero: sheets of its structures, ground,
    props and living cast, cut (`npx @funpixel/tools cut`) before the slice is built from them;
-   without it a fresh Blue Freight build coded its world from shapes.
+   without it one fresh build coded its world from shapes.
 2. **Write five AD rules.** The critic panel reads them:
    each checkable in a frame (colour roles, outline weight, light, material, actor readability at
    a stated phone size); no universal percentage for hero size.
@@ -36,7 +36,7 @@ game, the moves below are what held our bar games' looks together.
    paying for new art. Check phone and desktop; a rule revised to excuse a defect stops measuring anything.
    For a game with a moment ladder, a target frame per moment and captures of the same seconds
    from a recorded run make a loop: name the biggest difference, fix it, recapture. Judge
-   generated models under the game's own light, where Held Note's near-black textures were
+   generated models under the game's own light, where one game's near-black textures were
    lifted into white blow-outs. Both, with what they found:
    [prompts.md](prompts.md#target-frames-at-moments-and-the-loop-that-closes-the-gap).
    Match the targets' quality, not their density (`score` warns on a busy or clipped frame); the rubric,
@@ -55,7 +55,7 @@ game, the moves below are what held our bar games' looks together.
   a target, hero or key art where the comparison is worth its cost.
 - Before the game exists, `npx @funpixel/tools look --sheet` puts every sprite at play heights
   (24, 48, 96 px) on a neutral band and on the real ground colour (`roles.ground` or `--ground`)
-  and measures each against it. The Hot Gates' sheet found its terracotta army vanishing on the
+  and measures each against it. One game's sheet found its terracotta army vanishing on the
   pass floor at 24 px before any game code.
 - A pixel-art look can be exact rather than imitated: `pixelArt` (scale, palette) in
   `funpixel.json` has `assets process` and `gen` snap every picture to the grid and palette, and
@@ -89,7 +89,7 @@ funpixel.json `art3d` declares it with its reason and a proof frame (skill `funp
 
 ## Worked example
 
-Fold Room's sandstone rooms wore dark pills: `look --hud` read system type, 20 dark plates and
+One game's sandstone rooms wore dark pills: `look --hud` read system type, 20 dark plates and
 the scaffold's glyphs. A `## UI` section chose sandstone plaques, a carved face and an inked icon
 family; a generated plate went in through `border-image`.