React Best Practices
CheckedHelps with React, best practices as part of building frontend UIs and user experiences workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add tech-leads-club/agent-skills --skill react-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
tech-leads-club
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned tech-leads-club/agent-skills at 6df68d5202.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 6df68d5202
- Scanned
- 60 files, 5,658 lines
About this skill
What it does
This skill provides access to Vercel's comprehensive performance optimization guide for React and Next.js applications. It contains 57 rules, categorized by priority (Critical, High, Medium-High, Medium, Low-Medium, and Low), designed to guide automated refactoring and code generation aimed at improving application performance. The skill focuses on areas like eliminating waterfalls, optimizing bundle size, enhancing server-side performance, and improving client-side data fetching.
When to use it
- When writing new React components or Next.js pages.
- During implementation of data fetching (client or server-side).
- When reviewing code for potential performance bottlenecks.
- To refactor existing React/Next.js codebases.
- For optimizing bundle size and load times.
Key capabilities
- Provides access to 57 Vercel React Best Practices rules.
- Categorizes rules by priority (Critical, High, Medium-High, etc.).
- Offers specific guidance on eliminating waterfalls (
async-*prefixed rules). - Includes recommendations for bundle size optimization (
bundle-*prefixed rules). - Provides advice on server-side performance improvements (
server-*prefixed rules).
Example prompts
- "What are the best practices for optimizing bundle size in a Next.js application?"
- "How can I improve data fetching performance using React Suspense?"
- "Show me examples of how to use
Promise.all()for parallel operations." - "Give me recommendations for server-side caching in React."
Tips & gotchas
- The skill focuses specifically on React and Next.js development; it's not a general coding assistant.
- Rules are categorized by priority, so focus on the "Critical" rules first for maximum impact.
- Familiarity with basic React and Next.js concepts is helpful to understand the recommendations.