architecture-patterns

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.

Install with Tessl CLI

npx tessl i github:wshobson/agents --skill architecture-patterns

What are skills?

Overall
score

75%

Review — 70%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 97%

↓ 0.98x

Agent success when using this skill

Validation — 14 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a competent description that clearly communicates its purpose and includes an explicit 'Use when' clause, which is its strongest aspect. However, it could be improved by listing more concrete actions/deliverables and expanding trigger terms to include common abbreviations and alternative phrasings that users naturally employ when discussing these architectural patterns.

Suggestions

Add more concrete actions like 'define bounded contexts', 'create layer boundaries', 'structure dependency injection', 'separate domain from infrastructure'

Expand trigger terms to include common variations: 'DDD', 'ports and adapters', 'onion architecture', 'layered architecture', 'separation of concerns'

Dimension	Reasoning	Score
Specificity	Names the domain (backend architecture) and lists specific patterns (Clean Architecture, Hexagonal Architecture, DDD), but doesn't describe concrete actions beyond 'implement' and 'refactoring' - lacks specific deliverables like 'create layer boundaries', 'define domain models', or 'structure dependency injection'.	2 / 3
Completeness	Clearly answers both what (implement backend architecture patterns including specific named patterns) and when (architecting complex backend systems or refactoring for maintainability) with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'Clean Architecture', 'Hexagonal Architecture', 'Domain-Driven Design', 'backend systems', and 'refactoring', but misses common variations users might say like 'ports and adapters', 'onion architecture', 'DDD', 'layered architecture', 'separation of concerns', or 'dependency inversion'.	2 / 3
Distinctiveness Conflict Risk	Reasonably specific to backend architecture patterns, but could overlap with general 'code refactoring' skills or 'software design' skills. The mention of 'refactoring existing applications' is broad enough to potentially conflict with other refactoring-focused skills.	2 / 3
	Total	9 / 12 Passed

Implementation

73%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides excellent actionable code examples with complete, executable implementations of Clean Architecture, Hexagonal Architecture, and DDD patterns. However, it's verbose with conceptual explanations Claude doesn't need, and lacks explicit workflows for when/how to apply these patterns during actual system design or refactoring tasks.

Suggestions

Remove or significantly condense the 'Core Concepts' section - Claude already knows these architectural patterns; jump directly to implementation examples

Add a concrete workflow for applying these patterns: e.g., '1. Identify bounded contexts → 2. Define domain entities → 3. Create ports → 4. Implement adapters → 5. Validate dependency direction'

Trim the 'When to Use This Skill' bullet list - it's self-evident from the skill description

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary explanatory content (e.g., explaining what Clean Architecture layers are, what DDD patterns mean) that Claude already knows. The 'When to Use This Skill' section and 'Core Concepts' overview add bulk before getting to actionable content.	2 / 3
Actionability	Provides fully executable Python code examples with complete implementations including entities, repositories, use cases, controllers, and adapters. Code is copy-paste ready with proper imports and realistic patterns.	3 / 3
Workflow Clarity	While the code examples show how components connect, there's no explicit step-by-step workflow for implementing these patterns. Missing validation checkpoints for architectural decisions or refactoring processes. The 'Best Practices' and 'Common Pitfalls' sections are lists rather than actionable workflows.	2 / 3
Progressive Disclosure	Good structure with clear sections, references to external files (references/clean-architecture-guide.md, assets/clean-architecture-template/), and appropriate content organization. The main skill provides overview and examples while pointing to detailed guides.	3 / 3
	Total	10 / 12 Passed

Validation

88%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	14 / 16 Passed

Reviewed: about 4 hours ago

Table of Contents

Discovery Implementation Validation

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.