art
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the creator's
SKILL.mdskills/1511-homie/3889-art/SKILL.md
GitHubArt for a studio's game
Build time, never a frame of play. Everything here happens once, before anybody plays, and costs nothing at runtime: never call an image model from a game's loop or from anything a person waits on. If you want one there, you want a baked asset instead.
One script: scripts/art.mjs in this skill's folder (Claude Code:
node "${CLAUDE_PLUGIN_ROOT}/skills/art/scripts/art.mjs" <command>), from inside the studio. Node 22,
ffmpeg and Chrome; --json on every command. Art jobs live in art/<slug>/ (the images, the
budget.json, the .request and .json receipts beside each generated file); every paid call is
also a line in art/receipts.jsonl.
node <art.mjs> check # ffmpeg, Chrome, the studio; the fal key checked for free (only generated images need it)
1. The cover, first, always
The cover is what a stranger sees before pressing anything: the studio's game page, the directory card, a link preview. Start from the game itself:
npm run dev # background task
node <art.mjs> frame <game> --url http://127.0.0.1:8787 # frames of the big screen playing, the busiest picked
node <art.mjs> cover <game> --from art/frames/frame-04.png [--focus 0.6,0.4]
frame films the game's big screen (bots playing in a live room) with the platform's own furniture
hidden (the join QR, the status chip, result cards) and keeps the frame with the most visible detail.
cover crops it to 16:9 around the focus, writes cover.jpg (1600x900, under 400 KB) into the game
and names it in game.json ("cover": "cover.jpg"): the site and the directory use it until the game's
landing has a still of its own (hero/wide.jpg), which then is its picture everywhere.
Open the cover and look. A cover is a picture of the GAME: no QR code, no share panel, no debug text, not the waiting screen (a picture of nothing happening). Dark or featureless frames get a warning: a black card on a page reads as a black box.
A painted cover from that frame, when the person wants one (paid, below): write the prompt from
the game you just played, never from its title. Describe what is on screen: the palette, the time of
day, what the player is doing, the shapes. A cover that promises something the game does not contain
is the one failure here that matters: a person presses Play expecting that picture and meets
something else. Use the real frame as the image reference ("@file:art/frames/frame-04.png" in the
input) so the painting keeps the game's layout.
2. Paid images: price, budget, one call at a time
Generated images come from fal through the person's own account: they create a key at
https://fal.ai/dashboard/keys and set FAL_KEY in the environment Claude or Codex runs in (never
pasted into the chat, never written into the studio). fal's hosted MCP (https://mcp.fal.ai/mcp)
finds models and reads their input schemas and prices; paid calls go through art.mjs gen, which
prices, caps, receipts and resumes (the MCP's own run does none of that).
node <art.mjs> price --model fal-ai/flux/dev --input art/cover/input.json # free: fal's unit price x this input
node <art.mjs> budget cover --cap <dollars the person agreed to>
node <art.mjs> gen cover --model fal-ai/flux/dev --input art/cover/input.json --out cover-painted.jpg --dry-run
node <art.mjs> gen cover --model fal-ai/flux/dev --input art/cover/input.json --out cover-painted.jpg --yes
- Tell the person the price and ask for a cap before the first call.
genrefuses with no budget, refuses past the cap, and asks again without--yes. - The receipt is written the moment fal accepts the job. Running the same
genagain resumes it from<out>.request: it never pays twice. A cut-off call is resumed, not re-sent. - Never run paid generation in a loop to "try until it is good". Look at what came back, change the prompt, run it once more. Spend the riskiest image first.
- No real people, no real brands, no copyrighted characters, no "in the style of" a living artist, in prompts or references.
3. Backdrops, textures, plates
A procedural gradient sky is the tell that a game was generated; a painted one costs one image at build time and loads like any other asset. Good candidates: a skybox or far matte, a ground or wall texture, a character plate, a title card. Bad: anything the game generates procedurally for a reason.
node <art.mjs> tile art/floor/floor.png # does it tile? seam numbers and a 2x2 preview
node <art.mjs> fit art/floor/floor.png --out games/<id>/public/art/floor.jpg --width 1024 --max-kb 250
node <art.mjs> sheet art/floor # everything in a job, labelled, to look at
- Models are bad at tiling. Ask for a texture, then check it: a seam over 2 shows as a grid of lines in the game. Mirror-blend the edges or make it tile yourself before it ships.
- Size is a feature. A phone downloads every byte before the first round. Fit backdrops to the
size they are drawn at, JPEG (or WebP where ffmpeg has it) for pictures, PNG only for hard-edged
sprites with transparency. Then play it again: the
playtestskill's first row times the load; an asset that doubled the load time made the game worse. - Put art where the game's own build puts assets (
games/<id>/public/for a bundled game, the game's folder for a static one) and load it with a relative path.
4. Art direction: paintovers, then change the game
Images do not fix a game that looks unfinished; the best-loved browser games often ship no texture files at all. What makes a frame look finished is light, contrast between the subject and the ground, detail at more than one scale, and a clear horizon or depth. The method:
- A style sheet (
art/STYLE.md): palette (five colours with their jobs), light (where it comes from, how hard), shapes, type, and what the look is willing to risk. - Paintovers: real frames of the game (
frame), painted over by an image model with the style sheet as the prompt and the frame as the reference. These are the TARGET, never shipped as the game. - Change the game's own rendering (lights, materials, fog, the floor, the camera) until frames of the running game match the paintover; compare them side by side.
- Judge blind: frames of the old build, the new one and a reference game the person admires,
shuffled under random labels, scored by a fresh reviewer before the labels are revealed (the
playtestskill's review). A reference is a bar, not a template.
Tell the person
What was made and where it is used, the file sizes, what it cost (from the receipts) against the cap, what is a real frame and what is generated, and the pictures themselves.
Never
- Never ship generated art as a screenshot of gameplay, or a cover that shows what the game does not have.
- Never spend without a budget, past it, or without a receipt; never print or store a key.
- Never replace art a person made without asking.