architecture-patterns

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

Quality

27%

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 names specific architecture patterns which gives it some identity, but it reads more like a course title than a skill description. It lacks concrete actions (what Claude will actually do), explicit trigger guidance (when to use it), and natural user-facing keywords. The use of marketing-style language ('Master proven') adds fluff without aiding skill selection.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about structuring a backend project, organizing code layers, implementing DDD patterns, or designing ports and adapters.'

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 infrastructure concerns.'

Include common keyword variations users might naturally say: 'DDD', 'onion architecture', 'ports and adapters', 'project structure', 'code organization', 'layered architecture'.

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 like 'structure project layers', 'define bounded contexts', or 'implement ports and adapters'.	2 / 3
Completeness	Describes what the skill covers (architecture patterns) but completely lacks any 'Use when...' clause or 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' portion is also somewhat vague about concrete actions, placing this at 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

22%

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 high-level outline that defers all substantive content to a non-existent referenced file. It lacks any concrete, actionable guidance — no code examples, no specific architectural templates, no decision frameworks, and no validation steps. The instructions read like a table of contents rather than a skill that Claude can execute.

Suggestions

Add concrete, executable examples for at least one architecture pattern (e.g., a Clean Architecture folder structure with sample code showing dependency direction and interface definitions).

Replace the vague 5-step workflow with specific, actionable steps including validation checkpoints — e.g., 'Verify no inner layer imports outer layer modules by running: grep -r "import.*infrastructure" domain/'.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential patterns, checklists, and templates directly in the skill.

Remove the generic 'Limitations' section and 'Use this skill when/Do not use' lists, replacing them with a concise decision matrix for choosing between Clean, Hexagonal, and DDD architectures.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add moderate value but are somewhat verbose. The 'Limitations' section contains generic boilerplate that Claude already knows. The instructions themselves are reasonably lean but could be tighter.	2 / 3
Actionability	The instructions are entirely abstract and high-level ('Clarify domain boundaries', 'Select an architecture pattern', 'Define module boundaries'). There are no concrete code examples, specific commands, architectural diagrams, or executable guidance. The skill describes rather than instructs.	1 / 3
Workflow Clarity	The five numbered steps are vague directives without concrete details, validation checkpoints, or feedback loops. Step 4 mentions 'validation checks' but doesn't specify what they are. There's no clear sequence showing how to actually implement any architecture pattern.	1 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed content, which is a good progressive disclosure pattern. However, no bundle files are provided, meaning the referenced file doesn't exist, making the reference a dead link. The main content is too thin to stand alone without the referenced resource.	2 / 3
	Total	6 / 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: 431bfad

Reviewed: 2 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.