agentleFS
dmarafettidmarafetti/ai-writer-extension/.agents/skills/vercel-react-best-practices/SKILL.md

vercel-react-best-practices

Skill0 starsChanged 4 months agoNo licenceView on GitHub

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

We split this skill into the rules it gives an agent

1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 118 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 118 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Trending

Rising: 20 new projects took it in the last 4 weeks, 1.3× the 4 weeks before.

Week of Aug 30: 0 new projectsWeek of Sep 6: 7 new projectsWeek of Sep 13: 3 new projectsWeek of Sep 20: 5 new projectsWeek of Sep 27: 5 new projectsWeek of Oct 4: 13 new projectsWeek of Oct 11: 1 new projectWeek of Oct 18: 1 new project
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.
  • Other versions264 projects use a version of this.

    Word for word · 142

    1. vercel-labs/agent-skills★ 33k100% same
    2. udecode/plate★ 17k100% same
    3. open-metadata/OpenMetadata★ 16k100% same
    4. Arize-ai/phoenix★ 12k100% same
    5. trycompai/crm★ 12k100% same
    6. mengxi-ream/read-frog★ 10k100% same
    7. 1weiho/open-slide★ 9.6k100% same
    8. basketikun/infinite-canvas★ 9.5k100% same
    9. zai-org/ZCode★ 8.4k100% same
    10. zhukunpenglinyutong/idea-claude-code-gui★ 7.4k100% same

    132 more not listed

    Edited · 118

    1. Significant-Gravitas/AutoGPT★ 188k91% same
    2. calesthio/OpenMontage★ 74k92% same
    3. CherryHQ/cherry-studio★ 53k97% same
    4. polarsource/polar★ 10k91% same
    5. caorushizi/mediago★ 9.3k98% same
    6. mfts/papermark★ 9.2k95% same
    7. papermark/papermark★ 9.2k95% same
    8. midudev/preguntas-entrevista-react★ 7.8k99% same
    9. Kiranism/next-shadcn-dashboard-starter★ 7.2k97% same
    10. dinerojs/dinero.js★ 6.8k95% same

    108 more not listed

    Wrote their own version · 4

    1. QuantumNous/new-api★ 51ksame name
    2. coco-research/coco★ 797same name
    3. extra-org/extra★ 118same name
    4. composio-community/opencode-skills★ 14same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use dep-refs, feature-boundary-planner and 8 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • betacatslingSkill

      dep-refs

      Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.

      Also in 5 projects that use this

    • betacatslingSkill

      feature-boundary-planner

      Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.

      Also in 5 projects that use this

    • Cartograf666Skill

      architecture-governance

      Bootstrap, document, enforce, and review a project's architecture through layer responsibilities, dependency direction, architecture manifests, legacy baselines, Change Envelopes, cross-layer approval policy, and deterministic architecture checks. Use when starting a project, auditing an existing codebase, planning cross-layer work, preventing architecture erosion, reviewing structural changes, or deciding whether implementation may expand into another layer.

      Also in 5 projects that use this

    • VercelSkill

      next-upgrade

      Upgrade Next.js to the latest version following official migration guides and codemods

      Also in 10 projects that use this

    • thongdn-itSkill

      nuqs

      nuqs (type-safe URL query state) best practices for Next.js applications. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, or Next.js routing with state.

      Also in 4 projects that use this

    • VercelSkill

      vercel-react-view-transitions

      Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

      Also in 37 projects that use this

    • +3 more from vercel-labs
  • In this repository11 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.