conceptual-data-modeling

Included with Lifetime

$97 forever

High-level conceptual data model — business entities + relationships in domain language. No technology or normalization concerns. Precedes logical + physical models.

General

What this skill does


# Conceptual Data Modeling

You produce a high-level conceptual data model — business-level entities, relationships, and key rules — in domain language. First of three modeling layers: conceptual → logical → physical.

## Core rules

- **Business language, not technical** — no columns, keys, types, indexes
- **Entities from the domain** — often aligned with bounded contexts (`ddd-strategic-modeling`)
- **Relationships cardinal** — 1:1, 1:N, M:N with meaning
- **Key business rules captured** — "customer must have verified email before order"
- **Independent of technology** — same conceptual model could run on SQL, NoSQL, graph

## Output per entity

| Field | Description |
|---|---|
| **Name** | Domain term |
| **Definition** | 1–2 sentences |
| **Identity** | What makes it unique (business-wise, not FK) |
| **Key attributes** | 3–5 most-important — no exhaustive list |
| **Business rules** | Invariants |

## Output per relationship

| Field | Description |
|---|---|
| **From → To** | Entities |
| **Cardinality** | 1:1 / 1:N / M:N |
| **Role name** | What this means ("customer places order") |
| **Optionality** | Required / optional |
| **Business rule** | Any conditions |

## Diagram

Mermaid ERD.

## Report

```markdown
# Conceptual Data Model: [Domain]

## Scope
[Domain, bounded context reference]

## Entities
[Per entity: name + definition + identity + key attributes + rules]

## Relationships
[Typed with cardinality + optionality + role]

## Business Rules
[Cross-entity invariants]

## ERD
[Mermaid]
```

## Failure behavior
- Mixed in technical details → strip to domain
- No domain context → interview
- mmdc failure → see mixin

Files: 1

Size: 1.9 KB

Complexity: 10/100

Category: General

Source: https://github.com/ssiertsema/claude-code-plugins/tree/main/conceptual-data-modeling/skills/conceptual-data-modeling

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts