react-performance

A collection of rules for improving the runtime performance of React and Next.js applications, including rendering, data loading, and shipped JavaScript.

In plain words
What is it for?
Reviewing or refactoring React components, hooks, and Next.js pages; reducing re-renders and bundle size; and addressing slow loading or interaction problems.
Why use it?
It helps locate and reduce slow renders, repeated work, large bundles, request delays, and poor Web Vitals.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/clubpay/ronykit/react-performance
Any agent
npx skills add clubpay/ronykit --skill react-performance
Clone the repo
git clone --depth 1 https://github.com/clubpay/ronykit

Made for: Claude Code, Codex.

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,713 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00064 $0.02713
Opus 5 $0.00032 $0.01357
Sonnet 5 $0.00013 $0.00543
Haiku 4.5 $0.00006 $0.00271

Measured yesterday against content hash 66494d60ef52, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

react-performance scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ronyup/internal/skeleton/skills/react-performance/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

React Performance

70 performance rules for React and Next.js, vendored from Vercel Engineering's react-best-practices (MIT). The full rule set lives in rules/ — each file is self-contained (impact metric + incorrect→correct code). This SKILL.md is the index and router: it carries the highest-impact patterns inline so you can act without opening anything, and points you to the exact rule file for depth.

For Server Components, data fetching, caching, Server Actions, and route-level code splitting at a higher level, see nextjs-modern. The async-* and server-* rules here are the detailed reference for that same ground.

When to use

  • Writing or reviewing React components, hooks, or Next.js pages for speed.
  • Chasing slow renders, janky interactions, large bundles, or poor Core Web Vitals (LCP, INP, TTFB).
  • Refactoring code that re-renders too often or ships too much JS.

How to use the rules (read this first)

  1. Measure before optimizing. Profile the proven bottleneck with the React DevTools Profiler, the Next.js bundle analyzer, and a Lighthouse/Web Vitals pass. Don't memoize on a hunch — most "just to be safe" memoization only adds cost.
  2. Apply in priority order (table below) — the top categories move the needle far more than the bottom ones.
  3. Open the specific rule file before applying it, using the routing table and index below. Each rules/<name>.md has the exact incorrect→correct code and the impact metric. Match the example, don't paraphrase from memory.

Priority order

# Category Impact Prefix
1 Eliminate waterfalls CRITICAL async-
2 Bundle size CRITICAL bundle-
3 Server-side perf HIGH server-
4 Client data fetching MEDIUM-HIGH client-
5 Re-render optimization MEDIUM rerender-
6 Rendering performance MEDIUM rendering-
7 JavaScript hot paths LOW-MEDIUM js-
8 Advanced patterns LOW advanced-

Read the full file on GitHub · 215 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 215 lines · 64 tokens per session scan A 66494d60ef52

Subscribe to this mod's changes

react-performance is a skill published in the GitHub repository clubpay/ronykit (38 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 64 tokens to every session and 2,713 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.