ddd-evaluator

Name: ddd-evaluator
Availability: InStock
Author: mikecubed

Analyze source code for DDD tactical patterns, anti-patterns, and modeling quality.

Updated Mar 18, 2026

Search Tags:#architecture #ddd #domain-driven-design #code-review #antipatterns #evaluator

Ready to run

npx skills add https://github.com/mikecubed/agent-orchestration --skill ddd-evaluator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ddd-evaluator
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/patterns/skills/ddd-evaluator
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill ddd-evaluator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Evaluates codebases to determine conformance with Domain-Driven Design (DDD) practices, identifies tactical patterns such as Entities, Value Objects, Aggregates, and Repositories, and flags modeling quality issues like invariants enforcement and ubiquitous language gaps.

Core Features & Use Cases

Pattern analysis across the codebase to detect Entities, Value Objects, Aggregates, Repositories, and related anti-patterns.
Modeling quality assessment focusing on Ubiquitous Language consistency and invariants enforcement across the domain layer.
Actionable insights for architects and developers with health summaries and recommended refactors.

Quick Start

Provide the path to the codebase you want evaluated.

Frequently Asked Questions about ddd-evaluator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I evaluate my source code for Domain-Driven Design pattern conformance?▼

To evaluate source code for Domain-Driven Design conformance, you provide a codebase path to the evaluator, which then analyzes it to detect tactical DDD patterns, anti-patterns, and ubiquitous language gaps. It generates a report with health metrics.

What are common DDD anti-patterns to look for during a code review?▼

Common Domain-Driven Design anti-patterns identified during code review include missing invariants enforcement in entities, improper aggregate boundaries, and ubiquitous language gaps between code naming and domain language. The evaluator flags these modeling quality issues.

Can I use a DDD evaluator to check ubiquitous language consistency across my domain layer?▼

Yes, you can use a DDD evaluator to check ubiquitous language consistency by evaluating naming conventions against the domain language across the codebase. It identifies gaps where code structure diverges from domain terminology.

How do I validate aggregate and repository implementations in my codebase?▼

You validate aggregate and repository implementations by running a pattern analysis on the codebase, which classifies code structures against expected DDD tactical patterns and flags modeling quality issues. It produces actionable findings for architects.

Does DDD code analysis work for codebases across different domain types?▼

Yes, DDD code analysis is applicable to codebases across different domains. It validates entities, value objects, aggregates, and repositories by reading the code before classifying, ensuring domain-agnostic conformance evaluation.