home / skills / shotaiuchi / dotclaude / design-domain

design-domain skill

safe

This skill evaluates design proposals against domain best practices, reference architectures, and regulatory considerations to ensure correct bounded contexts

npx playbooks add skill shotaiuchi/dotclaude --skill design-domain

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.9 KB

---
name: design-domain
description: >-
  Domain-specific design analysis. Apply when evaluating design proposals
  against industry best practices, reference architectures, known pitfalls,
  and domain-specific constraints.
user-invocable: false
---

# Domain Expert Perspective

Evaluate design proposals against industry knowledge and domain best practices.

## Analysis Checklist

### Domain Alignment
- Verify the design models core domain concepts accurately
- Check that ubiquitous language is used consistently across the proposal
- Assess whether bounded contexts are properly identified and separated
- Look for domain logic scattered outside the core domain layer
- Confirm that domain invariants are enforced at the appropriate level

### Reference Architectures
- Compare the proposal against established reference architectures
- Check for proven patterns applicable to this specific problem domain
- Verify that deviations from standard approaches are justified
- Assess whether case studies from similar systems support the design

### Industry Pitfalls
- Identify known anti-patterns specific to this domain
- Check for common failure modes seen in similar production systems
- Verify that lessons learned from public post-mortems are applied
- Look for scaling issues that are well-documented in the domain

### Regulatory & Compliance
- Check that data handling meets relevant regulatory requirements
- Verify audit trail and traceability requirements are addressed
- Assess whether retention and deletion policies are accounted for
- Look for jurisdiction-specific constraints that affect the design

## Output Format

Report findings with strength ratings:

| Strength | Description |
|----------|-------------|
| Strong | Well-aligned with domain best practices and standards |
| Moderate | Generally sound with some domain-specific gaps |
| Weak | Misaligned with established domain patterns or regulations |
| Neutral | Insufficient domain context to assess alignment |

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

FAQ

What output format do you provide?

I provide a concise findings report with concrete issues, recommended remediations, and a strength rating (Strong, Moderate, Weak, Neutral).

How deep is the compliance check?

I identify likely regulatory gaps and audit requirements but do not replace legal or full compliance audits; use my findings to focus deeper reviews.

Can you justify deviations from reference architectures?

Yes. I evaluate whether deviations are documented, supported by case studies or trade-off analysis, and whether risks are mitigated.