
Accelint Ts Testing
Opinionated vitest testing guidance for TypeScript projects that emphasizes what not to do. The skill covers test organization using the AAA pattern, property-based testing with fast-check for roundtrip and idempotence checks, and a test doubles hierarchy (fakes over stubs over mocks). It's notably strict about avoiding loose assertions like toBeTruthy, never mocking your own pure functions, and never testing constants files or library internals. Includes a mandatory type checking step before marking tests complete. Most useful when you're trying to prevent brittle tests or optimize slow suites, though the prescriptive tone won't be for everyone. Worth reviewing if your team keeps hitting flaky test issues.
- skills.sh installs
- 350
- GitHub stars
- 25
- last updated
- Aug 21, 2026
Install
$ npx -y skills add gohypergiant/agent-skills --skill accelint-ts-testing --agent claude-codeInstalls into .claude/skills of the current project.
Files
Vitest Best Practices
Comprehensive patterns for writing maintainable, effective vitest tests. Focused on expert-level guidance for test organization, clarity, and performance.
NEVER Do When Writing Vitest Tests
Sponsors
Details
- Repository
- github.com/gohypergiant/agent-skills
- Categories
- Testing & QA, Documentation, AI & Agent Building, Debugging
- First seen
- Jun 3, 2026
More from gohypergiant/agent-skills
All 14- Accelint Ts Performance347
- Accelint React Best Practices335
- Accelint Ts Best Practices334
- Accelint Security Best Practices323
- Accelint React Testing282
- 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