blip-plugin-developerlisted

## STOP - Read before ANY tool call 1. Read `{{GUARDRAILS_PATH}}` 2. Read `_shared/sdd-opcodes/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 - User asks for `/blip-plugin-developer`, `blip plugin`, or a **new** Blip React extension - User wants scaffold + documentation setup before implementation For **existing** Blip plugin repos ( `blip-ds` in `package.json` ), use `/react-developer` instead. ## Outcome A correctly scaffolded Blip plugin repo with `config:plugin` applied, profile documented, SDD path chosen, and clear handoff to implementation skills. ## Lazy-load references | When | Path (after `sync-cursor.ps1`) | |------|--------------------------------| | Integration overview | `docs/blip-plugin-integration.md` (in target or toolkit repo) | | Architecture | `{{TOOLKIT_ROOT}}/skills/_shared/blip-guidelines/plugin-architecture.md` | | Design system | `{{TOOLKIT_ROOT}}/skills/_shared/blip-guidelines/design-system.md` | | Iframe messages | `{{TOOLKIT_ROOT}}/skills/_shared/blip-guidelines/blip-ifr