What problem does it solve? Frontend code reviews often miss concrete regressions because reviewers lack a consistent, evidence-based checklist across accessibility, component architecture, data contracts, and performance. This Skill turns review requests into structured findings with severity levels, file-line references, and concrete fix directions. ## Core Features & Use Cases - Scoped Rule Routing: Reads only the rule packs matched by the diff, covering accessibility, component architecture, data/query contracts, testing, performance, and code quality. - Severity-Ranked Findings: Reports P0-P3 findings tied to observable failures, violated contracts, or demonstrated maintenance risks, each with reproduction path and fix direction. - Dify-Specific Packs: Ships optional rule packs for Dify UI primitives and runtime invariants, which are skipped when reviewing non-Dify projects. - Use Case: Paste a pull request diff for a React form component and receive findings such as missing label relationships, incorrect disabled-state handling, or effects that should be event handlers, ordered by severity. ## Quick Start Review the current pending changes in my frontend project and report any accessibility, architecture, or performance issues with severity levels.