CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

test-strategy-brief.mdskills/software-testing/templates/

Test Strategy Brief

Change Summary

<!-- What is being built or changed? -->

Top Risks and Failure Modes

<!-- Wrong result, boundary handling, persistence mismatch, broken protocol, concurrency, workflow breakage -->

Primary Public Seams

<!-- Entry points clients use -->

Chosen Test Levels and Why

<!-- Unit, integration, contract, end-to-end -->

Planned Examples, Boundaries, Invariants, Contracts

<!-- Key test cases and properties to verify -->

Doubles and Real Dependencies

<!-- What to mock/fake/stub and what to use for real -->

Coverage Checks to Use Diagnostically

<!-- What coverage criteria will guide us -->

Stop Rule

<!-- When will we stop adding tests? -->

skills

tile.json