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.
69
Quality
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/architecture-patterns/SKILL.mdQuality
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 description has good structure with an explicit 'Use when' clause and names specific architecture patterns, making it complete. However, it lacks concrete action verbs describing what deliverables or artifacts the skill produces, and could benefit from more natural trigger term variations that users commonly use when discussing these patterns.
Suggestions
Add more specific concrete actions like 'define bounded contexts, create layer boundaries, implement ports and adapters, model domain aggregates'
Include common trigger term variations users might say: 'DDD', 'ports and adapters', 'onion architecture', 'layered architecture', 'separation of concerns', 'dependency inversion'
| 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 ports and adapters, model aggregates'. | 2 / 3 |
Completeness | Clearly answers both what (implement backend architecture patterns including specific named patterns) and when (explicit 'Use when architecting complex backend systems or refactoring existing applications for better maintainability'). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Clean Architecture', 'Hexagonal Architecture', 'Domain-Driven Design', 'backend systems', and 'maintainability', but misses common variations users might say like 'ports and adapters', 'onion architecture', 'DDD', 'layered architecture', 'separation of concerns'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to backend architecture patterns, but could overlap with general 'code refactoring' skills or 'software design' skills. The specific pattern names help distinguish it, but 'complex backend systems' is somewhat broad. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, appropriately delegating detailed content to a separate playbook. However, the core instructions are too abstract and lack actionable guidance—there are no concrete examples, code snippets, or specific commands that would help Claude execute these architectural patterns. The skill reads more like a table of contents than executable guidance.
Suggestions
Add at least one concrete code example showing a Clean Architecture or Hexagonal Architecture folder structure with sample interfaces
Include specific validation criteria or checklists inline (e.g., 'Verify: no domain layer imports from infrastructure layer')
Provide a concrete example of defining module boundaries with actual interface definitions rather than abstract instructions
Add a minimal worked example showing before/after of a refactoring step
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what Clean Architecture or DDD are. Every section serves a purpose without padding or concepts Claude already knows. | 3 / 3 |
Actionability | The instructions are vague and abstract ('Clarify domain boundaries', 'Select an architecture pattern') with no concrete code, commands, or specific examples. It describes what to do rather than showing how to do it. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints, feedback loops, or concrete verification criteria. 'Validation checks' are mentioned but not specified, and there's no guidance on what to do if validation fails. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-signaled one-level-deep reference to the implementation playbook. The skill appropriately delegates detailed content to a separate resource file. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- duclm1x1/Dive-Ai
- Commit
20ba150
- Reviewed
Table of Contents
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.