Reference tile for Themis, a Node.js and TypeScript unit test framework designed for AI coding agents. Covers unit-test authoring, Jest/Vitest migration, agent-readable failure output with repair hints, and first-class integrations for Claude Code, Cursor, and generic agents.
98
94%
Does it follow best practices?
Impact
99%
2.91xAverage score across 20 eval scenarios
Passed
No known issues
--reporter agent in script
0%
100%
--rerun-failed in script
0%
100%
failures[].cluster mentioned
0%
100%
failures[].repairHints mentioned
0%
100%
sourceFile/lineNumber mentioned
0%
100%
No stack trace re-reading
70%
100%
expected/actual mentioned
100%
100%
Script comment explains why agent reporter
0%
100%
--claude-code flag used
100%
100%
CLAUDE.md mentioned in notes
100%
100%
Skill file path mentioned
0%
100%
Slash commands mentioned
100%
100%
PostToolUse hook mentioned
80%
100%
generate command in setup.sh
60%
100%
Skill auto-load behavior described
0%
100%
Hook feedback loop described
100%
100%
Clock controlled in scheduler test
100%
100%
Network mocked in rate test
100%
100%
test() for aggregateRecords
0%
50%
intent() for ReportScheduler
100%
100%
Triple-slash reference present
0%
100%
No Jest/Vitest APIs in test files
0%
100%
Nondeterminism handling documented
100%
100%
Tests in __themis__/tests
100%
100%
Deterministic assertions
100%
100%
.themis/ gitignored
0%
100%
__themis__/reports/ gitignored
0%
100%
__themis__/shims/ gitignored
0%
100%
init --agents in setup
0%
100%
generate src/ in setup
100%
100%
.themis/ described as framework-managed
0%
100%
__themis__/tests described as committed
0%
100%
No Jest/Vitest setup
100%
100%
Triple-slash reference in pipeline test
0%
100%
Triple-slash reference in utility test
0%
100%
intent() for DocumentParser
0%
100%
test() for normalizeText
0%
100%
intent has context phase
0%
100%
intent has run phase
0%
100%
intent has assert/verify phase
0%
100%
No Jest/Vitest APIs in test files
0%
100%
Reference directive explained
83%
100%
intent for pipeline
0%
100%
test for slugify
0%
100%
No Jest describe/it/expect
0%
100%
No Jest import
100%
100%
DECISIONS.md present
0%
100%
intent rationale in DECISIONS.md
0%
100%
test rationale in DECISIONS.md
28%
100%
themis migrate command used
0%
100%
No manual Jest rewrite
0%
100%
Built-in workflow first
0%
100%
rerun-failed mentioned
0%
100%
update-contracts mentioned
0%
100%
No Jest config preserved
100%
100%
MIGRATION_NOTES.md present
100%
100%
No Jest devDependencies kept
100%
100%
No tests/*.cjs shim
100%
100%
No tests/*.setup.* file
100%
100%
No jest.config shim
0%
100%
No moduleNameMapper
0%
100%
APPROACH.md present
100%
100%
APPROACH.md no-shim rationale
0%
100%
Test files use Themis constructs
0%
100%
Test files in __themis__/tests
0%
100%
generate command in script
100%
100%
intent for runPipeline
0%
100%
test for aggregateStep
0%
100%
Tests in __themis__/tests
0%
100%
.themis/ described as artifact output
100%
100%
__themis__/tests described as committed
0%
100%
No Jest/Vitest APIs in tests
0%
100%
GENERATION_REPORT.md present
100%
100%
themis migrate vitest in script
0%
100%
--rewrite-imports --convert flags used
0%
100%
No manual sed/awk rewrite
100%
100%
--rerun-failed in script
0%
100%
--update-contracts in script
0%
100%
Vitest deps removal mentioned
100%
100%
Three failure states documented
66%
100%
Built-in commands before manual work
60%
100%
Final themis test confirms stable
20%
90%
Table of Contents