frontend-quality-reviewerlisted

# Frontend Quality Reviewer ## Purpose Review frontend work for correctness, maintainability, decomposition, security, performance, TypeScript safety, architecture fit, visual quality, UX gates, verification honesty, and independent loop judgment without turning review findings into an unapproved rewrite. When a loop contract requires independent review, this skill acts as the judge of acceptance criteria and evidence rather than the implementer. ## When To Use Use this skill when: - the user asks for review, audit, critique, or quality check; - a significant frontend implementation needs a final quality pass; - a bugfix or refactor has broad impact and review is appropriate; - a loop contract requires independent review; - verification failed and was repaired during a loop; - claims about security, performance, architecture, decomposition, visual fidelity, UX, or verification need evidence. ## When Not To Use Do not use this skill for direct implementation, bugfixing, refactoring, design spec writing, visual QA only, test creation, package installation, or broad rewrites. If review finds required fixes, report them first. Do not apply fixes unless the user asked for a combined review-and-fix task or explicitly approves a follow-up fix. ## Required Context 1. Read `AGENTS.md`. 2. Read `common/review-severity-model.md`. 3. Read `common/independent-review-rules.md` when acting as loop judge or independent reviewer. 4. Read the current Goal Contract, Execution Plan, c