Apply software design principles across architecture and implementation using deterministic decision workflows, SOLID checks, structural patterns, and anti-pattern detection; use when reviewing designs, refactoring modules, or resolving maintainability and coupling risks.
Does it follow best practices?
Evaluation — 99%
↑ 1.01xAgent success when using this tile
Validation for skill structure
{
"context": "Refactoring an anemic domain model - tests whether the agent identifies anti-patterns and applies rich entity design principles correctly",
"type": "weighted_checklist",
"checklist": [
{
"name": "Classifies design decision type correctly",
"description": "Identifies this as a tactical design decision",
"max_score": 10
},
{
"name": "Identifies anemic domain model anti-pattern",
"description": "Recognizes that entities are data containers without behavior",
"max_score": 20
},
{
"name": "Identifies scattered business logic in services",
"description": "Points out business rules are in service layer instead of entities",
"max_score": 15
},
{
"name": "Recommends rich entity refactoring",
"description": "Suggests moving business logic into domain entities",
"max_score": 20
},
{
"name": "Uses BAD/GOOD format for recommendations",
"description": "Shows problematic code and improved alternatives",
"max_score": 15
},
{
"name": "Documents tradeoffs of rich entities",
"description": "Explains benefits and costs of rich vs anemic domain models",
"max_score": 10
},
{
"name": "Proposes concrete entity methods for business rules",
"description": "Shows specific methods like canBorrow(), borrow() on entities",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i pantheon-ai/software-design-principlesevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
references