This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design". Use for architecture decision records (ADRs), tech stack evaluation, system design reviews, dependency analysis, and generating architecture diagrams in Mermaid, PlantUML, or ASCII format.
89
78%
Does it follow best practices?
Impact
96%
1.81xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./engineering-team/senior-architect/SKILL.mdArchitecture diagram generation
Script invocation
0%
100%
Mermaid format flag
0%
100%
Component type flag
0%
100%
Layer type flag
0%
100%
File output flag
0%
100%
ASCII format flag
0%
100%
Dependency analysis and architecture assessment
Dependency analyzer script
0%
100%
JSON output flag (deps)
0%
100%
Circular check flag
0%
0%
Project architect script
0%
100%
Verbose flag used
0%
100%
JSON output flag (architect)
0%
100%
Architecture decision records and tech stack selection
ADR context section
100%
100%
ADR options section
75%
87%
ADR decision section
100%
100%
ADR trade-offs section
100%
100%
PostgreSQL chosen
100%
100%
Database selection workflow
100%
100%
Modular monolith pattern
100%
100%
Strangler fig migration
100%
100%
Technology stack selection
JWT for auth
100%
100%
Access token lifetime
100%
100%
Refresh token lifetime
100%
100%
PKCE for mobile OAuth
100%
100%
No implicit flow
100%
100%
Kafka for event streaming
100%
100%
Redis for caching
100%
100%
API response cache TTL
0%
100%
GraphQL for mobile
40%
100%
URL path versioning
100%
100%
Capacity planning and API design
DAU to RPS conversion
100%
100%
Compute requirement calculated
100%
100%
70% CPU headroom
0%
100%
Storage requirement calculated
100%
100%
Bandwidth requirement calculated
100%
100%
50% bandwidth headroom
0%
100%
Review triggers documented
100%
100%
API resources as nouns
100%
100%
Error response format
28%
100%
Standard HTTP status codes
100%
100%
Architecture pattern selection and event design
Event Sourcing recommended
100%
100%
CQRS recommended
100%
100%
Hexagonal architecture for fraud rules
100%
100%
Team size assessed
100%
100%
Domain boundaries before microservices
100%
100%
DomainEvent required fields
75%
100%
DomainEvent metadata fields
50%
100%
Deployment diagram command
0%
100%
Layer check command
0%
100%
Diagram saved to file
0%
100%
967fe01
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.