Review frontend code for accessibility, UI security, missing states, and UX regressions. Use when asked to review React components, run a pre-merge frontend review, or check a11y and unsafe rendering.
Installs into .claude/skills of the current project.
Are you the author of Frontend Review?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/aiskillstore-frontend-review)
---
name: frontend-review
description: Review frontend code for accessibility, UI security, missing states, and UX regressions. Use when asked to review React components, run a pre-merge frontend review, or check a11y and unsafe rendering.
---
# Frontend Review
Review UI code with a pre-merge mindset. Findings come first. Focus on behavior regressions, accessibility gaps, risky form handling, unsafe rendering, and missing user states.
## Workflow
1. Identify the UI surface and user flows affected.
2. Check accessibility, security-sensitive inputs, loading states, and error states.
3. Report findings by severity with concrete code references.
4. Prefer actionable fixes over generic advice.
## Output Contract
- Start with findings, ordered by severity.
- Include file references for each finding.
- Call out open questions separately from confirmed issues.
- If there are no findings, say that explicitly and note residual risks or test gaps.
## Reference Map
- Read `references/checklist.md` for the review standard.
