CtrlK
BlogDocsLog inGet started
Tessl Logo

ddd-tactical-patterns

Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.

64

Quality

78%

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

The canonical home for this skill is ddd-tactical-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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.

A lean, well-structured skill body with an executable example and a verified one-level-deep reference. It is concise and well-organized, with only minor gaps in actionable step specificity and explicit validation checkpoints.

Suggestions

Add an explicit validation checkpoint to the workflow, e.g. 'After modeling aggregates, verify each invariant is enforced inside a method and cannot be bypassed.'

Tighten one or two instructions into concrete, copy-paste-style guidance (e.g. show the value-object construction-with-validation pattern as a second code snippet).

DimensionReasoningScore

Conciseness

The body is lean with short bulleted sections, a tight 5-step list, one compact executable example, and no padding or re-explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Provides concrete directives and an executable TypeScript example with real invariant checks, but the numbered instructions are high-level design guidance rather than copy-paste-ready steps, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 5-step sequenced workflow is present (invariants → value objects → domain behavior → events → repositories) with no destructive/batch operations needing validation caps, but it lacks explicit validation checkpoints.

4 / 5

Progressive Disclosure

Under 50 lines, well-organized into clear sections, with a single one-level-deep reference to references/tactical-checklist.md (verified to exist and contain relevant content); easy navigation.

5 / 5

Total

18

/

20

Passed

Description

70%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 clearly names the niche and its building blocks but lacks an explicit 'when to use' trigger clause, capping completeness. It is distinctive and uses good trigger terms for its domain.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when modeling domain logic, designing aggregate boundaries, or refactoring an anemic model into behavior-rich objects.'

Convert one or two building-block nouns into concrete verbs (e.g. 'design aggregates around invariants', 'emit domain events on state transitions') to push specificity toward 5.

Include a couple of natural shorthand trigger terms (e.g. 'anemic domain model', 'rich domain model') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists the DDD domain plus five concrete building blocks (entities, value objects, aggregates, repositories, domain events) and 'explicit invariants', but they are pattern nouns rather than concrete actions, so it falls below the comprehensive multi-action anchor at 5.

4 / 5

Completeness

Clearly answers 'what' (apply tactical patterns using the listed building blocks with explicit invariants) but the description field omits any 'Use when...' trigger clause, so per the cap it cannot exceed 3.

3 / 5

Trigger Term Quality

Includes natural terms a developer would say ('DDD tactical patterns', 'aggregates', 'value objects', 'domain events') with good coverage, but misses broader synonyms or shorthand variations that would warrant a 5.

4 / 5

Distinctiveness Conflict Risk

'DDD tactical patterns' is a clear niche with distinct, specific triggers (aggregates, value objects, domain events) and minimal overlap with other skills.

5 / 5

Total

16

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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