architecture-patterns
tessl install github:secondsky/claude-skills --skill architecture-patternsImplement 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.
Review Score
72%
Validation Score
14/16
Implementation Score
65%
Activation Score
67%
Generated
Validation
Total
14/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
Implementation
Suggestions 3
Score
65%Overall Assessment
The skill provides excellent, executable code examples demonstrating Clean Architecture, Hexagonal Architecture, and DDD patterns in Python. However, it's verbose with explanatory content Claude already knows, lacks clear implementation workflows with validation steps, and could benefit from better progressive disclosure by splitting detailed implementations into separate reference files.
Suggestions
- Remove or significantly condense the 'When to Use This Skill' and 'Core Concepts' sections - Claude already understands these architectural patterns
- Add a clear step-by-step workflow for implementing these patterns in a new project or refactoring an existing one, with validation checkpoints
- Split detailed code examples into separate reference files (e.g., CLEAN_ARCHITECTURE.md, HEXAGONAL.md, DDD.md) and keep SKILL.md as a concise overview with navigation
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill includes some unnecessary explanatory content (e.g., 'When to Use This Skill' section with 7 bullet points, 'Core Concepts' section explaining what Clean Architecture/Hexagonal/DDD are). Claude already knows these architectural patterns; the skill should focus on project-specific conventions or executable patterns. |
Actionability | 3/3 | Provides fully executable Python code examples with complete implementations including entities, repositories, use cases, and adapters. Code is copy-paste ready with proper imports and realistic implementations. |
Workflow Clarity | 2/3 | The skill presents patterns and code examples but lacks clear step-by-step workflows for implementing these architectures. No validation checkpoints or sequence for migrating existing code or setting up new projects. Best Practices and Common Pitfalls are listed but not integrated into actionable workflows. |
Progressive Disclosure | 2/3 | Content is reasonably organized with clear sections, but it's a monolithic document with no references to external files for detailed patterns. The 200+ lines could benefit from splitting detailed implementations into separate reference files while keeping SKILL.md as an overview. |
Activation
Suggestions 2
Score
67%Overall Assessment
This description has good structure with explicit 'what' and 'when' clauses, and names specific architecture patterns. However, it lacks concrete action verbs describing deliverables and misses common trigger term variations that users might naturally use when seeking architecture guidance.
Suggestions
- Add more concrete actions like 'define bounded contexts', 'create layer boundaries', 'structure dependency injection', 'separate domain from infrastructure'
- Include common trigger term variations: 'DDD', 'ports and adapters', 'onion architecture', 'code organization', 'separation of concerns', 'layered architecture'
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | 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'. |
Completeness | 3/3 | Clearly answers both what ('Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design') and when ('Use when architecting complex backend systems or refactoring existing applications for better maintainability') with explicit trigger guidance. |
Trigger Term Quality | 2/3 | Includes some relevant terms 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 'code organization'. |
Distinctiveness Conflict Risk | 2/3 | Reasonably specific to architecture patterns, but 'backend systems' and 'refactoring' are broad terms that could overlap with general coding skills or other backend-focused skills. The specific pattern names help distinguish it, but the scope could still conflict with general software design skills. |