CtrlK
BlogDocsLog inGet started
Tessl Logo

evilissimo/modular-software-design

Use before implementing or refactoring software when the task requires designing module boundaries, APIs, layers, abstractions, services, repositories, adapters, or architecture. Helps coding agents 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.

93

1.13x
Quality

94%

Does it follow best practices?

Impact

93%

1.13x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-2/

{
  "context": "Tests architecture critique template usage and ability to diagnose shallow layers, pass-throughs, leakage, and strategic refactoring.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Template shape",
      "description": "Uses an architecture critique structure with 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 proposing fixes.",
      "max_score": 10
    },
    {
      "name": "Module map",
      "description": "Maps current modules with responsibility, interface/callers/dependencies, or decisions owned.",
      "max_score": 8
    },
    {
      "name": "Pass-through methods",
      "description": "Identifies service/manager/repository forwarding or same-shaped get_user methods as pass-through/shallow modules.",
      "max_score": 10
    },
    {
      "name": "Layer duplication",
      "description": "Identifies duplicated CRUD-shaped abstractions across adjacent layers.",
      "max_score": 8
    },
    {
      "name": "Leaked details",
      "description": "Flags HTTP request, transaction, SQL row, raw status code, or database details crossing inappropriate boundaries.",
      "max_score": 12
    },
    {
      "name": "Distinct layers",
      "description": "Recommends layer responsibilities that translate transport at the boundary, coordinate use cases, represent domain policy, and hide persistence.",
      "max_score": 10
    },
    {
      "name": "Small refactor",
      "description": "Recommends small strategic refactorings or migration path rather than a broad rewrite.",
      "max_score": 10
    },
    {
      "name": "Deep operation",
      "description": "Proposes a deeper use-case/domain operation that hides joining, active-member/privacy policy, or profile assembly from callers.",
      "max_score": 8
    },
    {
      "name": "Actionable errors",
      "description": "Suggests replacing raw status codes/generic error maps with domain concepts or actionable errors.",
      "max_score": 6
    },
    {
      "name": "Priority order",
      "description": "Provides a prioritized list of recommended changes.",
      "max_score": 8
    }
  ]
}

evals

README.md

SKILL.md

tile.json