architecture-patterns

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

Quality

33%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/architecture-patterns/SKILL.md

Quality

Content

35%Scale 1-3

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 thin wrapper that defers all substantive content to an external playbook. The instructions are abstract and vague, offering no concrete code, specific patterns, or executable guidance. While the structure is reasonable and it correctly uses progressive disclosure, the SKILL.md body itself provides almost no actionable value.

Suggestions

Add at least one concrete, executable architecture example (e.g., a Clean Architecture folder structure with sample code showing dependency direction) directly in the SKILL.md.

Replace the abstract instruction steps with specific, actionable guidance — e.g., 'Define ports as interfaces in the domain layer, implement adapters in the infrastructure layer' with code snippets.

Add validation checkpoints to the workflow, such as 'Verify no domain layer imports from infrastructure layer using dependency analysis tools' or specific test commands.

Trim the 'Use this skill when' / 'Do not use this skill when' sections to 2-3 items each, as these are meta-instructions Claude can infer.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add moderate bloat — Claude doesn't need extensive lists of when to apply architectural patterns. The description is repeated in the heading. However, the instructions section itself is reasonably lean.	2 / 3
Actionability	The instructions are entirely abstract and vague — 'Clarify domain boundaries,' 'Select an architecture pattern,' 'Define module boundaries' are descriptions of what to do, not concrete executable guidance. There are no code examples, no specific commands, no concrete patterns shown, and the real content is deferred entirely to an external playbook.	1 / 3
Workflow Clarity	There is a numbered sequence of steps, but they lack validation checkpoints and are too abstract to guide a multi-step architectural process. Step 4 mentions 'validation checks' but doesn't specify what they are. The workflow is more of a high-level outline than an actionable sequence.	2 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed content, which is appropriate progressive disclosure. However, the SKILL.md itself provides almost no substantive overview content — it's essentially an empty shell pointing to one external file, making the overview too thin to be useful on its own.	2 / 3
	Total	7 / 12 Passed

Description

32%Scale 1-3

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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/architecture-patterns/SKILL.md
Commit: 7520423

Reviewed: ~11 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.