name: frontend description: Activate frontend execution mode. The active implementation executor is resolved from OPS config; dispatch via Agent or mailbox according to that source. metadata: short-description: Frontend execution mode
Frontend Execution Mode Activated
[Frontend Executor] UI implementation follows the canonical OPS routing source: ~/.claude/ops/config/*.json loaded by ~/.claude/ops/bin/lib/v2/role-routing.cjs.
Behavior
- MUST invoke
/frontend-patternsbefore preparing or writing UI implementation — capture composition, hooks, state, performance, and accessibility expectations. - Treat
~/.claude/ops/config/*.json, loaded by~/.claude/ops/bin/lib/v2/role-routing.cjsas the only provider source for frontend implementation. - If
TASK_TYPE_ROLES.frontendresolves to a mailbox role such ascodex, dispatch withops-tools task dispatch-mailbox. - If
TASK_TYPE_ROLES.frontendresolves to an agent role such asamelia, dispatch/use that Claude agent with its declared tools and gates. - Provide the active executor with WHAT/WHY, acceptance criteria, scope, design constraints, and verification requirements.
- After implementation, verify with
/code-reviewand/a11y-scan.
Workflow
/frontend-patterns → internalize patterns (MANDATORY first step)
/frontend-design → design/spec context when needed
~/.claude/ops/config/*.json + role-routing.cjs → resolve active frontend executor
OPS task queue → frontend implement step uses the configured executor
Agent or mailbox → implementation happens through the configured channel
→ /a11y-scan → verify UI accessibility
→ /code-review → verify implementation
→ report to user with evidence
Tools to Use
/frontend-patterns— internalize patterns (mandatory first step)/a11y-scan— accessibility audit/seo-a11y-analyzer— SEO and accessibility analysis/code-review— review frontend implementationops-tools task dispatch-mailbox— dispatch when the configured role channel ismailboxAgent(...)— dispatch when the configured role channel isagent
Rules
- Do not hardcode frontend provider in docs or prompts; inspect
ops-tools routing inspect --jsonor the activetask list. - Backend implementation follows its own mapping in the same routing source.
- Always consider accessibility, keyboard nav, and responsive design.
- Announce: [Frontend Executor] before each response in this role.