Index of every page on this site: llms.txt
All skills
jame581 avatar

/using-godot-prompter

@426e8ab
by Jan Mesarčjame581/godotprompter979 stars
63
Run it yourself

Bootstrap skill — establishes how to find and use GodotPrompter skills, with platform-specific tool mapping

Use this Skill: https://skilld.dev/gh/jame581/godotprompter/using-godot-prompter

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈33 tokens for metadata: the name and description. ≈2.2k when used: this file. ≈3.4k more on demand in 7 files.

Description uses 1.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈130 characters, or 1.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Using GodotPrompter

Related skills: godot-project-setup for scaffolding a new project, godot-grill for settling open design decisions first, godot-brainstorming for design exploration, godot-code-review for reviewing finished code, godot-debugging for diagnosing runtime issues.

GodotPrompter provides Godot 4.x domain-specific skills for AI coding agents. Skills cover project setup, architecture patterns, gameplay systems, UI, multiplayer, testing, and deployment — for both GDScript and C#.

How to Access Skills

In Claude Code: Use the Skill tool with the skill name (e.g., Skill: "godot-prompter:state-machine").

In Copilot CLI: Use the skill tool. Skills are auto-discovered from installed plugins.

In Gemini CLI: Deprecated (succeeded by Antigravity CLI).

In Grok Build: Skills are discovered from the installed plugin (grok plugin install jame581/GodotPrompter --trust); invoke them by name.

In Cursor: Skills are loaded via custom instructions / rules system.

In Codex: Skills load natively via the AGENTS.md re-export. Follow skill instructions directly; tool mapping is in references/codex-tools.md, beside this SKILL.md.

In OpenCode: Skills are discovered from the installed plugin. Use the /skills command to browse or invoke skills directly. See .opencode/INSTALL.md for setup.

In Antigravity (2.0, IDE, CLI): Skills activate automatically when your prompt matches a skill's description — no tool call. Install with agy plugin install https://github.com/jame581/GodotPrompter; manual, workspace and global paths: references/installation.md. Tool mapping: references/antigravity-tools.md.

Install commands for every host: README.md, references/installation.md.

Coexistence with Other Plugins (e.g., Superpowers)

<!-- SESSION-CARD-START -->

GodotPrompter is active in this Godot project.

Workflow plugins decide how; GodotPrompter decides what. Both apply.

RULE: before building a new Godot system, invoke the matching godot-prompter:* skill. Subagents too.

Situation Start with
New system, or the requirements are unclear godot-grill — settle decisions, then design and build
New system, design settled by the user the domain skill below — build
Change or extend a system the project has its code; no skill unless replacing it or asked for the pattern
Bug fix its code; godot-debugging or the domain skill for engine pitfalls
No Godot content: docs, generic CI, repo tooling no skill

Then report before you build: name the pattern you picked, the alternative you rejected, and why. The choice is the developer's. A report states; it never ends on your own questions. A design decision needs the developer's answer or go-ahead first? Invoke godot-grill.

Building… Start with
Movement, input, cameras player-controller, input-handling, camera-system
Architecture state-machine, event-bus, scene-organization, component-system, resource-pattern, dependency-injection
Gameplay systems inventory-system, dialogue-system, ability-system, save-load
Enemy AI ai-navigation
UI, HUD, i18n godot-ui, hud-system, responsive-ui, localization
Animation, tweens, audio animation-system, tween-animation, audio-system
Physics, 2D, 3D physics-system, 2d-essentials, 3d-essentials
Shaders, rendering, VFX, procgen, math shader-basics, rendering-pipeline, particles-vfx, procedural-generation, math-essentials
Networking multiplayer-basics, multiplayer-sync, dedicated-server, web-services
Mobile, XR, native, threads mobile-development, xr-development, gdextension, multithreading
Editor tools, assets addon-development, assets-pipeline
GDScript / C# idioms gdscript-patterns, gdscript-advanced, csharp-godot, csharp-signals
Test, debug, profile, review godot-testing, godot-debugging, godot-optimization, godot-code-review
Setup, design, export godot-project-setup, godot-grill, godot-brainstorming, export-pipeline, web-export
Addons (if installed) limboai, beehave, popochiu, dialogue-manager, phantom-camera

Red flags (new systems) — you are rationalizing:

Thought Reality
"I know how CharacterBody2D works" Knowing the class ≠ knowing the pattern. Invoke.
"The plan says what to build" The plan says what. The skill says how. Invoke.
"It's small, a quick fix" A new system still sets architecture. Invoke — then say what you picked.
"The skill shows one pattern, so it's settled" Skills carry trade-offs. Surface them; don't decide alone.
"I'll explain it once it works" A choice reported after the code is a fait accompli, not a choice.
<!-- SESSION-CARD-END -->

When Not to Load a Skill

Domain skills are for building a new system; each load costs up to 16 KB. Otherwise:

  • The project already has the system. To change or extend it (a new item field, one more ability), read and follow the project's code. Load the domain skill only to replace or redesign that system, or when the user asks for the pattern.
  • A bug fix starts from the project's code too; load godot-debugging, or the domain skill when the cause is an engine pitfall.
  • The task has no Godot content. Docs, generic CI and repo tooling with no Godot content need no skill, godot-brainstorming included (Godot export CI is export-pipeline's, editor tooling addon-development's).

Mentor mode (godot-mentor) is the exception: it loads the matching skill on purpose, to teach.

Workflow: From Idea to Working Game

GodotPrompter handles the full development workflow. No other plugins required.

1. Design Phase

Load godot-prompter:godot-grill first when design decisions are open — it settles them in rounds and records them. Then godot-prompter:godot-brainstorming guides you through:

  • Proposing architectural approaches with trade-offs
  • Designing scene trees, signal maps, and data flow
  • Creating an implementation plan with ordered tasks

2. Implementation Phase

For each task in the plan, load the relevant domain skill:

  • Building a player? Load godot-prompter:player-controller and godot-prompter:state-machine
  • Adding an inventory the project does not have yet? Load godot-prompter:inventory-system
  • Need save/load? Load godot-prompter:save-load

3. Review Phase

Load godot-prompter:godot-code-review to review the code against Godot-specific checklists.

Plan Storage

GodotPrompter has no plans folder of its own. Save implementation plans where this project keeps them, checking in order: the user's instructions or the project's agent instructions file (CLAUDE.md, AGENTS.md, …); then the planning skill's convention; then an existing plans directory. If none applies, ask the user, suggesting docs/plans/, or use docs/plans/ when you cannot ask (a subagent or non-interactive run). Per-scene designs from godot-brainstorming stay next to the scene, in the root script's comment block or a DESIGN.md.

Platform Adaptation

Skills use Claude Code tool names as the canonical reference. Non-Claude platforms: see the appropriate tool mapping file in references/ for your platform's equivalents:

Skill and Agent Index

Every skill by category with a one-line description, and the nine agents (godot-game-architect, godot-game-dev, godot-code-reviewer, and six specialists): references/skill-index.md, beside this SKILL.md. Read it when the table above does not name the skill you need.


Implementation Checklist

  • Identified the matching domain skill via the table above before writing a new system (none for work inside an existing one)
  • Invoked the identified skill with the Skill tool (or platform equivalent) before implementation
  • When a workflow plugin is also active (Superpowers, etc.), still invoked the relevant godot-prompter domain skill during implementation — they are complementary, not exclusive
  • After implementation, ran godot-prompter:godot-code-review to validate against Godot best practices
  • Logged any newly-discovered domain gap that no current skill covers, so it can become a future skill

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts6d3 checks · Risk SAFE
  • Gen Agent Trust Hub6d

    This skill serves as a bootstrap and reference guide for using the GodotPrompter suite of tools for Godot engine development. It provides tool mapping for various AI agent platforms and lists specialized skills for architecture, gameplay, and UI. No security issues were detected.

  • Socket7d

    No alerts

  • Snyk6d

    Risk: LOW · No issues

Signed by skilld at 426e8ab. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated last week

README badge

README badge for jame581/godotprompter/using-godot-prompter