agentleFS
liangdabiaoliangdabiao/Godogen/.claude/skills/godogen/SKILL.md

godogen

Skill120 starsChanged 7 months agoMITView on GitHub

This skill should be used when the user asks to "make a game", "build a game", "generate a game", or wants to generate or update a complete Godot game from a natural language description.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Read each sub-file from ${CLAUDE_SKILL_DIR}/ when you reach its pipeline stage.

    line 13
  2. Very specific:

    Read task-execution.md before starting.

    line 61
  3. Very specific:

    When you need to look up a Godot class API (methods, properties, signals), use Skill(skill="godot-api") with your query.

    line 68
  4. Very specific:

    After capturing screenshots, verify with Skill(skill="visual-qa").

    line 82
  5. Distinctive:

    Keep important state in files so the pipeline can resume even after compaction or clear:

    line 92
  6. Distinctive:

    After completing each task: update PLAN.md status, write discoveries to MEMORY.md, git commit.

    line 99
  7. Very specific:

    If the context becomes polluted from debugging loops, manually compact with: /compact "Discard failed debugging attempts."

    line 101
  8. Distinctive:

    VQA reports are clear signal: If a significant issue is reported, fix it.

    line 110

≈ “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

Game Generator — Orchestrator

Generate and update Godot games from natural language.

Capabilities

Read each sub-file from ${CLAUDE_SKILL_DIR}/ when you reach its pipeline stage.

FilePurposeWhen to read
visual-target.mdGenerate reference imagePipeline start
decomposer.mdDecompose into task DAGAfter visual target
scaffold.mdArchitecture + skeletonAfter decomposition
asset-planner.mdBudget and plan assetsIf budget provided
asset-gen.mdAsset generation CLI refWhen generating assets
rembg.mdBackground removalOnly when an asset needs transparency removed
sprite-gen.mdSprite sheet animation generationWhen generating animated characters
task-execution.mdTask workflow + commandsBefore first task
quirks.mdGodot gotchasBefore writing code
(godot-api skill)GDScript syntax refWhen unsure about GDScript syntax
scene-generation.mdScene buildersTargets include .tscn
test-harness.mdVerification scriptsBefore test harness
capture.mdScreenshot/videoBefore capture
visual-qa.mdVisual QA (forked skill)After capture
android-build.mdAPK exportUser requests Android

Pipeline

User request
    |
    +- Check if PLAN.md exists (resume check)
    |   +- If yes: read PLAN.md, STRUCTURE.md, MEMORY.md -> skip to task execution
    |   +- If no: continue with fresh pipeline below
    |
    +- Generate visual target -> reference.png + ASSETS.md (art direction only)
    +- Analyze risks + define verification criteria -> PLAN.md
    +- Design architecture -> STRUCTURE.md + project.godot + stubs
    |
    +- If budget provided (and no asset tables in ASSETS.md):
    |   +- Plan and generate assets -> ASSETS.md + updated PLAN.md with asset assignments
    |
    +- Show user a concise plan summary (risk tasks if any, main build scope)
    |
    +- Execute (see Execution below)
    |
    +- If user requested Android app:
    |   +- Read android-build.md, add ETC2/ASTC to project.godot, create export_presets.cfg, export APK
    |
    +- Summary of completed game

Execution

Read task-execution.md before starting. Three phases:

  1. Risk tasks (if any) — implement each in isolation, verify, commit
  2. Main build — implement everything else, verify, present results (video for new games), commit

Godot API Lookup

When you need to look up a Godot class API (methods, properties, signals), use Skill(skill="godot-api") with your query. This runs in a separate context to avoid loading large API docs into the main pipeline.

Be specific about what you need — the docs are comprehensive and full returns are large:

  • Targeted query — ask for specific methods/signals to get a concise answer: "CharacterBody3D: what method applies velocity and slides along collisions?"
  • Full API — only request when you need to survey the entire class: "full API for AnimationPlayer"

Examples:

  • Skill(skill="godot-api") "TileMapLayer: methods for setting/getting cells and their alternatives"
  • Skill(skill="godot-api") "full API for CharacterBody3D"
  • Skill(skill="godot-api") "which class handles 2D particle effects?"
  • Skill(skill="godot-api") "GDScript: tween parallel syntax and callbacks"

Visual QA

After capturing screenshots, verify with Skill(skill="visual-qa"). Runs in a forked context with Claude's native vision.

  • Static: Skill(skill="visual-qa") "Check reference.png against screenshots/{task}/frame0003.png — Goal: ..., Verify: ..."
  • Dynamic: Skill(skill="visual-qa") "Check reference.png against frame1.png frame2.png ... — Goal: ..., Verify: ..."
  • Question: Skill(skill="visual-qa") "Are surfaces showing magenta? screenshots/{task}/frame*.png"

Save output to visual-qa/{N}.md. See visual-qa.md for full usage.

Context Hygiene

Keep important state in files so the pipeline can resume even after compaction or clear:

  • PLAN.md — task statuses, always up to date before moving on
  • STRUCTURE.md — architecture reference, update if scaffolding changes
  • MEMORY.md — discoveries, quirks, workarounds, what worked/failed
  • ASSETS.md — asset manifest with paths and generation details

After completing each task: update PLAN.md status, write discoveries to MEMORY.md, git commit. This ensures the pipeline can resume from any point by reading these files.

If the context becomes polluted from debugging loops, manually compact with: /compact "Discard failed debugging attempts."

Visual QA

Don't trust code — verify on screenshots. The most common failure mode: code looks correct, you assume it works, and report "everything's fine." Then screenshots reveal broken placement, wrong scale, missing elements, clipped geometry — dozens of small details that go wrong in unexpected ways, especially with custom assets. Visual QA is your quality partner: use it actively after every task, not as a formality.

Visual QA runs inline with each task. Never ignore a fail verdict — always act on it before marking a task done.

VQA reports are clear signal. If a significant issue is reported, fix it. If you genuinely believe it's a false positive — report it to the user and let them decide. Never silently ignore a fail verdict.

  • pass/warning — move on.
  • fail — fix the issue. If you've already attempted up to 3 fix cycles, decide:
    • Replan — reset architecture, rewrite plan, and/or regenerate assets if the root cause is upstream.
    • Escalate — surface the issue to the user if you can't determine the right fix.

The final task in PLAN.md is a presentation video — a script that showcases gameplay in a ~30-second cinematic MP4.

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.