Black Ice: a snowbound arctic outpost at dusk, with relay masts and a tracked vehicle in the foreground
Open-source skill · v1.0.0 8 gates · 0 npm dependencies

A 1.4 MB game.
A cheaper model.
One harness.

Saltline was a 1.4 MB single-file shooter made with Claude Fable 5.2 — zero external assets, and a model-written generator behind every container and surface. This is the open-source harness that asks whether a low-cost model can be held to the same production standard. So far: 318 KB, four hostile roles, a boss, 8/8 gates.

1,423,668bytes · the Saltline reference
318 KBthe skill-built shooter
8 / 8executable gates, not adjectives
0npm deps · external assets

01The question

The file was never the point.

Saltline got shared as “a 1.4 MB AAA game”. That description is wrong in an informative way: it is not AAA, and 1.4 MB is not a compression win. The content was never stored — it was generated by code at runtime.

Saltline: a rainy container port at dusk, with a container canyon, light masts and wet ground
Saltline / container port / reference frameThird-party capture, comparison only

A model wrote a generator, not a scene.

The file is about half inlined three.js and half game: world building, materials, shaders, player and enemy logic, UI and synthesized audio. No images. No models. No audio files. The code is smaller than the content it generates because the content was never stored as data.

What matters is not the size. It is that the generator — the geometry kit, the surface functions, the lighting rig, the animation solvers, the audio graph and the self-tests — was written by a model. And that changes the economics of who can build one.

How the harness answers it

1.42 MBone HTML file · ~443 KB gzipped
0external images, audio or models
~8 hreported generation time · ~$550 API

02The answer

Not the same game.
The same discipline.

The first skill-built shooter passed every gate it had and still felt like a demo. The second generation made the product a gate. It is a third of the size and a more finished game.

Black Ice title screen: a live 3D arctic outpost, a typographic title, premise, start, settings and controls
BLACK ICE · 318 KB · DeepSeek V4.1 Flash · 8/8 gatesTitle over the live scene, HUD hidden

01 / shell

Title, settings, pause, save, touch.

Six screens that a player can inspect, not a modal floating over a live HUD. Settings persist. The best run persists. The first minute is treated as product.

product gate

02 / content

Four roles, a boss, two tools.

Raiders, wasps, shielded heavies and Warden Prime. A rifle and a chain-lightning gauntlet. One four-beat objective chain, not a wave counter with a new colour.

content budget

03 / loop

A win, a loss, a named cause.

Lethal damage fails the run and names the attacker and weapon. The playtest drives the win, the loss and the restart headlessly. A counter is not feedback.

playtest gate

03Two runs, two verdicts

Should you use the skill?

The honest answer depends on what you are shipping. Two controlled runs, same model, same single-file constraint, different harness.

Sunset District: a city kart race on a wet downtown street
3D city kartcontrolled A/B

Use it — when the deliverable is a finished race.

The no-skill build had a strong arcade core and a thin shell. The skill build added settings, save, touch, objectives, a signature wet-road reflection and a four-lap race structure. The size went up; so did the product.

890 KBno skill
1.58 MBwith skill
4 laps5 rivals · 636 calls

Read the city-kart case

Black Ice gameplay: relay markers, compass, health and ammo over a snowbound yard
3D shooterthree generations

Use it — with a product-first budget.

The first skill run optimised the frame and lost the product: one enemy, one gun, no shell. The fix was not another shader. It was a product gate, an explicit art direction and a playtest that drives the loop. Black Ice is the result.

318 KBskill v2
4 + 1roles + boss
8 / 8gates

Read the shooter case

04What it is

A skill is a procedure.
A harness disagrees.

SKILL.md tells the model what to decide and in what order. The harness turns every judgement that matters into a check, so a weak model does not have to re-derive taste from memory.

LOOK

Does it read as photographic?

Fixed cameras, a project reference profile, tone checks, spatial flatness and a ranked defect list. The worst camera decides, not the hero shot.

render · score · calibrate · diagnose

SOLIDS

Can you walk through it?

Collider parity from the scene graph, penetration, world bounds, bare edges and walk-through tests. A collider list that drifts from the geometry is a bug.

census · collide

LOOP

Can it be won, lost, restarted?

A page-owned selftest or a declarative plan. Prompts must not promise actions out of range. Damage must name its cause. Reset must reset.

playtest

PRODUCT

Is it a game or a frame?

Title, settings, pause, save, touch, content breadth, HUD hierarchy, audio events, cameras and measured performance budgets.

product · mobile

“A gate that lives only in a README stops being run.”

05The acceptance command

Eight gates.
One verdict.

This is the actual output on Black Ice. A red verdict is a build failure, not a report. The look gate falls back to tone and emptiness when no project profile exists, and says so.

shadersNo compile/link error; __READY becomes true.PASS
censusSegments, surface maps and identity budgets.PASS
collideParity, penetration, bounds, bare edges, walk-through.PASS
lightsEvery light has a fixture within its mount distance.PASS
playtestWin, loss, named cause, visible consequence, restart.PASS
productShell, content, save, touch, HUD, audio, budgets.PASS
mobile390×844, no overflow, touch reachable.PASS
lookWorst declared camera vs the project profile, or tone fallback.PASS
terminal / clone and verify
# Node 22+, Python 3.10+, Pillow, Chrome
git clone https://github.com/NorwinYu/photoreal-game.git
cd photoreal-game
python3 -m pip install -r requirements.txt

./install.sh ~/.agents/skills

node harness/verify.mjs \
  --dir ../my-game --page index.html

No npm packages. No build step. No API key. The renderer is a small Chrome CDP client; the metrics are Python and Pillow.

Read the harness docs

06What it catches

The failures that look fine.

Every rule in the skill came from a run that broke. These are four of the useful ones — not hypotheticals, and not all of them visual.

DEFECT / 01

The frame was almost black.

A top-level clamp collided with a three.js symbol after inlining. Exposure, albedo and lighting were all fine; the shader never compiled. The shader gate exists because a black frame looks like a lighting problem.

caught by / shaders

DEFECT / 02

The snowcat came apart.

Every at() push had no matching done(), so parts inherited an accumulated offset and floated into the sky. The fix was a transform stack, not a material.

caught by / human + close camera

DEFECT / 03

The prompt lied.

The marker appeared at 3.0 m; the action worked at 1.8 m. The prompt named the key at every distance. No screenshot could show it. The playtest now checks both directions.

caught by / playtest

DEFECT / 04

The boss could not lose.

The death hook set boss.dead before the victory timer was queued. Killing it worked; the run never ended. The playtest drove the loop to a win instead of reading the counter back.

caught by / playtest

07The evidence

Runs, not adjectives.

All runs are DeepSeek V4.1 Flash, single-file and self-contained. The question in each run was different. The A/B runs are harness comparisons, not controlled model benchmarks.

RunHarnessSizeWhat it provesVerdict
Sundown Circuit
city kart
none890 KBA cheap model can ship a complete arcade racer without the skill.Strong core, thinner shell
Sunset District
city kart
skill + gates1.58 MBThe harness adds the product layer and a signature wet-road system.Use it
Neon Breach
shooter
none304 KBContent breadth can carry a stylized game without photorealism.Strong content, style mismatch
Ironsight
shooter, unpublished
skill v11.50 MBThe first skill run passed 6/6 and still felt like a demo.Not enough
Black Ice
shooter
skill v2318 KBProduct gates and a portable playtest turn the procedure into a game.Use it, with a budget
Saltline
reference
—1.42 MBThe target: a model-written generator with a coherent look and self-tests.Reference

Black Ice: 8/8 gates, 163 draw calls, 127k triangles, 12 lights, 0 network requests.Measured on the shipped build

08Use it / skip it

The skill is not free.

It buys a product layer and a paper trail. It costs rounds. If you only need a look, capture the frame and skip the gates.

USE IT WHEN

The deliverable is a game.

There is a win, a loss, a restart and someone other than you will play it. The first minute matters. You need to hand the build to a reviewer without explaining what is missing.

racing · shooters · stealth · haulage · repair

SKIP IT WHEN

You need a frame, not a loop.

A mood board, a look test, a concept still or a 30-second prototype. The product gate will reject it by design, and the calibration profile will measure the wrong thing.

stills · style tests · one-day prototypes

DO NOT USE IT WHEN

The style is deliberately flat.

Cel shading, diagrammatic UI, CAD readability. The procedure transfers, but the photoreal profile does not. Replace the look gate with a style-consistent one.

stylized · precision · no camera

The honest version

The skill does not make a cheap model into an art director. It makes the gap visible early.

Read the docs

09Install

Three commands
to a red verdict.

The skill works as a plain instruction file. The harness is what makes it checkable. Both are in the repo; neither needs an account.

01 / clone
git clone https://github.com/NorwinYu/photoreal-game.git
cd photoreal-game
python3 -m pip install -r requirements.txt
02 / install the skill
./install.sh ~/.agents/skills
# or: cp SKILL.md ../my-game/AGENTS.md
03 / verify
node harness/verify.mjs \
  --dir ../my-game --page index.html
Does it work with Unity, Unreal or Godot?

The procedure transfers; the bundled harness assumes a web page. The five levers — light, materials, density, image formation, geometry detail — are engine-independent. The page contract is the integration point: if an engine build can expose a scene graph, a collider test, a fixed camera and a test hook, the gates can be adapted.

Is this a template for Saltline?

No. It is a procedure plus gates. It does not ship Saltline's world, palette or assets, and it does not promise the same result. The case studies show what changed when the harness was used, including the runs that failed.

Why eight gates instead of one score?

Because a single score hides the failure class. A frame can be beautiful and unplayable; a loop can be correct and look like plastic. The gates are ordered by failure class: behaviour, craft, visual, polish. The look gate is last for a reason.

What does it need?

Node.js 22+, Python 3.10+ with Pillow, and Chrome or Chromium. No npm packages, no build step, no API key. The site and the games make no network requests.

Can I contribute a case study?

Yes — that is the most useful contribution. Include the model, the harness version, the gate output, the failures and 2–4 fixed-camera stills. See CONTRIBUTING.md.

Open source / MIT

Hold the model to the standard.

Star the repo, play the builds, or send a case study with the failures left in. The point is not that a cheap model can write a game. The point is that it can be held to the same standard.