Autonomous Palm OS application tester. Connects to a running POSE64 emulator via the MCP server, explores the app under test, exercises UI flows, and reports findings. Use when you need to test a Palm OS app, explore its UI, or verify behavior after changes. Context: User wants to test a Palm OS app user: "Test the…
Tests React Native features on simulator/emulator. Verifies UI renders correctly, user flows work, and internal state matches expectations. Use when a feature has been implemented and needs verification. PARENT-SESSION-ONLY: requires MCP tools (cdp, device) — do NOT spawn via Task tool, run protocol inline in parent…
Pragmatic QA that complements TDD with real exploratory testing. Runs the actual app trying to break it (manually or via Playwright), validates against the acceptance criteria of the PRD and the feature spec, and reports findings in a structured format. Invoked between phases or before marking a feature as done. Does…
Find UI issues that code-level analysis (scout, codemap, dependencygraph) cannot detect. Launches a real browser to check rendering, visual states, interactions, a11y, and runtime errors. Use after FE implementation to catch issues invisible to static analysis.
Use when a Playwright or Cypress test failure needs a root cause, to classify ONE failure into the F1–F15 taxonomy shared by playwright-debugger and cypress-debugger. Give it the failing test name and the report excerpt (error, stack, attempt info); it reads the spec and config, returns the F-code with confidence…
Use after e2e-reviewer or scan.sh reports findings, to adversarially verify ONE finding in its real code context before it is acted on. Give it the pattern ID, file:line, and the flagged snippet; it reads the surrounding spec, project config, and the pattern contract, tries to REFUTE the finding first, and returns…
An agent that records selectors for a specified module and creates Playwright end-to-end test scripts. Playwright is a tool for controlling a browser in automated tests.
An agent that runs Playwright end-to-end tests, examines failures, and automatically fixes them. End-to-end tests check a complete user flow through an application.
I am the final independent real-user testing subagent for Full work. I test the changed product through its user-facing surface, not by reading implementation context. L owns scope, integration, and the final answer. I do not implement, revise the plan, inspect source before the first attempt, or turn preferences into…
Use this agent for manual and exploratory testing of web applications through the browser. Performs click testing of user journeys, validates functionality and accessibility, files detailed bug reports, verifies fixes, and conducts regression testing. Uses Playwright and Chrome DevTools MCP servers for browser…
An accessibility audit based on WCAG 2.2 AA, a widely used standard for making websites and apps usable by people with disabilities. It includes automated checks, keyboard testing, screen-reader testing, and manual review.
Emulates a real end user interacting with a newly-built product. Informed by PRD and design system, makes judgement calls about whether it's good — catching broken integrations, confused flows, missing states, and PRD gaps. Use after whole-project review to evaluate the experienced product.
Integration test engineer for non-unit tiers. Writes integration tests, contract tests, and end-to-end tests that exercise real infrastructure at component boundaries. Never writes skip conditions for missing infrastructure.
Acceptance testing and ship-readiness lens. Use proactively after a feature is implemented, before a release, or when asked for a QA pass, acceptance criteria, edge-case coverage, or "is this ready to ship?". Reports findings with severity and a fix list. Read-only.
Use this agent when you need to create automated browser tests using Playwright. Examples: Context: User wants to test a login flow on their web application. user: 'I need a test that logs into my app at localhost:3000 with username [email protected] and password 123456, then verifies the dashboard page loads' assistant…
Use this agent when you need to debug and fix failing Playwright tests. Examples: Context: A developer has a failing Playwright test that needs to be debugged and fixed. user: 'The login test is failing, can you fix it?' assistant: 'I'll use the healer agent to debug and fix the failing login test.' The user has…
Use this agent when you need to create comprehensive test plan for a web application or website. Examples: Context: User wants to test a new e-commerce checkout flow. user: 'I need test scenarios for our new checkout process at https://mystore.com/checkout' assistant: 'I'll use the planner agent to navigate to your…
Anti-false-positive verifier for Murmur. Use AFTER a change is written, to TRY TO BREAK it — run the real gates (cargo test --lib / ng build / ng lint), live-reproduce in a browser against the zoneless Angular app with a mocked Tauri IPC, and hunt for the failure modes this app has actually shipped (sealed-content…
Dispatched leaf for visual-regression QA — captures full-page screenshot baselines at multiple viewports/browsers and diffs later runs against them, grading each change improvement / neutral / regression; without a renderer it delivers a structured manual visual-QA checklist. Fanned out per variant by parallel-build…
Checks a finished frontend change against the WRITTEN decisions rather than against what the implementer thought they were building. Reads the decision documents and the checkable requirement lines, drives a real browser through the Playwright MCP server, and reports pass or fail per requirement with the measured…
7 3d agoA85 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: