tibursocampos/agent-dev-toolkit / core/skills/blip-plugin-developer
blip-plugin-developer
VerifiedScaffold a new Blip React plugin (create-blip-extension), config:plugin, and SDD handoff to react-developer. Use for new Blip plugins or when invoking /blip-plugin-developer.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| reference.md | markdown | 636 B |
| references/documentation-flow.md | markdown | 918 B |
| references/handoff-impl.md | markdown | 1.7 KB |
| references/must-not.md | markdown | 686 B |
| references/related-docs.md | markdown | 100 B |
| references/scaffold.md | markdown | 1.9 KB |
| references/working-rule.md | markdown | 252 B |
references/handoff-impl.md
View on GitHub# blip-plugin-developer — Phase 3 handoff
### Phase 3 - Handoff (implementation)
When scaffolded code or handoff notes touch source: discover architectural patterns; follow `structure-and-quality.md` §1 (operator order and the established project style outrank the toolkit style bar; do not restyle existing members without an explicit yes) plus Blip/React overlays; on greenfield / no clear comment-language mirror, ask before writing narrative comments/docs (identifiers stay English).
Ask in the **user chat language** what to implement next. Route by scope:
| Scope | Next step |
|-------|-----------|
| Net-new UI / redesign | Create `docs/DESIGN-BRIEF.md` with `target_stack: react` and Blip/BDS notes in section 9, then hand off to `react-developer` |
| Plugin implementation | `/react-developer` (auto-loads `blip-guidelines/` when `blip-ds` present) |
| Backend API (.NET) | `/dotnet-developer` in **separate repo** - not in plugin scaffold session |
**DESIGN-BRIEF:** write a project-specific brief using `{{TOOLKIT_ROOT}}/skills/_shared/frontend-guidelines/frontend-practices.md` as general guidance. Keep substantial design discovery and implementation in separate sessions.
**External API:** if Phase 1 answer was REST backend, remind user to read `external-api-integration.md` during `react-developer` sessions.
## Complexity profiles
Choose by technical criteria only — not by historic repo names.
| Profile | Criteria |
|---------|----------|
| **Lite** | Single route, BDS web components, no AuthProvider, minimal or no permission gates |
| **Full** | Multi-route, AuthProvider, buckets, `blip-ds-react` (or equivalent wrappers), segment tracking as needed |
Load `auth-and-permissions.md` only for Full profile.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |