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

new

Skill2 starsChanged 13 days agoMITView on GitHub

Create a new Godot 4 game from the godot-kit template, with script-error checks, screenshots and input replay working from the first minute. Use for "start a new Godot game", "scaffold a prototype", "make a new project from the template", and for adding godot-kit's Shot autoload to an existing Godot project. 「新しいゲームを作って」「Godot で新作を始めたい」「プロトタイプを 1 本立てて」などで使う。

  • Reads credentials

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use upgrade, gate and 2 more.

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.
  • agenticnotetakingSkill

    upgrade

    Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

    Also in 4 projects that use this

  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Default is portrait mobile (720x1280).

    line 17
  2. Distinctive:

    Write the first two lines of the game's CLAUDE.md.

    line 27
  3. Very specific:

    If the game shows non-Latin text, put a font in assets/fonts/ and set [gui] theme/custom_font in project.godot.

    line 28
  4. Very specific:

    Add Shot="*res://scripts/shot.gd" (adjust the path) under [autoload] in project.godot.

    line 50
  5. Very specific:

    Add a kit.env only if the Godot project is not at the repository root (GAME_DIR=client) or the game needs a specific Godot binary …

    line 52

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

Start a new Godot game

godot-kit new <game_id> "<title shown in the game>" [--landscape] [--dir DEST] [--lang en|ja]
  • game_id: lowercase letters, digits, hyphens. It becomes the folder name and the id used in logs.
  • Default is portrait mobile (720x1280). --landscape makes a 1280x720 desktop project.
  • Destination: --dir, else $GODOT_KIT_GAMES_DIR/<game_id> from the user config, else ./<game_id>.
  • --lang ja writes the starter documents in Japanese. It runs git init and does not commit.

After creating it

  1. cd <dest> && tools/check.sh must pass.
  2. Fill in docs/DESIGN.md before writing gameplay code: the one-sentence pitch, one play session, and what the player hesitates over every time. If the answer to the last one is "nothing", the design is not ready. Load the rules skill here. Where the direction could go two ways, offer the person two or three options with a recommendation.
  3. Write the first two lines of the game's CLAUDE.md.
  4. If the game shows non-Latin text, put a font in assets/fonts/ and set [gui] theme/custom_font in project.godot.

What the template contains

FilePurpose
kit.envPer-game values for godot-kit (GAME_ID, GAME_TITLE). Optional
scripts/shot.gdThe Shot autoload: screenshots, input replay (--tap --hold --swipe --click --move --key), the --demo flag
tools/check.shThis game's checks. Grows with the game
docs/DESIGN.mdThe spec
assets/CREDITS.mdWhere sounds and fonts came from

Self-play is the game's job: when Shot.demo is true, make the game play itself so screenshots and recordings can reach the interesting moments. Keep game logic separate from drawing and make randomness reproducible from a --seed, so that runs can be compared.

Adding godot-kit to an existing game

The commands work without any setup (they find project.godot and use the folder name as the id). Only screenshots and input replay need one thing:

  1. Copy ${CLAUDE_SKILL_DIR}/../../template/scripts/shot.gd into the game.
  2. Add Shot="*res://scripts/shot.gd" (adjust the path) under [autoload] in project.godot.

Add a kit.env only if the Godot project is not at the repository root (GAME_DIR=client) or the game needs a specific Godot binary (GODOT_CMD=tools/godot).

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.