agentleFS
vl4dtvl4dt/godot-skills/skills/godot-brainstorming/SKILL.md

godot-brainstorming

Skill8 starsChanged 5 months agoMITView on GitHub

Architecture decision patterns for Godot game development across genres (RPG, platformer, RTS, puzzle). Covers scene organization, state machines, network architecture, and component composition. Use when designing a Godot game's architecture or making Godot-specific technical decisions.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    When the MCP bridge is running (Phase 2), these tools can inspect your live project:

    line 125

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Godot Brainstorming & Architecture

Help design game architecture using Godot's node-based composition model.

Scene Organization Strategies

Composition Over Inheritance

Godot's strength is scene composition. Prefer composing small, focused scenes over deep inheritance hierarchies.

# Instead of: PlayerCharacter extends CharacterBody2D with all abilities
# Use: Compose a player from reusable components
# - BaseCharacter (CharacterBody2D) — movement, health
# - InventoryComponent (Node) — inventory logic
# - AbilitySystem (Node) — ability management

Scene Hierarchy Patterns

PatternWhen to UseExample
Single root sceneEntire game/levelMain.tscn, Level1.tscn
Component scenesReusable behaviorsHealthBar.tscn, ProgressBar.tscn
Entity templatesInstantiable objectsEnemy.tscn, Collectible.tscn
UI compositionsComplex screensMainMenu.tscn, SettingsPanel.tscn

State Machine Patterns

AnimationTree State Machine

@export var animation_tree: AnimationTree
@onready var state_machine: AnimationNodeStateMachinePlayback = \
    animation_tree.get("parameters/playback")

func change_state(new_state: String):
    state_machine.travel(new_state)

Custom State Machine

For complex AI or game logic:

class_name GameState extends RefCounted

var current_state: String = "menu"

func transition_to(new_state: String):
    var prev = current_state
    current_state = new_state
    on_transition(prev, new_state)

func on_transition(from: String, to: String):
    match to:
        "playing": handle_playing()
        "paused": handle_paused()

Network Architecture Decisions

Authoritative Server Model

  • Best for competitive multiplayer
  • Server validates all actions
  • Client sends inputs, server simulates

Peer-to-Peer Model

  • Best for casual/co-op games
  • Lower latency for local interactions
  • Higher cheating risk

Godot 4.7: Steam Frame Integration

For multiplayer with Steam, use the new Steam Frame configuration for lobby management and overlay features.

Genre-Specific Patterns

RPG Architecture

  • Entity-component system for character stats
  • Dialogue tree system (use RichTextLabel + custom parser)
  • Save/load system using JSON or Resource serialization

Platformer Architecture

  • Level streaming for large worlds
  • Input buffering for responsive controls
  • TileMapLayer for layered level design

RTS Architecture

  • Pathfinding with A* on NavigationMesh
  • Unit grouping and selection system
  • Command queue pattern for input handling

Godot 4.7 Brainstorming Considerations

  • tween_await() — Use for sequential animation chains instead of nested callbacks
  • VirtualJoystick — Built-in mobile controls simplify mobile game development
  • Control offset transforms — New UI animation system enables complex transitions without custom shaders

MCP Bridge Tools (Optional — Live Editor Integration)

When the MCP bridge is running (Phase 2), these tools can inspect your live project:

  • scene_tree — Inspect current scene hierarchy for architecture decisions
  • class_db_info — Query class capabilities to choose the right node type
  • map_project — Generate a project graph to visualize architecture
  • project_settings_read — Check current project configuration during brainstorming

Note: MCP tools require the Godot editor to be running with the MCP plugin enabled. Skills work independently without the bridge.

References

  • Scene Composition Patterns
  • State Machine Implementations
  • Network Architecture Guide

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.