db-conceptual-modeling
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.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9