agentleFS
Sign inStart free
vlad-ryzhkovvlad-ryzhkov/ai-context-engineering-for-frontend/.agents/skills/react-doctor/SKILL.md

react-doctor

Skill2 starsChanged 8 months agoUnlicenseView on GitHub

React Doctor health check (React-only)

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use turborepo, make-interfaces-feel-better and 10 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

    gh-stack

    Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.

    Also in 3 projects that use this

  • +2 more from AnasX7

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 53 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:

    Read AGENTS.md to understand the project philosophy and tech stack.

    line 9
  2. Distinctive:

    Do NOT guess the procedure and do NOT output anything yet.

    line 13

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

INSTRUCTIONS

You are acting as a Frontend Lead. Read AGENTS.md to understand the project philosophy and tech stack.

LOGIC SOURCE

Do NOT guess the procedure and do NOT output anything yet. You MUST use your file-reading tool to fetch and strictly follow:

  1. First, read the core agent context: .claude/frontend_agent.md
  2. Second, read the specific skill protocol: .claude/skills/react-doctor/SKILL.md
  3. Execute based STRICTLY on the logic and output format defined in those files.

CRITICAL REMINDERS

  • React-only — auto-skips Vue projects
  • Report saved to audit/react-doctor-report_{timestamp}.md

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