pantheon-ai/software-design-principles
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
Evaluation results
93%
Code Review: E-Commerce Order Service
Apply SOLID principles for code review
Classifies decision type
100%
100%
Checks SRP compliance
100%
100%
Checks OCP compliance
90%
100%
Checks LSP compliance
80%
80%
Checks ISP compliance
90%
90%
Checks DIP compliance
100%
100%
Detects god class anti-pattern
100%
100%
Detects hardcoded secrets
57%
43%
Detects bypassed interfaces
100%
100%
Documents with BAD/GOOD format
100%
100%
Documents tradeoffs
100%
100%
Checks TypeScript strictness
100%
100%
With context: $0.5723 · 2m 46s · 17 turns · 592 in / 8,844 out tokens
98%
-2%Architecture Decision: Notification Service
Architecture decision for new microservice
Classifies decision type
100%
100%
Checks dependency direction
100%
100%
Avoids circular dependencies
100%
100%
Clear interface ownership
100%
100%
Entity purity
100%
100%
Uses ADR format
100%
87%
Documents alternatives
100%
100%
Documents risks
100%
100%
Includes validation step
100%
100%
With context: $0.7232 · 3m 18s · 25 turns · 19 in / 10,239 out tokens
100%
1%Refactoring: UserManagement Service
Refactoring legacy monolithic code
Classifies decision type
100%
100%
Applies SRP
100%
100%
Applies OCP
100%
100%
Applies DIP
100%
100%
Avoids god class
100%
100%
Evaluates pattern necessity
100%
100%
Documents tradeoffs
100%
100%
Does not premature optimize
100%
100%
Uses BAD/GOOD format
100%
100%
Includes validation
88%
100%
With context: $0.5269 · 2m 37s · 14 turns · 62 in / 7,936 out tokens
100%
Interface Design: Payment Provider Integration
Interface design for external integrations
Applies DIP
100%
100%
Applies ISP
100%
100%
Clear interface ownership
100%
100%
Avoids concrete coupling
100%
100%
Uses dependency injection
100%
100%
Documents tradeoffs
100%
100%
Includes validation step
100%
100%
With context: $0.6131 · 2m 25s · 22 turns · 19 in / 7,586 out tokens
100%
3%Feature Design: Product Review System
Avoiding YAGNI violations in new feature design
Classifies decision type
100%
100%
Applies design workflow
100%
100%
Avoids YAGNI violation
100%
100%
Solves current need
100%
100%
Plans for refactoring
100%
100%
Documents tradeoffs
100%
100%
Applies SOLID where relevant
70%
100%
Includes validation step
100%
100%
With context: $0.4796 · 2m 10s · 18 turns · 283 in / 6,090 out tokens
100%
Design Review: Domain Model Refactoring
rich entities
Classifies design decision type correctly
100%
100%
Identifies anemic domain model anti-pattern
100%
100%
Identifies scattered business logic in services
100%
100%
Recommends rich entity refactoring
100%
100%
Uses BAD/GOOD format for recommendations
100%
100%
Documents tradeoffs of rich entities
100%
100%
Proposes concrete entity methods for business rules
100%
100%
With context: $0.5690 · 2m 3s · 23 turns · 19 in / 5,959 out tokens
100%
Architecture Decision: Message Queue vs Direct API Calls
architecture documentation
Classifies as architectural decision
100%
100%
Uses proper ADR format
100%
100%
Documents alternatives with rationale
100%
100%
Explains chosen decision clearly
100%
100%
Documents risks and mitigation
100%
100%
Includes validation steps
100%
100%
Applies architectural dependency checks
100%
100%
With context: $0.4720 · 2m 38s · 13 turns · 13 in / 6,905 out tokens
Install with Tessl CLI
npx tessl i pantheon-ai/software-design-principles- Evaluated
- Agent
- Claude Code
Table of Contents