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

regression-test-plan.mdskills/software-testing/templates/

Regression Test Plan

Bug Symptom

<!-- What failed in production or testing? -->

Reproduction Level

<!-- Unit, integration, or end-to-end test that reproduces the symptom -->

Minimal Failing Case

<!-- The smallest input/state that triggers the bug -->

Neighbouring Edges to Add

<!-- Boundary values and related cases that should also be protected -->

Root-Cause-Focused Lower-Level Test

<!-- Test near the actual fault if it helps localise and protect -->

Related Contracts or Integrations to Protect

<!-- Other seams that could have similar issues -->

skills

tile.json