# Godot Brainstorming

Use when designing a new Godot feature or system, guides scene tree planning, node...

- Repository: https://github.com/jame581/GodotPrompter (914 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add jame581/GodotPrompter --skill godot-brainstorming -g -a claude-code -y`
Codex: `npx skills add jame581/GodotPrompter --skill godot-brainstorming -g -a codex -y`
Cursor: `npx skills add jame581/GodotPrompter --skill godot-brainstorming -g -a cursor -y`
Gemini CLI: `npx skills add jame581/GodotPrompter --skill godot-brainstorming -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add jame581/GodotPrompter`

## Description

Use when designing a new Godot feature or system, guides scene tree planning, node type selection, and architectural decisions

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Godot Brainstorming

A structured design process for Godot 4.3+ features and systems, from blank slate to a clear scene tree, signal map, and data flow before you write a single line of implementation code.

> **Related skills:** **godot-grill** for settling open design decisions first, **scene-organization** for scene tree composition patterns, **component-system** for component-based architecture, **event-bus** for signal-based communication design.

---

## Process: How to Brainstorm

Do NOT jump straight to designing. Follow these steps:

### Step 1: Settle the decisions
If the request has open design decisions (scope, dimension, authority, data home, …), invoke `godot-prompter:godot-grill` and let it run to its end. Skip it when a record in the project's decisions or ADR directory already covers this feature, or the user has stated the decisions. Either way, check what already exists (code, scenes, assets). Carry the record into Step 2, approaches must respect its settled rows.

### Step 2: Propose 2-3 approaches
With the decisions settled, propose architectural options with trade-offs. For example:
- "Enum FSM vs Node FSM for your state machine, here's when each fits"
- "EventBus vs direct signals for your systems, here's the trade-off"
Lead with your recommendation and explain why.

### Step 3: Design with approval
Present the design section by section (scene tree, signal map, data flow). Ask "does this look right?" after each section before continuing.

### Step 4: Prepare for implementation

After the design is approved:

1. **Offer the agent instructions section**, Ask whether to add the GodotPrompter integration section to the file this project already uses for agent instructions (see Agent Instructions Injection below). It is what tells subagents and future sessions to use GodotPrompter skills. Skip silently if a `## GodotPrompter` section already exists in any of them, or if the user has declined before. Never add it without agreement.

The rest: https://github.com/jame581/GodotPrompter/blob/HEAD/skills/godot-brainstorming/SKILL.md