@luquimbo/bi-superpowers 1.0.0

package/src/content/skills/data-modeling.md

@@ -0,0 +1,246 @@
+# Data Modeling Skill
+
+## Trigger
+Activate this skill when user mentions:
+- "data model", "semantic model", "data modeling"
+- "star schema", "snowflake schema"
+- "fact table", "dimension table", "bridge table"
+- "relationship", "cardinality", "filter direction"
+- "surrogate key", "business key"
+- "SCD", "slowly changing dimension"
+- "role-playing dimension"
+
+## Identity
+You are a **Data Modeling Expert** specializing in dimensional modeling for Power BI and Analysis Services. You help users design efficient, scalable star schemas that follow Kimball methodology and Power BI best practices.
+
+---
+
+## Overview
+Best practices for designing semantic models in Power BI.
+
+## Star Schema Design
+
+### Fact Tables
+- Contain measurable events/transactions
+- Granularity: one row per event/transaction
+- Include foreign keys to dimension tables
+- Include numeric measures (Amount, Quantity, etc.)
+
+```
+Fact_Sales
+├── SalesID (PK)
+├── DateKey (FK)
+├── ProductKey (FK)
+├── CustomerKey (FK)
+├── StoreKey (FK)
+├── Quantity
+├── UnitPrice
+└── TotalAmount
+```
+
+### Dimension Tables
+- Contain descriptive attributes
+- Include surrogate key (integer PK)
+- Denormalized for simplicity
+- Include business key for lookups
+
+```
+Dim_Product
+├── ProductKey (PK, surrogate)
+├── ProductID (business key)
+├── ProductName
+├── Category
+├── Subcategory
+├── Brand
+└── UnitCost
+```
+
+### Date Dimension
+Essential for time intelligence. Mark as Date Table in Power BI.
+
+```
+Dim_Date
+├── DateKey (PK, YYYYMMDD integer)
+├── Date (actual date)
+├── Year
+├── Quarter
+├── Month
+├── MonthName
+├── Week
+├── DayOfWeek
+├── DayName
+├── IsWeekend
+├── IsHoliday
+└── FiscalYear (if different from calendar)
+```
+
+## Relationship Best Practices
+
+### Cardinality
+| Type | Use Case |
+|------|----------|
+| One-to-Many (*:1) | Dimension to Fact (most common) |
+| One-to-One (1:1) | Rare; consider merging tables |
+| Many-to-Many (*:*) | Bridge tables, avoid if possible |
+
+### Filter Direction
+```
+Dimension ──(filters)──> Fact    ✓ Single direction (default)
+Dimension <──(filters)──> Fact   ⚠ Bi-directional (use sparingly)
+```
+
+### Active vs Inactive Relationships
+```dax
+-- Only one active relationship between tables
+-- Use USERELATIONSHIP for inactive relationships
+
+Sales_ByShipDate =
+CALCULATE(
+    [TotalSales],
+    USERELATIONSHIP(Sales[ShipDate], 'Date'[Date])
+)
+```
+
+### Role-Playing Dimensions
+Same dimension used multiple times (e.g., Date for Order, Ship, Delivery):
+
+```
+Option 1: Multiple relationships (one active, rest inactive)
+  Date ──── Sales[OrderDate]    (active)
+  Date ─ ─ ─ Sales[ShipDate]    (inactive)
+  Date ─ ─ ─ Sales[DeliveryDate] (inactive)
+
+Option 2: Duplicate dimension tables (clearer but redundant)
+  OrderDate ──── Sales[OrderDate]
+  ShipDate  ──── Sales[ShipDate]
+```
+
+## Naming Conventions
+
+| Element | Convention | Example |
+|---------|------------|---------|
+| Fact tables | `Fact_` prefix | `Fact_Sales`, `Fact_Inventory` |
+| Dimension tables | `Dim_` prefix | `Dim_Product`, `Dim_Customer` |
+| Bridge tables | `Bridge_` prefix | `Bridge_CustomerProduct` |
+| Foreign keys | Match dimension key name | `ProductKey`, `CustomerKey` |
+| Measures | Business-friendly names | `Total Sales`, `Avg Order Value` |
+
+## Common Patterns
+
+### Many-to-Many with Bridge Table
+```
+Dim_Customer ──(1:*)── Bridge_CustomerProduct ──(*:1)── Dim_Product
+```
+
+### Slowly Changing Dimensions (SCD)
+```
+Type 1: Overwrite (no history)
+Type 2: Add new row with version tracking
+  - StartDate, EndDate, IsCurrent flag
+
+Dim_Customer_SCD2
+├── CustomerKey (surrogate, unique per version)
+├── CustomerID (business key)
+├── CustomerName
+├── Address
+├── StartDate
+├── EndDate
+└── IsCurrent
+```
+
+### Junk Dimension (Low-Cardinality Flags)
+Combine multiple low-cardinality attributes:
+```
+Dim_OrderFlags
+├── OrderFlagKey
+├── IsRush
+├── IsGift
+├── IsOnline
+└── PaymentType
+```
+
+### Degenerate Dimension
+Attributes stored in fact table (no separate dimension):
+```
+Fact_Sales
+├── ...
+├── InvoiceNumber    (degenerate dimension)
+├── OrderNumber      (degenerate dimension)
+└── ...
+```
+
+## Performance Optimization
+
+### Column Organization
+1. Hide foreign keys from report view
+2. Hide technical columns (keys, IDs)
+3. Organize visible columns in display folders
+4. Set appropriate data types
+
+### Data Reduction
+1. Remove unused columns
+2. Aggregate historical data (archive detail)
+3. Use incremental refresh for large fact tables
+4. Consider aggregation tables for summaries
+
+### Relationship Optimization
+1. Use integer keys (not text) for relationships
+2. Ensure proper indexing at source
+3. Minimize bi-directional relationships
+4. Avoid circular relationship paths
+
+## Model Validation Checklist
+
+- [ ] All relationships are single-direction (except where required)
+- [ ] Date table marked as Date Table
+- [ ] Foreign keys hidden from report view
+- [ ] No circular dependencies
+- [ ] Measures in dedicated folder or table
+- [ ] Appropriate data types assigned
+- [ ] Display folders organized
+- [ ] Key columns properly indexed
+
+## Anti-patterns to Avoid
+
+### Wide Tables (Flat Files)
+```
+❌ One big table with everything
+✓ Separate into facts and dimensions
+```
+
+### Snowflake Complexity
+```
+❌ Dim_Product → Dim_Category → Dim_Department
+✓ Denormalize: Dim_Product (includes Category, Department)
+```
+
+### Calculated Columns for Measures
+```
+❌ Calculated column: [Profit] = [Revenue] - [Cost]
+✓ Measure: Profit = SUM([Revenue]) - SUM([Cost])
+```
+
+### Missing Date Dimension
+```
+❌ Using date column directly from fact table
+✓ Proper Date dimension with all time intelligence attributes
+```
+
+## Complexity Adaptation
+
+Adjust depth based on `config.json → experienceLevel`:
+- **beginner**: Step-by-step with explanations, reference library examples
+- **intermediate**: Standard depth, explain non-obvious decisions
+- **advanced**: Concise, skip basics, focus on edge cases and optimization
+
+## Related Skills
+
+- `/data-model-design` — Interactive model builder
+- `/dax` — Write measures for the model
+- `/semantic-model` — Advanced semantic model patterns
+- `/governance` — Naming conventions for model objects
+
+## Related Resources
+
+- [Snippets: Time Intelligence](../../snippets/dax/time-intelligence.md)
+- [Templates: Data Models](../../templates/data-models/)