agentleFS
GiammeGiamme/linear-spanks/skills/extras/tech-react/SKILL.md

tech-react

Skill1 starsChanged 28 days agoMITView on GitHub

Technology skill loaded when working in a React ecosystem.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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. Distinctive:

    When building React components, prioritize functional purity and rendering efficiency:

    line 11
  2. Distinctive:

    Functional Components: Use functional components and Hooks exclusively.

    line 13
  3. Distinctive:

    Derived State: Avoid storing state that can be computed from existing state or props on the fly.

    line 14
  4. Very specific:

    Dependencies: Ensure useEffect, useMemo, and useCallback dependency arrays are exhaustive and accurate.

    line 15
  5. Very specific:

    Render Optimization: Do not use React.memo or useMemo prematurely.

    line 16
  6. Distinctive:

    Colocation: Keep component styles, tests, and specific utilities colocated in the same directory as the component.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.

When building React components, prioritize functional purity and rendering efficiency:

  1. Functional Components: Use functional components and Hooks exclusively. Do not write Class components.
  2. Derived State: Avoid storing state that can be computed from existing state or props on the fly.
  3. Dependencies: Ensure useEffect, useMemo, and useCallback dependency arrays are exhaustive and accurate.
  4. Render Optimization: Do not use React.memo or useMemo prematurely. Only use them when you have proven a rendering bottleneck.
  5. Colocation: Keep component styles, tests, and specific utilities colocated in the same directory as the component.

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.