React Best Practices
v1.0.0React and Next.js performance optimization guidelines from Vercel Engineering. 57 rules across 8 categories for writing, reviewing, and refactoring React code.
⭐ 4· 3.8k·59 current·61 all-time
by@wpank
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the provided content: a ruleset for React and Next.js performance. Files (README, SKILL.md, AGENTS.md and many rule markdowns) all align with the stated goal. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md + AGENTS.md are guidance documents for humans and for agents to use when writing/refactoring code. They do not request secrets or system files. Note: AGENTS.md explicitly targets automation/LLMs and is intended for agents to perform maintenance/refactors; that is coherent with the skill purpose but means an agent using this skill could modify your codebase if allowed—review any automated changes before applying.
Install Mechanism
No install spec in the registry (instruction-only). SKILL.md and README show example install commands (npx clawhub, copy into local skill dirs) but the skill package itself includes no install script or extracted binaries. Low install risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. The guidance mentions common libraries (better-all, lru-cache, @vercel/analytics) but does not request tokens or secrets; the requested capabilities are proportionate to the stated purpose.
Persistence & Privilege
always:false and disable-model-invocation:false (normal). The skill does not request persistent presence, nor does it modify other skills or system-wide settings. Autonomous agent invocation is allowed by default but is not a unique privilege of this skill.
Assessment
This appears to be a coherent, instruction-only guide for improving React/Next.js performance and does not request credentials or install arbitrary code. Before you enable an agent to act autonomously with this skill, consider: (1) provenance — the registry metadata lists no homepage and source is unknown, so verify the origin if you require an official Vercel document; (2) automation risk — AGENTS.md is written for LLMs and enables automated refactors, so require human review or use a dry-run mode when letting an agent change your code; (3) dependency recommendations — some rules suggest libraries (better-all, lru-cache, @vercel/analytics); add third-party libs deliberately and review licenses; (4) validate any suggested code changes in CI and tests. If you only want read-only guidance, this skill is low-risk; if you plan to let an agent automatically modify code, apply normal code-review safeguards.Like a lobster shell, security has layers — review code before you run it.
latestvk973nk8swb926qgh7r7m27nn5580wdmd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.