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 skills add pomerium/mcp-app-typescript-template --skill vercel-react-best-practicesgit clone --depth 1 https://github.com/pomerium/mcp-app-typescript-templateWrote 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.
[](https://agentmods.dev/skills/pomerium/mcp-app-typescript-template/vercel-react-best-practices)<a href="https://agentmods.dev/skills/pomerium/mcp-app-typescript-template/vercel-react-best-practices"><img src="https://agentmods.dev/badge/skills/pomerium/mcp-app-typescript-template/vercel-react-best-practices.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00067 | $0.01333 |
| Opus 5 | $0.00034 | $0.00666 |
| Sonnet 5 | $0.00013 | $0.00267 |
| Haiku 4.5 | $0.00007 | $0.00133 |
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 8d 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 — 27 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 — 128 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
What ships with it
48 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 64 KB
- rules/advanced-event-handler-refs.md 1.5 KB
- rules/advanced-use-latest.md 1.2 KB
- rules/async-api-routes.md 1.1 KB
- rules/async-defer-await.md 2.0 KB
- rules/async-dependencies.md 956 B
- rules/async-parallel.md 659 B
- rules/async-suspense-boundaries.md 2.5 KB
- rules/bundle-barrel-imports.md 2.3 KB
- rules/bundle-conditional.md 954 B
- rules/bundle-defer-third-party.md 927 B
- rules/bundle-dynamic-imports.md 798 B
- rules/bundle-preload.md 1.1 KB
- rules/client-event-listeners.md 2.0 KB
- rules/client-localstorage-schema.md 2.0 KB
- rules/client-passive-event-listeners.md 1.6 KB
- rules/client-swr-dedup.md 1.1 KB
- rules/js-batch-dom-css.md 1.8 KB
- rules/js-cache-function-results.md 1.9 KB
- rules/js-cache-property-access.md 536 B
- rules/js-cache-storage.md 1.6 KB
- rules/js-combine-iterations.md 768 B
- rules/js-early-exit.md 1.1 KB
- rules/js-hoist-regexp.md 1.0 KB
- rules/js-index-maps.md 850 B
- rules/js-length-check-first.md 1.7 KB
- rules/js-min-max-loop.md 2.1 KB
- rules/js-set-map-lookups.md 532 B
- rules/js-tosorted-immutable.md 1.7 KB
- rules/rendering-activity.md 566 B
- rules/rendering-animate-svg-wrapper.md 1.1 KB
- rules/rendering-conditional-render.md 938 B
- rules/rendering-content-visibility.md 818 B
- rules/rendering-hoist-jsx.md 993 B
- rules/rendering-hydration-no-flicker.md 2.2 KB
- rules/rendering-svg-precision.md 588 B
- rules/rerender-defer-reads.md 983 B
- rules/rerender-dependencies.md 833 B
- rules/rerender-derived-state.md 724 B
- rules/rerender-functional-setstate.md 2.9 KB
- rules/rerender-lazy-state-init.md 2.0 KB
- rules/rerender-memo.md 1.1 KB
- rules/rerender-transitions.md 1.0 KB
- rules/server-after-nonblocking.md 2.0 KB
- rules/server-cache-lru.md 1.3 KB
- rules/server-cache-react.md 2.2 KB
- rules/server-parallel-fetching.md 1.5 KB
- rules/server-serialization.md 1006 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.
- 8d ago First seen · 128 lines · 67 tokens per session scan A 89b72306d5bc
vercel-react-best-practices is a skill published in the GitHub repository pomerium/mcp-app-typescript-template (20 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 1,333 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 27 lines, and is treated as a copy.
Other skills, from other repositories
storybook
Storybook is the fidelity oracle, not the runtime. The converter bundles the package's compiled dist/ into dsbundle.js - the same bundle the claude.ai/design agent builds with - and generates each preview by compiling the story source module itself (hooks, fixtures, local helpers - the whole closure comes along), with…
design-sync
Push a React design system to claude.ai/design. This runs a converter that bundles the real component code (from Storybook or a bare package) and uploads it. Use when the user runs /design-sync or says "sync my design system to Claude Design".
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
nitrostack-ui-widgets
Best practices for linking tools to interactive frontend widgets using @Widget and @nitrostack/widgets SDK (including state sync, tool calling, display modes, media queries, and chat actions).
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.
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.