architecture-patterns

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

Quality

51%

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

Quality

Content

42%Weight 40%Scale 1-5

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

The content is well-organized and lean in structure but offers only abstract, non-executable guidance and defers all concrete detail to a playbook file that is missing from the bundle. Validation is mentioned but never concretized into checkpoints.

Suggestions

Inline at least one concrete artifact (a sample module/dependency-rule diagram, an interface skeleton, or a migration checklist) so the skill is actionable without the missing playbook.

Restore or create `resources/implementation-playbook.md` so the deferred reference resolves; otherwise inline the essential patterns.

Add explicit validation checkpoints (e.g., 'Verify dependencies point inward before proceeding to step N') and a fix-retry loop for the migration step.

Remove the duplicated playbook reference and the verbatim description under the H1, and trim the DBOS-specific prose in step 5.

Dimension	Reasoning	Score
Conciseness	The body is short and sectioned, but it repeats the frontmatter description verbatim under the H1, duplicates the `resources/implementation-playbook.md` reference (Instructions and Resources), and step 5 is a verbose DBOS-specific plug ("persist workflow state, providing crash recovery without adding architectural complexity").	3 / 5
Actionability	The five instructions are high-level directives ("Clarify domain boundaries", "Select an architecture pattern that fits") with no concrete code, commands, or examples; the only detailed material is deferred to a referenced file that is not present.	2 / 5
Workflow Clarity	A numbered 5-step sequence is present, but validation appears only as an abstract mention in step 4 ("validation checks") with no explicit checkpoints or fix-retry feedback loops for migration/refactoring work.	3 / 5
Progressive Disclosure	Clean section structure with a well-signaled one-level reference, but the referenced file `resources/implementation-playbook.md` does not exist in the bundle (no resources/ directory), so navigation to the deferred detail is broken.	3 / 5
	Total	11 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 a clear, distinctive domain with recognizable trigger terms, but it is missing an explicit "Use when" clause and relies on abstract verbs rather than concrete capabilities. It is solid but capped on completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g., 'Use when designing new backend systems or refactoring a monolith into Clean/Hexagonal/DDD layers').

Replace abstract verbs ('Master', 'build') with concrete skill actions (e.g., 'Select, lay out, and document Clean/Hexagonal/DDD architectures').

Add common synonyms such as 'ports and adapters' and 'onion architecture' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("backend architecture patterns") and concrete patterns (Clean, Hexagonal, DDD) but the only verbs are abstract ("Master", "build maintainable, testable, and scalable systems") rather than concrete actions the skill performs.	3 / 5
Completeness	Has a clear "what" (master backend architecture patterns) but no "Use when..." trigger clause, so per the boundary guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	Strong natural keywords developers actually say ("Clean Architecture", "Hexagonal Architecture", "Domain-Driven Design"), though it omits common synonyms like "ports and adapters" or "onion architecture".	4 / 5
Distinctiveness Conflict Risk	The named patterns carve a clear niche, but the broad "backend architecture" scope and the many listed related skills (event-sourcing, saga, workflow-automation, dbos) signal minor overlap risk with sibling architecture skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/architecture-patterns/SKILL.md
Commit: debb2ec

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