Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
itallstartedwithaidea avatar

React Best Practices

  • 53 installs
  • 31 repo stars
  • Updated April 12, 2026
  • itallstartedwithaidea/agent-skills

Apply 40+ prioritized React performance rules automatically when you write or review UI code before ship.

About

React Best Practices is an agent skill from the Agent Skills collection that encodes more than forty React performance rules grouped into eight priority categories. Solo and indie builders shipping SPAs, dashboards, or React Native–adjacent web apps install it when performance regressions show up late—or when they want review guardrails before launch. The agent uses the skill while drafting or auditing React code, surfacing Critical fixes such as eliminating request waterfalls and shrinking bundles before Medium-tier re-render tweaks that rarely move real user metrics. Rules are ordered by measured impact, not implementation convenience, which helps time-boxed founders focus on network and load-path wins first. It pairs naturally with code review and pre-ship performance passes on Claude Code, Cursor, or Codex without replacing profiling tools or production RUM.

  • 40+ actionable rules across 8 impact-ordered priority categories from Critical to Low-Medium
  • Critical tier targets client-server waterfalls and bundle size before micro-optimizations
  • Each rule includes severity, before/after examples, and system-level guidance (SSR, splitting, fetch placement)
  • Agent applies rules automatically during implementation and code review conversations
  • Treats performance as architecture (fetch, render strategy, bundles) not isolated memo tweaks

React Best Practices by the numbers

  • 53 all-time installs (skills.sh)
  • +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #1,280 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Security screen: CRITICAL risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill react-best-practices

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs53
repo stars31
Security audit2 / 3 scanners passed
Last updatedApril 12, 2026
Repositoryitallstartedwithaidea/agent-skills

What it does

Apply 40+ prioritized React performance rules automatically when you write or review UI code before ship.

Files

SKILL.mdMarkdownGitHub ↗

React Best Practices

Part of Agent Skills™ by googleadsagent.ai™

Description

React Best Practices codifies 40+ rules across 8 priority categories, from Critical (eliminating waterfalls, reducing bundle size) to Low-Medium (JavaScript micro-optimizations). Each rule is actionable, includes a severity rating, and provides before/after code examples. The agent applies these rules automatically when writing or reviewing React code.

The rules are ordered by impact, not by ease of implementation. Eliminating client-server waterfalls and reducing bundle size yield the largest performance gains and therefore receive Critical priority. Server-side rendering performance and client data fetching patterns follow. Re-render optimization—often the first thing developers reach for—is rated Medium because it rarely causes measurable user-facing performance problems compared to network and bundle issues.

This skill treats React performance as a system property, not a component property. The highest-impact optimizations happen at the architecture level: where data is fetched, how bundles are split, and which rendering strategy is chosen. Component-level optimizations (memoization, key stability) are included but correctly deprioritized.

Use When

  • Writing new React components or pages
  • Reviewing React code for performance issues
  • Debugging slow page loads or sluggish interactions
  • Optimizing Core Web Vitals (LCP, FID, CLS)
  • Migrating from client-side to server-side rendering
  • Reducing JavaScript bundle size

How It Works

graph TD
    A[React Code Change] --> B{Priority Scan}
    B --> C["🔴 Critical: Waterfalls"]
    B --> D["🔴 Critical: Bundle Size"]
    B --> E["🟠 High: Server Perf"]
    B --> F["🟡 Med-High: Client Fetch"]
    B --> G["🟡 Medium: Re-renders"]
    B --> H["🟡 Medium: Render Perf"]
    B --> I["🔵 Low-Med: Micro-opts"]
    C --> J[Apply Fixes by Priority]
    D --> J
    E --> J
    F --> J
    G --> J
    H --> J
    I --> J

Rules are evaluated in priority order. Critical issues are flagged as blockers; lower-priority items are noted as suggestions. The agent applies the highest-impact fixes first.

Implementation

Critical: Eliminate Client-Server Waterfalls

// BAD: Sequential fetches create waterfalls
function Dashboard() {
  const user = use(fetchUser());         // 200ms
  const posts = use(fetchPosts(user.id)); // 200ms after user resolves
  const stats = use(fetchStats(user.id)); // 200ms after user resolves
  // Total: 600ms sequential
}

// GOOD: Parallel fetches with server components
async function Dashboard() {
  const user = await fetchUser();
  const [posts, stats] = await Promise.all([
    fetchPosts(user.id),
    fetchStats(user.id),
  ]);
  // Total: 400ms (user + parallel posts/stats)
}

Critical: Bundle Size Reduction

// BAD: Import entire library
import { format } from "date-fns";

// GOOD: Tree-shakeable import
import { format } from "date-fns/format";

// BAD: Eager loading heavy components
import { HeavyChart } from "./HeavyChart";

// GOOD: Lazy loading with Suspense
const HeavyChart = lazy(() => import("./HeavyChart"));

Medium: Re-render Optimization

// BAD: New object reference every render
<UserContext.Provider value={{ user, theme, locale }}>

// GOOD: Stable reference with useMemo
const contextValue = useMemo(
  () => ({ user, theme, locale }),
  [user, theme, locale]
);
<UserContext.Provider value={contextValue}>

Best Practices

  • Fix Critical issues before optimizing Medium or Low items
  • Measure before optimizing—use React DevTools Profiler and Lighthouse
  • Prefer server components for data fetching; reserve client components for interactivity
  • Use dynamic(() => import(...)) for any component not visible in the initial viewport
  • Avoid premature useMemo/useCallback—profile first to confirm the re-render is costly
  • Keep client component boundaries as narrow as possible to minimize hydration cost

Platform Compatibility

PlatformSupportNotes
CursorFullLint + review integration
VS CodeFullESLint plugin support
WindsurfFullReact-aware analysis
Claude CodeFullCode review application
ClineFullRule-based review
aiderPartialManual rule application

Related Skills

  • Composition Patterns
  • View Transitions
  • Web Design Guidelines
  • Edge Rendering

Keywords

react performance best-practices bundle-size waterfall-elimination server-components re-render-optimization core-web-vitals

---

© 2026 googleadsagent.ai™ | Agent Skills™ | MIT License

Related skills

FAQ

Is React Best Practices safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.