React Best Practices
Prioritized React and Next.js guidance for data flow, bundles, and rendering.
Composition Patterns
Reshape growing React component APIs with composition and explicit state boundaries.
The editorial verdict
Where it earns its place.
A targeted companion for component libraries accumulating boolean props and tangled state. It favors compound components and explicit composition, with React-version details included in the guidance. It will help structure a system, but it does not choose the system’s visual language.
Reach for it when
- Refactoring reusable React component APIs
- Separating state management from component presentation
Think twice if
- You need a complete component implementation library
- Your project 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.