electron-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 [ ] User confirmed current action (sim) -> If any unchecked: STOP ``` --- ## Trigger Use when user asks for `/electron-developer`, `electron fix`, or a small isolated Electron implementation. ## Outcome Working main/preload/renderer changes, validated with build and documented smoke (app launch), with optional handoff to `/commit`. ## Renderer stack (orchestration) Detect renderer framework from `package.json`: | Dependency | Lazy-load guidelines | |------------|---------------------| | `react` | `react-guidelines/` | | `vue` | `vue-guidelines/` | | Neither | `javascript-guidelines/`, `html-css-guidelines/` | **Stay in `electron-developer` identity** - load stack guidelines for UI patterns only; do not switch to `react-developer` / `vue-developer`. ## When to escalate to SDD Recommend `sdd-spec` -> `sdd-plan` -> `sdd-develop` if two or more apply: main+renderer+packaging overhaul, auto-update pipeline, cross-repo impact, 10+ files, or exi