arc

Run mechanical verification and comprehensive codebase audit.

Smart commit, push, and npm publish with auto-splitting across domains.

Turn ideas into validated feature specs through collaborative dialogue with expert review.

Scope-aware planning and implementation with TDD.

Go-live and shareability checklist.

Quick code quality check per task. Verifies implementation is well-built — not just spec-compliant. Runs after spec-reviewer, before commit. Fast gate check, not deep review. <example> Context: Task just passed spec-reviewer. user: "Quick code quality check before commit" assistant: "I'll dispatch code-reviewer for a fast quality gate" <commentary> Spec says WHAT to build, code-reviewer checks HOW it's built. Quick pass/fail. </commentary> </example>

Use when a test fails unexpectedly during implementation. Investigates root cause systematically, distinguishes between test bugs and implementation bugs, and applies minimal fixes. Prefers event-based solutions over timeout increases. <example> Context: Test fails with timing-related error during implementation. user: "Test 'should complete batch' is failing with timeout" assistant: "I'll use the debugger to investigate the root cause" <commentary> Timing failures need systematic investigation, not timeout increases. Debugger will trace the issue. </commentary> </example> <example> Context: Multiple tests failing after a refactor. user: "3 tests in user-service.test.ts are now failing" assistant: "Let me dispatch the debugger to investigate these failures" <commentary> Concentrated failures in one file suggest a common root cause. Debugger will identify it. </commentary> </example>

Runs and fixes E2E tests (Playwright). Handles flaky tests, timing issues, and selector problems. Iterates until green or reports blockers. Keeps verbose output contained. <example> Context: E2E tests created as part of implementation. user: "Run the e2e tests for checkout flow" assistant: "I'll dispatch e2e-runner to run and fix any issues" <commentary> E2E tests produce verbose output. e2e-runner handles iteration and reports summary. </commentary> </example> <example> Context: E2E tests failing after UI changes. user: "E2E tests are broken after the redesign" assistant: "Let e2e-runner investigate and fix the selector issues" <commentary> UI changes often break selectors. e2e-runner will update them systematically. </commentary> </example>

Writes E2E tests with Playwright. Tests complete user journeys in real browsers — signup flows, checkout processes, authentication. Includes auth setup for Clerk and WorkOS. <example> Context: New feature needs end-to-end coverage. user: "Write E2E tests for the onboarding flow" assistant: "I'll dispatch e2e-test-writer to create Playwright tests for the full journey" <commentary> Multi-page user journey = E2E test. Real browser, real interactions. </commentary> </example>

Implements UI components from Figma designs. Use when the user provides a Figma URL or asks to build something from a design. The agent extracts design specifications via Figma MCP and generates production-ready code that respects the codebase's existing design system. Examples: - <example> Context: User shares a Figma link for a new component. user: "Implement this card component: [Figma URL]" assistant: "I'll use the figma-builder agent to build this component." </example> - <example> Context: User wants to add a new section matching a design. user: "Add the pricing section from this Figma file" assistant: "Let me implement that pricing section from the Figma design." </example>

Comprehensive codebase audit with verification and specialized reviewers. Generates actionable reports. Use when asked to "audit the codebase", "review code quality", "check for issues", "security review", or "performance audit". By default, run the complete audit: mechanical checks first, then specialist reviewers, then a scored report.

Smart commit, push, and npm publish with auto-splitting across domains. Creates atomic commits. Use when asked to "commit", "push changes", "publish", "save my work", or after completing implementation work. Automatically groups changes into logical commits.

Internal bridge from /arc:ideate feature specs to /arc:implement execution plans. Creates implementation plans with exact file paths, test code, and TDD cycles. Invoked by /arc:implement, not directly.

Turn ideas into validated feature specs through collaborative dialogue with built-in expert review. Use when asked to "design a feature", "plan an approach", "think through implementation", or when starting new work that needs product and technical shaping before coding.

Scope-aware implementation workflow with TDD and continuous quality checks. Use when asked to "implement this", "build this feature", "execute the plan", or after /arc:ideate has created a feature spec. For small work it creates a lightweight inline plan; for larger work it creates or loads a full implementation plan and executes task-by-task with build agents.