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.

Quality

51%

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 ./.agent/skills/architecture-patterns/SKILL.md

Quality

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 explicit 'what' and 'when' clauses, and names specific architecture patterns. However, it lacks concrete action verbs describing deliverables and misses common trigger term variations that users might naturally use when seeking architecture guidance.

Suggestions

Add more specific concrete actions like 'define bounded contexts', 'create layer boundaries', 'structure dependency injection', 'separate domain from infrastructure'

Include common trigger term variations: 'DDD', 'ports and adapters', 'onion architecture', 'code organization', 'separation of concerns', 'layered architecture'

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 domain models', or 'structure dependency injection'.	2 / 3
Completeness	Clearly 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 applications for better maintainability') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'Clean Architecture', 'Hexagonal Architecture', 'Domain-Driven Design', 'backend systems', and 'refactoring', but misses common variations users might say like 'ports and adapters', 'onion architecture', 'DDD', 'layered architecture', 'separation of concerns', or 'code organization'.	2 / 3
Distinctiveness Conflict Risk	Reasonably specific to architecture patterns, but 'backend systems' and 'refactoring' are broad terms that could overlap with general coding skills, code review skills, or other backend-focused skills. The specific pattern names help but aren't sufficient to fully distinguish it.	2 / 3
	Total	9 / 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 primarily as a table of contents rather than actionable guidance. It correctly identifies when to use architecture patterns but fails to provide any concrete, executable content - no code examples, no specific patterns, no decision frameworks. All value is deferred to external resources, making the skill body itself nearly empty of actionable instruction.

Suggestions

Add at least one concrete code example showing a basic Clean Architecture or Hexagonal Architecture structure (e.g., folder layout, interface definition, dependency injection pattern)

Include a decision matrix or quick criteria for choosing between Clean Architecture, Hexagonal Architecture, and DDD based on project characteristics

Add specific validation checkpoints in the workflow (e.g., 'Verify no domain layer imports from infrastructure', 'Run dependency analysis tool')

Trim the 'Use this skill when' section to 2-3 key scenarios and remove the 'Do not use' section entirely

Dimension	Reasoning	Score
Conciseness	The skill is relatively brief but includes some unnecessary content like the extensive 'Use this skill when' and 'Do not use this skill when' lists that Claude could infer. The actual instructions are lean but the surrounding context adds bulk.	2 / 3
Actionability	The instructions are vague and abstract ('Clarify domain boundaries', 'Select an architecture pattern') with no concrete code, commands, or specific examples. Everything actionable is deferred to an external resource without any executable guidance in the skill itself.	1 / 3
Workflow Clarity	Steps are listed in sequence (1-4) but lack validation checkpoints, feedback loops, or specific criteria for decision points. 'Validation checks' are mentioned but not defined, and there's no guidance on what to do if validation fails.	2 / 3
Progressive Disclosure	References to external resources are present and one-level deep, but the skill body itself provides almost no substantive content - it's essentially just a pointer to implementation-playbook.md. The overview should contain more actionable quick-start content.	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: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

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