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

suite-review-template.mdskills/software-testing/templates/

Existing Test Suite Review

Coverage Assessment

  • High-risk areas covered?
  • End-to-end overuse?
  • Coverage gaps that matter?

Quality Assessment

  • Flaky tests?
  • Tight coupling to implementation?
  • Weak assertions?
  • Mystery guests?
  • Excessive setup?
  • Duplicated helpers?

Architecture Feedback

  • Hidden coupling
  • Implicit dependencies
  • Oversized modules
  • Weak observability
  • Missing ports/adapters
  • Places where mocks compensate for bad structure

Recommendations

  • Removals:
  • Rewrites:
  • Additions:
  • Refactoring suggestions that improve both design and tests:

skills

tile.json