Lean and efficient: tight code examples, rule statements, and good/bad contrast without explaining concepts Claude already knows, so every token earns its place.

Provides executable code (expectOk/expectErr imports), concrete naming patterns, decision tables, and copy-paste-ready good/bad examples rather than vague direction.

Conventions are organized into clearly sequenced sections with explicit decision rules (When to Split / When NOT to Split); no destructive batch workflow is present that would require validate-fix-retry loops.

Body is an overview that signals five one-level-deep reference files with 'If working with X, read [references/...]' triggers; all referenced files exist and are appropriately split out.

Lists multiple concrete actions — 'setup functions, factories, Result assertion helpers, organization, type testing, naming, and pruning low-value tests' — matching the anchor for enumerating specific actions.

Explicitly answers both what (the conventions list) and when ('Use when: ...') with explicit triggers, matching the top anchor.

Natural quoted triggers ('write tests', 'add a test', 'fix this test', 'delete tests', 'prune tests', 'audit tests') plus '*.test.ts' give good coverage of terms a user would actually say.

A clear, narrow niche (test file conventions) with distinct, specific triggers makes overlap with other skills unlikely.