agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/react-best-practices/SKILL.md

react-best-practices

Skill0 starsChanged 8 months agoMITView on GitHub

用于 React / Next.js 现有代码优化：当用户要检查渲染性能、data fetching、bundle size、缓存、架构健康或性能回退时使用。Combine with `frontend-design` when 先改界面再做工程收口；Prefer `frontend-design` when the main goal is 新界面设计或视觉重构；Do not use for 与 React/Next 无关的问题。

66 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use composition-patterns, python-best-practices and 6 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.
  • eeaSkill

    composition-patterns

    React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

    Also in 4 projects that use this

  • jefflesterSkill

    python-best-practices

    Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.

    Also in 3 projects that use this

  • MicrosoftSkill

    code-quality

    Statically check changed C# against the same deterministic rules github-code-quality[bot] runs on pull requests, so a contributor can fix likely findings before opening the PR and keep the bot's inline comments to a minimum. Activate when a contributor asks to "check code quality", "run code quality on my changes", "will the code quality bot complain", "pre-check before I open the PR", "code quality check", or similar. Scoped to C#. Reads the diff and compares it against the enumerated csharp-code-quality rule set below — no CodeQL download or build required. This is a fast approximation of a dataflow engine, not a reproduction; report accordingly. Does NOT apply fixes unless explicitly asked.

    Also in 5 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 10 projects that use this

  • JetBrainsSkill

    webapp-testing

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    Also in 7 projects that use this

  • ttmouseSkill

    notebooklm

    Automate Google NotebookLM - create notebooks, add sources, generate podcasts/videos/quizzes, download artifacts. Supports browser-based content extraction for anti-crawler platforms (Twitter/X, LinkedIn, etc.). Activates on explicit /notebooklm or intent like "create a podcast about X

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep examples generic, privacy-safe, and portable across hosts.

    line 21
  2. Distinctive:

    Do not use for non-React stacks or pure product strategy work.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 56 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

react-best-practices

Intent

  • 用于 React / Next.js 现有代码优化：当用户要检查渲染性能、data fetching、bundle size、缓存、架构健康或性能回退时使用。Combine with frontend-design when 先改界面再做工程收口；Prefer frontend-design when the main goal is 新界面设计或视觉重构；Do not use for 与 React/Next 无关的问题。

Default operating pattern

  1. Clarify audience, surface, success metric, and implementation boundary.
  2. Study relevant patterns, references, or constraints before proposing a direction.
  3. Define structure, interaction, copy, and visual hierarchy with a reusable rationale.
  4. Pressure-test accessibility, motion, maintainability, and platform fit.
  5. Return a concise recommendation and the next implementation move.

Pack fit

  • Included in: product-design
  • Keep examples generic, privacy-safe, and portable across hosts.

Boundary

  • Do not use for non-React stacks or pure product strategy work.

Download now (ZIP)

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.

Check your setup, free