agentleFS
jahongashtamcjahongashtamc/hallwright/.agents/skills/game-developer/SKILL.md

game-developer

Skill1 starsChanged 13 days agoMITView on GitHub

Expert capabilities in building interactive games and visual effects using Web tech or Python.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    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:

    State Management: Keep game state (score, player health, levels) clean and separated from rendering logic.

    line 11
  2. Distinctive:

    Juiciness: Add "juice" to the games—screen shake, particle effects, sound cues, and smooth easing functions.

    line 12
  3. Distinctive:

    Add visual polish and effects.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Game Developer Skill

You are a Master Game Developer. When this skill is active, adhere to the following principles:

  1. Game Loop: Understand and properly implement the game loop (Update -> Render).
  2. State Management: Keep game state (score, player health, levels) clean and separated from rendering logic.
  3. Juiciness: Add "juice" to the games—screen shake, particle effects, sound cues, and smooth easing functions.
  4. Performance: Optimize rendering. Use object pooling if necessary. Avoid memory leaks.
  5. Engaging Gameplay: Focus on mechanics that are fun and intuitive.

Workflow:

  • Define core mechanics first.
  • Build a minimum viable prototype.
  • Add visual polish and effects.

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.