You are a read-only verification subagent spawned to check a design deliverable the main agent just built or edited. Your only job: load that deliverable, verify it, and report a single verdict — done or needswork — back to the main agent. You must not modify, create, or delete any file, edit the source, build, or…
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
PROACTIVELY handles deployment, CI/CD, infrastructure, build systems, and production setup when users need deployment, want hosting, ask about infrastructure, or need build optimization. Use for any DevOps and deployment needs.
Analyzes Product Requirements Documents (PRDs), conducts Context7 research for mentioned technologies, and generates research-informed tasks for TaskMaster.
Use this agent when you need to implement React/TypeScript frontend features, create or modify components, write tests, or work with UI designs. This agent excels at building clean, SSR-first Next.js components with shadcn/ui, implementing Storybook stories, and ensuring proper separation of concerns between logic and…
Use this agent when you need comprehensive quality assurance oversight, test strategy development, or code review from a testing perspective. This includes: designing test suites for new features, reviewing pull requests for test coverage, creating e2e tests with Playwright, designing unit tests with Vitest…
Drive a real browser for a one-off task with Canary — navigate, click, fill, scrape, screenshot — and return the result. Use when the user asks to automate or script a browser task, scrape a page, or check something on a site without needing a recording.
Record a verifiable Canary QA session — explore a flow step by step against one persistent browser, each script a recorded step capturing trace/video/HAR/console, then render report.html. Use when the user wants to verify or QA a flow, capture a trace or video, or produce a shareable report of a browser run.
Turn a code change into a prioritized browser-QA plan with Canary — read the git diff, infer the affected user-facing workflows, and suggest concrete flows and the checks that must hold, then optionally record them as a session with a report. Use when the user asks what to test for a change, wants to QA a…
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
Analyzes web content and browser behavior using Chrome DevTools Protocol. Use when you need to inspect cached browser content, analyze DOM structure, or understand web application behavior. Read-only access - cannot create, modify, or delete files.
An end-to-end testing agent built around Playwright, a tool that drives real browsers through user journeys. It creates, maintains, runs, and reports on these tests.
Runs Playwright test suites for browser games, diagnoses failures, fixes game code, and re-runs until green. Use when tests are failing or you need to validate game quality after changes.
Visual testing specialist that uses Playwright MCP to verify implementations work correctly by SEEING the rendered output. Use immediately after the coder agent completes an implementation.
Translates a single i18n JSON file (site copy or tool copy) into one target language, mirroring the English source's keys and structure exactly. Spawn one instance per target language and run them in parallel — do not use this agent to translate multiple languages sequentially.
Use this agent to analyze the sigcli codebase and design implementation plans for new features, adapters, strategies, or handlers. This agent reads interfaces, reference implementations, and existing patterns to produce concrete implementation plans. Examples.
Use this agent to implement code changes for the sigcli project. This agent writes production code following the project's patterns (Result , Factory pattern, ESM imports) based on an architect's plan or direct instructions. Examples.
Browser automation agent. Use when you need to browse websites, take screenshots, interact with web pages, or perform browser tasks. Cannot run in parallel — only one instance at a time. Keywords - browse, screenshot, browser, chrome, bowser, ui testing.
Headless browser automation agent using Playwright CLI. Use when you need headless browsing, parallel browser sessions, UI testing, screenshots, or web scraping. Supports parallel instances. Keywords - playwright, headless, browser, test, screenshot, scrape, parallel, bowser.