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.
npx agentmods add skills/nicepkg/vsync/vercel-react-best-practicesnpx skills add nicepkg/vsync --skill vercel-react-best-practicesgit clone --depth 1 https://github.com/nicepkg/vsyncWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00067 | $0.01299 |
| Opus 5 | $0.00034 | $0.00649 |
| Sonnet 5 | $0.00013 | $0.00260 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
vercel-react-best-practices 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 2d ago.
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.
This is a copy
81% identical to vercel-react-best-practices — 47 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel React Best Practices
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
When to Apply
Reference these guidelines when:
- Writing new React components or Next.js pages
- Implementing data fetching (client or server-side)
- Reviewing code for performance issues
- Refactoring existing React/Next.js code
- Optimizing bundle size or load times
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Eliminating Waterfalls | CRITICAL | async- |
| 2 | Bundle Size Optimization | CRITICAL | bundle- |
| 3 | Server-Side Performance | HIGH | server- |
| 4 | Client-Side Data Fetching | MEDIUM-HIGH | client- |
| 5 | Re-render Optimization | MEDIUM | rerender- |
| 6 | Rendering Performance | MEDIUM | rendering- |
| 7 | JavaScript Performance | LOW-MEDIUM | js- |
| 8 | Advanced Patterns | LOW | advanced- |
Quick Reference
1. Eliminating Waterfalls (CRITICAL)
async-defer-await- Move await into branches where actually usedasync-parallel- Use Promise.all() for independent operationsasync-dependencies- Use better-all for partial dependenciesasync-api-routes- Start promises early, await late in API routesasync-suspense-boundaries- Use Suspense to stream content
2. Bundle Size Optimization (CRITICAL)
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 speed
3. Server-Side Performance (HIGH)
server-cache-react- Use React.cache() for per-request deduplicationserver-cache-lru- Use LRU cache for cross-request cachingserver-serialization- Minimize data passed to client componentsserver-parallel-fetching- Restructure components to parallelize fetchesserver-after-nonblocking- Use after() for non-blocking operations
What ships with it
53 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.
- AGENTS.md 74 KB
- rules/advanced-event-handler-refs.md 1.4 KB
- rules/advanced-use-latest.md 1.0 KB
- rules/async-api-routes.md 1.1 KB
- rules/async-defer-await.md 2.0 KB
- rules/async-dependencies.md 1.3 KB
- rules/async-parallel.md 654 B
- rules/async-suspense-boundaries.md 2.5 KB
- rules/bundle-barrel-imports.md 2.3 KB
- rules/bundle-conditional.md 949 B
- rules/bundle-defer-third-party.md 920 B
- rules/bundle-dynamic-imports.md 791 B
- rules/bundle-preload.md 1.1 KB
- rules/client-event-listeners.md 1.9 KB
- rules/client-localstorage-schema.md 1.9 KB
- rules/client-passive-event-listeners.md 1.6 KB
- rules/client-swr-dedup.md 1.1 KB
- rules/js-batch-dom-css.md 3.2 KB
- rules/js-cache-function-results.md 1.9 KB
- rules/js-cache-property-access.md 532 B
- rules/js-cache-storage.md 1.6 KB
- rules/js-combine-iterations.md 753 B
- rules/js-early-exit.md 1.1 KB
- rules/js-hoist-regexp.md 1.0 KB
- rules/js-index-maps.md 837 B
- rules/js-length-check-first.md 1.7 KB
- rules/js-min-max-loop.md 2.2 KB
- rules/js-set-map-lookups.md 532 B
- rules/js-tosorted-immutable.md 1.7 KB
- rules/rendering-activity.md 564 B
- rules/rendering-animate-svg-wrapper.md 1.2 KB
- rules/rendering-conditional-render.md 980 B
- rules/rendering-content-visibility.md 815 B
- rules/rendering-hoist-jsx.md 1.0 KB
- rules/rendering-hydration-no-flicker.md 2.3 KB
- rules/rendering-svg-precision.md 588 B
- rules/rendering-usetransition-loading.md 2.0 KB
- rules/rerender-defer-reads.md 973 B
- rules/rerender-dependencies.md 824 B
- rules/rerender-derived-state.md 728 B
- rules/rerender-functional-setstate.md 2.9 KB
- rules/rerender-lazy-state-init.md 2.0 KB
- rules/rerender-memo-with-default-value.md 1.1 KB
- rules/rerender-memo.md 1.1 KB
- rules/rerender-simple-expression-in-memo.md 1018 B
- rules/rerender-transitions.md 1.0 KB
- rules/server-after-nonblocking.md 2.0 KB
- rules/server-auth-actions.md 2.6 KB
- rules/server-cache-lru.md 1.3 KB
- rules/server-cache-react.md 2.2 KB
- rules/server-dedup-props.md 2.0 KB
- rules/server-parallel-fetching.md 1.5 KB
- rules/server-serialization.md 996 B
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.
- 2d ago First seen · 126 lines · 67 tokens per session scan A 81bad0edc74b
vercel-react-best-practices is a skill published in the GitHub repository nicepkg/vsync (57 stars, last pushed 7mo ago), licensed MIT. It adds 67 tokens to every session and 1,299 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to vercel-react-best-practices, differing in 47 lines, and is treated as a copy.
Other skills, from other repositories
snip
You are an expert at writing declarative YAML filters for snip, a CLI proxy that reduces LLM token consumption by filtering shell output.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
reviewing-changes
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.
setting-up-a-project
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.