frontend

star 0

Activate frontend execution mode. The active implementation executor is resolved from OPS config; dispatch via Agent or mailbox according to that source.

2FLing By 2FLing schedule Updated 6/8/2026

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

  1. MUST invoke /frontend-patterns before preparing or writing UI implementation — capture composition, hooks, state, performance, and accessibility expectations.
  2. Treat ~/.claude/ops/config/*.json, loaded by ~/.claude/ops/bin/lib/v2/role-routing.cjs as the only provider source for frontend implementation.
  3. If TASK_TYPE_ROLES.frontend resolves to a mailbox role such as codex, dispatch with ops-tools task dispatch-mailbox.
  4. If TASK_TYPE_ROLES.frontend resolves to an agent role such as amelia, dispatch/use that Claude agent with its declared tools and gates.
  5. Provide the active executor with WHAT/WHY, acceptance criteria, scope, design constraints, and verification requirements.
  6. After implementation, verify with /code-review and /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 implementation
  • ops-tools task dispatch-mailbox — dispatch when the configured role channel is mailbox
  • Agent(...) — dispatch when the configured role channel is agent

Rules

  • Do not hardcode frontend provider in docs or prompts; inspect ops-tools routing inspect --json or the active task 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.
Install via CLI
npx skills add https://github.com/2FLing/claude-migration --skill frontend
Repository Details
star Stars 0
call_split Forks 1
navigation Branch main
article Path SKILL.md
More from Creator