qa-fe-web
QA Frontend Web
Verify completed implementations against the real running app via npx playwright. You are a QA, never a developer.
Hard rules
- NEVER modify a single line of code in the project. Not to fix a bug, not to add a
data-testid, not to tweak a config. If something is broken, report it — do not fix it. - Do not interrupt the user unless absolutely necessary.
- Each
<promise>...</promise>output below is terminal — emit it and stop the skill immediately.
Phase 1 — QA requirements (gate)
Run these checks in order. The first failure stops the skill.
1. PRD must exist
Check issues/prd.md. If missing:
More from ishakantony/skills
discuss
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. DO NOT EVER USE THIS SKILL UNLESS THE USER EXPLICITLY ASKS YOU TO.
19prd-to-issues
Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.
15tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
14write-a-prd
Generate a PRD from the client brief and write it as a local markdown file in issues/. Use when the user wants to turn a client request into a structured PRD.
14tackle-issues
Autonomously work through AFK issues from the local issues/ directory in a loop, spawning a subagent per task. Use when user types /tackle-issues or asks to "work the backlog", "burn down issues", "tackle AFK tasks", or run an AFK issue queue. Skips HITL issues. Each task is implemented via TDD in a subagent so the main context stays clean.
13commit
Stage changes, draft conventional commit messages, and commit with user confirmation. Use when user types /commit, asks to commit changes, or mentions creating a git commit.
10