Agent skill · Documentation

godot-csharp

Use C#/.NET in Godot 4.x: partial classes extending nodes, the PascalCase lifecycle (_Ready/_Process/_PhysicsProcess), [Export] fields, [Signal] delegates as C# events, GetNode<T>, and calling between C# and GDScript. Use when writing Godot game code in C# (.cs files, .csproj), needing the Godot .NET build, converting GDScript patterns to C#, or wiring Godot signals as C# events.

gamedev-skillsgithub.com/gamedev-skillsGitHub ↗
claude-codeclinecodexcursorcopilotwindsurfApache-2.0
Install
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill godot-csharp --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Requires: Godot 4.3+ .NET (C#); .NET 6.0 SDK for 4.3/4.4, .NET 8 for 4.5+
Path: skills/godot/godot-csharp/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 406
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Godot C# / .NET (4.x) Write Godot game code in C#: node subclasses, the engine lifecycle, exports, signals as events, and GDScript interop. Targets **Godot 4.3+ (.NET / C#)**; install the .NET SDK that matches your Godot version — **.NET 6.0** for 4.3/4.4, **.NET 8** for 4.5+. ## When to use - Use when scripting a Godot game in C# (`.cs` + `.csproj`), translating GDScript idioms to C#, exposing `[Export]` fields, or wiring `[Signal]` delegates and GetNode<T>. **When *not* to use:** GDScript-specific syntax → `godot-gdscript`; engine concepts that are language-neutral (scenes, physics, animation) → the relevant `godot-*` skill. You need the **Godot .NET build** + the .NET SDK installed; the standard build can't run C#. ## Core workflow 1. **Use the Godot .NET editor build** and install the matching .NET SDK (.NET 6.0 for Godot 4.3/4.4, .NET 8 for 4.5+). Creating the first C# script generates a `.csproj`/`.sln`. Build with the editor or `dotnet build`. 2. **Every node script is a `partial` class** extending a Godot type (the source generator relies on `partial`). The file/class name should match the node script. 3. **Override lifecycle methods in PascalCase** with `double` delta: `

What's inside
Steps it walks through
  1. When to use
  2. Core workflow
  3. Patterns
  4. 1. A node script: lifecycle, [Export], GetNode<T>
  5. 2. Signals as C# events
  6. 3. Instancing a scene in C
  7. 4. Interop with GDScript nodes
  8. Pitfalls
  9. References
  10. Related skills
Ships with 1 file
  • references/csharp-setup-and-interop.md
More from awesome-gamedev-agent-skills
All skills →
About this skill
What does the godot-csharp skill do?

Use C#/.NET in Godot 4.x: partial classes extending nodes, the PascalCase lifecycle (_Ready/_Process/_PhysicsProcess), [Export] fields, [Signal] delegates as C# events, GetNode<T>, and calling between C# and GDScript. Use when writing Godot game code in C# (.cs files, .csproj), needing the Godot .NET build, converting GDScript patterns to C#, or wiring Godot signals as C# events.

How do I install it?

Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill godot-csharp --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From gamedev-skills/awesome-gamedev-agent-skills, a repository with 406 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going