domain-modeler
Extract domain model from user journeys/requirements. Reads user stories or journey docs, identifies business entities, relationships, attributes, and constraints, then produces structured data model documentation. Use when starting a new project, onboarding a new domain, or when user-journeys change significantly. Triggers: 'domain modeling', 'extract entities', 'data model from requirements', 'business abstraction', 'design data model', or when user-journeys.md is created/modified.
npx skills add majiayu000/claude-skill-registry --skill domain-modeler --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Domain Modeler Structured workflow for extracting a technology-agnostic domain model from user journeys and requirements documentation. Produces data model docs that serve as the single source of truth for both database schema and API design. > **Design Philosophy:** Domain-model-first. The domain model is derived from business requirements and is technology-agnostic. Both the database schema (SQLAlchemy models) and API contract (OpenAPI spec) are downstream consumers of this model — neither is the "source of truth." ## When to Use - **New project:** After writing user journeys, before any technical design - **Major requirements change:** When user journeys are significantly modified - **New bounded context:** When a new business domain is added to an existing project ## Inputs | Input | Required | Description | |-------|----------|-------------| | User journeys / stories | **Yes** | The primary requirements doc (e.g., `docs/user-journeys.md`) | | Existing specs | Optional | Any constraints, business rules, or technical requirements already documented | | Domain expert feedback | Optional | Clarifications from stakeholders on ambiguous business logic | ## Outputs | Output | Purpo
- When to Use
- Inputs
- Outputs
- Workflow
- Step 1: Extract Business Entities
- Step 2: Identify Relationships
- Step 3: Define Attributes
- Step 4: Define Constraints and Business Rules
- Step 5: Define CRUD Operations
- Step 6: Review and Validate
- Adapting for Different Projects
- Anti-Patterns
What does the domain-modeler skill do?
Extract domain model from user journeys/requirements. Reads user stories or journey docs, identifies business entities, relationships, attributes, and constraints, then produces structured data model documentation. Use when starting a new project, onboarding a new domain, or when user-journeys change significantly. Triggers: 'domain modeling', 'extract entities', 'data model from requirements', 'business abstraction', 'design data model', or when user-journeys.md is created/modified.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill domain-modeler --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.