TypeScript testing conventions and TDD practices. Use when writing tests, fixing bugs, or organizing test files.
/plugin marketplace add jasonkuhrt/claude-marketplace/plugin install typescript@jasonkuhrtThis skill inherits all available tools. When active, it can use any tool Claude has access to.
foo.ts → foo.test.tsdescribe blocks for each export (unless single export)src/arr/traits/eq.test.ts, don't use describe('Arr.Eq implementation') - the file path already indicates thisCRITICAL: Use Test.describe() NOT comments for grouping:
// ❌ BAD - inline comments for grouping
// Long flags
test('--verbose works', ...)
test('--quiet works', ...)
// ✅ GOOD - Test.describe for grouping
Test.describe('long flags', () => {
test('--verbose works', ...)
test('--quiet works', ...)
})
CRITICAL: Before implementing ANY bug fix:
No exceptions - TDD is mandatory for bug fixes. Only skip for complex integration scenarios (e.g., massive deep state in Playwright browser tests).
READ THE JSDOC - Before using ANY test API, read the actual JSDoc documentation in the source code. Never guess the API signature. Find usage examples in the codebase if needed.
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.