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 an explicit 'Use when' clause and names specific architecture patterns, making it complete. However, it lacks concrete action verbs describing what deliverables or artifacts the skill produces, and could benefit from more natural trigger term variations that users commonly use when discussing these patterns.

Suggestions

Add more specific concrete actions like 'define bounded contexts, create layer boundaries, implement ports and adapters, model domain aggregates'

Include common trigger term variations users might say: 'DDD', 'ports and adapters', 'onion architecture', 'layered architecture', 'separation of concerns', 'dependency inversion'

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 ports and adapters, model aggregates'.	2 / 3
Completeness	Clearly answers both what (implement backend architecture patterns including specific named patterns) and when (explicit 'Use when architecting complex backend systems or refactoring existing applications for better maintainability').	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'Clean Architecture', 'Hexagonal Architecture', 'Domain-Driven Design', 'backend systems', and 'maintainability', but misses common variations users might say like 'ports and adapters', 'onion architecture', 'DDD', 'layered architecture', 'separation of concerns'.	2 / 3
Distinctiveness Conflict Risk	Reasonably specific to backend architecture patterns, but could overlap with general 'code refactoring' skills or 'software design' skills. The specific pattern names help distinguish it, but 'complex backend systems' is somewhat broad.	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 provides no concrete examples, code snippets, or specific techniques that Claude could immediately apply. The heavy reliance on external resources without any executable content in the main skill significantly limits its utility.

Suggestions

Add at least one concrete code example showing a Clean Architecture or Hexagonal Architecture structure (e.g., a directory layout with sample interface definitions)

Include a minimal executable pattern or template that demonstrates dependency inversion without requiring the external playbook

Add explicit validation checkpoints to the workflow, such as 'Verify no domain layer imports from infrastructure' with a specific check command or code snippet

Reduce or remove the 'Use this skill when' and 'Do not use this skill when' sections, as these are largely inferrable from the skill description

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary sections like the verbose 'Use this skill when' and 'Do not use this skill when' lists that explain obvious use cases Claude could infer. The instructions section is appropriately lean.	2 / 3
Actionability	The skill provides only vague, abstract guidance with no concrete code examples, specific commands, or executable patterns. Instructions like 'Select an architecture pattern' and 'Define module boundaries' describe rather than instruct, and all actual implementation details are deferred to an external file.	1 / 3
Workflow Clarity	The four-step workflow provides a basic sequence but lacks validation checkpoints and feedback loops. Step 4 mentions 'validation checks' but doesn't specify what they are or how to recover from failures. For complex architectural work, this is insufficient.	2 / 3
Progressive Disclosure	The skill appropriately references external resources with one-level-deep links, but the main content is too thin - it's essentially just a pointer to the playbook with almost no standalone value. The overview should contain more actionable quick-start content before deferring to detailed resources.	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: 3395991

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