agentleFS
TobiasMue91TobiasMue91/tobiasmue91.github.io/.claude/skills/improve-game/SKILL.md

improve-game

Skill59 starsChanged 2 days agoMITView on GitHub

Remake one game on gptgames.dev as the best version of it that can be built today - claim, design thesis, art direction with critique, rebuild, filmstrip critique rounds, PR.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. OpusGameLabs/game-creator★ 360same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the new page from an empty file.

    line 22
  2. Distinctive:

    Every visual choice is deliberate: if you cannot say why this font, this colour and this shape belong to this game and not to any other, …

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remake one game on gptgames.dev as the best version of it that can be built today. Make every decision yourself and explain the important ones in the PR. Do not stop to ask me, unless the claim in step 1 fails.

Game requested (may be empty): $ARGUMENTS

THE BAR Measure it against the best commercial version of this kind of game that exists now. Not against the old page, not against the original from years ago, and not against other pages on this site. A stranger who came across it should believe someone was paid to design it.

WHAT YOU MAY CHANGE Nearly everything. Keep the file name and URL, the core idea the catalogue entry promises, the depth the old game offers its players (step 2), and any saved data worth migrating. Look, structure, screens, modes and even the name are open. Write the new page from an empty file. Do not read the old page's code until step 7. If the page already has a DOM-free core that a suite in test/ checks, you may keep that core, because its tests prove it. Everything around it starts fresh.

  1. CLAIM THE GAME before anything else. With no game requested above, run python util/claim.py; with one, run python util/claim.py games/<id>.html. It prints the game that is now yours. If it fails, that game is taken: stop and tell me. The claim branch it pushes is the only extra branch you may push. Never touch another session's claim.
  2. UNDERSTAND THE GAME, NOT THE PAGE. In a few lines: what the best versions of this game do well, what the one moment is that makes it satisfying, what the player should feel, and what a phone player needs. That is your design thesis. Then play the old page in a browser for a few minutes (play it, do not read its code) and list what it offers a player: modes, progression, upgrades, unlocks, meta systems, content. That list is a floor, not a wish list. The remake keeps at least that much depth, reworked to fit the new design, unless a system is broken or redundant. Name every system you drop in the PR, with the reason. In genres whose appeal is the long game (incremental, idle, roguelite, management), the progression systems are part of the core, not extras.
  3. CHOOSE THE ART DIRECTION. Derive it from the design thesis and the game's theme: palette, typography, shapes, a motion idea and a sound idea. Write down why each belongs to this game; a reason that would fit any game is not a reason. The game gets its own identity, independent of the rest of the site. Build a static mockup of the main screen in your scratchpad, not in the repo, and screenshot it at desktop and phone size. Then show the screenshots, one sentence about the game and the principles below to a critic: a subagent that has not seen your reasoning. It reviews as a harsh critic: would a stranger call this bad? What looks cheap, what is confusing, what is weakest? Scores from 1 to 10 for first impression, clarity, art direction and phone. Revise the mockup until every score is at least 8 before writing the game.
  4. THE FIRST 30 SECONDS. Before any code, write out step by step what a new player on a phone sees, touches and learns, what happens on their first mistake, at the end of a game and when they come back tomorrow. List every screen state and how you get in and out of each.
  5. BUILD IT as CLAUDE.md describes a page. Every input gets feedback in the same frame. Everything that moves is eased. No layout jumps, a steady frame rate, readable contrast, reduced motion respected. Check the recurring mistakes CLAUDE.md lists.
  6. CORRECTNESS WHERE IT MATTERS. The rules the game stands on belong in a DOM-free core with a suite in test/ if a change in one corner could quietly break another. No console errors. Tests must not eat the session; most of the effort belongs in steps 3, 4 and 8.
  7. MIGRATION. Only now read the old page, for its saved data, so existing progress and best scores survive.
  8. CRITIQUE THE GAME, IN ROUNDS. In headless Chromium, record filmstrips (8 to 12 frames each) of the key moments, on desktop and on a phone. Give them to a fresh critic as in step 3, now also scoring feel. Fix the biggest issues and repeat until every score is at least 8, for at most four rounds. If you disagree with the critic, show why in the next round instead of arguing.
  9. HOUSEKEEPING AND COMMIT as in CLAUDE.md. The commit message says what the new game is and why it looks and plays the way it does. Push, open a PR, and give me before/after screenshots and the critic's last scores.

PRINCIPLES

  • Faithfulness is owed to the mechanics, not to how the game used to look.
  • Every visual choice is deliberate: if you cannot say why this font, this colour and this shape belong to this game and not to any other, choose again.
  • Everything on screen serves play. A panel, label, number or effect that neither helps the player decide nor makes them feel something goes.
  • The game teaches through play, not through text. Settings and modes only where the game would be worse without them.
  • Polish before features: add no new system the core game does not need. This is about new systems; what the old game already offered is covered by step 2.

One game per session.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.