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 ...
74
Quality
62%
Does it follow best practices?
Impact
94%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-architecture-patterns/SKILL.mdQuality
Discovery
89%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 well-crafted skill description with explicit trigger guidance and domain-specific terminology. The 'Use when' clause provides clear selection criteria, and the named patterns (Clean Architecture, Hexagonal, DDD) serve as distinctive triggers. The main weakness is that the description appears truncated, and the concrete actions could be more detailed beyond 'implement' and 'refactoring'.
Suggestions
Expand the concrete actions to include more specific capabilities like 'define bounded contexts', 'structure dependency injection', 'create port/adapter interfaces', or 'separate domain from infrastructure layers'
| 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'. The description is truncated, limiting assessment of full capabilities. | 2 / 3 |
Completeness | Explicitly 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...'). Has explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Clean Architecture', 'Hexagonal Architecture', 'Domain-Driven Design', 'backend systems', 'refactoring'. These are terms developers naturally use when seeking architectural guidance. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on specific architectural patterns (Clean, Hexagonal, DDD) for backend systems. Distinct triggers like 'Clean Architecture' and 'Hexagonal Architecture' are unlikely to conflict with general coding or other architecture skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions more as a table of contents than actionable guidance. It lacks concrete examples of Clean Architecture, Hexagonal Architecture, or DDD patterns, instead deferring entirely to an external playbook. The instructions are too abstract to be immediately useful, and the 'when to use' sections add little value for Claude.
Suggestions
Add at least one concrete code example showing a Clean Architecture or Hexagonal Architecture folder structure and interface definition
Include a minimal executable example demonstrating dependency inversion or port/adapter pattern
Add validation checkpoints to the workflow (e.g., 'Verify no domain layer imports from infrastructure before proceeding')
Remove or significantly condense the 'Use this skill when' and 'Do not use this skill when' sections - these are obvious from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary sections like 'Use this skill when' and 'Do not use this skill when' which explain obvious use cases Claude could infer. The instructions themselves are lean. | 2 / 3 |
Actionability | The skill provides only high-level abstract guidance ('Clarify domain boundaries', 'Select an architecture pattern') without any concrete code examples, specific commands, or executable patterns. It describes what to do rather than showing how. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints or feedback loops. For complex architectural work involving migrations and refactoring, there should be explicit validation steps between phases. | 2 / 3 |
Progressive Disclosure | References to external resources exist (implementation-playbook.md) but the main content lacks substance - it's essentially just a pointer to another file without providing a useful quick-start or overview of the actual patterns. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- boisenoise/skills-collections
- Commit
5c5ae21
- 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.