Composition Patterns
Reshape growing React component APIs with composition and explicit state boundaries.
React Best Practices
Prioritized React and Next.js guidance for data flow, bundles, and rendering.
The editorial verdict
Where it earns its place.
A useful engineering companion once the interface has a visual direction. Its rule collection organizes React and Next.js performance work by impact, including waterfalls, bundles, and rendering behavior. It is guidance for investigation and refactoring; the catalog has not measured a speedup from applying it.
Reach for it when
- Reviewing React or Next.js interface code
- Prioritizing performance-oriented refactoring
Think twice if
- You need visual art direction
- Your frontend does not use React
Before you install
Compatibility & contents.
- Claude Code
- partial
- Cursor
- partial
- Codex
- partial
- Gemini CLI
- partial
- GitHub Copilot
- partial
- License
- MIT
- Bundled scripts
- None found
- Hooks
- None found
Native: documented support. Partial: setup or adaptation may be needed. Not verified: the source has not established this fact. “None found” describes the inspected skill, not a security audit. Read the methodology.
Source context
The repository, in numbers.
Source: GitHub / vercel-labs/agent-skills. Repository totals may be shared by several skills. Snapshot fetched ; these are not live counts. Check the snapshot date for freshness. Popularity is not a measure of design quality.
Watch the overlap.
No conflicts are recorded. This does not establish that every combination has been tested.