CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clean-architecture

Provides implementation patterns for Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design in Java 21+ Spring Boot 3.5+ applications. Use when structuring layered architectures, separating domain logic from frameworks, implementing ports and adapters, creating entities/value objects/aggregates, or refactoring monolithic codebases for testability and maintainability.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A well-structured, highly actionable skill body with complete per-layer code examples and explicit architecture-compliance validation, but it is padded by triple-repeated best-practice lists, re-explanations of standard DDD concepts, and detailed content duplicated in the reference files. Consolidating the redundant sections and pushing duplicated detail into the references would make it both leaner and better disclosed.

Suggestions

Collapse 'Apply Best Practices', 'Best Practices', and 'Constraints and Warnings' into a single deduplicated section (or fold the pitfalls into their relevant layer sections) — the domain-purity, records-as-value-objects, factory-methods, typed-IDs, and ArchUnit guidance currently appears three times.

Move detail that duplicates the reference files (records/sealed classes/typed IDs from java-clean-architecture.md, JPA mapping/DI/transaction patterns from spring-boot-implementation.md) into those files and replace it with contextual links, e.g. under section 3: 'For sealed-class domain events and Result types, see references/java-clean-architecture.md'.

Fix the small code inconsistencies so examples are truly copy-paste ready: define `mapItems`/`OrderMapper` (or note them as assumed), and make Example 7's `new Money("10.00", EUR)` match Example 2's `Money(BigDecimal, Currency)` constructor.

DimensionReasoningScore

Conciseness

Section 1 re-explains standard DDD tactical concepts (entities, value objects, aggregates) Claude already knows, and the 'Apply Best Practices' list, 'Best Practices' section, and 'Constraints and Warnings' repeat the same guidance (domain purity, immutable records, rich domain model, factory methods, strongly-typed IDs, ArchUnit) nearly verbatim three times. Mostly useful content, but noticeably could be tightened, matching anchor 3.

3 / 5

Actionability

Concrete, near-complete executable Java code for every layer plus tests, a specific package tree, a runnable grep compliance check, and an ArchUnit snippet — mostly copy-paste ready with minor gaps: `mapItems`/`OrderMapper` are never defined, and `new Money("10.00", EUR)` in Example 7 does not compile against Example 2's `Money(BigDecimal, Currency)` record. Fits anchor 4 rather than the fully executable anchor 5.

4 / 5

Workflow Clarity

A clear numbered sequence (understand concepts → packages → domain → application → infrastructure → adapter → best practices → validate → tests) with explicit validation checkpoints (grep for Spring annotations in domain/, ArchUnit dependency tests, entity-exposure and transaction checks). Anchor 5 additionally requires error-recovery feedback loops ('if check fails, fix and re-run'), which are only implicit here, so anchor 4 is the best fit.

4 / 5

Progressive Disclosure

The two reference files exist, are one level deep, and are clearly listed in a References section, but the ~410-line body inlines detailed patterns (records for value objects, strongly-typed IDs, factory methods, JPA mapping, DI patterns) that are duplicated in `references/java-clean-architecture.md` and `references/spring-boot-implementation.md`, and the body never links to them contextually. Content that should be separate is inline, matching anchor 3.

3 / 5

Total

14

/

20

Passed

Description

91%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.

A strong description with explicit what and when clauses, concrete stack scoping, and comprehensive natural trigger terms including synonyms. Only minor improvements available: a slightly more concrete action framing and tighter 'refactoring' trigger scoping.

DimensionReasoningScore

Specificity

Lists several specific actions ('implementing ports and adapters, creating entities/value objects/aggregates, refactoring monolithic codebases') anchored to a concrete stack (Java 21+ Spring Boot 3.5+), matching anchor 4. The 'Provides implementation patterns for' framing is slightly more generic than anchor 5's fully concrete, comprehensive action list.

4 / 5

Completeness

Explicitly answers both what ('Provides implementation patterns for Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design in Java 21+ Spring Boot 3.5+ applications') and when ('Use when structuring layered architectures, separating domain logic from frameworks, implementing ports and adapters, creating entities/value objects/aggregates, or refactoring monolithic codebases') with concrete trigger phrases, exactly matching anchor 5.

5 / 5

Trigger Term Quality

Comprehensive natural terms users would actually say: 'Clean Architecture', 'Hexagonal Architecture (Ports & Adapters)', 'Domain-Driven Design', 'layered architectures', 'entities/value objects/aggregates', 'refactoring monolithic codebases'. Synonyms are included (Hexagonal = Ports & Adapters), matching anchor 5; no relevant natural term is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Java/Spring Boot layered architecture patterns) with distinct triggers and minimal conflict risk. Minor overlap: 'refactoring monolithic codebases for testability and maintainability' could also trigger a general refactoring or testing skill, fitting anchor 4 rather than the fully distinct anchor 5.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

giuseppe-trisciuoglio/developer-kit

Path

plugins/developer-kit-java/skills/clean-architecture/SKILL.md

Reviewed

Table of Contents

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.