dotnet-developerlisted

## STOP - Read before ANY tool call 1. Read `{{GUARDRAILS_PATH}}` 2. Read `_shared/sdd-artifacts/SESSION.md`; load session-state for `$Cwd` 3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell 4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only 5. This skill body is **English**; user-facing prompts may be **(pt-BR)** ### Step -1 - Gate check (report in chat before continuing) ``` Gate check: [ ] guardrails.mdc read [ ] SESSION.md read; session-state loaded [ ] PIPELINE.md read (SDD skills only) [ ] User confirmed current action (sim) -> If any unchecked: STOP ``` --- ## Trigger Invoke when the user asks for: `/dotnet-developer`, `dotnet fix`, `implement .NET feature`, or for **small** backend work that does not need a full PRD/PLAN cycle. ## Outcome Working **.NET** code and tests in the open workspace: build and tests green, on a valid feature branch, with optional commit handoff. Does not replace SDD for multi-step or cross-repo features. ## When to prefer SDD instead Recommend `/sdd-spec` -> `sdd-plan` -> `sdd-develop` if **two or more** apply: | Signal | Indicator | |--------|-----------| | Layers | 3+ layers (Domain, Application, Infrastructure, API) | | Database | New or altered schema / migrations | | Repos | Backend and another repo or service | | Integrations | New messaging, external APIs, or consumers | | Size | 10+ files or estimated 4+ hours | | PLAN exists | User already has an a