agentleFS
EstebanT1112EstebanT1112/codex-engineering-workflow/skills/react-testing/SKILL.md

react-testing

Skill0 starsChanged 2 months agoMITView on GitHub

Write or repair behavior-focused tests for React web components, hooks, and pages using the repository's existing Vitest or Jest, React Testing Library, network mocks, and accessibility assertions. Use when React test code is part of the requested change.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use orch-pipeline, parallel-execution-optimizer 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.
  • renepfSkill

    orch-pipeline

    Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

    Also in 4 projects that use this

  • marcusgollSkill

    parallel-execution-optimizer

    Identify and execute independent operations in parallel for 3-5x speedup. Auto-analyzes task dependencies, groups into batches, launches parallel Task() calls. Applies to /optimize (5 checks), /ship pre-flight (5 checks), /implement (task batching), /prototype (N screens). Auto-triggers when detecting multiple independent operations in a phase.

    Also in 5 projects that use this

  • ronmkrSkill

    vite-patterns

    Vite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.

    Also in 6 projects that use this

  • RojiosSkill

    defi-amm-security

    Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.

    Also in 5 projects that use this

  • renepfSkill

    prediction-market-oracle-research

    Research prediction markets as data sources or oracle signals for products, agents, dashboards, and corporate decision intelligence. Use for source-grounded analysis of market-implied probabilities, caveats, and integration patterns without investment advice.

    Also in 3 projects that use this

  • nek1987Skill

    react-performance

    Performance optimization for React web applications. Use when optimizing renders, implementing virtualization, memoizing components, or debugging performance issues.

    Also in 9 projects that use this

  • +2 more from renepf

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the focused test first, then the impacted suite and repository checks.

    line 19
  2. Very specific:

    Use tdd-workflow for the red-green-refactor sequence and react-patterns for component implementation.

    line 25
  3. Distinctive:

    Do not add a new runner, DOM shim, MSW, axe, or browser framework solely because this skill names the category.

    line 27

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

Workflow

  1. Detect the actual React version, test runner, DOM environment, test utilities, provider wrappers, and existing conventions.
  2. Choose the smallest test that observes user-visible behavior or a stable hook contract.
  3. Query by role, name, label, or visible text and interact through the same controls a user uses.
  4. Mock network boundaries with the repository's established mechanism; avoid mocking the component's own implementation details.
  5. Cover the relevant success, failure, loading, validation, or accessibility behavior without duplicating framework behavior.
  6. Reproduce regressions with a failing test before the fix when practical.
  7. Run the focused test first, then the impacted suite and repository checks.

Test Boundary

  • Component tests cover rendering, interactions, validation, callbacks, and local request states.
  • Browser or end-to-end tests cover navigation, real browser layout, multi-page flows, and deployed integration.
  • Use tdd-workflow for the red-green-refactor sequence and react-patterns for component implementation.

Do not add a new runner, DOM shim, MSW, axe, or browser framework solely because this skill names the category.

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.