quarkus-ddd

Scaffold and generate Domain-Driven Design components with Hexagonal Architecture in Quarkus projects. Use this skill whenever the user wants to create a new bounded context, add an aggregate, create value objects, scaffold a DDD module, add a new subdomain, or generate any DDD tactical pattern (aggregate, entity, value object, command, event, repository, service, endpoint) in a Quarkus/Java project. Also trigger when the user mentions 'hexagonal architecture', 'ports and adapters', or asks to add a new feature following DDD patterns.

Quality

89%

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

Quality

Content

86%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 body is highly actionable with executable code for every architectural layer and a clear generation order. Adding explicit compile/verify checkpoints after scaffolding would lift workflow clarity further.

Suggestions

Add an explicit validation/compile checkpoint after the scaffolding sequence (e.g., 'Run `mvn quarkus:dev` or `./mvnw compile` and confirm no errors before considering the scaffold complete').

Move the repeated source citations (Evans/Vernon/Cockburn) to a short references note or trim them to reduce tokens while keeping the authoritative signal.

Expand the Testing section beyond method-naming and a single unit-test stub to include an executable integration-test and REST Assured example matching the generated code.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code and minimal padding; the inline author citations (Evans, Vernon, Cockburn) add tokens without explaining basics Claude already knows, with only minor trimmable commentary.	4 / 5
Actionability	Fully executable, copy-paste ready Java code for every layer plus a naming table, package structure, generation order, and config — covering all common cases.	5 / 5
Workflow Clarity	Clear sequenced generation order (1–11) with an explicit critical ordering rule (persist in isolated transaction, publish AFTER persistence); validation checkpoints are implicit rather than explicit verify steps.	4 / 5
Progressive Disclosure	Single self-contained SKILL.md with well-organized sections, headers, tables, and code blocks; no external references are needed for this scope.	5 / 5
	Total	18 / 20 Passed

Description

92%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 is comprehensive and well-structured, clearly stating both capabilities and trigger conditions with concrete examples. Minor opportunity to add a few more natural synonyms for trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('create a new bounded context, add an aggregate, create value objects, scaffold a DDD module, add a new subdomain') with comprehensive coverage of DDD tactical patterns.	5 / 5
Completeness	Explicitly answers both 'what' (scaffold/generate DDD components in Quarkus) and 'when' ('Use this skill whenever...', 'Also trigger when...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural triggers ('create a new bounded context', 'hexagonal architecture', 'ports and adapters') but a few common user phrasings are not covered as synonyms.	4 / 5
Distinctiveness Conflict Risk	Clear niche combining Quarkus, DDD, and hexagonal architecture with distinct triggers, minimizing overlap with other skills.	5 / 5
	Total	19 / 20 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: jeremyrdavis/agentic-skills-for-quarkus
Path: skills/quarkus-ddd/SKILL.md
Commit: 393c86e

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