@luquimbo/bi-superpowers 5.0.1 → 5.0.2

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "AI-powered skills for Power BI Desktop development. Works with Claude Code, GitHub Copilot, Codex, Gemini CLI, and Kilo Code.",
-    "version": "5.0.1",
+    "version": "5.0.2",
     "repository": "https://github.com/luquimbo/bi-superpowers"
   },
   "plugins": [

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "bi-superpowers",
   "description": "Claude Code plugin for Power BI, Microsoft Fabric, and semantic model workflows powered by the official Microsoft MCP servers.",
-  "version": "5.0.1",
+  "version": "5.0.2",
   "author": {
     "name": "Lucas Sanchez"
   },

package/.claude-plugin/skill-manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "bi-superpowers",
-  "version": "5.0.1",
+  "version": "5.0.2",
   "skillCount": 6,
   "skills": [
     {

package/.plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "spec": "open-plugin-spec@1",
   "name": "bi-superpowers",
-  "version": "5.0.1",
+  "version": "5.0.2",
   "description": "Claude Code plugin for Power BI, Microsoft Fabric, and semantic model workflows powered by the official Microsoft MCP servers.",
   "author": {
     "name": "Lucas Sanchez"

package/AGENTS.md

@@ -16,7 +16,7 @@
 - All semantic-model changes must go through the Power BI Modeling MCP against Power BI Desktop, then be persisted by Desktop save/export. Do not hand-edit `.tmdl` or other semantic model files.
 - Report and visual design changes are manual Power BI Desktop work. Never edit PBIR report artifacts directly: no `.Report/**/visual.json`, `page.json`, `report.json`, `definition.pbir`, theme/resource JSON, coordinates, bookmarks, slicers, card settings, conditional formatting, or free-form visual changes by file patch.
 - The only permitted report mutation is the plugin-owned field-swap/rebind command for template adaptation. Agents may not patch PBIR by hand, even when the requested change is "just replacing a measure." The command may write PBIR only to replace source fields/measures in existing visuals with target model fields/measures, using an explicit source-to-target mapping and preserving visual type, layout, formatting, interactions, IDs, theme, and bookmarks. The command must support dry-run, backup, validation, and a tight write scope limited to data bindings (`projections`, `prototypeQuery`, query refs, field parameters, sort/filter field references when required). If that command is unavailable, field swaps stay manual in Power BI Desktop.
-- **Template is the reference.** The BISuperpowers smoke-test template (`examples/smoke-test/pbip-files/template.pbip`) encodes the patterns this plugin treats as default for any project: Auto Date/Time disabled, Date Table marked, `discourageImplicitMeasures: true`, the dedicated `Métricas` table with one-level display folders (`Auxiliar`, fact-table folders such as `Ventas`, and `Ratios`), period comparison via `Aux Comparaciones` (Sallieri pattern), parameterizable currency conversion via the Power Query `MonedaBase` parameter + `Modelo Configuración[ValorTexto]` + `Tipo de cambio[TipoCambioBase]`, dynamic dimensions via field parameters (`Aux Dimensiones ventas`), calculation groups for time intelligence, IBCS-aligned JSON theme. All specialist skills (`bi-kickoff`, `bi-modeling`, `bi-dax`, `bi-performance`, `bi-connect`) replicate these patterns in new projects and audit/migrate existing projects toward them. They are the floor, not optional decoration.
+- **Template is the reference.** The BISuperpowers sales template (`templates/sales/sales-template.pbip`) encodes the patterns this plugin treats as default for any project: Auto Date/Time disabled, Date Table marked, `discourageImplicitMeasures: true`, the dedicated `Métricas` table with one-level display folders (`Auxiliar`, fact-table folders such as `Ventas`, and `Ratios`), period comparison via `Aux Comparaciones` (Sallieri pattern), parameterizable currency conversion via the Power Query `MonedaBase` parameter + `Modelo Configuración[ValorTexto]` + `Tipo de cambio[TipoCambioBase]`, dynamic dimensions via field parameters (`Aux Dimensiones ventas`), calculation groups for time intelligence, IBCS-aligned JSON theme. All specialist skills (`bi-kickoff`, `bi-modeling`, `bi-dax`, `bi-performance`, `bi-connect`) replicate these patterns in new projects and audit/migrate existing projects toward them. They are the floor, not optional decoration.
 
 ## Project Entry Points
 - `AGENTS.md` (this file) — operational context, conventions, install + publish flow.
@@ -247,7 +247,7 @@ Los 6 skills quedan disponibles como MCP prompts. Claude Desktop is a compatibil
 Use `validation/` when the user wants to test the plugin against public fixtures
 or private client projects. Keep this boundary:
 
-- `examples/smoke-test/` is the public fixture area.
+- `templates/<domain>/` is the public template area (today: `templates/sales/`). Each template ships its own `AGENTS.md` and PBIP package.
 - `validation/projects/*.json` stores sanitized metadata only.
 - `validation/cases/*.md` stores manual validation playbooks.
 - `validation.local.json` stores private local repo paths and is gitignored.
@@ -258,7 +258,7 @@ screenshots with private data, or private Git remotes into this public repo. Run
 structural checks with:
 
 ```bash
-super validate-projects --project template
+super validate-projects --project sales-template
 super validate-projects --strict
 ```
 

package/CHANGELOG.md

@@ -7,6 +7,41 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [5.0.2] — 2026-05-08
+
+### Changed — 2026-05-08 (templates folder + Calendario merge)
+
+- Moved the canonical reference template from `examples/smoke-test/pbip-files/template.*`
+  to `templates/sales/sales-template.*` to make room for additional template
+  domains (`templates/<domain>/`). Removed the `examples/smoke-test/` umbrella
+  and the orphaned `super-test.*` Desktop cache. Filename rename to
+  `sales-template.*` was performed via Power BI Desktop "Save As" so the PBIP
+  descriptor JSONs (`.pbip` and `Report/definition.pbir`) were never
+  hand-edited.
+- `templates/` now ships in the npm tarball (added to `package.json` files
+  whitelist). Excluded `**/.pbi/localSettings.json` from the tarball — those
+  files contain DPAPI-encrypted machine-specific Desktop bindings and must not
+  ship.
+- Updated all repo-side references (skills, AGENTS.md, README.md,
+  ARCHITECTURE.md, CONTRIBUTING.md, validation registry) to point at the new
+  `templates/sales/` location.
+- Merged the `Calendar` Power Query helper into the loaded `Calendario` Date
+  Table. `Calendario` is now rolling (ends at `Today` adjusted by the
+  `ZonaHoraria` parameter) and exposes 7 hidden 4-4-5 fiscal columns
+  (`Fiscal445Year`, `Fiscal445MonthNr`, `Fiscal445QuarterNr`,
+  `Fiscal445SemesterNr`, `Fiscal445MonthKey`, `Fiscal445QuarterKey`,
+  `Fiscal445SemesterKey`) consumed by `Aux Períodos`. The `Calendar` named
+  expression was deleted; `Aux Períodos` rebound to `Calendario` and renamed
+  `[Date]` → `[Fecha]` references.
+
+### Removed — 2026-05-08 (orphan measures in sales template)
+
+- Deleted 5 unused measures from `Métricas`: `Tipo de cambio seleccionado`,
+  `Ventas brutas`, `Métrica seleccionada`, `Color de tarjeta de tendencia`,
+  `Color de barras de tendencia`. Audit confirmed zero consumers in report
+  visuals, other measures, calculation items, or UDFs. Total measure count:
+  32 → 27.
+
 ### Fixed — 2026-05-08 (release readiness review)
 
 - Updated all template-reference guidance to match the current smoke-test

package/README.md

@@ -504,6 +504,7 @@ bin/
 commands/
 skills/
 src/content/
+templates/
 desktop-extension/
 config.json
 config.example.json
@@ -518,16 +519,16 @@ The npm package does not include:
 
 ```text
 docs/superpowers/
-examples/smoke-test/
 validation/
 validation.local.example.json
 validation.local.json
 node_modules/
 *.test.js
+**/.pbi/localSettings.json
 ```
 
-`examples/smoke-test/` is intentionally repo-only. It is used for QA and manual validation, not for user installs.
-`validation/` is also repo-only. It stores sanitized validation descriptors and playbooks for project QA; private project paths live in `validation.local.json`, which must never be committed.
+`templates/` ships canonical reference templates (today: `templates/sales/`). Each template is a complete PBIP package with `AGENTS.md`, semantic model, and report definition — used as the canonical "template-as-reference" by all specialist skills, and as the source for the upcoming `bi-kickoff` "create from template" branch (which will copy `templates/<domain>/` into `<user-repo>/pbip-files/<projectName>.*` with renaming).
+`validation/` is repo-only. It stores sanitized validation descriptors and playbooks for project QA; private project paths live in `validation.local.json`, which must never be committed.
 
 ---
 
@@ -582,7 +583,7 @@ Power BI work without committing customer repositories.
 Public fixtures live in:
 
 ```text
-examples/smoke-test/
+templates/sales/
 ```
 
 Sanitized validation metadata lives in:
@@ -604,7 +605,7 @@ map client projects on your own machine.
 Run the structural validation:
 
 ```bash
-super validate-projects --project template
+super validate-projects --project sales-template
 ```
 
 Run every descriptor, treating skipped private projects as failures:

package/bin/commands/validate-projects.js

@@ -9,7 +9,7 @@
  *
  * Usage:
  *   super validate-projects
- *   super validate-projects --project template
+ *   super validate-projects --project sales-template
  *   super validate-projects --root C:\path\to\bi-superpowers
  */
 

package/commands/bi-modeling.md

@@ -334,7 +334,7 @@ Read `config.json → experienceLevel` if available; otherwise infer from how th
 
 ## Template Patterns to Replicate
 
-The BISuperpowers smoke-test template (`examples/smoke-test/pbip-files/template.pbip` in the plugin repo, or the bundled copy that ships with `super install`) is the canonical reference. When designing a new model or auditing an existing one, replicate these structures **by default**:
+The BISuperpowers sales template (`templates/sales/sales-template.pbip` in the plugin repo, or the bundled copy that ships with `super install`) is the canonical reference. When designing a new model or auditing an existing one, replicate these structures **by default**:
 
 ### Structural patterns
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@luquimbo/bi-superpowers",
-  "version": "5.0.1",
+  "version": "5.0.2",
   "description": "Open-source Power BI Desktop toolkit for Claude Code, GitHub Copilot, Codex, Gemini CLI, and Kilo Code. Ships 6 BI skills and 2 official Microsoft MCP servers.",
   "main": "bin/cli.js",
   "bin": {
@@ -78,6 +78,7 @@
     "commands/",
     "skills/",
     "src/content/",
+    "templates/",
     "theme/",
     "desktop-extension/",
     "config.json",
@@ -86,6 +87,7 @@
     "LICENSE",
     "CHANGELOG.md",
     "AGENTS.md",
-    "!**/*.test.js"
+    "!**/*.test.js",
+    "!**/.pbi/localSettings.json"
   ]
 }

package/skills/bi-connect/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "bi-connect"
 description: "Use when the user asks about Power BI MCP Connection Skill, especially phrases like \"connect Power BI\", \"PBI connection\", \"MCP connection\", \"Power BI MCP\", \"DAX UDF\", \"DAX user-defined function\"."
-version: "5.0.1"
+version: "5.0.2"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-connect.md instead. -->

package/skills/bi-connect/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "5.0.1";
+const BUNDLED_INSTALLED_VERSION = "5.0.2";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/skills/bi-dax/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "bi-dax"
 description: "Use when the user asks about Power BI DAX Expert Skill, especially phrases like \"bi-dax\", \"/bi-dax\", \"DAX\", \"medida DAX\", \"DAX measure\", \"fórmula DAX\"."
-version: "5.0.1"
+version: "5.0.2"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-dax.md instead. -->

package/skills/bi-dax/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "5.0.1";
+const BUNDLED_INSTALLED_VERSION = "5.0.2";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/skills/bi-kickoff/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "bi-kickoff"
 description: "Use when the user asks about Project Kickoff Skill, especially phrases like \"I'm starting a brand-new BI project from scratch\", \"analizar proyecto\", \"analyze project\", \"project kickoff\", \"nuevo proyecto\", \"new project\"."
-version: "5.0.1"
+version: "5.0.2"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-kickoff.md instead. -->

package/skills/bi-kickoff/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "5.0.1";
+const BUNDLED_INSTALLED_VERSION = "5.0.2";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/skills/bi-modeling/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "bi-modeling"
 description: "Use when the user asks about Power BI Data Modeling Skill, especially phrases like \"bi-modeling\", \"bi modeling\", \"/bi-modeling\", \"modelar\", \"modelo semántico\", \"semantic model\"."
-version: "5.0.1"
+version: "5.0.2"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-modeling.md instead. -->
@@ -336,7 +336,7 @@ Read `config.json → experienceLevel` if available; otherwise infer from how th
 
 ## Template Patterns to Replicate
 
-The BISuperpowers smoke-test template (`examples/smoke-test/pbip-files/template.pbip` in the plugin repo, or the bundled copy that ships with `super install`) is the canonical reference. When designing a new model or auditing an existing one, replicate these structures **by default**:
+The BISuperpowers sales template (`templates/sales/sales-template.pbip` in the plugin repo, or the bundled copy that ships with `super install`) is the canonical reference. When designing a new model or auditing an existing one, replicate these structures **by default**:
 
 ### Structural patterns
 

package/skills/bi-modeling/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "5.0.1";
+const BUNDLED_INSTALLED_VERSION = "5.0.2";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/skills/bi-performance/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "bi-performance"
 description: "Use when the user asks about Power BI Performance Skill, especially phrases like \"bi-performance\", \"/bi-performance\", \"performance\", \"rendimiento\", \"lento\", \"slow\"."
-version: "5.0.1"
+version: "5.0.2"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-performance/SKILL.md instead. -->

package/skills/bi-performance/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "5.0.1";
+const BUNDLED_INSTALLED_VERSION = "5.0.2";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/skills/bi-start/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "bi-start"
 description: "Use when the user asks about BI Start Skill, especially phrases like \"bi-start\", \"bi start\", \"/bi-start\", \"empezar\", \"comenzar\", \"arranco\"."
-version: "5.0.1"
+version: "5.0.2"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-start.md instead. -->

package/skills/bi-start/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "5.0.1";
+const BUNDLED_INSTALLED_VERSION = "5.0.2";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

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

@@ -307,7 +307,7 @@ Read `config.json → experienceLevel` if available; otherwise infer from how th
 
 ## Template Patterns to Replicate
 
-The BISuperpowers smoke-test template (`examples/smoke-test/pbip-files/template.pbip` in the plugin repo, or the bundled copy that ships with `super install`) is the canonical reference. When designing a new model or auditing an existing one, replicate these structures **by default**:
+The BISuperpowers sales template (`templates/sales/sales-template.pbip` in the plugin repo, or the bundled copy that ships with `super install`) is the canonical reference. When designing a new model or auditing an existing one, replicate these structures **by default**:
 
 ### Structural patterns
 

package/templates/sales/AGENTS.md

@@ -0,0 +1,33 @@
+# AGENTS.md — Instrucciones para agentes de IA en este proyecto Power BI
+
+## Regla crítica 1: siempre usar el Power BI MCP para escribir
+
+Cuando crees o modifiques medidas DAX, tablas, columnas, relaciones o cualquier elemento del modelo semántico, DEBES usar el servidor MCP de Power BI Desktop. NO edites archivos TMDL (`.tmdl`, `.tmd`) directamente. Esos archivos los gestiona el motor tabular. Editarlos a mano basado en tu conocimiento de entrenamiento es propenso a errores y probablemente rompa el modelo.
+
+## Regla crítica 2: verificar la conexión MCP al iniciar sesión
+
+Antes de hacer cualquier cambio al proyecto, verifica que el MCP de Power BI Desktop esté conectado a una instancia abierta. Si no lo está, avisa al usuario para que abra el archivo `.pbip` en Power BI Desktop primero.
+
+## Regla crítica 3: los archivos TMDL son SOLO LECTURA
+
+Puedes LEER archivos TMDL para entender la estructura del modelo, las relaciones, las medidas. Es a veces más rápido que consultar por MCP. Pero NUNCA ESCRIBAS en esos archivos.
+
+## Regla crítica 4: consultar Microsoft Learn MCP para documentación técnica
+
+Cuando el usuario pregunte sobre funciones DAX, propiedades de Power BI, conectores o capacidades de Fabric, consulta el Microsoft Learn MCP antes de responder. No respondas de memoria sobre temas donde la documentación puede haber cambiado desde tu fecha de corte de entrenamiento. Si el Learn MCP no está disponible, avisa al usuario antes de responder.
+
+## Regla crítica 5: flujo completo
+
+Escribir via MCP. Leer via archivos. Versionar via Git. Después de cambios significativos, sugiere al usuario hacer un commit.
+
+## Estructura del proyecto
+
+La carpeta raíz del proyecto es un repositorio Git independiente.
+
+- Archivo `/sales-template.pbip`: archivo del proyecto Power BI (renombralo al nombre de tu proyecto si lo adaptás)
+- Carpeta `/sales-template.SemanticModel/`: definición del modelo (archivos TMDL, **SOLO LECTURA para agentes**)
+- Carpeta `/sales-template.Report/`: definición del reporte (**SOLO LECTURA para agentes**)
+
+Si renombrás los archivos `template.*` para tu proyecto, actualizá también las referencias internas:
+- `<tu-proyecto>.pbip` → campo `artifacts[0].report.path` apunta a `<tu-proyecto>.Report`
+- `<tu-proyecto>.Report/definition.pbir` → campo `datasetReference.byPath.path` apunta a `../<tu-proyecto>.SemanticModel`

package/templates/sales/sales-template.Report/.platform

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://developer.microsoft.com/json-schemas/fabric/gitIntegration/platformProperties/2.0.0/schema.json",
+  "metadata": {
+    "type": "Report",
+    "displayName": "sales-template"
+  },
+  "config": {
+    "version": "2.0",
+    "logicalId": "04b20925-5d76-439b-98f1-a45b9ad6ea5d"
+  }
+}