evilissimo/software-design
Use before implementing or refactoring software. Contains two skills: (1) Modular Software Design — for designing module boundaries, APIs, layers, abstractions, services, repositories, adapters, or architecture, helping reduce total system complexity by creating deep modules, hiding implementation knowledge, avoiding leakage and pass-through APIs, comparing alternative designs, documenting interfaces before coding, and critiquing existing architecture; and (2) Software Testing — for writing unit tests, integration tests, or end-to-end tests, creating mocks/stubs/fakes, designing a testing strategy, doing TDD, reviewing test quality, fixing flaky tests, or refactoring test suites, generating risk-focused test plans, picking appropriate test levels, choosing between mocks/fakes/real dependencies, and applying Arrange-Act-Assert patterns with concrete examples.
88
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
test-design-checklist.mdskills/software-testing/templates/
Test Design Checklist
- Behaviour protected: What observable behaviour does this test verify?
- Risk targeted: What failure mode does this test protect against?
- Level chosen: Is this the cheapest level that can expose this risk?
- Oracle chosen: What will the test observe and assert?
- Boundary cases: Are key boundaries covered?
- Invalid cases: Are invalid inputs and error paths covered?
- Invariants or properties: Are there properties worth testing with generated inputs?
- Dependency treatment: Real, fake, stub, spy, or mock—and why?
- Readability check: Can someone understand the scenario without reading the implementation?
- Brittleness check: If internals change but behaviour stays the same, will this test still pass?