architecture-patterns

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-architecture-patterns/SKILL.md

Quality

Discovery

32%

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

The description reads more like a course title or marketing tagline than a functional skill description. While it names specific architecture patterns, it lacks concrete actions, explicit trigger guidance ('Use when...'), and natural keyword variations. The use of 'Master proven' is promotional fluff that doesn't help Claude decide when to select this skill.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about structuring a backend project, organizing code layers, implementing Clean Architecture, Hexagonal/Ports-and-Adapters, or Domain-Driven Design patterns.'

Replace vague outcome language ('maintainable, testable, scalable') with concrete actions like 'Structures project directories into domain/application/infrastructure layers, defines bounded contexts, implements repository patterns, and separates business logic from framework concerns.'

Remove promotional language ('Master proven') and add natural trigger term variations such as 'DDD', 'ports and adapters', 'onion architecture', 'project structure', 'code organization'.

Dimension	Reasoning	Score
Specificity	Names the domain (backend architecture) and some specific patterns (Clean Architecture, Hexagonal Architecture, DDD), but describes outcomes ('maintainable, testable, scalable') rather than concrete actions. No specific actions like 'structure project layers', 'define bounded contexts', or 'implement ports and adapters' are listed.	2 / 3
Completeness	Describes 'what' at a high level (architecture patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also vague enough to warrant a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Clean Architecture', 'Hexagonal Architecture', and 'Domain-Driven Design' that users might mention, but misses common variations like 'ports and adapters', 'onion architecture', 'DDD', 'layered architecture', 'project structure', or 'separation of concerns'.	2 / 3
Distinctiveness Conflict Risk	The mention of specific architecture patterns (Clean, Hexagonal, DDD) provides some distinctiveness, but 'backend architecture' is broad enough to overlap with general coding skills, project scaffolding skills, or design pattern skills.	2 / 3
	Total	7 / 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 is essentially a thin wrapper that delegates all substantive content to an external playbook. The instructions are vague and abstract, providing no concrete architectural patterns, code examples, or specific guidance despite the title promising mastery of Clean Architecture, Hexagonal Architecture, and DDD. The content fails to deliver actionable value on its own.

Suggestions

Add at least one concrete, executable code example showing a key pattern (e.g., a Clean Architecture folder structure with sample interface/implementation code)

Replace the abstract instruction steps with specific, actionable guidance — e.g., 'Define ports as interfaces in domain/ports/, implement adapters in infrastructure/adapters/'

Include a brief inline summary of each architecture pattern (Clean, Hexagonal, DDD) with decision criteria, so the skill provides value without requiring the external playbook

Trim the 'Use this skill when' / 'Do not use this skill when' sections to 2-3 bullets each to improve conciseness

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add moderate bloat — Claude doesn't need seven bullet points explaining when to use architecture patterns. The instructions themselves are reasonably lean but the overall content has unnecessary padding.	2 / 3
Actionability	The instructions are entirely abstract ('Clarify domain boundaries', 'Select an architecture pattern', 'Define module boundaries') with no concrete code, commands, specific examples, or executable guidance. Despite claiming to cover Clean Architecture, Hexagonal Architecture, and DDD, no actual patterns, code structures, or templates are provided inline.	1 / 3
Workflow Clarity	There is a numbered sequence of steps, but they are high-level and lack validation checkpoints. Step 4 mentions 'validation checks' but doesn't specify what they are. The workflow essentially delegates all detail to an external resource file.	2 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed content, which is appropriate progressive disclosure. However, the SKILL.md itself provides almost no substantive overview content — it's too thin to serve as a useful entry point, and the reference is mentioned redundantly in both Instructions and Resources sections.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 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: f1697b6

Reviewed: 3 days 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.