From bee-dev-team
16 specialist developer agents for backend (PHP), database, frontend (React + Vue.js + React Native/Expo), design, UI implementation, QA (backend + frontend), and SRE. Dispatch when you need deep technology expertise.
npx claudepluginhub luanrodrigues/ia-frmwrk --plugin bee-dev-teamThis skill uses the workspace's default tool permissions.
The bee-dev-team plugin provides 16 specialized developer agents. Use them via `Task tool with subagent_type:`.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
The bee-dev-team plugin provides 16 specialized developer agents. Use them via Task tool with subagent_type:.
See CLAUDE.md and bee:using-bee for canonical workflow requirements and ORCHESTRATOR principle. This skill introduces dev-team-specific agents.
Remember: Follow the ORCHESTRATOR principle from bee:using-bee. Dispatch agents to handle complexity; don't operate tools directly.
<block_condition>
If any condition applies, STOP and ask user.
always pause and report blocker for:
| Decision Type | Examples | Action |
|---|---|---|
| Technology Stack | PHP for new service | STOP. Check existing patterns. Ask user. |
| Architecture | Monolith vs microservices | STOP. This is a business decision. Ask user. |
| Infrastructure | Cloud provider choice | STOP. Check existing infrastructure. Ask user. |
| Testing Strategy | Unit vs E2E vs both | STOP. Check QA requirements. Ask user. |
You CANNOT make technology decisions autonomously. STOP and ask.
See shared-patterns/shared-anti-rationalization.md for universal anti-rationalizations (including Specialist Dispatch section).
Self-sufficiency bias check: If you're tempted to implement directly, ask:
If any answer is yes → You MUST DISPATCH the specialist. This is NON-NEGOTIABLE.
See shared-patterns/shared-anti-rationalization.md for universal anti-rationalizations (including Specialist Dispatch section and Universal section).
<cannot_skip>
These requirements are NON-NEGOTIABLE:
| Requirement | Why It Cannot Be Waived |
|---|---|
| Dispatch to specialist | Specialists have standards loading, you don't |
| 8-gate development cycle | Gates prevent quality regressions |
| Parallel reviewer dispatch | Sequential review = 3x slower, same cost |
| TDD in Gate 0 | Test-first ensures testability |
| User approval in Gate 7 | Only users can approve completion |
User cannot override these. Time pressure cannot override these. "Simple task" cannot override these.
See shared-patterns/shared-pressure-resistance.md for universal pressure scenarios (including Combined Pressure Scenarios and Emergency Response).
Critical Reminder:
See shared-patterns/shared-pressure-resistance.md → Emergency Response section for the complete protocol.
Emergency Dispatch Template:
Task tool:
subagent_type: "bee:backend-engineer-php"
model: "opus"
prompt: "URGENT PRODUCTION INCIDENT: [brief context]. [Your specific request]"
IMPORTANT: Specialist dispatch takes 5-10 minutes, not hours. This is NON-NEGOTIABLE even under CEO pressure.
See shared-patterns/shared-pressure-resistance.md → Combined Pressure Scenarios section.
<dispatch_required agent="{specialist}"> Use Task tool to dispatch appropriate specialist based on technology need. </dispatch_required>
| Agent | Specializations | Use When |
|---|---|---|
bee:backend-engineer-php | PHP Services, MySQL/MongoDB, Kafka/RabbitMQ, OAuth2/JWT, gRPC, concurrency | PHP services, ORM patterns, auth/authz, concurrency issues |
bee:database-engineer | Schema design, indexing, query optimization, migration safety, replication, sharding, tuning | DB schema design, index strategy, migration planning, query optimization, scaling |
bee:frontend-bff-engineer-typescript | Next.js API Routes BFF, Clean/Hexagonal Architecture, DDD patterns, Inversify DI, repository pattern | BFF layer, Clean Architecture, DDD domains, API orchestration |
bee:frontend-designer | Bold typography, color systems, animations, unexpected layouts, textures/gradients | Landing pages, portfolios, distinctive dashboards, design systems |
bee:ui-engineer | Wireframe-to-code, Design System compliance, UX criteria satisfaction, UI states implementation | Implementing from product-designer specs (ux-criteria.md, user-flows.md, wireframes/) |
bee:qa-analyst | Test strategy, coverage analysis, API testing, fuzz/property/integration/chaos testing (PHP) | Backend test planning, coverage gaps, quality gates (PHP-focused) |
bee:qa-analyst-frontend | Vitest, Testing Library, axe-core, Playwright, Lighthouse, Core Web Vitals, snapshot testing | Frontend test planning, accessibility, visual, E2E, performance testing (React) |
bee:frontend-engineer-vuejs | Vue 3, Nuxt 3, Pinia, VeeValidate, shadcn-vue, Composition API, TypeScript | Vue.js/Nuxt 3 components, state management, forms, performance optimization |
bee:ui-engineer-vuejs | Wireframe-to-Vue-code, Design System compliance (shadcn-vue), UX criteria satisfaction, UI states | Implementing from product-designer specs (ux-criteria.md, user-flows.md, wireframes/) |
bee:qa-analyst-frontend-vuejs | Vitest, Vue Testing Library, axe-core, Playwright, Lighthouse, Core Web Vitals, Vue snapshots | Vue.js/Nuxt 3 test planning, accessibility, visual, E2E, performance testing |
bee:frontend-engineer-react-native | React Native, Expo, NativeWind, Zustand, React Hook Form, Reanimated, React Navigation, TypeScript | React Native/Expo mobile components, state management, forms, performance optimization |
bee:ui-engineer-react-native | Wireframe-to-RN-code, Design System compliance (NativeWind), UX criteria satisfaction, UI states | Implementing from product-designer specs into React Native/Expo mobile screens |
bee:qa-analyst-frontend-react-native | Jest, React Native Testing Library, Detox, Maestro, accessibility, device coverage, E2E mobile flows | React Native/Expo test planning, accessibility, E2E, performance testing |
bee:sre | Structured logging, tracing, health checks, observability | Logging validation, tracing setup, health endpoint verification |
Dispatch template:
Task tool:
subagent_type: "bee:{agent-name}"
model: "opus"
prompt: "{Your specific request with context}"
Frontend Agent Selection:
bee:frontend-designer = visual aesthetics, design specifications (no code)bee:frontend-bff-engineer-typescript = business logic/architecture, BFF layerbee:ui-engineer = implementing UI from product-designer specs into React/Next.jsbee:ui-engineer-vuejs = implementing UI from product-designer specs into Vue 3/Nuxt 3bee:ui-engineer-react-native = implementing UI from product-designer specs into React Native/Expobee:frontend-engineer-vuejs = Vue 3/Nuxt 3 development without design specsbee:frontend-engineer-react-native = React Native/Expo mobile development without design specsWhen to use bee:ui-engineer vs bee:ui-engineer-vuejs vs bee:ui-engineer-react-native:
Use bee:ui-engineer (React), bee:ui-engineer-vuejs (Vue.js/Nuxt 3), or bee:ui-engineer-react-native (React Native/Expo) when product-designer outputs exist in docs/pre-dev/{feature}/. All three agents specialize in translating design specifications into production code while ensuring all UX criteria are satisfied — choose based on the project's frontend stack.
Both can be used together: Get developer specialist guidance during design, then run general reviewers before merge.
If you need multiple specialists (e.g., backend engineer + SRE), dispatch in parallel (single message, multiple Task calls):
✅ CORRECT:
Task #1: bee:backend-engineer-php
Task #2: bee:sre
(Both run in parallel)
❌ WRONG:
Task #1: bee:backend-engineer-php
(Wait for response)
Task #2: bee:sre
(Sequential = 2x slower)
Remember:
"I need a PHP service. Let me dispatch
bee:backend-engineer-phpto design it."
"I'll manually read PHP best practices and design the service myself."
Agents: See "16 Developer Specialists" table above.
Skills: bee:using-dev-team (this), bee:dev-cycle (8-gate backend workflow), bee:dev-cycle-frontend (9-gate React frontend workflow), bee:dev-cycle-frontend-vuejs (9-gate Vue.js/Nuxt 3 frontend workflow), bee:dev-cycle-frontend-react-native (9-gate React Native/Expo frontend workflow), bee:dev-refactor (backend/general codebase analysis), bee:dev-refactor-frontend (React frontend codebase analysis), bee:dev-refactor-frontend-vuejs (Vue.js/Nuxt 3 frontend codebase analysis), bee:dev-refactor-frontend-react-native (React Native/Expo codebase analysis)
Commands: /bee:dev-cycle (backend tasks), /bee:dev-cycle-frontend (React frontend tasks), /bee:dev-cycle-frontend-vuejs (Vue.js frontend tasks), /bee:dev-cycle-frontend-react-native (React Native/Expo tasks), /bee:dev-refactor (analyze backend/general codebase), /bee:dev-refactor-frontend (analyze React frontend codebase), /bee:dev-refactor-frontend-vuejs (analyze Vue.js/Nuxt 3 frontend codebase), /bee:dev-refactor-frontend-react-native (analyze React Native/Expo codebase), /bee:dev-status, /bee:dev-cancel, /bee:dev-report
Note: Missing agents? Check .claude-plugin/marketplace.json for bee-dev-team plugin.
All workflows converge to the 8-gate development cycle:
| Workflow | Entry Point | Output | Then |
|---|---|---|---|
| New Feature | /bee:pre-dev-feature "description" | docs/pre-dev/{feature}/tasks.md | → /bee:dev-cycle tasks.md |
| Direct Tasks | /bee:dev-cycle tasks.md | — | Execute 6 gates directly |
| Refactoring | /bee:dev-refactor | docs/bee:dev-refactor/{timestamp}/tasks.md | → /bee:dev-cycle tasks.md |
| Frontend Refactoring | /bee:dev-refactor-frontend | docs/bee:dev-refactor-frontend/{timestamp}/tasks.md | → /bee:dev-cycle-frontend tasks.md |
| Vue.js Refactoring | /bee:dev-refactor-frontend-vuejs | docs/bee:dev-refactor-frontend-vuejs/{timestamp}/tasks.md | → /bee:dev-cycle-frontend-vuejs tasks.md |
| React Native Refactoring | /bee:dev-refactor-frontend-react-native | docs/bee:dev-refactor-frontend-react-native/{timestamp}/tasks.md | → /bee:dev-cycle-frontend-react-native tasks.md |
8-Gate Development Cycle:
| Gate | Focus | Agent(s) |
|---|---|---|
| 0: Implementation | TDD: RED→GREEN→REFACTOR | bee:backend-engineer-*, bee:frontend-bff-engineer-typescript, bee:ui-engineer, bee:ui-engineer-vuejs, bee:ui-engineer-react-native |
| 1: Unit Testing | Unit tests, coverage ≥85% | bee:qa-analyst |
| 2: Fuzz Testing | Input mutation, edge cases | bee:qa-analyst |
| 3: Property Testing | Invariant testing | bee:qa-analyst |
| 4: Integration Testing | External dependencies | bee:qa-analyst |
| 5: Chaos Testing | Failure injection | bee:qa-analyst |
| 6: Review | 6 reviewers IN PARALLEL | bee:code-reviewer, bee:business-logic-reviewer, bee:security-reviewer, bee:test-reviewer, bee:nil-safety-reviewer, bee:consequences-reviewer |
| 7: Validation | User approval: APPROVED/REJECTED | User decision |
Gate 0 Agent Selection for Frontend:
docs/pre-dev/{feature}/ux-criteria.md exists (React stack) → use bee:ui-engineerdocs/pre-dev/{feature}/ux-criteria.md exists (Vue.js stack) → use bee:ui-engineer-vuejsdocs/pre-dev/{feature}/ux-criteria.md exists (React Native stack) → use bee:ui-engineer-react-nativebee:frontend-bff-engineer-typescriptbee:frontend-engineer-vuejsbee:frontend-engineer-react-nativeKey Principle: Backend follows the 8-gate process. Frontend (React, Vue.js, and React Native) follows the 9-gate process.
Use /bee:dev-cycle-frontend for React/Next.js frontend-specific development:
| Gate | Focus | Agent(s) |
|---|---|---|
| 0: Implementation | TDD: RED→GREEN→REFACTOR | bee:frontend-engineer, bee:ui-engineer, bee:frontend-bff-engineer-typescript |
| 1: Accessibility | WCAG 2.1 AA, axe-core, keyboard nav | bee:qa-analyst-frontend |
| 3: Unit Testing | Vitest + Testing Library, ≥85% | bee:qa-analyst-frontend |
| 4: Visual Testing | Snapshots, states, responsive | bee:qa-analyst-frontend |
| 5: E2E Testing | Playwright, cross-browser, user flows | bee:qa-analyst-frontend |
| 6: Performance | Core Web Vitals, Lighthouse > 90 | bee:qa-analyst-frontend |
| 7: Review | 6 reviewers IN PARALLEL | bee:code-reviewer, bee:business-logic-reviewer, bee:security-reviewer, bee:test-reviewer, bee:nil-safety-reviewer, bee:consequences-reviewer |
| 8: Validation | User approval: APPROVED/REJECTED | User decision |
Use /bee:dev-cycle-frontend-vuejs for Vue.js/Nuxt 3 frontend-specific development:
| Gate | Focus | Agent(s) |
|---|---|---|
| 0: Implementation | TDD: RED→GREEN→REFACTOR | bee:frontend-engineer-vuejs, bee:ui-engineer-vuejs, bee:frontend-bff-engineer-typescript |
| 1: Accessibility | WCAG 2.1 AA, axe-core, keyboard nav | bee:qa-analyst-frontend-vuejs |
| 3: Unit Testing | Vitest + Vue Testing Library, ≥85% | bee:qa-analyst-frontend-vuejs |
| 4: Visual Testing | Snapshots, states, responsive | bee:qa-analyst-frontend-vuejs |
| 5: E2E Testing | Playwright, cross-browser, user flows | bee:qa-analyst-frontend-vuejs |
| 6: Performance | Core Web Vitals, Lighthouse > 90 | bee:qa-analyst-frontend-vuejs |
| 7: Review | 6 reviewers IN PARALLEL | bee:code-reviewer, bee:business-logic-reviewer, bee:security-reviewer, bee:test-reviewer, bee:nil-safety-reviewer, bee:consequences-reviewer |
| 8: Validation | User approval: APPROVED/REJECTED | User decision |
Use /bee:dev-cycle-frontend-react-native for React Native/Expo mobile-specific development:
| Gate | Focus | Agent(s) |
|---|---|---|
| 0: Implementation | TDD: RED→GREEN→REFACTOR | bee:frontend-engineer-react-native, bee:ui-engineer-react-native |
| 1: Accessibility | WCAG 2.1 AA, accessible labels, focus | bee:qa-analyst-frontend-react-native |
| 3: Unit Testing | Jest + React Native Testing Library, ≥85% | bee:qa-analyst-frontend-react-native |
| 4: Visual Testing | Snapshots, states, responsive | bee:qa-analyst-frontend-react-native |
| 5: E2E Testing | Detox/Maestro, device coverage, user flows | bee:qa-analyst-frontend-react-native |
| 6: Performance | JS thread, startup time, bundle size | bee:qa-analyst-frontend-react-native |
| 7: Review | 6 reviewers IN PARALLEL | bee:code-reviewer, bee:business-logic-reviewer, bee:security-reviewer, bee:test-reviewer, bee:nil-safety-reviewer, bee:consequences-reviewer |
| 8: Validation | User approval: APPROVED/REJECTED | User decision |
Backend → Frontend Handoff: When backend dev cycle completes, it produces a handoff with endpoints, types, and contracts. The frontend dev cycle consumes this handoff to verify E2E tests exercise the correct API endpoints.
| Step | Command | Output |
|---|---|---|
| 1. Backend | /bee:dev-cycle tasks.md | Backend code + handoff (endpoints, contracts) |
| 2. Frontend (React) | /bee:dev-cycle-frontend tasks-frontend.md | React/Next.js frontend code consuming backend endpoints |
| 2. Frontend (Vue.js) | /bee:dev-cycle-frontend-vuejs tasks-frontend.md | Vue 3/Nuxt 3 frontend code consuming backend endpoints |
| 2. Frontend (React Native) | /bee:dev-cycle-frontend-react-native tasks-frontend.md | React Native/Expo mobile code consuming backend endpoints |
Dispatch based on your need: