godot-code-gen

Unify Godot C# coding conventions across projects.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Zearain/ludum-dare-59 --skill godot-code-gen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: godot-code-gen
Source: https://github.com/Zearain/ludum-dare-59/tree/main/.opencode/skills/godot-code-gen
Command: npx skills add https://github.com/Zearain/ludum-dare-59 --skill godot-code-gen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Godot 4.6 C# development can vary across teams; this Skill unifies practices including naming conventions, export usage, signals, state machines, async/await, tweens, input handling, and performance guidelines to improve consistency and reliability.

Core Features & Use Cases

  • Code style and project conventions: assembly name, root namespace, file-per-class, file-scoped namespaces, Allman brace style, four-space indentation, and LF line endings to ensure uniformity across the codebase.
  • Node/component patterns and composition: guided usage of [Export] references, signals, and component-based scenes with thin orchestrator root scripts for reuse across entities like PlayerShip and Scout.
  • Lifecycle guides and common patterns: standard overrides (_Ready, _Process, _PhysicsProcess, _Input, _UnhandledInput) and patterns for state machines, resource usage, and scene instantiation to reduce bugs and speed up onboarding.

Quick Start

Adopt these conventions in your next Godot C# module to ensure consistent naming, structure, and performance.

Frequently Asked Questions about godot-code-gen

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Godot C# coding conventions across a team project?

To standardize Godot C# coding conventions, enforce assembly naming, root namespaces, file-per-class structures, file-scoped namespaces, Allman brace style, four-space indentation, and LF line endings to ensure uniformity across your codebase.

What are the best Godot C# patterns for signals and state machines?

The best Godot C# patterns for signals and state machines involve using thin orchestrator root scripts for component-based scenes, applying explicit [Export] references, and adhering to standard lifecycle overrides to reduce bugs and speed up onboarding.

Does this Godot C# code generation approach work for mobile and desktop games?

Yes, this Godot C# code generation approach applies to Godot-based game development across both mobile and desktop platforms, ensuring consistent patterns across modules, scenes, and plugins for team-scale projects.

How do I structure Godot C# scenes and components for reuse?

To structure Godot C# scenes for reuse, use component-based scenes guided by [Export] references and signals, pairing them with thin orchestrator root scripts to enable entity reuse across modules like PlayerShip and Scout.

What Godot C# lifecycle overrides and input handling patterns should I use?

Standard Godot C# lifecycle overrides include _Ready, _Process, _PhysicsProcess, _Input, and _UnhandledInput, paired with common patterns for async/await, tweens, and input handling to improve game reliability and performance.