Skills domain-modeling

📦

domain-modeling

Name: domain-modeling
Author: mattpocock

Content revision r2 Safe ⚙️ External commands

Clarify Your Software Domain Model

Inconsistent domain terms create unclear requirements and fragile boundaries. This skill builds a shared glossary, maps contexts, and records consequential decisions.

Supports: Claude Codex Code(CC)

🥉 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "domain-modeling" from https://skillstore.io/skills/mattpocock-domain-modeling.md and its manifest at https://skillstore.io/api/skills/mattpocock-domain-modeling/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/mattpocock-domain-modeling.md Signed manifest GET /api/skills/mattpocock-domain-modeling/manifest Signed lockfile GET /api/skills/mattpocock-domain-modeling/lockfile

Test it

Using "domain-modeling". Clarify whether account means a customer organization or a login identity.

Expected outcome:

Use Customer for the purchasing organization and User for a person with login access. Avoid Account because it combines distinct concepts.

Using "domain-modeling". Map Ordering, Billing, and Fulfillment as separate business areas.

Expected outcome:

Ordering owns order placement and emits OrderPlaced.
Fulfillment consumes OrderPlaced and owns picking and shipment.
Billing consumes ShipmentDispatched and owns invoice generation.

Using "domain-modeling". Document why the system uses domain events instead of synchronous service calls.

Expected outcome:

Ordering and Billing communicate through domain events. This preserves context autonomy and accepts delayed consistency in exchange for reduced runtime coupling.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 19 static findings are false positives caused by Markdown backticks, fenced examples, and ordinary documentation prose. The skill contains no executable commands, malicious intent, or prompt injection.

Files scanned

184

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (13)

CONTEXT-FORMAT.md:49-50 CONTEXT-FORMAT.md:50-51 CONTEXT-FORMAT.md:51 SKILL.md:8 SKILL.md:14-22 SKILL.md:22-24 SKILL.md:24-26 SKILL.md:26-38 SKILL.md:38-40 SKILL.md:40 SKILL.md:46-62 SKILL.md:62-64 SKILL.md:64

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/mattpocock-domain-modeling/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/mattpocock-domain-modeling/security.svg)](https://skillstore.io/skills/mattpocock-domain-modeling?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/mattpocock-domain-modeling?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/mattpocock-domain-modeling/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/mattpocock-domain-modeling.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

mattpocock. (2026). domain-modeling security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/mattpocock-domain-modeling/audits/5

BibTeX citation

@techreport{mattpocock-mattpocock-domain-modeling-2026,
  author = {mattpocock},
  title = {domain-modeling security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/mattpocock-domain-modeling/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "domain-modeling security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "mattpocock"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/mattpocock-domain-modeling/audits/5"
identifiers:
  - type: other
    value: "skillstore:mattpocock-domain-modeling:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Align Product Language

Resolve conflicting business terms and create a concise shared glossary before refining requirements.

Define Service Boundaries

Map bounded contexts and describe their ownership and relationships during system design.

Preserve Decision Context

Record important architecture choices and their rationale in short, focused ADRs.

Try These Prompts

Start a Domain Glossary

Review these business terms: [terms]. Propose precise definitions, identify overlaps, and draft the first CONTEXT.md glossary.

Resolve Conflicting Terms

Compare our discussion with the existing CONTEXT.md. List conflicts, ask focused questions, and update resolved definitions.

Map Bounded Contexts

Analyze these modules and workflows: [details]. Propose bounded contexts, ownership boundaries, relationships, and terms that need clarification.

Stress-Test a Model and Record Decisions

Challenge this domain model with edge cases: [model]. Refine ambiguous concepts and draft ADRs only for decisions meeting all qualification criteria.

Best Practices

Validate each proposed definition against concrete business scenarios and repository evidence.
Keep glossary entries short, domain-specific, and free from implementation details.
Create ADRs only for difficult-to-reverse decisions with real alternatives and non-obvious rationale.

Avoid

Do not use one term for distinct concepts or several terms for the same concept.
Do not turn CONTEXT.md into a technical specification, scratchpad, or implementation guide.
Do not create ADRs for routine, reversible, or obvious choices.

Frequently Asked Questions

What does this skill create?

It creates or updates domain glossaries, context maps, and concise architecture decision records.

Does it support multiple bounded contexts?

Yes. It uses CONTEXT-MAP.md to locate contexts and describe their relationships.

Will it inspect existing code?

Yes. It can compare code behavior with stated domain rules and surface contradictions.

Does CONTEXT.md contain implementation details?

No. CONTEXT.md is a domain glossary and should exclude implementation decisions.

When does it create an ADR?

It proposes an ADR only for consequential, surprising decisions that resulted from a real trade-off.

Can it replace a domain expert?

No. It structures questions and documentation, but domain experts must validate business meaning.

Developer Details

Author

mattpocock

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/mattpocock/skills/tree/main/skills/engineering/domain-modeling/

Ref

ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006

Maintenance freshness

7/25/2026

Usage

8 downloads · 0 views

File structure

📄 ADR-FORMAT.md

📄 CONTEXT-FORMAT.md

📄 SKILL.md