Agent skill

React Performance

by affaan-m in affaan-m/ECC

React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills).

MITAuto-check passedDevelopment

Install React Performance

skills CLI
$ npx skills add affaan-m/ECC --skill react-performance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC react-performance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/react-performance .claude/skills/react-performance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
react-performance
GitHub stars
274k
Used in
1 other repo
Token cost
~4.5k tokens
SKILL.md length
1,305 words
Files
1
Skills in repo
657
Repo updated
First seen
Licence
MIT

At a glance

React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills).

  • Works in 8 steps: Eliminating Waterfalls (CRITICAL) → Bundle Size Optimization (CRITICAL) → Server-Side Performance (HIGH) → …
  • Refactoring React/Next.js code for performance
  • SKILL.md covers When to Activate, Priority Index, 1. Eliminating Waterfalls… and 2. Bundle Size Optimization…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

React Performance is an agent skill from affaan-m/ECC. React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Web performance, Backend development and React components. It works with React, Next.js, Vercel and GitHub. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • Refactoring React/Next.js code for performance
  • Tasks that involve Web performance
  • Tasks that involve Backend development

Example prompts

  • “/react-performance”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Eliminating Waterfalls (CRITICAL)
  2. Bundle Size Optimization (CRITICAL)
  3. Server-Side Performance (HIGH)
  4. Client-Side Data Fetching (MEDIUM-HIGH)
  5. Re-render Optimization (MEDIUM)
  6. Rendering Performance (MEDIUM)
  7. JavaScript Performance (LOW-MEDIUM)
  8. Advanced Patterns (LOW)

What it can do on your machine

Read from SKILL.md and the folder at commit ef648e0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and css).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • nextjs.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

React Performance loads about 4.5k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 1,305 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit ef648e0, republished under its MIT licence (© affaan-m). 1,305 words, ~4,515 tokens.

Download SKILL.mdSave it as .claude/skills/react-performance/SKILL.md (or your agent's skills folder).
name
react-performance
description
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
metadata.origin
ECC

React Performance

Performance optimization patterns for React 18/19 and Next.js, adapted from Vercel Labs react-best-practices (MIT, v1.0.0). This skill organizes rules by priority and provides decision-tree guidance for active code review and refactoring.

When to Activate

  • Writing or reviewing React/Next.js code for performance
  • Diagnosing slow page loads, slow interactions, or high CPU on the client
  • Auditing bundle size or Lighthouse Core Web Vitals regressions
  • Removing waterfalls in Server Components / API routes
  • Reducing client-side re-renders
  • Optimizing long lists, animations, or hydration
  • Auditing optimization choices in PRs touching app/, pages/, components/, or data layers

Priority Index

PriorityCategoryPrefixWhen it matters
1 — CRITICALEliminating Waterfallsasync-Anytime await is followed by independent await
2 — CRITICALBundle Size Optimizationbundle-First-load JS, route-level imports, third-party libs
3 — HIGHServer-Side Performanceserver-RSC, Server Actions, API routes, SSR
4 — MEDIUM-HIGHClient-Side Data Fetchingclient-SWR / TanStack Query / raw fetch in hooks
5 — MEDIUMRe-render Optimizationrerender-High-frequency state updates, parent-child fan-out
6 — MEDIUMRendering Performancerendering-Long lists, animations, hydration
7 — LOW-MEDIUMJavaScript Performancejs-Hot loops, frequent allocations
8 — LOWAdvanced Patternsadvanced-Effect-event integration, stable refs

1. Eliminating Waterfalls (CRITICAL)

"Waterfalls are the #1 performance killer" — every sequential await adds full network latency.

Cheap conditions before await

Check sync conditions (props, env, hardcoded flags) before awaiting remote data.

ts
// INCORRECT
async function Page({ id }: { id: string }) {
  const flag = await getFlag("show-page");
  if (!flag || !id) return null;
  const data = await getData(id);
  // ...
}

// CORRECT — short-circuit on cheap sync condition first
async function Page({ id }: { id: string }) {
  if (!id) return null;
  const flag = await getFlag("show-page");
  if (!flag) return null;
  const data = await getData(id);
}
Defer awaits until used

Move await into the branch that uses it.

ts
// INCORRECT — awaits before deciding it needs the data
const user = await getUser(id);
if (mode === "guest") return renderGuest();
return renderUser(user);

// CORRECT
if (mode === "guest") return renderGuest();
const user = await getUser(id);
return renderUser(user);
Promise.all for independent work
ts
// INCORRECT — sequential
const user = await getUser(id);
const posts = await getPosts(id);
const followers = await getFollowers(id);

// CORRECT — parallel
const [user, posts, followers] = await Promise.all([
  getUser(id),
  getPosts(id),
  getFollowers(id),
]);
Partial dependencies — start early, await late
ts
// CORRECT — kick off all promises, await only when each result is needed
const userP = getUser(id);
const postsP = getPosts(id);
const profile = await getProfile(id);
if (profile.private) return null;
const [user, posts] = await Promise.all([userP, postsP]);
Suspense for streaming

Push <Suspense> boundaries close to the data so the page paints what it can while slower sub-trees stream in. The trade-off: layout shift when content arrives — reserve space (skeleton or min-height).

Server Components: parallel through composition
tsx
// INCORRECT — sibling awaits run sequentially inside one component
export default async function Page() {
  const user = await getUser();
  const cart = await getCart();
  return <View user={user} cart={cart} />;
}

// CORRECT — split into children, React runs them in parallel
export default async function Page() {
  return (
    <View>
      <UserSection />
      <CartSection />
    </View>
  );
}

2. Bundle Size Optimization (CRITICAL)

Direct imports, not barrels

Barrel index.ts files force the bundler to walk the entire module graph even when tree-shaking removes most of it. Direct imports save 200-800ms of first-load JS in many real-world apps.

ts
// INCORRECT
import { Button, Card, Modal } from "@/components";

// CORRECT
import { Button } from "@/components/Button";
import { Card } from "@/components/Card";
import { Modal } from "@/components/Modal";

Next.js 13.5+ has Optimize Package Imports that automates this for listed packages — use it; manual direct imports still required for non-listed libs.

Statically analyzable paths
ts
// INCORRECT — defeats bundler/trace analysis
const mod = await import(`./pages/${name}`);

// CORRECT — explicit per branch
const mod = name === "home" ? await import("./pages/home") : await import("./pages/about");
Dynamic imports for heavy components
tsx
import dynamic from "next/dynamic";

const HeavyChart = dynamic(() => import("./HeavyChart"), {
  loading: () => <Skeleton />,
  ssr: false, // when client-only
});
Defer third-party scripts

Load analytics, logging, support widgets AFTER hydration. Use next/script with strategy="afterInteractive" (default) or "lazyOnload".

Conditional module loading
tsx
if (user.role === "admin") {
  const { AdminPanel } = await import("./admin/AdminPanel");
  // ...
}
Preload on hover/focus

Trigger <link rel="preload"> or import() on hover so the bundle is in cache by the time the user clicks.

3. Server-Side Performance (HIGH)

Authenticate Server Actions like API routes

Every "use server" function is a public endpoint. Authenticate AND authorize inside the action — never rely on the calling Client Component's gating.

ts
"use server";
export async function deleteUser(formData: FormData) {
  const session = await getSession();
  if (!session?.user) throw new Error("Unauthorized");
  const targetId = String(formData.get("id"));
  if (session.user.role !== "admin" && session.user.id !== targetId) {
    throw new Error("Forbidden");
  }
  await db.user.delete({ where: { id: targetId } });
}
React.cache() for per-request deduplication
ts
import { cache } from "react";

export const getUser = cache(async (id: string) => {
  return db.user.findUnique({ where: { id } });
});

React.cache dedupes within a single request. Calling getUser("1") from three Server Components in the same render = one DB query.

LRU cache for cross-request data

For data that does NOT change per request (config, lookup tables), cache outside React with an LRU cache or unstable_cache.

Avoid duplicate serialization in RSC props

When a Server Component renders the same data into multiple Client Components, the data is serialized once per consumer. Lift the Client Component up and pass children.

Hoist static I/O to module scope
ts
// CORRECT — runs once at module load
const fontData = readFileSync(fontPath);

export async function Page() {
  return <Banner font={fontData} />;
}
No mutable module-level state in RSC/SSR

Module state on the server is shared across all requests — a race condition between users. Use request-scoped storage (headers(), cookies(), async context) instead.

Minimize data passed to Client Components

Only serialize what the Client needs. Strip fields, paginate, project columns at the DB layer.

Parallelize nested fetches with Promise.all per item
ts
const users = await getUsers();
const enriched = await Promise.all(
  users.map(async (u) => ({ ...u, posts: await getPostsFor(u.id) })),
);
Use after() for non-blocking work

Next.js 15 after() runs work after the response is sent — logging, cache warming, analytics.

ts
import { after } from "next/server";
export async function GET() {
  const data = await getData();
  after(() => logAnalytics(data));
  return Response.json(data);
}

4. Client-Side Data Fetching (MEDIUM-HIGH)

SWR / TanStack Query for deduplication

Multiple components calling useUser(id) should share one network request and one cache entry. Use SWR or TanStack Query — never roll your own useEffect + fetch for shared data.

Deduplicate global event listeners
tsx
// INCORRECT — every component adds its own
useEffect(() => {
  window.addEventListener("scroll", handler);
  return () => window.removeEventListener("scroll", handler);
}, []);

// CORRECT — single shared listener via a hook + global subject
const useScroll = createScrollHook(); // singleton subject under the hood
Passive listeners for scroll
ts
window.addEventListener("scroll", handler, { passive: true });

Improves scrolling smoothness; the listener cannot preventDefault().

localStorage: version + minimize
  • Always store a version field; bump on schema change and migrate or discard old data
  • Keep payloads small — localStorage is synchronous and blocks main thread

5. Re-render Optimization (MEDIUM)

Don't subscribe to state used only in callbacks
tsx
// INCORRECT — re-renders every time count changes
const count = useStore((s) => s.count);
const handler = () => doSomething(count);

// CORRECT — read once on call
const handler = () => {
  const count = useStore.getState().count;
  doSomething(count);
};
Extract expensive work into memoized components
tsx
// CORRECT — child re-renders only when `items` changes
const Heavy = memo(function Heavy({ items }: { items: Item[] }) {
  return <Chart data={transform(items)} />;
});
Hoist default non-primitive props
tsx
// INCORRECT — new array each render breaks memo
<List items={items ?? []} />

// CORRECT
const EMPTY: Item[] = [];
<List items={items ?? EMPTY} />
Primitive dependencies in effects
tsx
// INCORRECT — new object identity every render
useEffect(() => {}, [{ id, name }]);

// CORRECT — primitives
useEffect(() => {}, [id, name]);
Subscribe to derived booleans, not raw values
tsx
// INCORRECT — re-renders for any cart change
const cart = useStore((s) => s.cart);
const hasItems = cart.length > 0;

// CORRECT — re-renders only when emptiness flips
const hasItems = useStore((s) => s.cart.length > 0);
Derive during render, never via useEffect
tsx
// INCORRECT
const [full, setFull] = useState("");
useEffect(() => setFull(`${first} ${last}`), [first, last]);

// CORRECT
const full = `${first} ${last}`;
Functional setState for stable callbacks
tsx
// CORRECT
const increment = useCallback(() => setCount((c) => c + 1), []);
Lazy state initializer for expensive values
tsx
const [tree] = useState(() => parseTree(largeInput));
Avoid memo for simple primitives

useMemo(() => x + 1, [x]) is overhead. Memo earns its keep on object identity and expensive computation.

Split hooks with independent deps
tsx
// INCORRECT — both selectors re-run if either source changes
const { a, b } = useSomething(source1, source2);

// CORRECT
const a = useA(source1);
const b = useB(source2);
Move interaction logic into event handlers

Event handlers run only on the user action — useEffect re-runs whenever deps change.

startTransition for non-urgent updates
tsx
const [pending, startTransition] = useTransition();
startTransition(() => setFilters(newFilters));
useDeferredValue for expensive renders
tsx
const deferredQuery = useDeferredValue(query);
const results = useMemo(() => expensiveSearch(deferredQuery), [deferredQuery]);
useRef for transient frequent values

For values that change often but should not trigger re-render (timestamps, last-key, accumulators).

Show full SKILL.md (520 more words)Show less
Don't define components inside components
tsx
// INCORRECT — Inner is a new component on every Outer render
function Outer() {
  const Inner = () => <span />;
  return <Inner />;
}

Each render makes a new Inner type, defeating reconciliation and unmounting children.

6. Rendering Performance (MEDIUM)

Animate the wrapper, not the SVG

Transforming a <div> wrapper around an SVG is GPU-accelerated; transforming the SVG itself triggers paint.

content-visibility: auto for long lists
css
.row { content-visibility: auto; contain-intrinsic-size: auto 80px; }

Browser skips offscreen rendering — major win for lists with hundreds of rows.

Hoist static JSX
tsx
const STATIC_HEADER = <h1>Title</h1>;
function Page() {
  return <>{STATIC_HEADER}<Body /></>;
}
SVG: reduce coordinate precision

d="M10.123456,20.654321" → d="M10.12,20.65". Each digit costs bytes; the visual difference is sub-pixel.

Hydration no-flicker via inline script

For values needed before hydration (theme, locale), inline a <script> that sets document.documentElement.dataset.* before React mounts.

Suppress expected hydration mismatches narrowly
tsx
<time suppressHydrationWarning>{new Date().toLocaleString()}</time>

Use ONLY for known-divergent leaf nodes — never on a tree containing other children.

<Activity> for show/hide instead of mount/unmount

React 19 <Activity mode="visible|hidden"> keeps tree state and effects mounted but hides — cheaper than unmount/remount for tabs and accordions.

Ternary over && for conditional render
tsx
// INCORRECT — `0` renders as text node
{count && <Badge>{count}</Badge>}

// CORRECT
{count > 0 ? <Badge>{count}</Badge> : null}
useTransition for loading states

Pair startTransition with the action; React shows the previous UI as isPending while the next state computes.

React DOM resource hints
tsx
import { preload, preconnect } from "react-dom";
preload("/api/critical", { as: "fetch" });
preconnect("https://api.example.com");
defer / async on <script> tags

defer for ordered execution after DOMContentLoaded; async for fire-and-forget.

7. JavaScript Performance (LOW-MEDIUM)

  • Batch DOM/CSS changes — apply via class swap or cssText, not property-by-property
  • Map for repeated lookups — O(1) vs O(n) linear scan
  • Cache property access in loops — const len = arr.length
  • Memoize pure functions — module-level Map<key, result>
  • Cache localStorage reads — sync API; one read per render
  • Combine filter().map() into one pass — flatMap or single for
  • Check array length first before expensive comparisons
  • Early return from functions
  • Hoist RegExp out of loops — compilation is not free
  • Loop for min/max instead of sort() — O(n) vs O(n log n)
  • Set/Map for membership — O(1) vs Array.includes O(n)
  • toSorted() over mutation when immutability matters
  • flatMap to map and filter in one pass
  • requestIdleCallback for non-critical work

8. Advanced Patterns (LOW)

useEffectEvent deps

Values from useEffectEvent are stable — do NOT add them to effect deps.

Event handler refs

For stable callbacks passed to memoized children:

tsx
const handlerRef = useRef(handler);
useEffect(() => { handlerRef.current = handler; });
const stable = useCallback((arg) => handlerRef.current(arg), []);
Init once per app load

For module-level singletons (telemetry, logger), guard with a module-scope flag — not useEffect.

useLatest for stable callback refs
tsx
function useLatest<T>(value: T) {
  const ref = useRef(value);
  ref.current = value;
  return ref;
}

Automated Tools

Many of these rules are now automated:

  • Next.js 13.5+ Optimize Package Imports — barrel import optimization
  • React Compiler (RFC, in canary) — auto-memoization
  • Turbopack — faster builds, better tree-shaking
  • Bundle Analyzer (@next/bundle-analyzer) — visualize first-load JS

When the project ships React Compiler, demote rerender-* manual memoization rules to "review-only" — the compiler handles them. Manual useMemo/useCallback becomes unnecessary noise.

Lighthouse / Web Vitals Mapping

MetricMost relevant categories
LCP (Largest Contentful Paint)Waterfalls, Bundle Size, Resource Hints
INP (Interaction to Next Paint)Re-render, Rendering, JavaScript
CLS (Cumulative Layout Shift)Rendering (Suspense placement, image dimensions)
TBT (Total Blocking Time)Bundle Size, JavaScript, Defer Third-Party
FID (legacy)Bundle Size, Hydration

Attribution

Adapted from Vercel Labs react-best-practices skill (MIT License, copyright Vercel Engineering, v1.0.0 January 2026). Source: https://github.com/vercel-labs/agent-skills/tree/main/skills/react-best-practices.

This skill restructures and adapts the original 70-rule catalog into a single navigable reference. For the full original ruleset with extended examples, see the upstream repository.

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/react-performance of affaan-m/ECC.

Open the folder on GitHubat commit ef648e0

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

React Performance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

React Performance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
React Performance this skillaffaan-m/ECC274k1 repos~4.5kAutomated safety check: PassMIT
React Best Practicesryokun6/ryos1.3k—~2kAutomated safety check: PassMIT
Vercel React Best Practicesgambitph/Stackable350—~2kAutomated safety check: PassMIT
Vercel React Best Practicessanity-io/sanity6.4k130 repos~1.6kAutomated safety check: PassMIT
React Best Practicesmajiayu000/spellbook286—~1.1kAutomated safety check: PassMIT
React Best Practicesshapeshift/web2061 repos~2kAutomated safety check: PassMIT

Similar skills

  • React performance optimization guidelines from Vercel Engineering (vercel-labs/agent-skills).

    1.3k GitHub stars~2k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Vercel React Best Practices

    gambitph/Stackable

    React performance optimization guidelines from Vercel Engineering.

    350 GitHub stars~2k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Official

    React and Next.js performance optimization guidelines from Vercel Engineering.

    6.4k GitHub starsUsed in 130 repos~1.6k tokens
    Frontend & DesignAuto-check passed
  • React Best Practices

    majiayu000/spellbook

    React and Next.js performance playbook distilled from Vercel Engineering guidance.

    286 GitHub stars~1.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • React Best Practices

    shapeshift/web

    Comprehensive React and Next.js performance optimization guide with 40+ rules for eliminating waterfalls, optimizing bundles, and improving rendering.

    206 GitHub starsUsed in 1 repo~2k tokens
    DevelopmentAuto-check passed
  • React Refactor Tournament

    ragnar-pwninskjold/tech-snacks

    Review React/Next.js code against the real vercel-react-best-practices skill, backlog the performance findings keyed to actual rule ids + impact tiers, rank the most over-subscribed tiers, then fix…

    136 GitHub stars~1.3k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from affaan-m/ECC

All 657 skills in this repo
  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    274k GitHub starsUsed in 5 repos~1.9k tokens
    Auto-check passed
  • Videodb

    affaan-m/ECC

    Ingest, index, search, edit, and monitor video and audio with the VideoDB Python SDK — upload from files, URLs, or RTSP feeds, build spoken and scene indexes with timestamped search and playable…

    274k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    274k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    274k GitHub stars~2.9k tokensUpdated 2 days ago
    Auto-check passed
  • Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    274k GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed
  • Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    274k GitHub stars~3.5k tokensUpdated 2 days ago
    Auto-check passed

Questions about React Performance

What does React Performance do?

React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). React Performance is an agent skill from affaan-m/ECC.com/vercel-labs/agent-skills).

When should I use React Performance?

React Performance fits situations like: refactoring React/Next.js code for performance; tasks that involve Web performance; tasks that involve Backend development.

How do I install React Performance in Claude Code?

Run `npx skills add affaan-m/ECC --skill react-performance -a claude-code`. Or copy the skill folder (skills/react-performance in affaan-m/ECC) into .claude/skills/react-performance in your project. Claude Code loads it when a task matches its description.

How do I install React Performance in Codex?

Run `npx skills add affaan-m/ECC --skill react-performance -a codex`. Or copy the skill folder (skills/react-performance in affaan-m/ECC) into .agents/skills/react-performance in your project. Codex loads it when a task matches its description.

Can I use React Performance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill react-performance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/react-performance, .gemini/skills/react-performance, .github/skills/react-performance and .opencode/skills/react-performance in your project.

What does React Performance need to run?

SKILL.md names no scripts, command-line tools or credentials: React Performance is instructions for the agent only.

Does React Performance access the network?

SKILL.md names 2 domains. As links in the text: github.com and nextjs.org. This is read from the text; nothing was executed.

Is React Performance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does React Performance use?

React Performance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does React Performance use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to React Performance?

Skills that share tags, products or a category with React Performance: React Best Practices (ryokun6/ryos, 1.3k stars), Vercel React Best Practices (gambitph/Stackable, 350 stars), Vercel React Best Practices (sanity-io/sanity, 6.4k stars) and React Best Practices (majiayu000/spellbook, 286 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains React Performance?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 274,360 GitHub stars. The repository holds 657 skills in this directory. The repository was last updated on October 5, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.