judokon-test-author
Writes and updates automated tests for JU-DO-KON! using Vitest and Playwright. Use whenever logic, state, or behaviour changes.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Skill Instructions
This skill makes verification mandatory.
Inputs / Outputs / Non-goals
- Inputs: changed logic, affected features, relevant test locations.
- Outputs: updated tests, coverage notes, targeted test commands.
- Non-goals: full suite runs without need or DOM-mutation tests.
What this skill helps accomplish
- Protect game logic from regressions
- Validate state transitions and rules
- Ensure feature flags behave correctly
When to use this skill
- Adding or modifying battle logic
- Changing state machines
- Introducing new features or flags
- Fixing bugs
Testing principles
- No logic change without tests
- Test behaviour, not implementation
- State transitions must be explicit
- Feature flags require on/off coverage
Test execution
- Prefer targeted runs:
npx vitest run tests/<path>.test.js - Use
npm run test:battles:classicornpm run test:battles:cliwhen relevant.
DOM discipline
- Do not mutate DOM directly in tests; use component APIs or user-level events.
Required test types
- State transition tests
- Rule evaluation tests
- Feature flag toggle tests
- Smoke tests for entry wiring
Expected output
- New or updated test files
- Clear test descriptions
- Coverage-aware suggestions when gaps exist
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!