name: stage-tamagotchi-godot-csharp
description: >-
Apply engine-local C# development method and code style only when working in
engines/stage-tamagotchi-godot, including its .cs files, .csproj,
engine-local .editorconfig, and Godot-specific C# structure decisions. Do
not use for TypeScript, Electron, renderer code, shared workspace config,
repo-wide C# conventions, or any file outside
engines/stage-tamagotchi-godot.
Stage Tamagotchi Godot C#
- Confirm every touched file is under
engines/stage-tamagotchi-godot. If the task crosses that boundary, do not use this skill as the governing instruction set. - Before editing C# files, read:
engines/stage-tamagotchi-godot/docs/csharp-development-method.mdengines/stage-tamagotchi-godot/.editorconfigengines/stage-tamagotchi-godot/docs/csharp-style.md
- Treat the development-method document as the primary source of truth for
structure and feature usage. Treat
.editorconfigandcsharp-style.mdas secondary formatting and naming guidance. - Classify the change before coding:
- scene script
- runtime core
- contract and transport
- registry and discovery
- tooling and editor support
- Apply the local design method:
- keep scene scripts thin
- push durable logic into plain C# runtime objects
- make subsystem boundaries explicit through types
- use reflection for discovery, not steady-state execution
- use LINQ for cold-path querying and shaping, not hot-path loops
- use async at I/O and process boundaries, not as a default runtime model
- Apply the local low-level style baseline:
engines/stage-tamagotchi-godot/.editorconfig- 4 spaces, LF, UTF-8, 100 columns
- Allman braces
System.*usings first- keyword types such as
stringandint varonly when the type is obviousPascalCasefor types and memberscamelCasefor locals and parameters_camelCasefor private fields
- Keep changes local to the engine. Do not push these C# rules into repo root config or other workspaces.
- After changing C# files or the engine-local
.editorconfig, run the verification command fromengines/stage-tamagotchi-godot:
dotnet format --verify-no-changes
If verification fails because of pre-existing files outside the intended change scope, report that clearly instead of broadening the edit set silently.