From jacked
Use when testing UI changes for visual correctness, interactions, console errors, and edge cases. Performs browser-based QA and returns a detailed issue list for planning fixes.
npx claudepluginhub jackneil/claude-jacked --plugin jackedThis skill uses the workspace's default tool permissions.
First, check if a repo-scoped version exists in the current project:
Guides strict Test-Driven Development (TDD): write failing tests first for features, bugfixes, refactors before any production code. Enforces red-green-refactor cycle.
Guides systematic root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Guides A/B test setup with mandatory gates for hypothesis validation, metrics definition, sample size calculation, and execution readiness checks.
First, check if a repo-scoped version exists in the current project:
.claude/skills/qa/SKILL.md exists (Glob) → read and follow it instead of this file..claude/commands/qa.md exists (Glob) → read and follow it instead.Two commands are available — read the appropriate one and follow it:
~/.claude/commands/qa.md — Quick, focused QA pass (single agent). Visual, interactive, console, and edge case checks on specific changes. Best for targeted fixes or single-feature verification.~/.claude/commands/ux.md — Thorough parallel UX review (multiple agents). Tests 6 UX aspects across multiple pages simultaneously. Best when changes touch layout, navigation, or multiple components.Both are read-only detection tools — they return a detailed issue list but do NOT fix code. After receiving findings, use superpowers:writing-plans to build a fix plan from the issues, let the user iterate, then execute with /dcr verification.
Decision guide:
/qa/ux/jacked-setup qa to pre-configure browser tool and framework checks