domain-modeling

Codify domain entities, business rules, and permissions using structured templates.

Updated Jan 23, 2026

Search Tags:#permissions #domain-driven design #relationships #entity #domain-modeling #value-objects #business-rules

Ready to run

npx skills add https://github.com/alexsandrocruz/DominusLeads --skill domain-modeling-alexsandrocruz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/alexsandrocruz/DominusLeads/tree/main/backend/Sapienza.Leads/.claude/skills/domain-modeling
Command: npx skills add https://github.com/alexsandrocruz/DominusLeads --skill domain-modeling-alexsandrocruz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Domain modeling resolves ambiguity in complex business domains by codifying entities, relationships, business rules, and permissions into a single shared model.

Core Features & Use Cases

Entity Definition Templates: Standardized layouts for creating domain entities with aggregates, value objects, and persistence mappings.
Rule & Permissions Documentation: Conventions for BR-XXX rules and role-based access controls, ensuring governance and traceability.
Impact Analysis & Documentation: Structured templates to assess the effects of domain changes on related entities, APIs, and permissions.
Use Case: When designing a new domain module, apply the domain-modeling skill to draft entity definitions, rules, and permissions before implementation.

Quick Start

Create a new domain module and outline entities using the provided templates.
Document the business rules (BR-XXX) and associated permissions.
Run an impact analysis to capture changes and ensure consistency across the model.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

How do I document domain entities and business rules consistently?▼

Define domain-driven design entities and relationships using standardized templates for aggregates, value objects, and persistence mappings to eliminate ambiguity in complex business domains.

What is the best way to structure permissions in a domain model?▼

Structure permissions in a domain model by codifying role-based access controls alongside business rules, ensuring governance and traceability for every entity definition and relationship within the shared model.

How do I run an impact analysis for domain model changes?▼

Run an impact analysis for domain model changes using structured templates to assess effects on related entities, APIs, and permissions, capturing modifications to maintain consistency across the documentation.

When do I need to use domain modeling for my software project?▼

You need domain modeling when complex business domains suffer from ambiguity, requiring codified entities, business rules, and permissions into a single shared model before implementation begins.

Does domain modeling work without external dependencies?▼

Yes, domain modeling works without external dependencies, providing explicit templates for entity definitions, rules, permissions, roles, and impact analysis to enable consistent governance directly within your codebase.