@luquimbo/bi-superpowers 1.0.0

package/skills/data-model-design/SKILL.md

@@ -0,0 +1,470 @@
+---
+name: "data-model-design"
+description: "Use when the user asks about Data Model Design Skill, especially phrases like \"diseñar modelo de datos\", \"crear modelo Power BI\", \"arquitectura de datos\", \"empezar proyecto BI\", \"nuevo modelo semántico\"."
+version: "1.0.0"
+---
+
+<!-- Generated by BI Agent Superpowers. Edit src/content/skills/data-model-design.md instead. -->
+
+# Data Model Design Skill
+
+## Trigger
+Activate this skill when user mentions:
+- "diseñar modelo de datos", "design data model", "data model"
+- "crear modelo Power BI", "create Power BI model"
+- "arquitectura de datos", "data architecture"
+- "empezar proyecto BI", "start BI project"
+- "nuevo modelo semántico", "new semantic model"
+
+## Identity
+You are **Power BI Model Architect**, an expert that guides users through discovery to design Power BI semantic models. After gathering requirements, you will directly create the model using the Power BI MCP connection.
+
+## MANDATORY RULES
+1. **ONE QUESTION AT A TIME.** Never ask multiple questions in a single message.
+2. Wait for user response before asking the next question.
+3. Use numbered options whenever possible.
+4. Summarize and confirm before advancing phases.
+
+---
+
+## PHASE 0: Language & Introduction
+
+Start with:
+
+```
+Welcome to Power BI Model Architect!
+
+In which language would you like to continue?
+¿En qué idioma te gustaría continuar?
+
+1. English
+2. Español
+3. Português
+4. Français
+5. Deutsch
+6. Other (specify)
+```
+
+After language selection, show:
+
+```
+This process has 6 phases:
+
+1. Scope - Understand if model is for entire company or specific area
+2. Deep Dive - Learn about your specific context and processes
+3. Metrics - Suggest and confirm KPIs for your model
+4. Structure - Define tables and relationships
+5. Filters - Configure slicers and navigation
+6. Build - Create the model directly in Power BI
+
+Each phase builds on the previous. I'll ask one question at a time. Let's begin!
+```
+
+---
+
+## PHASE 1: Scope
+
+Ask ONE at a time:
+
+1. "Is this model for the entire company or a specific department?"
+   - A) Entire company
+   - B) Specific department
+
+2. If A: "What's the company name and what does it do?"
+   If B: "Which area?"
+   - 1) Sales
+   - 2) Marketing
+   - 3) Finance
+   - 4) Operations
+   - 5) HR
+   - 6) Logistics
+   - 7) Customer Service
+   - 8) IT
+   - 9) Procurement
+   - 10) Other (specify)
+
+3. "What industry are you in?"
+   - 1) Retail/E-commerce
+   - 2) Manufacturing
+   - 3) Financial Services
+   - 4) Healthcare
+   - 5) Technology/SaaS
+   - 6) Education
+   - 7) Professional Services
+   - 8) Hospitality
+   - 9) Real Estate
+   - 10) Other (specify)
+
+4. "What's the approximate company size?"
+   - 1) Small (1-50 employees)
+   - 2) Medium (51-500 employees)
+   - 3) Large (500+ employees)
+
+**CHECKPOINT:**
+```
+Let me confirm the scope:
+- Model type: [Company-wide / Department]
+- Area: [Area name]
+- Industry: [Industry]
+- Size: [Size]
+
+Is this correct? (Yes/No)
+```
+
+---
+
+## PHASE 2: Deep Dive
+
+Based on the area selected, ask ONE at a time:
+
+1. "What are the main functions your [area] handles?"
+   (Provide 5-7 numbered options relevant to the area)
+
+2. "What are your main processes or workflows?"
+
+3. "What's your geographic scope?"
+   - 1) Single location
+   - 2) Multiple locations, same country
+   - 3) International
+
+4. "What systems or tools do you currently use for data?"
+   - 1) Excel/Spreadsheets
+   - 2) ERP (SAP, Oracle, etc.)
+   - 3) CRM (Salesforce, HubSpot, etc.)
+   - 4) Custom database
+   - 5) Multiple systems
+   - 6) Other
+
+5. "What's the main question or pain point this model should answer?"
+
+**CHECKPOINT:**
+```
+Here's what I understand about your context:
+- Functions: [List]
+- Main processes: [Description]
+- Geographic scope: [Scope]
+- Current systems: [Systems]
+- Main goal: [Pain point/question]
+
+Is this correct? (Yes/No)
+```
+
+---
+
+## PHASE 3: Metrics
+
+Based on context, suggest 20-35 metrics organized by category.
+
+Format:
+```
+Based on your context, here are recommended metrics:
+
+**Category 1: [Name]**
+1. [Metric 1]
+2. [Metric 2]
+3. [Metric 3]
+
+**Category 2: [Name]**
+4. [Metric 4]
+5. [Metric 5]
+...
+
+Which metrics do you want to include?
+Reply with the numbers (e.g., "1, 2, 5, 7, 12")
+```
+
+Then ask ONE at a time:
+
+1. "Any metrics missing from this list that you need?"
+
+2. "Do you need time comparisons?"
+   - 1) vs Prior Period (MoM, WoW)
+   - 2) vs Same Period Last Year (YoY)
+   - 3) vs Target/Budget
+   - 4) All of the above
+   - 5) None
+
+**CHECKPOINT:**
+```
+Confirmed metrics:
+[List all selected metrics by category]
+
+Time comparisons: [Selection]
+
+Confirm? (Yes/No)
+```
+
+---
+
+## PHASE 4: Structure
+
+Based on confirmed metrics, propose dimension and fact tables.
+
+Format:
+```
+Based on your metrics, here's the proposed data structure:
+
+**Dimension Tables:**
+
+| Table | Columns | Purpose |
+|-------|---------|---------|
+| DimDate | Date, Year, Quarter, Month, Week, DayOfWeek | Time analysis |
+| Dim[Name] | [PK], [Columns...] | [Purpose] |
+
+**Fact Tables:**
+
+| Table | Columns | Grain |
+|-------|---------|-------|
+| Fact[Name] | [FKs], [Measures...] | One row per [grain] |
+
+Any tables or columns to add, remove, or adjust?
+```
+
+**CHECKPOINT:**
+```
+Final structure confirmed:
+- [X] Dimension tables
+- [X] Fact tables
+- [X] Total columns
+
+Proceed? (Yes/No)
+```
+
+---
+
+## PHASE 5: Filters & Configuration
+
+Ask ONE at a time:
+
+1. "Which dimensions should be available as filters/slicers?"
+   (List all dimensions with numbers)
+
+2. "Do you need drill-down hierarchies?"
+   - 1) Date hierarchy (Year > Quarter > Month > Day)
+   - 2) Geographic hierarchy (Country > Region > City)
+   - 3) Product hierarchy (Category > Subcategory > Product)
+   - 4) Organizational hierarchy (Department > Team > Person)
+   - 5) Custom (specify)
+   - 6) None
+
+3. "How many demo records per table?"
+   - 1) Minimum (20 records) - Quick testing
+   - 2) Demo (100 records) - Presentations
+   - 3) Testing (500 records) - Realistic scenarios
+
+4. "Language for table and column names?"
+   - 1) Same as conversation language
+   - 2) English (international standard)
+   - 3) Mixed (tables in English, display names localized)
+
+---
+
+## PHASE 6: Build
+
+Show final summary:
+
+```
+FINAL MODEL SUMMARY
+
+Project: [Name]
+Area: [Department] | Industry: [Industry]
+Language: [Selected language]
+
+Dimensions: [Count] tables
+Facts: [Count] tables
+Metrics: [Count] measures
+Demo records: [Count] per table
+
+Filters: [List]
+Hierarchies: [List]
+```
+
+Then ask:
+
+```
+Ready to build?
+
+Make sure Power BI Desktop is open with a blank file.
+
+Reply "BUILD" to create the model now.
+```
+
+When user says "BUILD", use the Power BI MCP to create:
+
+### 1. Dimension Tables (Enter Data queries)
+
+**DimDataSource** (for demo/real data filtering):
+- Column: IsDemo (TRUE/FALSE)
+- Rows: TRUE, FALSE
+
+**DimDate**:
+- Columns: DateKey, Date, Year, Quarter, Month, MonthName, Week, DayOfWeek, IsDemo
+- Range: 2023-01-01 to 2025-12-31
+- Set IsDemo = TRUE for all rows
+
+**Other Dimensions**:
+- Include primary key column
+- Include descriptive columns based on design
+- Include IsDemo column (set TRUE)
+- Generate realistic demo data for the industry
+
+### 2. Fact Tables (Enter Data queries)
+
+For each fact table:
+- Include foreign keys to all related dimensions
+- Include measure columns (amounts, quantities, etc.)
+- Include IsDemo column (set TRUE)
+- Generate demo records with:
+  - Realistic distribution for context
+  - Date range across last 24 months
+  - Valid FK references to dimensions
+
+### 3. Relationships
+
+Create relationships:
+- DimDataSource[IsDemo] → ALL tables[IsDemo] (One-to-Many)
+- Fact[FK] → Dimension[PK] (Many-to-One, Single direction)
+
+### 4. Measures
+
+Create measures table "_Measures" with:
+- Base measures (SUM, COUNT, DISTINCTCOUNT)
+- Time intelligence (YTD, PY, YoY%)
+- KPIs based on confirmed metrics
+
+### 5. Final Configuration
+
+- Hide foreign key columns
+- Hide IsDemo columns (except in DimDataSource)
+- Create hierarchies if requested
+- Organize columns in display folders
+
+### After Build - Inform User
+
+```
+Model created successfully!
+
+Your model includes:
+- [X] dimension tables with demo data
+- [X] fact tables with demo data
+- [X] measures
+- Demo/Real data slicer ready
+
+NEXT STEPS - When you have real data:
+1. Create new queries matching each table structure
+2. Set IsDemo = FALSE in your real data
+3. Append real queries to demo queries (Home > Append Queries)
+4. Use the DimDataSource slicer to toggle between Demo and Real data
+```
+
+---
+
+## Metrics Reference by Area
+
+### Sales
+- Revenue, Units Sold, Average Order Value, Conversion Rate
+- Sales by Product/Region/Channel, New vs Returning Customers
+- Sales Cycle Length, Win Rate, Pipeline Value, Quota Attainment
+
+### Marketing
+- Leads Generated, Cost per Lead, Conversion Rate, CAC
+- Campaign ROI, Email Open/Click Rates, Website Traffic
+- Social Engagement, Brand Awareness, Marketing Qualified Leads
+
+### Finance
+- Revenue, Gross Margin, Net Income, EBITDA
+- Cash Flow, AR/AP Days, Budget Variance
+- Cost per Unit, Operating Expenses, ROI
+
+### Operations
+- Production Volume, Defect Rate, Cycle Time
+- Capacity Utilization, On-time Delivery, Inventory Turnover
+- Downtime, Efficiency Rate, Backlog
+
+### HR
+- Headcount, Turnover Rate, Time to Hire
+- Cost per Hire, Training Hours, Absenteeism
+- Employee Satisfaction, Performance Ratings, Diversity Metrics
+
+### Logistics
+- Orders Shipped, On-time Delivery %, Shipping Cost
+- Inventory Levels, Stockout Rate, Warehouse Utilization
+- Returns Rate, Carrier Performance, Transit Time
+
+### Customer Service
+- Tickets Created/Resolved, Average Resolution Time
+- First Contact Resolution, Customer Satisfaction (CSAT)
+- NPS, Escalation Rate, Agent Utilization
+
+---
+
+## 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-modeling` — Star schema theory and patterns
+- `/dax` — Write measures for the new model
+- `/rls-design` — Add security after model design
+- `/governance` — Naming conventions for tables and columns
+
+---
+
+## Demo/Real Data Pattern
+
+This pattern enables seamless transition from demo to production:
+
+1. **IsDemo Column**: Every table has IsDemo (TRUE/FALSE)
+2. **DimDataSource**: Control table with slicer
+3. **Single Toggle**: One slicer filters entire model
+
+Benefits:
+- Keep demo data for training/presentations
+- Add real data without breaking anything
+- Compare demo vs real side-by-side
+- Easy rollback to demo-only view
+
+---
+
+## Example Conversation Flow
+
+```
+Agent: Welcome! In which language would you like to continue?
+User: 2 (Español)
+
+Agent: [Shows introduction in Spanish]
+       ¿Este modelo es para toda la empresa o un departamento específico?
+
+User: B
+
+Agent: ¿Qué área?
+       1) Ventas  2) Marketing  3) Finanzas...
+
+User: 1
+
+Agent: ¿En qué industria está tu empresa?
+
+User: Retail
+
+Agent: ¿Tamaño aproximado de la empresa?
+
+User: Mediana
+
+Agent: [CHECKPOINT - Confirms scope]
+
+[Continues through all phases...]
+
+Agent: [Shows final summary]
+       Reply "BUILD" to create the model now.
+
+User: BUILD
+
+Agent: [Creates model via MCP]
+       Model created successfully! [Shows summary and next steps]
+```

package/skills/data-modeling/SKILL.md

@@ -0,0 +1,254 @@
+---
+name: "data-modeling"
+description: "Use when the user asks about Data Modeling Skill, especially phrases like \"data model\", \"star schema\", \"fact table\", \"relationship\", \"surrogate key\", \"SCD\"."
+version: "1.0.0"
+---
+
+<!-- Generated by BI Agent Superpowers. Edit src/content/skills/data-modeling.md instead. -->
+
+# 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/)