frontend-code-review
Conducts detailed code reviews for frontend files to ensure quality and compliance with UI guidelines.
Install
mkdir -p .claude/skills/frontend-code-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/559" && unzip -o skill.zip -d .claude/skills/frontend-code-review && rm skill.zipInstalls to .claude/skills/frontend-code-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Review Dify frontend code for correctness, accessibility, component design, dify-ui usage, data/query boundaries, performance, and tests. Trigger for `.tsx`, `.ts`, `.js`, UI, React, Next.js, pending-change, or focused frontend review requests.Key capabilities
- →Review frontend code for accessibility and semantic HTML
- →Audit component architecture and state management
- →Validate data query contracts and API integration
- →Check performance against Vercel-based guidelines
- →Identify security and authorization leaks in UI code
How it works
The skill applies a set of rule packs covering accessibility, component architecture, and performance to the provided code. It identifies issues by comparing the code against established Dify-specific invariants and industry standards.
Inputs & outputs
When to use frontend-code-review
- →Reviewing component code
- →Auditing frontend accessibility
- →Checking performance standards
- →Validating UI implementation
About frontend-code-review
Checks frontend code for correctness, accessibility, and architectural standards. It supports both focused file reviews and inspection of pending changes against established frontend rules.
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
When not to use it
- →Reviewing backend-only code under api/
Prerequisites
Limitations
- →Does not automatically implement fixes
- →Requires specific local documentation context for full accuracy
How it compares
It automates the application of specific project-wide coding standards and design system rules rather than relying on generic linting.
Compared to similar skills
frontend-code-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| frontend-code-review (this skill) | 11 | 5mo | No flags | Advanced |
| frontend-developer | 27 | 7mo | No flags | Intermediate |
| frontend-patterns | 11 | 5mo | Review | Intermediate |
| next-best-practices | 0 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by langgenius
View all by langgenius →You might also like
frontend-developer
sickn33
Build React components, implement responsive layouts, and handle client-side state management. Masters React 19, Next.js 15, and modern frontend architecture. Optimizes performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.
frontend-patterns
affaan-m
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
next-best-practices
pedronauck
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
senior-frontend
FISCFED9
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
frontend-patterns
forgivesam168
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
accessibility-compliance
wshobson
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.