
Accelint React Testing
Load this when you're writing React tests and need to remember the query hierarchy or stop reaching for test IDs. It's opinionated about Testing Library best practices: getByRole over everything, userEvent instead of fireEvent, screen queries over destructured ones. The NEVER sections are extensive and specific, like why fireEvent.click misses the focus/mousedown/mouseup sequence that real users trigger. If you keep writing tests that break on refactors or miss accessibility issues, this will push you toward user-centric patterns. Covers async utilities, custom renders with providers, and why snapshots of entire trees are usually a waste.
- skills.sh installs
- 282
- GitHub stars
- 25
- last updated
- Aug 21, 2026
Install
$ npx -y skills add gohypergiant/agent-skills --skill accelint-react-testing --agent claude-codeInstalls into .claude/skills of the current project.
Files
React Testing Best Practices
Expert guidance for writing maintainable, user-centric React component tests with Testing Library. Focused on query selection, accessibility-first testing, and avoiding implementation details.
NEVER Do When Writing React Tests
Sponsors
Details
- Repository
- github.com/gohypergiant/agent-skills
- Categories
- Frontend Development, Testing & QA, Documentation, Code Review & Quality, AI & Agent Building, Productivity & Planning, Design & UI/UX, CLI & Terminal
- First seen
- Jun 3, 2026
More from gohypergiant/agent-skills
All 14- Accelint Tanstack Query Best Practices279
- Accelint Ts Documentation263
- Accelint Skill Manager230
- Humanizer140
- Skill Judge134
- Ask Questions If Underspecified132
- Accelint Nextjs Best Practices386
- Accelint Readme Writer386
- Accelint Ts Testing350
- Accelint Ts Performance347
- Accelint React Best Practices335
- Accelint Ts Best Practices334
- Accelint Security Best Practices323