logical-data-modeling
Logical data model — technology-agnostic detail with normalized entities, attributes, data types, keys (PK/FK/natural), constraints, cardinality, referential integrity. Applies normalization 1NF-3NF. Between conceptual and physical.
What this skill does
# Logical Data Modeling You produce a logical data model — normalized, detailed, but technology-agnostic. Between conceptual (business) and physical (DB-specific). ## Core rules - **Normalization target**: 3NF default (most practical); 2NF acceptable for certain analytical use cases - **Generic types**: use `string`, `integer`, `decimal(p,s)`, `boolean`, `date`, `timestamp`, `binary`, `text` — not vendor-specific - **Keys explicit**: PK / FK / natural / surrogate - **Constraints specified**: NOT NULL, UNIQUE, CHECK - **Referential integrity**: CASCADE / RESTRICT / SET NULL / NO ACTION per FK ## Normalization | Form | Rule | |---|---| | 1NF | Atomic values, no repeating groups | | 2NF | 1NF + no partial dependencies on composite key | | 3NF | 2NF + no transitive dependencies | | BCNF | 3NF + every determinant is a candidate key (stricter) | Default 3NF. De-normalize only in physical model per query pattern. ## Per entity | Field | Description | |---|---| | **Name** | Entity name | | **Description** | Purpose | | **Attributes** | Table: name / type / length / nullable / default / constraint | | **Primary key** | Natural or surrogate | | **Alternate keys** | Other unique constraints | | **Foreign keys** | To other entities with cascade rule | | **Indexes hinted** (for physical) | Expected access patterns | ## Per relationship | Field | Description | |---|---| | **Name** | Relationship name | | **Type** | Identifying / non-identifying / many-to-many | | **Cardinality** | 1:1 / 1:N / M:N with min/max | | **FK location** | Which side holds the FK | | **Cascade** | ON DELETE / ON UPDATE behavior | M:N relationships resolved via junction entities in logical model. ## Diagram Mermaid ERD with attributes + keys. ## Report ```markdown # Logical Data Model: [Domain] ## Scope [Conceptual reference, normalization target] ## Entities [Per entity: attributes + keys + constraints] ## Relationships [Typed with cardinality + FK + cascade] ## Normalization Verification [3NF checks per entity] ## Referential Integrity Rules [Cascade decisions per FK] ## Access Pattern Hints [For physical-model input] ## ERD ``` ## Failure behavior - Vendor-specific types mixed in → strip to generic - Un-normalized → apply normalization - No conceptual reference → light conceptual first - mmdc failure → see mixin
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.