Frontend review skills yaojingang yao meta skill examples evolution frontend review final
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill frontend-review__skills-yaojingang-yao-meta-skill-examples-evolution-frontend-review-finalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review frontend code for accessibility, risky UI security issues, missing states, and common UX regressions. Use when asked to review React, UI, frontend components, forms, a11y, or pre-merge frontend quality.
SKILL.md
0.9 KB, as published. Nobody here has run it
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
- Identify the UI surface and user flows affected.
- Check accessibility, security-sensitive inputs, loading states, and error states.
- Report findings by severity with concrete code references.
- 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.