picopilot 0.1.3 → 0.1.4

package/dist/engine/scaffold/scaffold.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"scaffold.d.ts","sourceRoot":"","sources":["../../../src/engine/scaffold/scaffold.ts"],"names":[],"mappings":"AAiBA;;;;GAIG;AACH,eAAO,MAAM,gBAAgB,sBAAsB,CAAC;AAEpD;;;;GAIG;AACH,wBAAgB,MAAM,IAAI,MAAM,CAM/B;AAED;;;;;GAKG;AACH,wBAAgB,OAAO,IAAI,MAAM,CAehC;AAED,2FAA2F;AAC3F,wBAAgB,aAAa,IAAI,MAAM,CAEtC;AAED;;;;;;;;GAQG;AACH,wBAAgB,QAAQ,IAAI,MAAM,CAmNjC;AAED;;;;GAIG;AACH,MAAM,WAAW,YAAY;IAC5B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CACzB;AAED;;;;;;GAMG;AACH,wBAAgB,aAAa,IAAI,YAAY,EAAE,CAO9C"}
+{"version":3,"file":"scaffold.d.ts","sourceRoot":"","sources":["../../../src/engine/scaffold/scaffold.ts"],"names":[],"mappings":"AAiBA;;;;GAIG;AACH,eAAO,MAAM,gBAAgB,sBAAsB,CAAC;AAEpD;;;;GAIG;AACH,wBAAgB,MAAM,IAAI,MAAM,CAM/B;AAED;;;;;GAKG;AACH,wBAAgB,OAAO,IAAI,MAAM,CAehC;AAED,2FAA2F;AAC3F,wBAAgB,aAAa,IAAI,MAAM,CAEtC;AAED;;;;;;;;GAQG;AACH,wBAAgB,QAAQ,IAAI,MAAM,CAkOjC;AAED;;;;GAIG;AACH,MAAM,WAAW,YAAY;IAC5B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CACzB;AAED;;;;;;GAMG;AACH,wBAAgB,aAAa,IAAI,YAAY,EAAE,CAO9C"}

package/dist/engine/scaffold/scaffold.js

@@ -141,6 +141,21 @@ Two checks that catch the bugs models ship most:
   losing, meaning it is too easy)? does it escalate? is it fair (no unavoidable
   loss)? If you drove a full round and nothing threatened you, tune it before
   calling it done. (The \`game-design-reference\` skill carries these self-checks.)
+- **JUDGE the frame, do not just confirm it drew.** When you look at a gameplay
+  screenshot, actively hunt for what is WRONG, do not narrate that it rendered.
+  "It renders" is NOT "it is good". Ask concretely:
+  - **Readability / contrast:** can you tell EVERY entity apart, from the
+    background AND from each other, at a glance? If a hazard or pickup blends
+    into the scenery (same or near colour), that is a bug, recolour it. Every
+    thing the player must react to has to be instantly distinguishable.
+  - **Layout fairness:** are hazards spaced and placed so a HUMAN can actually
+    clear them (react in ~250ms, not frame-perfect)? Gaps too tight to pass, or
+    an obstacle you cannot see coming, are fairness defects, not difficulty.
+  - **Honest quality:** does it look intentional, or just non-broken? If a
+    player saw this, would the visuals read as deliberate?
+  These are the \`game-design-reference\` readability + fairness lenses applied to
+  the IMAGE you are looking at, not only to the logic. Apply them to the actual
+  frame; fix what fails before calling it done.
 
 A green \`verify\`, a bare \`timeout\`, or a nice-looking title is NOT done.
 

package/dist/engine/scaffold/scaffold.js.map

@@ -1 +1 @@
-{"version":3,"file":"scaffold.js","sourceRoot":"","sources":["../../../src/engine/scaffold/scaffold.ts"],"names":[],"mappings":"AAAA,OAAO,EAAC,IAAI,EAAC,MAAM,kBAAkB,CAAC;AACtC,OAAO,EAAC,iBAAiB,EAAC,MAAM,oBAAoB,CAAC;AAErD;;;;;;;;;GASG;AAEH,0FAA0F;AAC1F,MAAM,YAAY,GAAG,EAAE,CAAC;AAExB;;;;GAIG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG,mBAAmB,CAAC;AAEpD;;;;GAIG;AACH,MAAM,UAAU,MAAM;IACrB,MAAM,IAAI,GAAG,IAAI,CAAC,KAAK,CACtB,sDAAsD,YAAY,aAAa,CAC/E,CAAC;IACF,IAAI,CAAC,UAAU,CAAC,KAAK,EAAE,GAAG,gBAAgB,IAAI,CAAC,CAAC;IAChD,OAAO,IAAI,CAAC,SAAS,EAAE,CAAC;AACzB,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,OAAO;IACtB,OAAO;;;;;;;;;;;;;CAaP,CAAC;AACF,CAAC;AAED,2FAA2F;AAC3F,MAAM,UAAU,aAAa;IAC5B,OAAO,iBAAiB,EAAE,CAAC;AAC5B,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,QAAQ;IACvB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiNP,CAAC;AACF,CAAC;AAYD;;;;;;GAMG;AACH,MAAM,UAAU,aAAa;IAC5B,OAAO;QACN,EAAC,IAAI,EAAE,SAAS,EAAE,OAAO,EAAE,MAAM,EAAE,EAAC;QACpC,EAAC,IAAI,EAAE,UAAU,EAAE,OAAO,EAAE,OAAO,EAAE,EAAC;QACtC,EAAC,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE,QAAQ,EAAE,EAAC;QACxC,EAAC,IAAI,EAAE,gBAAgB,EAAE,OAAO,EAAE,aAAa,EAAE,EAAC;KAClD,CAAC;AACH,CAAC"}
+{"version":3,"file":"scaffold.js","sourceRoot":"","sources":["../../../src/engine/scaffold/scaffold.ts"],"names":[],"mappings":"AAAA,OAAO,EAAC,IAAI,EAAC,MAAM,kBAAkB,CAAC;AACtC,OAAO,EAAC,iBAAiB,EAAC,MAAM,oBAAoB,CAAC;AAErD;;;;;;;;;GASG;AAEH,0FAA0F;AAC1F,MAAM,YAAY,GAAG,EAAE,CAAC;AAExB;;;;GAIG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG,mBAAmB,CAAC;AAEpD;;;;GAIG;AACH,MAAM,UAAU,MAAM;IACrB,MAAM,IAAI,GAAG,IAAI,CAAC,KAAK,CACtB,sDAAsD,YAAY,aAAa,CAC/E,CAAC;IACF,IAAI,CAAC,UAAU,CAAC,KAAK,EAAE,GAAG,gBAAgB,IAAI,CAAC,CAAC;IAChD,OAAO,IAAI,CAAC,SAAS,EAAE,CAAC;AACzB,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,OAAO;IACtB,OAAO;;;;;;;;;;;;;CAaP,CAAC;AACF,CAAC;AAED,2FAA2F;AAC3F,MAAM,UAAU,aAAa;IAC5B,OAAO,iBAAiB,EAAE,CAAC;AAC5B,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,QAAQ;IACvB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgOP,CAAC;AACF,CAAC;AAYD;;;;;;GAMG;AACH,MAAM,UAAU,aAAa;IAC5B,OAAO;QACN,EAAC,IAAI,EAAE,SAAS,EAAE,OAAO,EAAE,MAAM,EAAE,EAAC;QACpC,EAAC,IAAI,EAAE,UAAU,EAAE,OAAO,EAAE,OAAO,EAAE,EAAC;QACtC,EAAC,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE,QAAQ,EAAE,EAAC;QACxC,EAAC,IAAI,EAAE,gBAAgB,EAAE,OAAO,EAAE,aAAa,EAAE,EAAC;KAClD,CAAC;AACH,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "picopilot",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "An agent-first toolchain for PICO-8 game development, built on the incur CLI framework.",
   "license": "AGPL-3.0-only",
   "repository": {

package/src/commands/init.test.ts

@@ -143,6 +143,16 @@ describe('picopilot init: AGENTS.md carries the curated PICO-8 reference', () =>
 		expect(lower).toMatch(/sign|direction/);
 		expect(lower).toMatch(/can the player lose|player.*(lose|fail)/);
 		expect(lower).toContain('too easy');
+		// Judge the FRAME, not just confirm it drew: readability/contrast, layout
+		// fairness (spacing), and honest quality. These catch the tree-contrast /
+		// too-tight-gap / weak-graphics issues a large model still shipped.
+		expect(lower).toMatch(/judge the frame|judge the rendered/);
+		expect(lower).toContain('contrast');
+		expect(lower).toMatch(/distinguish/);
+		expect(lower).toMatch(/spaced|spacing|gap/);
+		// Framed as hunting for what is WRONG, and "renders" is not "good".
+		expect(lower).toContain('wrong');
+		expect(agents).toContain('"It renders" is NOT "it is good"');
 	});
 
 	it('warns against guessing the API and points at the shipped pico8-api reference', () => {

package/src/engine/scaffold/scaffold.ts

@@ -150,6 +150,21 @@ Two checks that catch the bugs models ship most:
   losing, meaning it is too easy)? does it escalate? is it fair (no unavoidable
   loss)? If you drove a full round and nothing threatened you, tune it before
   calling it done. (The \`game-design-reference\` skill carries these self-checks.)
+- **JUDGE the frame, do not just confirm it drew.** When you look at a gameplay
+  screenshot, actively hunt for what is WRONG, do not narrate that it rendered.
+  "It renders" is NOT "it is good". Ask concretely:
+  - **Readability / contrast:** can you tell EVERY entity apart, from the
+    background AND from each other, at a glance? If a hazard or pickup blends
+    into the scenery (same or near colour), that is a bug, recolour it. Every
+    thing the player must react to has to be instantly distinguishable.
+  - **Layout fairness:** are hazards spaced and placed so a HUMAN can actually
+    clear them (react in ~250ms, not frame-perfect)? Gaps too tight to pass, or
+    an obstacle you cannot see coming, are fairness defects, not difficulty.
+  - **Honest quality:** does it look intentional, or just non-broken? If a
+    player saw this, would the visuals read as deliberate?
+  These are the \`game-design-reference\` readability + fairness lenses applied to
+  the IMAGE you are looking at, not only to the logic. Apply them to the actual
+  frame; fix what fails before calling it done.
 
 A green \`verify\`, a bare \`timeout\`, or a nice-looking title is NOT done.
 

package/src/engine/skills/skills.test.ts

@@ -68,6 +68,12 @@ describe('picopilot skills: generation output (the authored discipline skills)',
 		expect(md).toContain('frame-perfect');
 		// Visibility (draw what you spr()).
 		expect(md).toContain('spr(');
+		// Readability judged on the RENDERED FRAME, not just the code: the
+		// contrast/spacing lens a large model skipped (it confirmed "renders" but
+		// never asked if entities were distinguishable or gaps clearable).
+		expect(md.toLowerCase()).toContain('rendered frame');
+		expect(md.toLowerCase()).toContain('contrast');
+		expect(md.toLowerCase()).toMatch(/distinguish|tell every entity apart/);
 		// Originality is a METHOD with a self-check, and lists NO concrete
 		// mechanics (the answer-menu trap). Assert the caveat that guards it.
 		expect(md.toLowerCase()).toContain('self-check');

package/src/skills/game-design-reference/SKILL.md

@@ -41,6 +41,8 @@ If you `spr(n)` an entity, sprite n must actually be DRAWN (a non-empty sprite),
 
 The player must be able to READ the game state at a glance and get FEEDBACK for every action: what am I, what is a hazard, what is a goal, did my input register, did I score or get hit. Motion trails, colour contrast, a HUD, particles/shake/sfx on events, these are not polish for its own sake, they are how the player perceives the state they must act on.
 
+**The self-check (apply it to the RENDERED FRAME, not just the code).** When you look at a gameplay screenshot, judge it, do not just confirm it drew. Looking for what is WRONG: can you tell EVERY entity apart from the background and from each other at a glance (a hazard the same colour as the scenery is a readability bug, recolour it)? is every hazard telegraphed and spaced so a human can react in ~250ms rather than by frame-perfect timing (a gap too tight to pass, or an off-screen hazard, is a fairness defect, not difficulty)? does it look intentional, or merely non-broken? "It renders" is not "it is readable and fair". Apply these lenses to the actual image and fix what fails before calling the game done.
+
 ## Difficulty curve and progression
 
 A good game GOES SOMEWHERE: it escalates. Ramp difficulty by introducing or combining MECHANICS (a new hazard type, a new interaction) over the playthrough, not merely by piling more of the same obstacle. More-of-the-same reads as samey and does not deepen; a new wrinkle does. Aim for a difficulty ARC with a satisfying peak, not a flat loop. Keep the first contact with each new mechanic gentle enough to learn it before it is tested under pressure.