agentleFS
Sign inStart free
sreejithramansreejithraman/SreeStack/skills/react-doctor/SKILL.md

react-doctor

Skill1 starsChanged 16 days agoMITView on GitHub

Use React Doctor to scan or fix React diagnostics, run its static design checks, capture a browser performance trace, or explain and configure Doctor rules.

52 other projects use a version of this, 32 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use turborepo, make-interfaces-feel-better 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.
  • VercelSkill

    turborepo

    Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries.

    Also in 5 projects that use this

  • studio-lgtmSkill

    make-interfaces-feel-better

    Apply design engineering best practices to polish UI components - use when reviewing or improving interfaces, animations, typography, or interaction details.

    Also in 4 projects that use this

  • AnasX7Skill

    better-accessibility

    Helps your project comply with accessibility standards and best practices.

    Also in 3 projects that use this

  • AnasX7Skill

    better-layout

    Helps with grouping, alignment, reading order, progressive disclosure and other details that make a good layout.

    Also in 3 projects that use this

  • SentrySkill

    vercel-composition-patterns

    Also in 6 projects that use this

  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 9 projects that use this

  • +2 more from AnasX7
  • +1 more from vercel-labs

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run npx react-doctor@latest --verbose (the default --scope full) to scan the full codebase.

    line 16
  2. Very specific:

    Run npx react-doctor@latest design --verbose.

    line 22
  3. Distinctive:

    When the user wants to understand a rule, disagrees with one, or wants to disable / tune which rules run (not fix code), read …

    line 37

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

React Doctor scans React codebases for security, performance, correctness, and architecture issues. Its 0–100 score summarizes those diagnostics, not the whole product experience. For scan or triage requests, report findings without editing code. Fix accepted findings when the request includes cleanup or implementation.

For a general scan or cleanup

Run npx react-doctor@latest --verbose (the default --scope full) to scan the full codebase. Triage findings by impact and evidence, with errors before warnings. Fix in-scope findings only when the task calls for changes.

For static design diagnostics

Run npx react-doctor@latest design --verbose. This selects design-tagged UI composition, typography, interaction, accessibility, and motion rules, including focused rules that remain opt-in during a general health scan. Treat the result as source-code findings. For an audit of the rendered interface and real interactions, use verify with ui-design rather than treating a clean scan as a pass.

For runtime performance problems:

Run npx react-doctor@latest scan <url> --format json in an interactive terminal. React Doctor opens an isolated system Chrome profile, records a DevTools trace while the user reproduces the slow interaction, and flashes purple outlines with component names as React renders. It stops when they press Enter. Read the structured summary first, then inspect the returned local .json.gz trace for CPU, browser, and React component evidence.

If the user needs their authenticated browser state, use --cdp <remote-debugging-url>. This requires Chrome to already be running with remote debugging. Never ask for cookies or copy the user's browser profile. Treat the trace as sensitive local application data and never upload it without explicit permission.

Configuring or explaining rules

When the user wants to understand a rule, disagrees with one, or wants to disable / tune which rules run (not fix code), read references/explain.md and follow it. Start with npx react-doctor@latest rules explain <rule>, then apply the narrowest control via npx react-doctor@latest rules disable|set|category|ignore-tag …, which edits your doctor.config.* (or package.json#reactDoctor).

Command

npx react-doctor@latest --verbose
FlagPurpose
.Scan current directory
--verboseShow affected files and line numbers per rule
--scope changedOnly report issues introduced vs the base branch (default: full)
--baseGit ref for --scope changed or --scope lines
--include-untrackedWith changed/files/lines scope, also scan nonignored untracked files
--scope linesOnly report issues on the changed lines
--scoreOutput only the numeric score
designRun only the focused UI design diagnostics

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