Stage Tamagotchi Godot C#

1. 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.

1. Before editing C# files, read:

- engines/stage-tamagotchi-godot/docs/csharp-development-method.md - engines/stage-tamagotchi-godot/.editorconfig - engines/stage-tamagotchi-godot/docs/csharp-style.md

1. Treat the development-method document as the primary source of truth for

structure and feature usage. Treat .editorconfig and csharp-style.md as secondary formatting and naming guidance.

1. Classify the change before coding:

- scene script - runtime core - contract and transport - registry and discovery - tooling and editor support

1. 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

1. 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 string and int - var only when the type is obvious - PascalCase for types and members - camelCase for locals and parameters - _camelCase for private fields

1. Keep changes local to the engine. Do not push these C# rules into repo

root config or other workspaces.

1. After changing C# files or the engine-local .editorconfig, run the

verification command from engines/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.