db-conceptual-modeling
A conceptual modeling workflow to define domain entities and relationships before physical schema implementation.
Install
mkdir -p .claude/skills/db-conceptual-modeling && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11745" && unzip -o skill.zip -d .claude/skills/db-conceptual-modeling && rm skill.zipInstalls to .claude/skills/db-conceptual-modeling
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Conceptual data modeling workflow for domain entities, relationships, and lifecycle boundaries. Use when teams must align on domain meaning before logical/physical schema decisions; do not use for index-only or migration-only tasks.Key capabilities
- →Model domain meaning for data
- →Define entity relationships with ownership and lifecycle semantics
- →Capture key invariants and conflict rules
- →Resolve term collisions across bounded contexts
- →Document conceptual assumptions for logical design
How it works
The skill identifies core concepts, actors, and business events, then defines entity relationships, invariants, and conflict rules. It resolves term collisions and documents conceptual assumptions to guide logical design.
Inputs & outputs
When to use db-conceptual-modeling
- →Resolving ambiguity in domain entities
- →Defining business relationship semantics
- →Aligning team understanding on core data concepts
About this skill
DB Conceptual Modeling
Overview
Use this skill to model domain meaning first, so later schema decisions reflect business semantics rather than accidental implementation details.
Scope Boundaries
- Teams disagree on entity meaning or relationship semantics.
- A new domain area is being introduced.
- Existing schema complexity suggests conceptual drift.
Core Judgments
- Entity versus value concept boundaries.
- Cardinality and ownership semantics of relationships.
- Lifecycle states and temporal meaning.
- Bounded-context boundaries and shared concepts.
Practitioner Heuristics
- Model business invariants explicitly before table design.
- Use language from domain experts, not only engineering jargon.
- Treat temporal facts (history, validity windows) as first-class concepts.
- Avoid polymorphic catch-all concepts that hide domain distinctions.
Workflow
- Identify core concepts, actors, and business events.
- Define entity relationships with ownership and lifecycle semantics.
- Capture key invariants and conflict rules.
- Resolve term collisions across bounded contexts.
- Document conceptual assumptions that drive downstream logical design.
Common Failure Modes
- Conceptual model mirrors current tables instead of domain reality.
- Relationship ownership is left implicit, causing write conflicts later.
- State transitions are not modeled, forcing ad hoc status flags.
Failure Conditions
- Stop when core terms remain ambiguous across stakeholders.
- Stop when invariants cannot be expressed at conceptual level.
- Escalate when bounded context boundaries are politically unresolved.
When not to use it
- →For index-only tasks
- →For migration-only tasks
- →When the conceptual model mirrors current tables instead of domain reality
Limitations
- →The skill focuses on aligning domain meaning before logical/physical schema decisions.
- →It stops when core terms remain ambiguous across stakeholders.
- →It stops when invariants cannot be expressed at the conceptual level.
How it compares
This skill prioritizes modeling domain meaning to ensure schema decisions reflect business semantics, unlike approaches that might focus directly on logical or physical schema without conceptual alignment.
Compared to similar skills
db-conceptual-modeling side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| db-conceptual-modeling (this skill) | 0 | 5mo | No flags | Intermediate |
| d365-technical-plan-designer | 0 | 3mo | No flags | Advanced |
| postgresql-table-design | 30 | 4mo | No flags | Intermediate |
| agentdb-advanced-features | 7 | 9mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by KentoShimizu
View all by KentoShimizu →You might also like
d365-technical-plan-designer
williamzhou1216
D365 技术设计与实施计划编排专家（把 spec 转成 plan）
postgresql-table-design
wshobson
Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
agentdb-advanced-features
ruvnet
Master advanced AgentDB features including QUIC synchronization, multi-database management, custom distance metrics, hybrid search, and distributed systems integration. Use when building distributed AI systems, multi-agent coordination, or advanced vector search applications.
event-store-design
wshobson
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
database-design
davila7
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
database-schema-designer
davila7
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.