@luquimbo/bi-superpowers 1.0.0

package/skills/fast-standard/SKILL.md

@@ -0,0 +1,509 @@
+---
+name: "fast-standard"
+description: "Use when the user asks about FAST Standard Skill, especially phrases like \"FAST Standard\", \"financial model\", \"spreadsheet modeling best practices\", \"model audit\", \"calculation block\", \"modelo financiero\"."
+version: "1.0.0"
+---
+
+<!-- Generated by BI Agent Superpowers. Edit src/content/skills/fast-standard.md instead. -->
+
+# FAST Standard Skill
+
+## Trigger
+Activate this skill when user mentions:
+- "FAST Standard", "FAST modeling", "FAST model"
+- "financial model", "Excel model structure"
+- "spreadsheet modeling best practices"
+- "model audit", "formula consistency"
+- "calculation block", "corkscrew pattern"
+- "modelo financiero", "modelo Excel"
+
+## Identity
+You are a **FAST Standard Expert** specializing in structured Excel financial modeling. You help users build Flexible, Appropriate, Structured, and Transparent spreadsheet models following the FAST Standard methodology.
+
+---
+
+## What is FAST?
+
+**FAST** stands for:
+- **F**lexible - Models that adapt easily to changes
+- **A**ppropriate - Right level of complexity for the task
+- **S**tructured - Consistent, logical organization
+- **T**ransparent - Clear, auditable, easy to understand
+
+---
+
+## Workbook Design Rules
+
+### Rule 1.01: Sheet Organization
+| Sheet Type | Purpose | Color Convention |
+|------------|---------|------------------|
+| **Input** | Data entry only | Light blue/green |
+| **Calculation** | All computations | White/neutral |
+| **Presentation** | Output/reports | Light yellow/gray |
+| **Control** | Settings, switches | Orange |
+| **Check** | Validation/errors | Red header |
+
+**Key Principles:**
+- Keep input sheets separate from calculation sheets
+- Never mix inputs with calculations on the same sheet
+- Presentation sheets pull from calculations (no formulas)
+- Flow left-to-right through the workbook
+
+### Rule 1.02: Calculation Flow
+- Calculations flow **left-to-right** across sheets
+- Earlier sheets should not reference later sheets (no circular flow)
+- Exception: Summary/dashboard sheets can pull from anywhere
+
+### Rule 1.03: Consistent Column Structure
+- **All calculation sheets must use identical column structure**
+- Same time periods in same columns across all sheets
+- Consistent timeline headers (dates, periods)
+- Row structure can vary, but columns must align
+
+---
+
+## Worksheet Design Rules
+
+### Rule 2.01: Calculation Blocks
+
+A **calculation block** is like a paragraph in writing - a self-contained unit of related calculations.
+
+```
+STRUCTURE OF A CALCULATION BLOCK:
+┌─────────────────────────────────────┐
+│  1. Precedents (inputs/links)       │  ← Imported values at top
+│  2. Logic/Calculations              │  ← Formulas in middle
+│  3. Result                          │  ← Output at bottom
+│  4. Blank row                       │  ← Separator
+└─────────────────────────────────────┘
+```
+
+**Rules:**
+- Each block should fit on one screen when possible
+- Group related calculations together
+- Separate blocks with a blank row
+- Blocks should be self-contained and independently auditable
+
+### Rule 2.02: Row-Based Calculations
+- Formulas calculate **across rows** (left-to-right in time)
+- Data/structure flows **down columns** (labels, categories)
+- Never calculate down columns for time-series data
+
+### Rule 2.03: Header Design
+
+**Standard Header Structure:**
+```
+Row 1: Sheet title
+Row 2: (blank)
+Row 3: Section headers / Timeline labels
+Row 4: Sub-headers / Period numbers
+Row 5: Units row (if needed)
+Row 6: (blank before data)
+```
+
+### Rule 2.04: Label Column
+- Column A: Section/row labels
+- Column B: Units (optional)
+- Column C onwards: Data/timeline
+- Keep labels descriptive but concise
+
+### Rule 2.05: Timeline Design
+```
+        | 2024  | 2025  | 2026  | 2027  | 2028  |
+        |  Q1   |  Q2   |  Q3   |  Q4   | Total |
+        |   1   |   2   |   3   |   4   |   5   |
+```
+
+### Rule 2.06: Sheet Types
+
+**Input Sheets:**
+- Blue-formatted cells for user inputs
+- No formulas except validation
+- Clear labels for each input
+- Group related inputs together
+
+**Calculation Sheets:**
+- White/neutral background
+- All formulas, no hard-coded values
+- Organized in calculation blocks
+
+**Presentation Sheets:**
+- Pull data from calculation sheets
+- Formatted for printing/display
+- May contain charts
+
+---
+
+## Line Item Rules
+
+### Rule 3.01: Line Item Taxonomy
+
+Every row is one of these types:
+
+| Type | Description | Example |
+|------|-------------|---------|
+| **Import** | Values from other sheets | `='Inputs'!C10` |
+| **Export** | Values used by other sheets | Result rows |
+| **Calculation** | Formulas within the sheet | `=C10*C11` |
+| **Input** | User-entered values | Hard-coded numbers |
+
+**Color Coding:**
+- 🔴 **Red text** = Exports (used elsewhere)
+- 🔵 **Blue text** = Imports (from elsewhere)
+- ⬛ **Black text** = Internal calculations
+
+### Rule 3.02: Formula Design Principles
+
+**The 24-Second Rule:**
+> A formula should be understandable within 24 seconds of looking at it.
+
+**Simplicity Guidelines:**
+- Maximum ~7 elements in a formula (Miller's Law)
+- If longer, break into helper rows
+- Avoid deeply nested functions
+
+```excel
+// BAD - Complex nested formula
+=IF(AND(A1>0,B1>0),IF(C1="Yes",A1*B1*1.1,A1*B1),0)
+
+// GOOD - Broken into steps
+Row 10: =A1*B1                    // Base calculation
+Row 11: =IF(C1="Yes",1.1,1)       // Adjustment factor
+Row 12: =IF(AND(A1>0,B1>0),1,0)   // Valid flag
+Row 13: =D10*D11*D12              // Final result
+```
+
+### Rule 3.03: Formula Consistency
+
+**CRITICAL: Each row should have ONE formula copied across all periods**
+
+```excel
+// GOOD - Same formula structure in every column
+D10: =C10*1.05    E10: =D10*1.05    F10: =E10*1.05
+
+// BAD - Different formulas in same row
+D10: =100         E10: =D10*1.05    F10: =500
+```
+
+**Anchor Columns:**
+- Column C (or first data column) may have a different "anchor" formula
+- All subsequent columns should have identical formulas
+
+### Rule 3.04: Labeling Conventions
+
+**Descriptive Labels:**
+```
+Revenue - Product A (units)
+Revenue - Product A ($ per unit)
+Revenue - Product A ($000s)
+```
+
+**Standard Abbreviations:**
+| Abbreviation | Meaning |
+|--------------|---------|
+| $000s | Thousands |
+| $m | Millions |
+| % | Percentage |
+| # | Count |
+| YoY | Year over Year |
+| QoQ | Quarter over Quarter |
+
+### Rule 3.05: Links Between Sheets
+
+**Import/Export Rules:**
+- Import at the TOP of calculation blocks
+- Export from the BOTTOM (results)
+- Color-code links (blue = import, red = export)
+
+```excel
+// IMPORT (blue): Bringing value from another sheet
+=Revenue!D15
+
+// EXPORT: The row that other sheets reference
+// (Mark with red text or comment)
+```
+
+### Rule 3.06: Timing Flags & Switches
+
+**Timing Flags:**
+- Binary flags (0 or 1) that control when calculations apply
+- Place in a dedicated row, reference throughout
+
+```excel
+Row 5: Construction Flag    | 1 | 1 | 1 | 0 | 0 |  // 1 during construction
+Row 6: Operations Flag      | 0 | 0 | 0 | 1 | 1 |  // 1 during operations
+```
+
+**Partial Period Factors (PPFs):**
+- Handle partial years/quarters
+- Factor between 0 and 1
+
+```excel
+Row 7: Days in Period       | 90 | 91 | 92 | 92 |
+Row 8: PPF                  | 0.25 | 0.25 | 0.25 | 0.25 |
+```
+
+### Rule 3.07: The Corkscrew Pattern
+
+For tracking balances over time (debt, assets, etc.):
+
+**4-Line Corkscrew (Simple):**
+```
+Opening Balance    |    0   |  100  |  150  |  120  |
++ Additions        |  100   |   50  |    0  |   30  |
+- Reductions       |    0   |    0  |  -30  |  -20  |
+= Closing Balance  |  100   |  150  |  120  |  130  |
+```
+
+**7-Line Corkscrew (Detailed):**
+```
+Opening Balance    |    0   |  100  |  150  |
++ Drawdowns        |  100   |   50  |    0  |
++ Interest         |    5   |    7  |    8  |
+- Repayments       |    0   |    0  |  -30  |
+- Fees             |   -5   |   -7  |   -8  |
++/- Adjustments    |    0   |    0  |    0  |
+= Closing Balance  |  100   |  150  |  120  |
+```
+
+**Corkscrew Rules:**
+- Opening balance = Previous period's closing balance
+- Closing balance = Opening + Additions - Reductions
+- First period opening usually references an input
+
+---
+
+## Excel Features Guidelines
+
+### Rule 4.01: Recommended Functions
+
+**PREFERRED:**
+| Function | Use Instead Of | Reason |
+|----------|---------------|--------|
+| `INDEX` | `CHOOSE` | More flexible, clearer |
+| `INDEX/MATCH` | `VLOOKUP` | Column insertions don't break |
+| `IFERROR` | Nested IFs for errors | Cleaner error handling |
+| `SUMPRODUCT` | Array formulas | No Ctrl+Shift+Enter needed |
+| `SUMIFS` | `SUMIF` | Multiple criteria support |
+
+**AVOID:**
+| Function | Problem |
+|----------|---------|
+| `INDIRECT` | Volatile, hard to audit |
+| `OFFSET` | Volatile, performance impact |
+| `NPV` | Timing assumptions unclear |
+| `IRR` | Can give multiple/no solutions |
+| Nested `IF` (>3 levels) | Hard to read/audit |
+
+### Rule 4.02: Named Ranges
+
+**General Rule: Avoid Named Ranges** in most cases because:
+- Hard to audit (can't see the reference)
+- Maintenance overhead
+- Can become orphaned
+
+**Exception - Use Names for:**
+- External workbook links
+- Key inputs referenced many times
+- Version control / model parameters
+
+**If Using Names:**
+```
+Naming Convention: [Sheet]_[Description]
+Examples:
+  Inputs_TaxRate
+  Inputs_StartDate
+  Assumptions_GrowthRate
+```
+
+### Rule 4.03: Formatting Standards
+
+**Number Formats:**
+| Data Type | Format | Example |
+|-----------|--------|---------|
+| Currency ($000s) | `#,##0` | 1,234 |
+| Currency ($m) | `#,##0.0` | 1.2 |
+| Percentages | `0.0%` | 5.5% |
+| Ratios | `0.00x` | 1.25x |
+| Dates | `mmm-yy` | Jan-24 |
+| Counts | `#,##0` | 1,234 |
+
+**Cell Colors:**
+| Purpose | Background | Text |
+|---------|------------|------|
+| Inputs | Light blue | Black |
+| Calculations | White | Black |
+| Imports | White | Blue |
+| Exports | White | Red |
+| Checks | Light red/green | Black |
+| Hardcoded | Yellow | Black |
+
+**Structural Formatting:**
+- Freeze panes: Row headers + timeline headers
+- Print setup: Repeat rows at top, fit to page width
+- Gridlines: Hide on presentation sheets
+
+---
+
+## Check Sheet Design
+
+Every model should have a **Check Sheet** that validates:
+
+```
+CHECK SHEET STRUCTURE
+┌────────────────────────────────────────┐
+│ Model Checks                           │
+├────────────────────────────────────────┤
+│ Balance Sheet Balances     ✓ OK        │
+│ Cash Flow Reconciliation   ✓ OK        │
+│ Debt Schedule Ties         ✓ OK        │
+│ Revenue Build-up           ✓ OK        │
+│ Circular Reference Check   ✓ OK        │
+├────────────────────────────────────────┤
+│ OVERALL STATUS:            ✓ ALL PASS  │
+└────────────────────────────────────────┘
+```
+
+**Check Formula Pattern:**
+```excel
+=IF(ABS(A1-B1)<0.01, "OK", "ERROR")
+// Use small tolerance for rounding
+```
+
+---
+
+## Common Patterns
+
+### Growth Rate Application
+```excel
+Base Value      |  100  |  100  |  100  |
+Growth Rate     |   5%  |   5%  |   5%  |
+Grown Value     |  100  |  105  |  110.25|
+
+Formula: =D10*(1+D11)  // Applied across
+```
+
+### Percentage Allocation
+```excel
+Total           | 1000  | 1100  | 1200  |
+Category A %    |  40%  |  40%  |  40%  |
+Category A $    |  400  |  440  |  480  |
+
+Formula: =D10*D11
+```
+
+### MIN/MAX Constraints
+```excel
+Calculated Value |  150  |  -20  |  300  |
+Floor (min 0)    |  150  |    0  |  300  |
+Cap (max 200)    |  150  |    0  |  200  |
+
+Floor: =MAX(D10, 0)
+Cap:   =MIN(D11, 200)
+```
+
+### Cumulative Sums
+```excel
+Period Value    |   10  |   20  |   15  |   25  |
+Cumulative      |   10  |   30  |   45  |   70  |
+
+Formula: =C12+D11  // Previous cumulative + current
+```
+
+---
+
+## Anti-Patterns (What NOT to Do)
+
+### 1. Mixed Inputs and Calculations
+```excel
+// BAD - Input mixed with formula
+A1: 100  (input)
+A2: =A1*1.05  (formula referencing input on same sheet)
+
+// GOOD - Separate sheets
+Inputs!A1: 100
+Calcs!A1: =Inputs!A1*1.05
+```
+
+### 2. Inconsistent Formulas Across Row
+```excel
+// BAD - Different logic in same row
+D5: =C5+10     E5: =D5*1.1    F5: =E5+20
+
+// GOOD - Same formula copied across
+D5: =C5+10     E5: =D5+10     F5: =E5+10
+```
+
+### 3. Overly Complex Single Formulas
+```excel
+// BAD - Everything in one cell
+=IF(AND($A5="Yes",B$3>2020),MAX(0,MIN(C5*D5*(1+$E$2),F5)),0)
+
+// GOOD - Break into readable steps
+Row 5: =C5*D5                    // Gross
+Row 6: =E5*(1+$E$2)              // With growth
+Row 7: =MAX(0,MIN(E6,F5))        // Constrained
+Row 8: =IF(AND($A5="Yes",B$3>2020),E7,0)  // Final
+```
+
+### 4. Circular References
+- **Never use circular references**, even with iteration enabled
+- Break the loop with a manual input or switch
+- If unavoidable, document extensively
+
+### 5. Hidden Rows/Columns with Logic
+```excel
+// BAD - Critical formula in hidden row
+(Hidden) Row 50: =SUM(D10:D49)*TaxRate
+
+// GOOD - All logic visible, or clearly marked
+Row 50: =SUM(D10:D49)*TaxRate  // Visible, with comment
+```
+
+---
+
+## Audit Trail Best Practices
+
+1. **Version Control Row**: Include model version and date in a consistent location
+2. **Change Log Sheet**: Track changes, dates, and authors
+3. **Documentation Sheet**: Explain key assumptions and methodology
+4. **Formula Audit**: Use Trace Precedents/Dependents regularly
+5. **Check Totals**: Include sum checks that should equal zero
+
+---
+
+## Quick Reference Card
+
+| Principle | Rule |
+|-----------|------|
+| Inputs | Separate sheet, blue cells |
+| Calculations | One formula per row, copy across |
+| Timing | Use flags (0/1) for periods |
+| Balances | Use corkscrew pattern |
+| Links | Import top, export bottom |
+| Colors | Blue=import, Red=export |
+| Formulas | 24-second rule, max 7 elements |
+| Checks | Dedicated check sheet |
+| Names | Avoid, except for external links |
+| Structure | Consistent columns across sheets |
+
+---
+
+## 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
+
+- `/excel-formulas` — Excel formula patterns for FAST models
+- `/governance` — Standards enforcement
+
+---
+
+## Related Resources
+
+- [Snippets: Excel Formulas](../excel-formulas/SKILL.md)
+- [Official FAST Standard](https://www.fast-standard.org/)

package/skills/governance/SKILL.md

@@ -0,0 +1,205 @@
+---
+name: "governance"
+description: "Use when the user asks about Governance Skill, especially phrases like \"naming convention\", \"governance\", \"documentation standard\", \"display folder\", \"convención de nombres\"."
+version: "1.0.0"
+---
+
+<!-- Generated by BI Agent Superpowers. Edit src/content/skills/governance.md instead. -->
+
+# Governance Skill
+
+## Trigger
+Activate this skill when user mentions:
+- "naming convention", "naming standard", "naming rules"
+- "governance", "standards", "best practices enforcement"
+- "documentation standard", "coding standard"
+- "display folder", "folder organization", "workspace organization"
+- "convención de nombres", "estándares", "gobernanza"
+
+## Identity
+You are a **BI Governance Specialist** who establishes and enforces naming conventions, documentation standards, and organizational best practices for Power BI, Fabric, and Excel projects. You help teams maintain consistency and quality across their BI assets.
+
+## MANDATORY RULES
+1. **CONSISTENCY OVER PREFERENCE.** Any consistent standard is better than no standard.
+2. **ENFORCE GENTLY.** Suggest improvements, don't demand rewrites of existing projects.
+3. **PRACTICAL STANDARDS.** Rules must be easy to follow — complex rules get ignored.
+4. **DOCUMENT THE WHY.** Every convention should have a clear rationale.
+5. **TEAM FIRST.** Standards should serve the team, not constrain individuals.
+
+---
+
+## Naming Conventions
+
+### Tables
+
+| Type | Convention | Example | Anti-Pattern |
+|------|-----------|---------|-------------|
+| Dimension | Singular noun | `Customer`, `Product`, `Date` | `Customers`, `DimCustomer`, `tbl_Customer` |
+| Fact | Singular noun or verb | `Sale`, `Order`, `Inventory` | `FactSales`, `fct_Sales` |
+| Bridge | Prefix with `Bridge` | `BridgeCustomerRegion` | `CustomerRegion_Bridge` |
+| Measure table | Prefix `_` | `_Measures`, `_KPIs` | `Measures Table`, `CalcMeasures` |
+| Config/Utility | Prefix `_` | `_Parameters`, `_DateConfig` | `Parameters` |
+| Calculated table | Document clearly | `CalendarTable` (with comment) | Unmarked calculated tables |
+
+### Columns
+
+| Type | Convention | Example |
+|------|-----------|---------|
+| Key (primary) | `[TableName]Key` | `CustomerKey`, `ProductKey` |
+| Key (alternate) | `[TableName]ID` or `[TableName]Code` | `CustomerID`, `ProductCode` |
+| Attribute | PascalCase, descriptive | `FirstName`, `OrderDate`, `ProductCategory` |
+| Flag/Boolean | `Is[Condition]` | `IsActive`, `IsDeleted`, `HasDiscount` |
+| Amount/Currency | Suffix with `Amount` | `SalesAmount`, `DiscountAmount` |
+| Count | Suffix with `Count` | `OrderCount`, `ItemCount` |
+| Date | Suffix with `Date` | `OrderDate`, `ShipDate`, `HireDate` |
+
+### Measures
+
+| Type | Convention | Example |
+|------|-----------|---------|
+| Base aggregation | PascalCase, descriptive | `TotalSales`, `OrderCount` |
+| Time intelligence | Suffix with period | `TotalSales_YTD`, `Revenue_PY` |
+| Ratio/Percentage | Suffix with `Pct` or `Ratio` | `MarginPct`, `ConversionRatio` |
+| KPI | Prefix with `KPI_` | `KPI_Revenue_Actual`, `KPI_Revenue_Target` |
+| Ranking | Prefix with `Rank_` | `Rank_TopProducts` |
+| Debug/Test | Prefix with `_` | `_Debug_RowCount`, `_Test_Total` |
+| Format string | Include in measure | Use format strings, not calculated strings |
+
+### Variables (DAX)
+
+| Convention | Example |
+|-----------|---------|
+| Prefix with `_` + PascalCase | `_CurrentSales`, `_PriorYear` |
+| Descriptive names | `_FilteredTable`, `_MaxDate` |
+| Avoid single letters | `_Result` not `_R` |
+
+### Power Query
+
+| Element | Convention | Example |
+|---------|-----------|---------|
+| Query name | PascalCase matching table | `Customer`, `Sale` |
+| Staging query | Prefix with `stg_` | `stg_Customer_Raw` |
+| Helper function | Prefix with `fn` | `fnCleanText`, `fnGetFiscalYear` |
+| Parameter | Prefix with `prm` | `prmServerName`, `prmStartDate` |
+| Step names | Descriptive, PascalCase | `FilteredActiveRows`, `RenamedColumns` |
+
+---
+
+## Display Folder Organization
+
+### Recommended Folder Structure
+
+```
+_Measures/
+├── 📁 Core Metrics
+│   ├── TotalSales
+│   ├── TotalCost
+│   └── GrossMargin
+├── 📁 Time Intelligence
+│   ├── TotalSales_YTD
+│   ├── TotalSales_PY
+│   └── TotalSales_YoY
+├── 📁 KPIs
+│   ├── KPI_Revenue_Actual
+│   ├── KPI_Revenue_Target
+│   └── KPI_Revenue_Status
+├── 📁 Rankings
+│   ├── Rank_TopProducts
+│   └── Rank_TopCustomers
+└── 📁 _Debug (hidden in production)
+    ├── _Debug_RowCount
+    └── _Test_Total
+```
+
+---
+
+## Workspace Organization
+
+### Development Lifecycle
+
+| Workspace | Purpose | Access |
+|-----------|---------|--------|
+| `[Project]-DEV` | Development and testing | Developers only |
+| `[Project]-TEST` | User acceptance testing | Developers + testers |
+| `[Project]-PROD` | Production | All authorized users |
+
+### Content Organization
+
+| Element | Convention |
+|---------|-----------|
+| Semantic model name | `[Domain] Model` (e.g., `Sales Model`) |
+| Report name | `[Domain] - [Purpose]` (e.g., `Sales - Executive Dashboard`) |
+| Dataflow name | `DF_[Source]_[Domain]` (e.g., `DF_SQL_Sales`) |
+| Pipeline name | `PL_[Action]_[Domain]` (e.g., `PL_Refresh_Sales`) |
+
+---
+
+## Documentation Requirements
+
+### Minimum Documentation
+
+Every model should have:
+1. **README** — Purpose, audience, refresh schedule, data sources
+2. **Data dictionary** — Table and column descriptions
+3. **Measure catalog** — All measures with business descriptions
+4. **Change log** — Major changes with dates and reasons
+
+### Measure Documentation Template
+
+```dax
+// Description: Calculates total sales for the current year to date
+// Business rule: Includes all confirmed and shipped orders, excludes cancelled
+// Owner: [team/person]
+// Last modified: [date]
+TotalSales_YTD = TOTALYTD([TotalSales], 'Date'[Date])
+```
+
+---
+
+## Review Checklists
+
+### Pre-Deployment Checklist
+
+- [ ] All tables follow naming conventions
+- [ ] All measures have display folders
+- [ ] No debug/test measures visible to users
+- [ ] RLS roles configured and tested
+- [ ] Date table marked as date table
+- [ ] All relationships documented
+- [ ] Performance tested with production data volume
+- [ ] Refresh schedule configured
+- [ ] Backup/recovery plan documented
+
+### Code Review Checklist
+
+- [ ] Measures use VAR/RETURN for repeated calculations
+- [ ] DIVIDE() used instead of / operator
+- [ ] No FILTER on fact tables (use dimension filters)
+- [ ] Variables follow naming conventions
+- [ ] Complex measures have comments
+- [ ] No hardcoded values (use parameters)
+
+---
+
+## 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` — Apply naming conventions to models
+- `/model-documenter` — Generate documentation per standards
+- `/deployment` — Governance in CI/CD pipelines
+
+---
+
+## Related Resources
+
+- [Model Documenter Skill](/model-documenter) — Generate documentation automatically
+- [DAX Skill](/dax) — DAX coding standards
+- [Data Modeling Skill](/data-modeling) — Model design standards
+- [Testing & Validation Skill](/testing-validation) — Quality assurance
+- [Snippets: Governance](library/snippets/governance/) — Naming convention references