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.

0.98x

Quality

68%

Does it follow best practices?

Impact

97%

0.98x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/architecture-patterns/SKILL.md

The canonical home for this skill is architecture-patterns in wshobson/agents

Quality

Content

53%Weight 40%Scale 1-5

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

The body is highly actionable with rich executable code, but it front-loads conceptual explanations Claude already knows and inlines large code blocks that should live in the referenced bundle files. The referenced references/ and assets/ paths do not exist, so progressive disclosure is poorly realized.

Suggestions

Remove or drastically shrink the 'Core Concepts' section — it explains architecture concepts Claude already knows and duplicates the later pattern sections.

Move the large per-pattern code examples into the referenced bundle files (references/*.md, assets/*) and actually create those files so the Resources links resolve.

Add an explicit step-by-step workflow for applying the patterns to a real system (e.g. identify bounded contexts → define ports → implement adapters → verify dependency direction), with a validation checkpoint confirming dependencies point inward.

Dimension	Reasoning	Score
Conciseness	The 'Core Concepts' section re-explains Clean/Hexagonal/DDD at a conceptual level that Claude already knows, and the opening line restates the frontmatter description; the bulk code is useful but the conceptual padding could be trimmed.	3 / 5
Actionability	Provides extensive concrete, executable Python (directory structure, entities, interfaces, use cases, adapters, controllers), but the hexagonal and DDD sections reference undefined classes (Order, OrderResult, Customer, OrderItem, OrderStatus, stripe) leaving minor gaps.	4 / 5
Workflow Clarity	Structured as a catalog (when-to-use → concepts → patterns → best practices → pitfalls) with a rough sequence, but there is no explicit multi-step application workflow or validation checkpoints.	3 / 5
Progressive Disclosure	The Resources section signals separate files (references/.md, assets/) but none of those bundle paths exist, and ~400 lines of detailed code that the references claim to hold are inlined directly in SKILL.md.	2 / 5
	Total	12 / 20 Passed

Description

83%Weight 40%Scale 1-5

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

A well-crafted description that clearly states what the skill does and when to use it, with concrete named patterns and natural trigger phrases. It is specific, third-person, and largely distinct from other skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several specific concrete patterns — 'Clean Architecture, Hexagonal Architecture, and Domain-Driven Design' — plus the action 'refactoring existing applications for better maintainability', giving good coverage with only minor gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('Implement proven backend architecture patterns including...') and 'when' ('Use when architecting complex backend systems or refactoring existing applications for better maintainability') with concrete triggers.	5 / 5
Trigger Term Quality	Includes natural user-facing terms like 'architecting complex backend systems', 'refactoring existing applications', and the named patterns; a few synonymous phrasings (e.g. 'ports and adapters') are absent.	4 / 5
Distinctiveness Conflict Risk	The named patterns give it a clear niche, but the trigger 'refactoring existing applications for better maintainability' has minor overlap risk with general refactoring or maintainability skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/architecture-patterns/SKILL.md
Commit: 6453c0b

Reviewed: about 9 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.