css-noop-checker: Skill for Claude Code

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

vercel-react-best-practices is a skill for Claude Code from purupurupu/css-noop-checker. It costs 67 tokens per session (1,533 once invoked), scanned A, a copy of react-performance, MIT.

A set of performance guidelines for React and Next.js, tools for building web applications with JavaScript. It covers data loading, page rendering, browser updates, and the amount of code sent to users.

In plain words
What is it for?
Use it when writing, reviewing, or refactoring React components and Next.js pages, especially when handling data fetching, bundle size, rendering, or re-renders.
Why use it?
It helps developers find patterns that make pages load slowly, perform unnecessary work, or send too much JavaScript to the browser.

Skill for Claude Code

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

This is purupurupu/css-noop-checker's own configuration. It tells Claude Code how to work on css-noop-checker 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 css-noop-checker configures →

Reuse

Borrowing it

Nothing to install: this file belongs to purupurupu/css-noop-checker. 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/purupurupu/css-noop-checker/main/.claude/skills/vercel-react-best-practices/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/purupurupu/css-noop-checker

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/purupurupu/css-noop-checker/vercel-react-best-practices/github.svg)](https://agentmods.dev/skills/purupurupu/css-noop-checker/vercel-react-best-practices)
Your own site
<a href="https://agentmods.dev/skills/purupurupu/css-noop-checker/vercel-react-best-practices"><img src="https://agentmods.dev/badge/skills/purupurupu/css-noop-checker/vercel-react-best-practices/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for vercel-react-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/purupurupu/css-noop-checker/vercel-react-best-practices"><img src="https://agentmods.dev/badge/skills/purupurupu/css-noop-checker/vercel-react-best-practices.svg" alt="Reviewed on agentmods" width="80" 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,533 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 80% 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.01533
Opus 5.5 $0.00027 $0.00613
Sonnet 5.5 $0.00013 $0.00307
Haiku 4.5 $0.00007 $0.00153

Measured 2mo ago against content hash 6038b0715ae8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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

80% identical to react-performance — 42 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 · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 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 57 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

Read the full file on GitHub · 139 lines

Files

What ships with it

59 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. 2mo ago First seen · 139 lines · 67 tokens per session scan A 6038b0715ae8

Subscribe to this mod's changes

vercel-react-best-practices is a skill published in the GitHub repository purupurupu/css-noop-checker (25 stars, last pushed 7mo ago), licensed MIT. It adds 67 tokens to every session and 1,533 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to react-performance, differing in 42 lines, and is treated as a copy.

Related

Other skills, from other repositories

migrate-oxlint

Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.

oxc-project/oxc · 44 tokens

devtools-vite-plugin

Configure @tanstack/devtools-vite for source inspection (data-tsd-source, inspectHotkey, ignore patterns), console piping (client-to-server, server-to-client, levels), enhanced logging, server event bus (port, host, HTTPS), production stripping (removeDevtoolsOnBuild), editor integration (launch-editor, custom…

TanStack/devtools · 93 tokens

devtools-marketplace

Publish plugin to npm and submit to TanStack Devtools Marketplace. PluginMetadata registry format, plugin-registry.ts, pluginImport (importName, type), requires (packageName, minVersion), framework tagging, multi-framework submissions, featured plugins.

TanStack/devtools · 54 tokens

devtools-production

Handle devtools in production vs development. removeDevtoolsOnBuild, devDependency vs regular dependency, conditional imports, NoOp plugin variants for tree-shaking, non-Vite production exclusion patterns.

TanStack/devtools · 43 tokens

devtools-bidirectional

Two-way event patterns between devtools panel and application. App-to-devtools observation, devtools-to-app commands, time-travel debugging with snapshots and revert. structuredClone for snapshot safety, distinct event suffixes for observation vs commands, serializable payloads only.

TanStack/devtools · 59 tokens

devtools-plugin-panel

Build devtools panel components that display emitted event data. Listen via EventClient.on(), handle theme (light/dark), use @tanstack/devtools-ui components. Plugin registration (name, render, id, defaultOpen), lifecycle (mount, activate, destroy), max 3 active plugins. Two paths: Solid.js core with devtools-ui for…

TanStack/devtools · 84 tokens