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

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/architecture-patterns/SKILL.md

The canonical home for this skill is jbvc/architecture-patterns

Quality

Content

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is admirably concise but lacks actionable guidance, validation steps, and a real reference bundle, so it currently over-promises detail that is not present. Either inline concrete decision criteria/templates or actually ship the referenced playbook.

Suggestions

Add concrete, executable guidance inline (e.g., a dependency-rule checklist, a sample module-boundary template, or decision criteria for choosing Clean vs Hexagonal vs DDD) instead of abstract verbs.

Create the referenced resources/implementation-playbook.md (or correct the path) so the progressive-disclosure pointer resolves to a real file.

Insert explicit validation checkpoints in the workflow (e.g., verify dependency direction, confirm domain boundaries against requirements) with a fix-and-retry loop for refactors.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no explanatory padding about what the patterns are or how they work; every line earns its place.	3 / 3
Actionability	The numbered instructions ('Clarify domain boundaries', 'Select an architecture pattern that fits', 'Define module boundaries') are abstract and describe intent rather than giving concrete, executable guidance, with no inline templates, decision criteria, or code.	1 / 3
Workflow Clarity	Four sequenced steps are listed, but there are no validation checkpoints or feedback loops for a risky refactor/migration task, which the rubric notes should cap this dimension at 2.	2 / 3
Progressive Disclosure	The body twice points to 'resources/implementation-playbook.md', but no resources directory or file exists, so the offloaded detail is unreachable and the reference is broken.	1 / 3
	Total	7 / 12 Passed

Description

75%

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 is well-formed with an explicit trigger clause and a clear, distinct niche, but its trigger-term coverage and action specificity are good rather than excellent. Adding the specific pattern names a user would mention and a second concrete action would round it out.

Suggestions

Surface the pattern names users actually say in the trigger clause, e.g. 'Use when the user mentions Clean Architecture, Hexagonal Architecture, ports and adapters, or DDD'.

Add at least one more concrete action to the capability list (e.g. 'define module boundaries and dependency rules') to lift specificity toward a 3.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ('Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design') but stops at a single generic action rather than listing multiple specific actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	Explicitly states what the skill does and follows with a clear 'Use when architecting complex backend systems or refactoring existing applications for better maintainability' trigger, satisfying both what and when.	3 / 3
Trigger Term Quality	Includes natural terms ('architecting complex backend systems', 'refactoring existing applications', 'maintainability') but omits common phrasings a user would actually say such as 'clean architecture', 'hexagonal', 'ports and adapters', or 'DDD', leaving gaps that keep it below 3.	2 / 3
Distinctiveness Conflict Risk	The niche is clearly scoped to backend architecture patterns with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/architecture-patterns/SKILL.md
Commit: e63f7dd

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