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

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

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 with no actionable content. It names important architecture patterns (Clean Architecture, Hexagonal, DDD) but provides zero concrete guidance, code examples, decision frameworks, or templates. The real value is deferred entirely to a referenced playbook file that doesn't exist in the bundle, making the skill non-functional in practice.

Suggestions

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

Replace the abstract instruction steps with a specific workflow: e.g., 'Step 1: Map domain entities → Step 2: Define ports/interfaces → Step 3: Implement adapters → Step 4: Validate dependency rules with this check...'

Include the `resources/implementation-playbook.md` bundle file or inline the most critical patterns and checklists directly in the SKILL.md so the skill is self-contained enough to be useful.

Remove the generic 'Limitations' boilerplate — Claude already knows to ask for clarification and not substitute for expert review.

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 the overall document has padding.	2 / 3
Actionability	The instructions are entirely abstract and vague — 'Clarify domain boundaries,' 'Select an architecture pattern,' 'Define module boundaries' — with no concrete code, commands, examples, or specific patterns. There is no executable guidance whatsoever; it describes rather than instructs.	1 / 3
Workflow Clarity	The five numbered steps are high-level abstractions without any concrete validation checkpoints, specific tools, or feedback loops. 'Provide migration steps and validation checks' is meta-instruction rather than an actual workflow. There is no clear sequence Claude could follow to produce a specific output.	1 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed content, which is a good structural choice. However, no bundle files are provided, meaning the referenced file doesn't exist, and the main SKILL.md itself lacks enough substantive content to serve as a useful overview — it's essentially an empty shell pointing to a missing resource.	2 / 3
	Total	6 / 12 Passed

Description

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 or marketing tagline than a functional skill description. It lacks concrete actions Claude would perform and entirely omits trigger guidance ('Use when...'), making it difficult for Claude to know when to select this skill over others.

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 ports from adapters.'

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, warranting a score of 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', 'layered architecture', 'DDD', 'bounded context', or 'project structure'.	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

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: sickn33/antigravity-awesome-skills
Commit: be20b37

Reviewed: 1 day 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.