architecture-general

Architecture decisions: layering, design patterns, microservices trade-offs, and domain-driven design

0.97x

Quality

48%

Does it follow best practices?

Impact

97%

0.97x

Average score across 2 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/architecture-general/SKILL.md

Evaluation results

95%

-5%

Order Management API — Project Skeleton

Layered architecture skeleton for order-management API

Criteria

Baseline

With context

Layer separation

100%

Domain has no infra imports

100%

Application layer no infra imports

100%

Thin controller

100%

Repository abstraction

100%

Repo impl in infrastructure

100%

Email adapter interface

100%

50%

Email adapter impl in infra

100%

Domain use-case file

100%

ARCHITECTURE.md layer description

100%

Payment Service Overhaul

Payment dispatcher refactor and cross-service design

Criteria

Baseline

With context

No monolithic if/else

100%

Provider abstraction

100%

Registry or map dispatch

100%

Async messaging recommended

100%

Timeout mentioned

87%

100%

Circuit breaker mentioned

100%

Retry / backoff mentioned

100%

API contract before impl

100%

Bounded context identification

100%

Services own their data

100%

Output files present

100%

Repository: ucdavis/ai-skills-registry
Path: skills/architecture-general/SKILL.md
Commit: c0b2e4b

Evaluated: about 1 month ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Order Management API — Project Skeleton Payment Service Overhaul

Is this your skill?

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.