@luquimbo/bi-superpowers 4.1.6 → 5.0.1

package/skills/report-design/references/cli-commands.md

@@ -1,184 +0,0 @@
-# `pbi` CLI — commands this skill still uses
-
-Historical context: this skill used to drive the entire report authoring via `pbi-cli-tool` (MIT, by MinaSaad1). That approach hit 3 regressions (see `native-visuals.md` → "Lo que este skill YA no hace via CLI"), so authoring moved to Node scripts (`apply-theme.js`, `create-visual.js`, `validate-pbir.js`).
-
-The CLI is still useful for:
-
-1. **Model introspection** via XMLA — `pbi connect`, `pbi measure list`, `pbi table list`, `pbi column list`. Microsoft Modeling MCP covers the same ground and is preferred when available.
-2. **Page creation** — `pbi report add-page` still works fine.
-3. **Schema-level sanity check** — `pbi report validate` catches malformed JSON, but NOT non-native visualTypes (use `validate-pbir.js` for that).
-
-Everything else (add visual, bind visual, set theme, set-container for style) is superseded. The sections below cover only the supported flows.
-
-All examples assume you're in the project root and `reportPath="./pbip-files/{proj}.Report"`.
-
----
-
-## Global flags
-
-- `-p, --path <path>` — path to the `.Report` folder. Prefer explicit `-p` over CWD auto-detection.
-- `--no-sync` — skip Desktop auto-sync after writes. **Use during the generation loop** (Desktop is closed in PHASE 3 anyway).
-- `--json` — machine-readable output for scripting.
-
----
-
-## Model introspection (preferred via Microsoft Modeling MCP)
-
-### Connect (once, after Desktop is open)
-
-```bash
-pbi connect
-```
-
-Auto-detects a running PBI Desktop instance on localhost and connects to its XMLA endpoint. Requires the standalone installer build (Microsoft Store version blocks this).
-
-### List measures / tables / columns
-
-```bash
-pbi measure list --json
-pbi table list --json
-pbi column list --table "{tableName}" --json
-```
-
-Returns arrays of `{table, name, description, ...}` suitable for building a `Table[Field]` ref map to pass to `create-visual.js --bind`.
-
-### Disconnect
-
-```bash
-pbi disconnect
-```
-
-Run before PHASE 3 (kill Desktop), otherwise the CLI keeps a stale socket.
-
----
-
-## Pages (structure)
-
-### List pages
-
-```bash
-pbi report -p "$reportPath" list-pages
-```
-
-### Add a page
-
-```bash
-pbi report --no-sync -p "$reportPath" add-page \
-  --name "{pageName}" \
-  --display-name "{Display Name}"
-```
-
-- `--name` — internal identifier (also folder name). Short lowercase ASCII or 20-char hex.
-- `--display-name` — what shows on the page tab.
-
----
-
-## Validation (two layers)
-
-Always run both.
-
-```bash
-# 1. Schema sanity (CLI)
-pbi report -p "$reportPath" validate
-
-# 2. Allowlist + role checks (Node script)
-node "{skillBundleDir}/scripts/validate-pbir.js" "$reportPath"
-```
-
-The CLI's `validate` reports `valid: True` even for `visualType: "stackedBarChart"` (not a native type — Desktop renders it as "objeto visual personalizado"). The Node validator catches that.
-
----
-
-## Theme
-
-Inspect the current theme:
-
-```bash
-pbi report -p "$reportPath" get-theme
-```
-
-Apply a custom theme **with the bundled helper, NOT `pbi report set-theme`** (the CLI's `set-theme` writes invalid metadata for PBI Desktop March 2026):
-
-```bash
-node "{skillBundleDir}/scripts/apply-theme.js" \
-  --report-path "$reportPath" \
-  --theme-file "{skillBundleDir}/references/themes/BISuperpowers.json"
-```
-
-For the full canonical `report.json` theme shape and why `set-theme` was replaced, see `apply-theme.js` header comment.
-
----
-
-## Reload Desktop
-
-```bash
-pbi report -p "$reportPath" reload
-```
-
-Sends `Ctrl+Shift+F5` via pywin32. **NOT enough** to pick up externally-written visuals — Desktop must be fully killed and relaunched (see `close-write-open-pattern.md`). Use `reload` only for small in-session refreshes.
-
----
-
-## Visuals (superseded — use `create-visual.js`)
-
-`pbi visual add`, `pbi visual bind`, `pbi visual update`, `pbi visual delete`, `pbi visual bulk-bind`, `pbi visual set-container` are **no longer driven by this skill**. Reasons:
-
-- `add --type` advertises 5 aliases (`card, line_chart, bar_chart, table, matrix`) but internally accepts ~20 more with PascalCase names. The inconsistency caused the skill's docs to lag behind the CLI's real capabilities.
-- `add --type pie` silently creates a `donutChart` (alias bug).
-- `add --type stackedBarChart` creates a visual with `visualType: "stackedBarChart"` that Desktop rejects at render time — not a native type.
-- `bind` doesn't expose all PBIR roles (`--column`, `--line`, `--x`, `--y`, `--size`, `--breakdown` exist only in `bulk-bind`, not `bind`).
-
-The replacement is a single Node script:
-
-```bash
-node "{skillBundleDir}/scripts/create-visual.js" \
-  -p "$reportPath" \
-  --page "$pageName" \
-  --type "{nativeVisualType}" \
-  -n "{visualName}" \
-  --x {x} --y {y} --width {w} --height {h} \
-  --bind "{role}={Table[Field]}" \
-  [--bind ...]
-```
-
-See `native-visuals.md` for the 27 supported types and their `--bind` roles.
-
----
-
-## Key conventions (unchanged)
-
-- **Binding syntax is `Table[Field]`**, quoting the table name with single quotes if it has spaces: `'Categorias Finanzas'[Categoria]`.
-- **`--no-sync` on every write** during the generation loop.
-- **`_Measures` prefix convention** — measures live in a hidden `_Measures` table (leading underscore); columns live in their fact or dim table. The Node scripts use this prefix as a disambiguation hint when a role accepts `any` kind (e.g. `tableEx.Values`).
-
----
-
-## Full end-to-end example
-
-```bash
-# PHASE 0: model introspection
-pbi connect
-pbi measure list --json > measures.json
-
-# PHASE 4.1: page
-pbi report --no-sync -p ./pbip-files/Foo.Report add-page --name overview --display-name "Resumen"
-
-# PHASE 4.2: visuals (via Node script)
-node scripts/create-visual.js -p ./pbip-files/Foo.Report --page overview --type card \
-  -n kpi_revenue --x 24 --y 24 --width 280 --height 120 \
-  --bind values='_Measures[Total Revenue]' --title "Ingresos"
-
-node scripts/create-visual.js -p ./pbip-files/Foo.Report --page overview --type lineChart \
-  -n revenue_trend --x 24 --y 200 --width 816 --height 320 \
-  --bind category='Fecha[Fecha]' --bind y='_Measures[Total Revenue]'
-
-# PHASE 4.3: theme
-node scripts/apply-theme.js --report-path ./pbip-files/Foo.Report --theme-file references/themes/BISuperpowers.json
-
-# PHASE 4.4: validation (both layers)
-pbi report -p ./pbip-files/Foo.Report validate
-node scripts/validate-pbir.js ./pbip-files/Foo.Report
-
-# PHASE 5: relaunch Desktop
-powershell -Command "Start-Process -FilePath 'C:\Program Files\Microsoft Power BI Desktop\bin\PBIDesktop.exe' -ArgumentList '\"<abs-path.pbip>\"'"
-```

package/skills/report-design/references/cli-setup.md

@@ -1,101 +0,0 @@
-# CLI setup — installing `pbi-cli-tool`
-
-This skill requires the [`pbi-cli-tool`](https://github.com/MinaSaad1/pbi-cli) CLI (MIT, by MinaSaad1) and its `pywin32` dependency for Power BI Desktop auto-sync. All commands below are idempotent — running them on an already-set-up system is safe.
-
-## Full setup sequence (run in order)
-
-Check each prerequisite; if it's already satisfied, skip to the next.
-
-### 1. Python 3.10+
-
-```bash
-python --version
-```
-
-If the output is `Python 3.10.x` or newer, continue. Otherwise install Python:
-
-**Microsoft Store** (easiest on Windows — adds to PATH automatically):
-- Open Microsoft Store → search "Python 3.13" (Publisher: Python Software Foundation) → Install
-- **Close and reopen the terminal** after install so `python` is on PATH
-
-**Manual from python.org**:
-- Download installer from https://www.python.org/downloads/
-- During install, check **"Add python.exe to PATH"**
-- Close and reopen the terminal
-
-### 2. `pipx`
-
-```bash
-pipx --version
-```
-
-If it reports a version, skip to step 3. Otherwise:
-
-```bash
-pip install --user pipx
-python -m pipx ensurepath
-```
-
-Close and reopen the terminal so the new PATH entries take effect. Then verify:
-
-```bash
-pipx --version
-```
-
-### 3. `pbi-cli-tool`
-
-```bash
-pbi --version
-```
-
-If it reports `3.10.x` or newer, skip to step 4. Otherwise:
-
-```bash
-pipx install pbi-cli-tool
-```
-
-### 4. Inject `pywin32` into the pbi-cli pipx environment
-
-The `pywin32` package lets `pbi` send keystrokes to Power BI Desktop for auto-sync. Without it, the CLI falls back to PowerShell-based signaling which is less reliable.
-
-```bash
-python -m pipx inject pbi-cli-tool pywin32
-```
-
-Verify the CLI picks it up:
-
-```bash
-pbi visual add --help
-# If the previous run printed "Error: pywin32 is not installed", run the inject.
-# If no such warning appears on subsequent runs, pywin32 is loaded.
-```
-
-### 5. Optional — upgrade later
-
-```bash
-pipx upgrade pbi-cli-tool
-python -m pipx inject pbi-cli-tool pywin32 --force   # refresh the injection
-```
-
-Run this periodically (monthly) since MinaSaad1 ships updates alongside Power BI Desktop schema bumps.
-
-## Troubleshooting
-
-**`pbi: command not found`** after install → terminal PATH needs refresh. Close and reopen. If still missing, `python -m pipx ensurepath` again.
-
-**`pip: command not found`** with Python installed → the Microsoft Store install sometimes doesn't put `pip` on PATH. Use `python -m pip ...` instead.
-
-**`Found a space in the pipx home path`** warning → harmless on Windows. The CLI works despite this.
-
-**`Error: pywin32 is not installed`** when running `pbi visual add` → you ran `pip install --user pywin32` (wrong scope). Instead run `python -m pipx inject pbi-cli-tool pywin32` so it lands in the CLI's isolated venv.
-
-## Sanity check (run after full setup)
-
-```bash
-pbi --version                    # should print a version
-pbi setup                        # should print "Environment is ready."
-pbi connect                      # should auto-detect running Power BI Desktop
-pbi disconnect                   # clean disconnect
-```
-
-If all four commands succeed, the skill can proceed to PHASE 1.

package/skills/report-design/references/close-write-open-pattern.md

@@ -1,80 +0,0 @@
-# The close-write-open pattern
-
-This is the most important pattern in the skill. Get it wrong and **none of the visuals you generate will render** — not because the JSON is invalid, but because Power BI Desktop refuses to re-read the files while it's open.
-
-## The core fact
-
-Power BI Desktop reads `visual.json`, `page.json`, and the rest of the PBIR tree **once**, when the `.pbip` is first loaded by the app process. After that, it holds the report in memory and ignores file changes on disk. This is **not** a bug we can work around with the public CLI — it's Desktop's current design.
-
-Kurt Buhler documents this explicitly in the `power-bi-agentic-development/plugins/pbip/skills/pbip/SKILL.md`:
-
-> **"PBI Desktop does not detect external changes. Close and reopen PBI Desktop after editing files externally."**
-
-The subtle part: **"close"** here means kill the `PBIDesktop.exe` process, not `File → Close` inside the app. A file-level close keeps the app process alive with its cache intact. When the user then opens the file again via "Recent files" or drag, Desktop uses its cached state and silently ignores any new visual folders on disk.
-
-## The correct sequence
-
-```
-1. User has Power BI Desktop open with the .pbip
-2. Skill asks user to save any pending Desktop-side work
-3. Skill kills PBIDesktop.exe (process-level)
-4. Skill writes visuals via pbi CLI (while Desktop is dead)
-5. Skill relaunches the .pbip via Start-Process
-6. A new Desktop process boots, reads files from disk fresh, renders everything
-```
-
-## Commands
-
-### Kill Desktop
-
-Use `cmd //c` in Git Bash to avoid the MSYS path-mangling bug that eats the `/IM` flag:
-
-```bash
-cmd //c "taskkill /IM PBIDesktop.exe /F"
-cmd //c "taskkill /IM msmdsrv.exe /F"   # Analysis Services — Desktop usually kills this itself but belt-and-braces
-```
-
-Verify termination:
-
-```bash
-tasklist | grep -iE "PBIDesktop|msmdsrv"   # should return no lines
-```
-
-### Relaunch the .pbip
-
-PowerShell's `Start-Process` runs the shell-open association, which for `.pbip` files launches Power BI Desktop:
-
-```bash
-powershell -Command "Start-Process -FilePath './pbip-files/MyProject.pbip'"
-```
-
-Desktop takes ~10-20 seconds to fully load the model and render the visuals. The user sees "loading" screens during that window.
-
-## What does NOT work (confirmed failures)
-
-- **`File → Close` + `File → Open Recent`** — keeps the process alive, cache persists, new visuals ignored
-- **`Ctrl+Shift+F5` (CLI `pbi report reload`)** — only triggers a data refresh, not a structural re-scan of disk
-- **`File → Save` after external writes** — Desktop saves its in-memory state back to disk, which may OVERWRITE the externally-written files with the old state. Dangerous.
-- **Reopening the file by path while the same Desktop process is running** — same process, same cache, same problem
-
-## Why `pbi report reload` exists if it doesn't solve this
-
-The reload command is useful for smaller cases: refreshing data, picking up a theme change, re-running a single-visual query. It's not meant to discover newly-added visual folders, and the CLI docs don't claim it does.
-
-## Gotchas
-
-- **User has unsaved work in Desktop**: killing the process without prompting loses that work. Always ask before taskkill. If they have changes, tell them to save first.
-- **msmdsrv.exe lingering**: Desktop usually cleans it up, but occasionally it stays. Kill it separately to free port 53xxx that the CLI uses for `pbi connect`.
-- **Start-Process can't find the .pbip**: the path needs to be relative to CWD or absolute. If you're in `bi-superpowers/` but the .pbip is under `examples/smoke-test/pbip-files/`, use the full relative path.
-- **User has multiple Desktops open**: `taskkill /IM PBIDesktop.exe /F` kills ALL of them. If the user works with multiple .pbip files simultaneously, warn them or narrow the kill to the specific PID (via `tasklist` first).
-- **Virus scanner delays**: some AV tools lock the .pbip briefly after relaunch, causing a ~5-10s delay before Desktop shows anything. Normal, just wait.
-
-## How this maps to the skill phases
-
-| Phase | What to do |
-|---|---|
-| PHASE 2 end | `pbi disconnect` before kill (socket cleanup) |
-| PHASE 3 | Kill Desktop (with user confirmation) |
-| PHASE 4 | Write via CLI (Desktop is dead — no sync conflicts) |
-| PHASE 5 | Relaunch via `Start-Process` |
-| Post-PHASE 5 | User visually confirms render |

package/skills/report-design/references/layouts/finance.md

@@ -1,65 +0,0 @@
-# Finance layout (3 pages)
-
-Assumed fact table: `GeneralLedger` (or similar). Common dims: `Date`, `Account`, `CostCenter`, `Scenario`. Key measures expected: total revenue, total expense, net profit, margin, variance vs budget.
-
-Roles used below (to be resolved via the MCP):
-- `primary-kpi` — top-line KPI (e.g., Net Revenue)
-- `secondary-kpi-1/2/3` — 3 supporting KPIs (e.g., Gross Margin, EBITDA, Expense)
-- `variance-measure` — signed delta (e.g., Variance vs Budget)
-- `time-dim-column` — date column from Date dim
-- `account-dim-column` — Account dim name or category
-- `costcenter-dim-column` — CostCenter dim
-
----
-
-## Page 1: `ResumenEjecutivo` / "Resumen Ejecutivo"
-
-**Grid (1280×720):**
-
-| Visual | Primitive | Position (x, y, w, h) | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | static text "Resumen Ejecutivo" |
-| KPI 1 | card | 16, 80, 280, 120 | `primary-kpi` |
-| KPI 2 | card | 312, 80, 280, 120 | `secondary-kpi-1` |
-| KPI 3 | card | 608, 80, 280, 120 | `secondary-kpi-2` |
-| KPI 4 (variance, signed) | card + conditional color | 904, 80, 280, 120 | `variance-measure` |
-| Revenue over time | line_chart | 16, 216, 816, 320 | `primary-kpi` × `time-dim-column` |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 216, 336, 80 | `'Date'[Year]` |
-| Scenario slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 312, 336, 80 | `Scenario[Scenario]` |
-
-**Design notes:**
-- Variance KPI: green/red conditional coloring is design intent only. Render as a plain card with theme/default colors unless a tested PBIR formatting implementation is available.
-- Year slicer default: current year (single-select).
-
----
-
-## Page 2: `AnalisisCuentas` / "Análisis por cuenta"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Análisis por cuenta" |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `'Date'[Year]` |
-| CostCenter slicer | slicer (manual JSON — see `references/slicer.md`) | 312, 80, 280, 80 | `CostCenter[Name]` |
-| Top accounts bar | bar_chart (horizontal) | 16, 176, 608, 480 | `primary-kpi` by `account-dim-column`, TopN 15 |
-| Detail matrix | matrix | 640, 176, 544, 480 | rows: `account-dim-column`, cols: `'Date'[Year]`, values: `primary-kpi` |
-
-**Design notes:**
-- Matrix uses gradient conditional formatting on the value column.
-- Bar chart sorts descending by `primary-kpi`.
-
----
-
-## Page 3: `DetalleVariance` / "Detalle de variance"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Detalle de variance vs budget" |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `'Date'[Year]` |
-| Scenario slicer | slicer (manual JSON — see `references/slicer.md`) | 312, 80, 280, 80 | `Scenario[Scenario]` |
-| Variance by costcenter | bar_chart | 16, 176, 608, 320 | `variance-measure` by `costcenter-dim-column`, bars colored by sign (diverging) |
-| Variance trend | line_chart | 640, 176, 544, 320 | `variance-measure` by `time-dim-column` |
-| Account × Month matrix | matrix | 16, 512, 1168, 144 | rows: `account-dim-column`, cols: `'Date'[Month]`, values: `variance-measure` with diverging gradient |
-
-**Design notes:**
-- Variance-sign coloring (diverging palette) is design intent only. Render bars/matrix with theme/default colors unless a tested PBIR formatting implementation is available.
-- The bottom matrix is short (144px) so it acts as a "heatmap strip" rather than a scrollable table.

package/skills/report-design/references/layouts/generic.md

@@ -1,46 +0,0 @@
-# Generic layout (3 pages) — fallback
-
-Use when `{domain}` is "otro" or unrecognized. Extract the "main" measure and "main" dimension from the model via MCP (usually the first fact-table measure and the first non-date dim column).
-
-Roles:
-- `primary-measure`, `secondary-measure`, `tertiary-measure` (whatever the model has)
-- `primary-dim-column`, `secondary-dim-column`
-
----
-
-## Page 1: `Resumen` / "Resumen"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Resumen" |
-| KPI 1 | card | 16, 80, 280, 120 | `primary-measure` |
-| KPI 2 | card | 312, 80, 280, 120 | `secondary-measure` |
-| KPI 3 | card | 608, 80, 280, 120 | `tertiary-measure` (or omit and widen KPI1) |
-| KPI 4 | card | 904, 80, 280, 120 | any YoY / variance measure available, else omit |
-| Main trend | line_chart | 16, 216, 816, 320 | `primary-measure` × `time-dim-column` |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 216, 336, 80 | `'Date'[Year]` |
-| Primary dim slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 312, 336, 80 | `primary-dim-column` |
-
-If the model has no `Date` table at all, drop the line chart and replace with a second bar chart.
-
----
-
-## Page 2: `Analisis` / "Análisis"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Análisis" |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `'Date'[Year]` |
-| By primary dim | bar_chart | 16, 176, 608, 480 | `primary-measure` by `primary-dim-column` |
-| By secondary dim | bar_chart | 640, 176, 544, 480 | `primary-measure` by `secondary-dim-column` |
-
----
-
-## Page 3: `Detalle` / "Detalle"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Detalle" |
-| Primary dim slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `primary-dim-column` |
-| Secondary dim slicer | slicer (manual JSON — see `references/slicer.md`) | 312, 80, 280, 80 | `secondary-dim-column` |
-| Detail matrix | matrix | 16, 176, 1168, 480 | rows: `primary-dim-column`, cols: `secondary-dim-column`, values: `primary-measure` + `secondary-measure` |

package/skills/report-design/references/layouts/hr.md

@@ -1,48 +0,0 @@
-# HR / People layout (3 pages)
-
-Assumed fact table: `HeadcountSnapshot` (or `EmployeeFact`). Dims: `Date`, `Employee`, `Department`, `Position`. Measures: headcount, hires, terminations, attrition rate, avg tenure, avg comp.
-
-Roles:
-- `headcount-measure`, `hires-measure`, `terminations-measure`, `attrition-rate-measure`
-- `department-dim-column`, `position-dim-column`
-
----
-
-## Page 1: `ResumenPlantilla` / "Resumen de plantilla"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Resumen de plantilla" |
-| KPI — Headcount | card | 16, 80, 280, 120 | `headcount-measure` |
-| KPI — Hires YTD | card | 312, 80, 280, 120 | `hires-measure` |
-| KPI — Terminations YTD | card | 608, 80, 280, 120 | `terminations-measure` |
-| KPI — Attrition % | card + conditional color | 904, 80, 280, 120 | `attrition-rate-measure` (red above threshold) |
-| Headcount over time | line_chart | 16, 216, 816, 320 | `headcount-measure` × `time-dim-column` |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 216, 336, 80 | `'Date'[Year]` |
-| Department slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 312, 336, 80 | `department-dim-column` |
-
----
-
-## Page 2: `AnalisisDepartamento` / "Análisis por departamento"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Análisis por departamento" |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `'Date'[Year]` |
-| Headcount by dept | bar_chart (horizontal) | 16, 176, 608, 480 | `headcount-measure` by `department-dim-column` |
-| Attrition by dept | bar_chart (horizontal) | 640, 176, 544, 480 | `attrition-rate-measure` by `department-dim-column` with diverging color |
-
-**Design notes:** Attrition chart colors bars by value (higher = redder) to surface hotspots immediately.
-
----
-
-## Page 3: `DetalleEmpleados` / "Detalle de empleados"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Detalle de empleados" |
-| Department slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `department-dim-column` |
-| Position slicer | slicer (manual JSON — see `references/slicer.md`) | 312, 80, 280, 80 | `position-dim-column` |
-| Employee matrix | matrix | 16, 176, 1168, 480 | rows: `Employee[FullName]`, cols: `'Date'[Year]`, values: `headcount-measure` (as snapshot) + tenure if available |
-
-**Design notes:** If the model has PII, strongly suggest adding RLS (`/pbi-connect` → MCP) before sharing. Surface this to the user during kickoff.

package/skills/report-design/references/layouts/marketing.md

@@ -1,45 +0,0 @@
-# Marketing layout (3 pages)
-
-Assumed fact: `Campaigns` / `MarketingSpend`. Dims: `Date`, `Channel`, `Audience`, `Product` / `Campaign`. Measures: spend, impressions, clicks, conversions, CPA, ROAS, CTR, conversion rate.
-
-Roles:
-- `spend-measure`, `conversions-measure`, `cpa-measure`, `roas-measure`
-- `ctr-measure`, `conversion-rate-measure`
-- `channel-dim-column`, `campaign-dim-column`, `audience-dim-column`
-
----
-
-## Page 1: `ResumenMarketing` / "Resumen de marketing"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Resumen de marketing" |
-| KPI — Spend | card | 16, 80, 280, 120 | `spend-measure` |
-| KPI — Conversions | card | 312, 80, 280, 120 | `conversions-measure` |
-| KPI — CPA | card | 608, 80, 280, 120 | `cpa-measure` |
-| KPI — ROAS | card + conditional | 904, 80, 280, 120 | `roas-measure` (green > 1, red < 1) |
-| Spend trend | line_chart | 16, 216, 816, 320 | `spend-measure` × `time-dim-column` |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 216, 336, 80 | `'Date'[Year]` |
-| Channel slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 312, 336, 80 | `channel-dim-column` |
-
----
-
-## Page 2: `AnalisisCanal` / "Análisis por canal"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Análisis por canal" |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `'Date'[Year]` |
-| Spend by channel | bar_chart | 16, 176, 608, 480 | `spend-measure` by `channel-dim-column` |
-| ROAS by channel | bar_chart | 640, 176, 544, 480 | `roas-measure` by `channel-dim-column`, diverging color |
-
----
-
-## Page 3: `FunnelCampañas` / "Funnel por campaña"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Funnel por campaña" |
-| Channel slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `channel-dim-column` |
-| Audience slicer | slicer (manual JSON — see `references/slicer.md`) | 312, 80, 280, 80 | `audience-dim-column` |
-| Campaign matrix | matrix | 16, 176, 1168, 480 | rows: `campaign-dim-column`, values: `spend-measure` + `conversions-measure` + `ctr-measure` + `conversion-rate-measure` + `cpa-measure` with column conditional color |

package/skills/report-design/references/layouts/operations.md

@@ -1,44 +0,0 @@
-# Operations / Supply Chain layout (3 pages)
-
-Assumed fact: `Orders` or `Shipments`. Dims: `Date`, `Customer`, `Product`, `Facility`. Measures: volume (orders/units), SLA %, open orders, aging.
-
-Roles:
-- `volume-measure`, `sla-measure`, `open-orders-measure`, `aging-measure`
-- `facility-dim-column`, `product-dim-column`
-
----
-
-## Page 1: `ResumenOperaciones` / "Resumen operacional"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Resumen operacional" |
-| KPI — Volume | card | 16, 80, 280, 120 | `volume-measure` |
-| KPI — SLA % | card + conditional | 312, 80, 280, 120 | `sla-measure` (red below target) |
-| KPI — Open orders | card | 608, 80, 280, 120 | `open-orders-measure` |
-| KPI — Aging (avg days) | card | 904, 80, 280, 120 | `aging-measure` |
-| Volume trend | line_chart | 16, 216, 816, 320 | `volume-measure` × `time-dim-column` |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 216, 336, 80 | `'Date'[Year]` |
-| Facility slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 312, 336, 80 | `facility-dim-column` |
-
----
-
-## Page 2: `AnalisisFacility` / "Análisis por facility"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Análisis por facility" |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `'Date'[Year]` |
-| SLA by facility | bar_chart | 16, 176, 608, 480 | `sla-measure` by `facility-dim-column`, diverging color (red below target) |
-| Volume by facility | bar_chart | 640, 176, 544, 480 | `volume-measure` by `facility-dim-column` |
-
----
-
-## Page 3: `DetalleOrdenes` / "Detalle de órdenes"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Detalle de órdenes" |
-| Facility slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `facility-dim-column` |
-| Status slicer | slicer (manual JSON — see `references/slicer.md`) | 312, 80, 280, 80 | order status column if present |
-| Orders matrix | matrix | 16, 176, 1168, 480 | rows: `product-dim-column` + `facility-dim-column`, values: `volume-measure` + `open-orders-measure` + `aging-measure` with gradient |

package/skills/report-design/references/layouts/sales.md

@@ -1,50 +0,0 @@
-# Sales / Revenue layout (3 pages)
-
-Assumed fact table: `Sales`. Common dims: `Date`, `Customer`, `Product`, `Salesperson`. Key measures: revenue, units, AOV, orders, revenue YoY.
-
-Roles:
-- `primary-kpi` — revenue total
-- `secondary-kpi-1/2/3` — units, orders, AOV
-- `yoy-measure` — revenue YoY %
-- `customer-dim-column`, `product-dim-column`, `salesperson-dim-column`
-
----
-
-## Page 1: `ResumenVentas` / "Resumen de ventas"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Resumen de ventas" |
-| KPI 1 — revenue | card | 16, 80, 280, 120 | `primary-kpi` |
-| KPI 2 — units | card | 312, 80, 280, 120 | `secondary-kpi-1` |
-| KPI 3 — orders | card | 608, 80, 280, 120 | `secondary-kpi-2` |
-| KPI 4 — YoY % | card + conditional color | 904, 80, 280, 120 | `yoy-measure` (signed) |
-| Revenue over time | line_chart | 16, 216, 816, 320 | `primary-kpi` × `time-dim-column` |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 216, 336, 80 | `'Date'[Year]` |
-| Channel / Segment slicer | slicer (manual JSON — see `references/slicer.md`) | 848, 312, 336, 80 | best available segmentation column |
-
----
-
-## Page 2: `ClientesProductos` / "Clientes y productos"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Clientes y productos" |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `'Date'[Year]` |
-| Top customers bar | bar_chart (horizontal) | 16, 176, 608, 480 | `primary-kpi` by `customer-dim-column`, TopN 10 |
-| Top products bar | bar_chart (horizontal) | 640, 176, 544, 480 | `primary-kpi` by `product-dim-column`, TopN 10 |
-
-**Design notes:** Both bar charts share the year slicer. Use descending sort.
-
----
-
-## Page 3: `PipelineDetalle` / "Pipeline y detalle"
-
-| Visual | Primitive | Position | Bindings |
-|---|---|---|---|
-| Page title | textbox (manual JSON — see `references/textbox.md`) | 16, 16, 1152, 48 | "Pipeline y detalle" |
-| Year slicer | slicer (manual JSON — see `references/slicer.md`) | 16, 80, 280, 80 | `'Date'[Year]` |
-| Salesperson slicer | slicer (manual JSON — see `references/slicer.md`) | 312, 80, 280, 80 | `salesperson-dim-column` |
-| Pipeline matrix | matrix | 16, 176, 1168, 480 | rows: `salesperson-dim-column`, cols: `'Date'[Month]`, values: `primary-kpi` + `secondary-kpi-2` |
-
-**Design notes:** Matrix uses conditional color scale on revenue column. Subtotals enabled.