toolhive-cloud-ui: Skill for Claude Code

.claude/skills/vercel-react-best-practices/SKILL.md

vercel-react-best-practices is a skill for Claude Code from stacklok/toolhive-cloud-ui. It costs 67 tokens per session (1,299 once invoked), scanned A, a copy of vercel-react-best-practices, Apache-2.0.

A set of Vercel Engineering guidelines for improving the performance of React and Next.js applications. It covers components, pages, data fetching, code size, and loading.

In plain words
What is it for?
Use it when writing, reviewing, or refactoring React components and Next.js pages, especially when working on data fetching, bundle size, re-renders, or load times.
Why use it?
It helps identify coding patterns that can slow down a web application, such as waiting for requests one after another or sending unnecessary JavaScript to the browser.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is stacklok/toolhive-cloud-ui's own configuration. It tells Claude Code how to work on toolhive-cloud-ui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything toolhive-cloud-ui configures →

Reuse

Borrowing it

Nothing to install: this file belongs to stacklok/toolhive-cloud-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/stacklok/toolhive-cloud-ui/main/.claude/skills/vercel-react-best-practices/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/stacklok/toolhive-cloud-ui

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for vercel-react-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/stacklok/toolhive-cloud-ui/vercel-react-best-practices.svg)](https://agentmods.dev/skills/stacklok/toolhive-cloud-ui/vercel-react-best-practices)
Your own site
<a href="https://agentmods.dev/skills/stacklok/toolhive-cloud-ui/vercel-react-best-practices"><img src="https://agentmods.dev/badge/skills/stacklok/toolhive-cloud-ui/vercel-react-best-practices.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 81% copy Near-identical to another mod 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.1 $0.00067 $0.01299
Opus 5 $0.00034 $0.00649
Sonnet 5 $0.00013 $0.00260
Haiku 4.5 $0.00007 $0.00130

Measured 7d ago against content hash 81bad0edc74b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 7d 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.

Origin

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.

.claude/skills/vercel-react-best-practices/SKILL.md · 126 lines

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

Read the full file on GitHub · 126 lines

Files

What ships with it

46 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. 7d ago First seen · 126 lines · 67 tokens per session scan A 81bad0edc74b

Subscribe to this mod's changes

vercel-react-best-practices is a skill published in the GitHub repository stacklok/toolhive-cloud-ui (11 stars, last pushed 9d ago), licensed Apache-2.0. 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.

Related

Other skills, from other repositories

21st-ui

Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.

21st-dev/magic-mcp · 63 tokens

webmcp-add-tool

Scaffolds a new WebMCP tool component using useMcpTool with Zod schema, handler, annotations, and wires it into the WebMCPProvider tree. Use when the user wants to expose functionality as an MCP tool, make something callable by AI, add a new tool, or create an AI-accessible action.

agentcathq/webmcp-react · 73 tokens

webmcp-setup

Bootstraps webmcp-react into an existing React or Next.js app. Installs dependencies, adds WebMCPProvider, creates a first tool, and configures the MCP client bridge. Use when the user wants to set up WebMCP, add MCP tools to their app, integrate webmcp-react, or make their React app accessible to AI agents.

agentcathq/webmcp-react · 80 tokens

add-widget

Add a new widget (React UI + MCP tool) to this template. Use when asked to "add a widget", "add a new tool with UI", "create a new widget", "scaffold a widget", or "build a new MCP App feature".

pomerium/mcp-app-typescript-template · 56 tokens

nextjs-supabase-auth

Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.

Kastalien-Research/thoughtbox · 40 tokens

using-react-hook-form-docs-mcp

How to effectively use the react-hook-form-docs-mcp search and doc-retrieval tools instead of relying on training-data memory of React Hook Form APIs.

Sannnao/react-docs-mcp · 41 tokens