Conciseness

The body is lean and avoids explaining concepts Claude already knows, with only minor redundancy (e.g., trigger conditions repeat the frontmatter and a few explanatory sentences could be trimmed).

Actionability

Provides copy-paste-ready commands (bun run test, test:coverage, --reporter=verbose), concrete config paths, and a numeric coverage target; the test-naming examples are illustrative patterns rather than fully runnable templates, leaving a minor gap.

Workflow Clarity

A clearly sequenced five-step workflow is paired with explicit validation (run before commit, >=80% coverage), a failure feedback loop ("if it fails unexpectedly, investigate"), and checklists for the complex process.

Progressive Disclosure

No bundle files exist; the ~130-line body is well-sectioned and self-contained with easy navigation, though the Edge Case Checklist and Common Mistakes table could optionally be split into references.

Specificity

Names the testing domain and two concrete actions ("writing and running tests", "quality standards") but does not enumerate broader coverage such as coverage analysis or regression handling, matching the anchor for 1-2 concrete actions.

Completeness

Explicitly states what it does ("Testing workflow and quality standards for writing and running tests") and gives concrete numbered "Use when" triggers, matching the anchor that requires both what and when with concrete trigger phrases.

Trigger Term Quality

Includes natural phrases a user would say ("writing new tests", "adding a new feature", "modifying logic") but omits common synonyms like unit tests, TDD, or test coverage.

Distinctiveness Conflict Risk

Targets a distinct test-writing workflow niche with specific triggers; minor overlap risk with closely related development skills keeps it just below a 5.