agentleFS
kotaroyamazakikotaroyamazaki/godot-agent-kit/skills/rules/SKILL.md

rules

Skill2 starsChanged 13 days agoMITView on GitHub

Shared rules for designing and building a Godot game with an AI agent: game feel and affordances, tutorials, what to verify before reporting, Godot pitfalls (mouse_filter, timers, viewports, iOS export), and git safety. Load this before designing a game's core loop or UI, before implementing or reviewing gameplay/UI code in a Godot project, and when a playtest says the game is confusing. Godot のゲームを設計・実装・レビューするとき、「分かりにくい」と言われたときに読む。

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${CLAUDE_SKILL_DIR}/../../RULES.md now and follow it for the rest of this task.

    line 12
  2. Very specific:

    If the person works in Japanese, ${CLAUDE_SKILL_DIR}/../../RULES.ja.md is the same content in Japanese.

    line 14
  3. Distinctive:

    When the same lesson has now been learned in a second game, propose adding it to RULES.md in one or two lines.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 12 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

Rules for Godot game work

Read ${CLAUDE_SKILL_DIR}/../../RULES.md now and follow it for the rest of this task. It is short (about 80 lines).

  • If the person works in Japanese, ${CLAUDE_SKILL_DIR}/../../RULES.ja.md is the same content in Japanese.
  • The game's own CLAUDE.md wins over these rules where they disagree.
  • When the same lesson has now been learned in a second game, propose adding it to RULES.md in one or two lines.

To make the rules load in every session instead of on demand, the person can import the file from a CLAUDE.md that sits above their games: add a line @<path printed by: godot-kit rules>.

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.