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.
93
94%
Does it follow best practices?
Impact
92%
1.12xAverage score across 5 eval scenarios
Passed
No known issues
criteria.jsonevals/scenario-2/
{
"context": "Tests modular architecture critique.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Critique structure",
"description": "Uses scope, module map, complexity symptoms, design smells, recommendations, and priority order.",
"max_score": 10
},
{
"name": "Symptoms first",
"description": "Frames issues as change amplification, cognitive load, hidden coupling, or unknown unknowns before fixes.",
"max_score": 10
},
{
"name": "Pass-throughs",
"description": "Identifies same-shaped forwarding get_user layers as shallow/pass-through modules.",
"max_score": 12
},
{
"name": "Layer duplication",
"description": "Identifies duplicated CRUD-shaped abstractions across adjacent layers.",
"max_score": 10
},
{
"name": "Leaks",
"description": "Flags HTTP request, transaction, raw row/status code, SQL/database details crossing boundaries.",
"max_score": 14
},
{
"name": "Distinct layers",
"description": "Recommends distinct transport/application/domain/infrastructure abstractions.",
"max_score": 10
},
{
"name": "Deep operation",
"description": "Proposes a deeper use-case/domain operation hiding profile assembly and policy.",
"max_score": 8
},
{
"name": "Small refactor",
"description": "Recommends strategic migration steps rather than a broad rewrite.",
"max_score": 10
},
{
"name": "Errors concepts",
"description": "Replaces raw status/error maps with domain concepts or actionable errors.",
"max_score": 8
},
{
"name": "Priority order",
"description": "Provides prioritized recommendations.",
"max_score": 8
}
]
}