Automated exploratory bug hunting on web applications — explore, detect, and report bugs via browser automation
Use this agent when the user wants to explore a running web application to find bugs. This agent navigates the app via browser automation, interacts with UI elements, monitors console and network for errors, and reports raw findings. <example> Context: User has a running web app and wants to find bugs. user: "Explore http://localhost:3000 and find bugs" assistant: "I'll launch the qa-explorer agent to navigate the app, interact with UI elements, monitor console and network errors, and report any bugs found." <commentary> User explicitly asks to explore a running app for bugs. The explorer agent will use browser tools to navigate, interact, and detect issues. </commentary> </example> <example> Context: User wants to test a specific feature in their web application. user: "Test the mandate creation flow on the portal" assistant: "I'll use the qa-explorer agent to systematically test the mandate creation flow — testing happy path, edge cases, and monitoring for errors." <commentary> Scope-guided exploration. The explorer focuses on a specific feature flow rather than the entire app. </commentary> </example> <example> Context: User wants to test the app with different user roles. user: "Hunt for bugs on the admin panel. I'll give you admin and regular user credentials." assistant: "I'll launch the qa-explorer agent to test the admin panel with both roles, checking for permission issues and role boundary violations." <commentary> Role-aware testing. The explorer tests with multiple credentials to find permission and authorization bugs. </commentary> </example>
Use this agent when raw QA findings need to be validated, filtered, and compiled into a structured bug report. This agent takes exploration results, removes false positives, verifies evidence, and produces a prioritized QA Bug Report. <example> Context: The qa-explorer agent has returned raw findings from a testing session. user: "Compile the bugs we found into a report" assistant: "I'll launch the qa-reporter agent to validate the findings, filter false positives, and compile a structured bug report with severity classification." <commentary> Raw findings exist from a previous exploration. The reporter validates, triages, and formats them into a clean report. </commentary> </example> <example> Context: User has a list of manually noted issues and wants a structured report. user: "I found several issues during manual testing, can you format them into a proper QA report?" assistant: "I'll use the qa-reporter agent to structure your findings into a standardized bug report with severity ratings and evidence." <commentary> User has informal findings that need professional formatting. The reporter applies severity classification and report structure. </commentary> </example> <example> Context: A QA exploration session has completed and the user wants the final output. user: "Generate the final bug report from this session" assistant: "I'll launch the qa-reporter agent to compile all findings into a prioritized bug report, filtering out false positives and duplicates." <commentary> End-of-session report generation. The reporter produces the definitive deliverable. </commentary> </example>
Use this skill whenever the user mentions QA, bug hunting, testing, quality assurance, exploratory testing, bug reports, severity classification, or wants to find bugs in a web application. Also use when the user says "test my app", "find bugs", "explore for issues", or asks about bug severity, test methodology, or report format. This is the foundational knowledge base for all qa-hunter testing work. When in doubt about whether QA testing principles apply, they do — load this skill.
Use this skill whenever the user wants to test a web application, needs a testing checklist, asks what to test, mentions form testing, navigation testing, console errors, network monitoring, i18n testing, accessibility testing in a QA context, or browser-based testing. Also use when the user says "test this page", "check for errors", "run through the checklist", or asks about edge cases to test. This skill provides the comprehensive testing checklists that qa-explorer agents use to systematically find bugs.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Custom Claude Code plugins for design, UX, QA, and development workflows.
Expert UI/UX plugin covering the full design lifecycle: conception, validation, and audit.
Commands:
| Command | Description |
|---|---|
/ux-design | Full UX design pipeline with web research and structured specs |
/ux-validate | Quick UX validation during development |
/ux-audit | Comprehensive UX audit with scoring (/100) and action plan |
Agents:
| Agent | Role |
|---|---|
ux-researcher | Web research on UX best practices, trends, and benchmarks |
ux-designer | Produces structured UX Specifications with wireframes |
ux-auditor | Evaluates interfaces against Nielsen heuristics and WCAG |
Skills (auto-activated):
| Skill | Domain |
|---|---|
ux-foundations | Nielsen heuristics, psychology laws, WCAG 2.2 AA, design systems |
ux-landing-page | Conversion optimization, hero sections, CTAs, pricing tables |
ux-saas-app | Navigation, onboarding, dashboards, notifications |
ux-admin-portal | Data tables, CRUD, bulk actions, RBAC, search/filters |
ux-audit-framework | Severity scales, scoring rubric, audit methodology |
Automated exploratory bug hunting on web applications. Explores via browser automation, detects bugs, and produces structured reports.
Prerequisites: Requires a Chrome DevTools MCP server (launch with claude --chrome).
Commands:
| Command | Description |
|---|---|
/qa-explore | Explore a running web app to find bugs (main command) |
/qa-audit | Systematic audit with specific checklists (i18n, a11y, forms, etc.) |
/qa-report | Compile raw findings into a structured bug report |
Agents:
| Agent | Role |
|---|---|
qa-explorer | Navigates apps via browser, interacts with UI, discovers bugs |
qa-reporter | Validates findings, filters false positives, compiles reports |
Skills (auto-activated):
| Skill | Domain |
|---|---|
qa-foundations | Oracle layers, bug severity (S0-S4), confidence levels, report format |
qa-web-testing | Testing checklists: forms, navigation, CRUD, console, network, i18n, a11y |
# Add the marketplace
claude plugin marketplace add WilliamFontaine/claude-plugins-marketplace
# Install a plugin
claude plugin install ux-expert@willdev-plugins
claude plugin install qa-hunter@willdev-plugins
Each plugin will be available in your next Claude Code session.
plugins/
├── ux-expert/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── agents/
│ ├── commands/
│ └── skills/
│ ├── ux-foundations/
│ ├── ux-landing-page/
│ ├── ux-saas-app/
│ ├── ux-admin-portal/
│ └── ux-audit-framework/
└── qa-hunter/
├── .claude-plugin/
│ └── plugin.json
├── agents/
├── commands/
└── skills/
├── qa-foundations/
└── qa-web-testing/
Expert UI/UX plugin: design, validate, and audit interfaces for SaaS, landing pages, and admin portals
npx claudepluginhub williamfontaine/claude-plugins-marketplace --plugin qa-hunterA UX regression testing skill for browser-based and webview-based apps. Runs after E2E to catch usability, journey, accessibility, and interface-quality issues before they ship.
UX testing toolkit for Claude Code — generate user journey stories, walk them through a real browser, and implement the issues found.
Canary browser automation + recorded QA sessions: a sandbox scripting reference, verify/automate/session/review skills, JTBD subagents, and /canary slash commands.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.