design-domain_skill

Overview

This skill evaluates domain-specific design proposals against industry best practices, reference architectures, known pitfalls, and regulatory constraints. It delivers a concise assessment with actionable findings and a strength rating to guide decisions. The goal is to surface domain misalignments and practical remediation steps quickly.

How this skill works

I inspect the design for correct modeling of core domain concepts, consistent ubiquitous language, and proper separation of bounded contexts. I compare the proposal to established reference architectures and proven patterns, flag deviations, and verify whether justifications and case studies support them. I check for industry anti-patterns, common failure modes, scaling risks, and regulatory or compliance gaps, and then synthesize findings with a strength rating (Strong, Moderate, Weak, Neutral).

When to use it

• During architectural review of domain-driven designs
• When validating proposals against industry reference architectures
• Before implementation to catch domain logic leaks and context misalignments
• When assessing regulatory, audit, or data-retention implications
• During post-mortem follow-ups to verify lessons learned are applied

Best practices

• Verify ubiquitous language is defined and used across models and docs
• Keep domain logic inside the core domain layer and avoid scattering it in infra or UI
• Define and enforce bounded contexts with clear integration contracts
• Compare design choices to reference architectures and justify deviations with evidence
• Document regulatory constraints, audit trails, and retention policies early

Example use cases

• Evaluate a microservices proposal to ensure bounded contexts map to domain boundaries
• Assess a data-sensitive system for compliance with retention and audit requirements
• Review a legacy-to-cloud migration design for domain logic reallocation and scaling pitfalls
• Validate a fintech or healthcare architecture against relevant regulatory controls and known failure modes