CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ddd-aggregate-design

Design rich domain aggregates with proper encapsulation, domain events, and the Export pattern. Use when implementing DDD aggregates with event sourcing patterns.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./dotfiles/shared/.config/claude/forgoty-marketplace/plugins/software-engineering/skills/ddd-aggregate-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 lean and demonstrates its rules with concrete Go code, but it is undermined by a dangling reference: DDD-RULES.md is cited as holding 'all aggregate design rules' yet is not in the bundle, and the code examples rely on helpers only that file would define. There is also no explicit step sequence for designing an aggregate, leaving the workflow implicit.

Suggestions

Add the missing DDD-RULES.md to the skill bundle (e.g., under references/), or inline the essential rules into SKILL.md — the current link points to a file that does not exist, breaking the skill's progressive-disclosure structure.

Define or inline the supporting pieces used by the code examples (eventRegister, addEvent, applayer.NewEvent, ErrEmptyOrder) so the patterns are copy-paste ready rather than depending on the missing rules file.

Add a short ordered workflow for designing a new aggregate (e.g., 1. identify invariants, 2. define factory with validation, 3. add actionable methods that record events, 4. implement Export) to make the sequence explicit instead of implied by example ordering.

DimensionReasoningScore

Conciseness

The body is compact with no padding explaining concepts Claude already knows, and the Go examples are tight. It drops below 5 because the opening line ('Design and implement rich domain aggregates with proper encapsulation, domain events, and the Export pattern') and the 'When to Use This Skill' section substantially restate the frontmatter description, which could be trimmed.

4 / 5

Actionability

Three concrete, mostly executable Go examples (NewOrder factory, Ship method, Export) directly demonstrate the stated rules. It is not a 5 because the examples depend on undefined helpers (eventRegister, addEvent, applayer.NewEvent) and the 'read DDD-RULES.md for all aggregate design rules' pointer leads to a file that is missing from the bundle, leaving minor gaps.

4 / 5

Workflow Clarity

The five core rules and ordered pattern examples imply a rough design sequence (factory → actions → events → Export), but there is no explicit sequenced workflow or checkpoints for designing an aggregate (e.g., identify invariants first, then factory, then methods). This matches the 'sequence present but checkpoints missing or implicit' anchor rather than the well-checkpointed anchor 4.

3 / 5

Progressive Disclosure

The body defers all detailed rules to '[DDD-RULES.md](DDD-RULES.md)' — clearly signaled and one level deep — but no references/, scripts/, or assets/ directories exist and DDD-RULES.md is absent from the bundle, so the referenced path is broken and the deferred content is unreachable. Effectively the skill's substance lives in a file that isn't shipped, which matches the anchor-2 failure ('content that clearly belongs in separate files is inlined; or references are buried' — here the inverse: referenced but missing) rather than a 3 where structure is merely suboptimal.

2 / 5

Total

13

/

20

Passed

Description

78%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, focused description that states concrete capabilities and includes an explicit 'Use when' clause in third person. The main gap is that the trigger list could enumerate more user-natural synonyms (aggregate root, anemic model) to improve both completeness and trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Design rich domain aggregates with proper encapsulation, domain events, and the Export pattern' — naming the domain plus three specific capabilities. It falls short of a 5 because phrases like 'proper encapsulation' and 'rich' are adjectival rather than fully enumerated concrete actions, but it clearly exceeds the 1–2-action level of a 3.

4 / 5

Completeness

It answers both parts: the 'what' ('Design rich domain aggregates with proper encapsulation, domain events, and the Export pattern') and an explicit 'when' ('Use when implementing DDD aggregates with event sourcing patterns'). The 'when' clause could be more specific with concrete user-mentionable triggers (e.g., 'when the user mentions aggregate roots, anemic models, or domain events'), which is exactly the anchor-4 shape rather than 5.

4 / 5

Trigger Term Quality

Natural trigger terms are present — 'DDD aggregates', 'domain events', 'event sourcing', 'encapsulation', 'Export pattern' — which a user working in this domain would plausibly say. Coverage is good but misses common variations users might use, such as 'anemic domain model', 'aggregate root', or 'tactical design', keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and narrowly defined — DDD aggregate design with event sourcing and a distinctive 'Export pattern' — so it is unlikely to trigger for unrelated skills. It matches the 'clear niche with distinct triggers; minimal conflict risk' anchor; at most there is marginal overlap with a generic event-sourcing skill, which is not enough to drop to 4.

5 / 5

Total

17

/

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

forgoty/dotfiles

Path

dotfiles/shared/.config/claude/forgoty-marketplace/plugins/software-engineering/skills/ddd-aggregate-design/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.