From curdx-flow
Invoke when the user wants to test a UI/frontend in a real browser — accessibility, performance, console errors, network traffic, visual regression. Triggers on "browser test", "test in browser", "UI test", "e2e test", "frontend test", "accessibility", "a11y", "WCAG", "lighthouse", "performance audit", "console error", "network request", "cross-browser", "responsive", "mobile test", "visual regression", "screenshot".
npx claudepluginhub curdx/curdx-flow --plugin curdx-flowThis skill is limited to using the following tools:
You are invoked when the user wants real-browser QA of a UI flow.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You are invoked when the user wants real-browser QA of a UI flow.
chrome-devtools MCP is available (mcp__chrome-devtools__*). If missing, fall back to a manual checklist.Confirm with the user:
http://localhost:3000 or remote)flow-qa-engineerDelegate to the flow-qa-engineer agent. It will:
mcp__chrome-devtools__new_pagemcp__chrome-devtools__click / fill / navigatelist_console_messages, list_network_requests, take_screenshot, optionally lighthouse_auditProduce .flow/specs/<active>/qa-report.md with:
If bugs found: suggest /curdx-flow:debug "<bug title>" for systematic root-cause analysis.
If accessibility violations: suggest fixes inline with WCAG refs.
flow-qa-engineer agent: @${CLAUDE_PLUGIN_ROOT}/agents/flow-qa-engineer.md