Vercel React Best Practices

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/react-best-practices

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

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.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How to Use, Full Compiled Document, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• 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
• Use when the request clearly matches the imported source intent: Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Use when writing new React components or Next.js pages, implementing data fetching (client or server-side), or....

Operating Table

metadata.json

ORIGIN.md

AGENTS.md

README.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: How to Use

Read individual rule files for detailed explanations and code examples:

rules/async-parallel.md
rules/bundle-barrel-imports.md
rules/_sections.md

Each rule file contains:

• Brief explanation of why it matters
• Incorrect code example with explanation
• Correct code example with explanation
• Additional context and references

Examples

Example 1: Ask for the upstream workflow directly

Use @react-best-practices-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @react-best-practices-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @react-best-practices-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @react-best-practices-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• 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-

Imported Operating Notes

Imported: Rule Categories by Priority

async-

bundle-

server-

client-

rerender-

rendering-

js-

advanced-

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/react-best-practices

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @prompt-engineer

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @prompt-engineering

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @prompt-engineering-patterns

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @prompt-library

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

• AGENTS.md
• README.md
• metadata.json
• _sections.md
• _template.md
• advanced-event-handler-refs.md

Imported Reference Notes

Imported: Quick Reference

1. Eliminating Waterfalls (CRITICAL)

• async-defer-await

  - Move await into branches where actually used

• async-parallel

  - Use Promise.all() for independent operations

• async-dependencies

  - Use better-all for partial dependencies

• async-api-routes

  - Start promises early, await late in API routes

• async-suspense-boundaries

  - Use Suspense to stream content

2. Bundle Size Optimization (CRITICAL)

• bundle-barrel-imports

  - Import directly, avoid barrel files

• bundle-dynamic-imports

  - Use next/dynamic for heavy components

• bundle-defer-third-party

  - Load analytics/logging after hydration

• bundle-conditional

  - Load modules only when feature is activated

• bundle-preload

  - Preload on hover/focus for perceived speed

3. Server-Side Performance (HIGH)

• server-cache-react

  - Use React.cache() for per-request deduplication

• server-cache-lru

  - Use LRU cache for cross-request caching

• server-serialization

  - Minimize data passed to client components

• server-parallel-fetching

  - Restructure components to parallelize fetches

• server-after-nonblocking

  - Use after() for non-blocking operations

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

• client-swr-dedup

  - Use SWR for automatic request deduplication

• client-event-listeners

  - Deduplicate global event listeners

5. Re-render Optimization (MEDIUM)

• rerender-defer-reads

  - Don't subscribe to state only used in callbacks

• rerender-memo

  - Extract expensive work into memoized components

• rerender-dependencies

  - Use primitive dependencies in effects

• rerender-derived-state

  - Subscribe to derived booleans, not raw values

• rerender-functional-setstate

  - Use functional setState for stable callbacks

• rerender-lazy-state-init

  - Pass function to useState for expensive values

• rerender-transitions

  - Use startTransition for non-urgent updates

6. Rendering Performance (MEDIUM)

• rendering-animate-svg-wrapper

  - Animate div wrapper, not SVG element

• rendering-content-visibility

  - Use content-visibility for long lists

• rendering-hoist-jsx

  - Extract static JSX outside components

• rendering-svg-precision

  - Reduce SVG coordinate precision

• rendering-hydration-no-flicker

  - Use inline script for client-only data

• rendering-activity

  - Use Activity component for show/hide

• rendering-conditional-render

  - Use ternary, not && for conditionals

7. JavaScript Performance (LOW-MEDIUM)

• js-batch-dom-css

  - Group CSS changes via classes or cssText

• js-index-maps

  - Build Map for repeated lookups

• js-cache-property-access

  - Cache object properties in loops

• js-cache-function-results

  - Cache function results in module-level Map

• js-cache-storage

  - Cache localStorage/sessionStorage reads

• js-combine-iterations

  - Combine multiple filter/map into one loop

• js-length-check-first

  - Check array length before expensive comparison

• js-early-exit

  - Return early from functions

• js-hoist-regexp

  - Hoist RegExp creation outside loops

• js-min-max-loop

  - Use loop for min/max instead of sort

• js-set-map-lookups

  - Use Set/Map for O(1) lookups

• js-tosorted-immutable

  - Use toSorted() for immutability

8. Advanced Patterns (LOW)

• advanced-event-handler-refs

  - Store event handlers in refs

• advanced-use-latest

  - useLatest for stable callback refs

Imported: Full Compiled Document

For the complete guide with all rules expanded:

AGENTS.md

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.