Comprehensive guide for building modern React and Next.js applications. Covers performance optimization, component architecture, shadcn/ui patterns, Motion animations, accessibility, and React 19+ features.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionreact-best-practicesExecute the skills CLI command in your project's root directory to begin installation:
Fetches react-best-practices from dedalus-erp-pas/foundation-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate react-best-practices. Access via /react-best-practices in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
2
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2
stars
Comprehensive guide for building modern React and Next.js applications. Covers performance optimization, component architecture, shadcn/ui patterns, Motion animations, accessibility, and React 19+ features.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Component Architecture | CRITICAL | arch- |
| 2 | Eliminating Waterfalls | CRITICAL | async- |
| 3 | Bundle Size Optimization | CRITICAL | bundle- |
| 4 | Server Components & Actions | HIGH | server- |
| 5 | shadcn/ui Patterns | HIGH | shadcn- |
| 6 | State Management | MEDIUM-HIGH | state- |
| 7 | Motion & Animations | MEDIUM | motion- |
| 8 | Re-render Optimization | MEDIUM | rerender- |
| 9 | Accessibility | MEDIUM | a11y- |
| 10 | TypeScript Patterns | MEDIUM | ts- |
arch-functional-components - Use functional components with hooks exclusivelyarch-composition-over-inheritance - Build on existing components, don't extendarch-single-responsibility - Each component should do one thing wellarch-presentational-container - Separate UI from logic when beneficialarch-colocation - Keep related files together (component, styles, tests)arch-avoid-prop-drilling - Use Context or composition for deep propsFunctional Components Only
// Correct: Functional component with hooks
function UserProfile({ userId }: { userId: string }) {
const { data: user } = useUser(userId)
return <div>{user?.name}</div>
}
// Incorrect: Class component
class UserProfile extends React.Component { /* ... */ }
Composition Pattern
// Correct: Compose smaller components
function Card({ children }: { children: React.ReactNode }) {
return <div className="rounded-lg border p-4">{children}</div>
}
function CardHeader({ children }: { children: React.ReactNode }) {
return <div className="font-semibold">{children}</div>
}
// Usage
<Card>
<CardHeader>Title</CardHeader>
<p>Content</p>
</Card>
Avoid Prop Drilling
// Incorrect: Passing props through many levels
<App user={user}>
<Layout user={user}>
<Sidebar user={user}>
<UserMenu user={user} />
</Sidebar>
</Layout>
</App>
// Correct: Use Context for shared state
const UserContext = createContext<User | null>(null)
function App() {
const user = useCurrentUser()
return (
<UserContext.Provider value={user}>
<Layout>
<Sidebar>
<UserMenu />
</Sidebar>
</Layout>
</UserContext.Provider>
)
}
async-defer-await - Move await into branches where actually usedasync-parallel - Use Promise.all() for independent operationsasync-dependencies - Handle partial dependencies correctlyasync-api-routes - Start promises early, await late in API routesasync-suspense-boundaries - Use Suspense to stream contentWaterfalls are the #1 performance killer. Each sequential await adds full network latency.
Parallel Data Fetching
// Incorrect: Sequential waterfalls
async function Page() {
const user = await fetchUser()
const posts = await fetchPosts()
const comments = await fetchComments()
return <div>{/* render */}</div>
}
// Correct: Parallel fetching
async function Page() {
const [user, posts, comments] = await Promise.all([
fetchUser(),
fetchPosts(),
fetchComments()
])
return <div>{/* render */}</div>
}
Strategic Suspense Boundaries
// Stream content as it becomes available
function Page() {
return (
<div>
<Header />
<Suspense fallback={<PostsSkeleton />}>
<Posts />
</Suspense>
<Suspense fallback={<CommentsSkeleton />}>
<Comments />
</Suspense>
</div>
)
}
bundle-barrel-imports - Import directly, avoid barrel filesbundle-dynamic-imports - Use next/dynamic for heavy componentsbundle-defer-third-party - Load analytics/logging after hydrationbundle-conditional - Load modules only when feature is activatedbundle-preload - Preload on hover/focus for perceived speedAvoid Barrel File Imports
// Incorrect: Imports entire library
import { Button } from '@/components'
import { formatDate } from '@/utils'
// Correct: Direct imports enable tree-shaking
import { Button } from '@/components/ui/button'
import { formatDate } from '@/utils/date'
Dynamic Imports
import dynamic from 'next/dynamic'
// Load only when needed
const HeavyChart = dynamic(() => import('./HeavyChart'), {
loading: () => <ChartSkeleton />,
ssr: false
})
function Dashboard({ showChart }) {
return showChart ? <HeavyChart /> : null
}
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
asyrafhussin/agent-skills
jwynia/agent-skills
kadajett/agent-nestjs-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
react-best-practices has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added react-best-practices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: react-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in react-best-practices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for react-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in react-best-practices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
react-best-practices has been reliable in day-to-day use. Documentation quality is above average for community skills.
react-best-practices fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for react-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: react-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 26