@atlashub/smartstack-cli 3.8.0 → 3.10.0

package/templates/skills/business-analyse/steps/step-01-cadrage.md

@@ -92,133 +92,10 @@ ELSE:
 > Skip organizational questions (adoption, change management, governance, KPIs).
 > Focus on functional decisions and technical challenges.
 
-### 3v. Vibe Coding — Lot 1: Problem & Scope
-
-**Goal:** Capture the core need and must-have features in a single batch.
-
-Ask via AskUserQuestion (2 questions):
-```
-question: "Quel est le besoin principal de cette application ?"
-header: "Besoin"
-options:
-  - label: "Automatiser un processus manuel"
-    description: "Remplacer des taches repetitives par une application"
-  - label: "Creer un outil manquant"
-    description: "Construire quelque chose qui n'existe pas encore"
-  - label: "Remplacer un outil existant"
-    description: "Remplacer un logiciel ou tableur qui ne convient plus"
-  - label: "Centraliser des donnees"
-    description: "Rassembler des informations dispersees en un seul endroit"
-```
-
-```
-question: "Quelles fonctionnalites sont indispensables pour la V1 ?"
-header: "Indispensable"
-multiSelect: true
-options:
-  → Generate 4 options dynamically from {feature_description}
-  → Each option = one functional area detected in the description
-  → Example for HR app: "Gestion des employes", "Saisie des heures", "Gestion des conges", "Rapports et exports"
-```
-
-**Store:**
-```yaml
-problem_type: string (from Q1)
-must_have_features: string[] (from Q2)
-```
-
-### 4v. Vibe Coding — Lot 2: Users & Permissions
-
-**Goal:** Determine access model (solo vs multi-user) and roles.
-
-Ask via AskUserQuestion:
-```
-question: "Qui va utiliser cette application ?"
-header: "Utilisateurs"
-options:
-  - label: "Moi seul"
-    description: "Application mono-utilisateur, je suis l'unique admin"
-  - label: "Quelques utilisateurs (2-10)"
-    description: "Petite equipe avec des roles differents"
-  - label: "Organisation (10+)"
-    description: "Deploiement a l'echelle d'une equipe ou entreprise"
-```
-
-```
-IF "Moi seul":
-  Auto-set:
-    applicationRoles = [{ role: "{App} Admin", level: "admin", permissionPattern: "business.{app}.*" }]
-    stakeholders = [{ role: "Developpeur", function: "Product owner et developpeur", involvement: "decision-maker", tasks: ["Toutes les operations"] }]
-  → SKIP role question
-
-IF "Quelques utilisateurs" or "Organisation":
-  Display standard 4-tier roles table, then ask:
-  question: "Ces 4 roles (Admin, Manager, Contributor, Viewer) conviennent-ils ?"
-  header: "Roles"
-  options:
-    - label: "Oui, parfait"
-      description: "Utiliser les 4 roles standards"
-    - label: "Personnaliser"
-      description: "Modifier les roles ou permissions"
-
-  Auto-set stakeholders from user type:
-    IF "Quelques utilisateurs":
-      stakeholders = [
-        { role: "Administrateur", function: "Gere le systeme et les utilisateurs", involvement: "decision-maker", tasks: ["Configuration", "Gestion utilisateurs"] },
-        { role: "Utilisateur", function: "Utilise le systeme au quotidien", involvement: "end-user", tasks: ["Saisie", "Consultation"] }
-      ]
-    IF "Organisation":
-      stakeholders = [
-        { role: "Administrateur", function: "Gere le systeme", involvement: "decision-maker", tasks: ["Configuration", "Gestion"] },
-        { role: "Manager", function: "Supervise et valide", involvement: "approver", tasks: ["Validation", "Reporting"] },
-        { role: "Utilisateur", function: "Operations quotidiennes", involvement: "end-user", tasks: ["Saisie", "Consultation"] }
-      ]
-```
-
-### 5v. Vibe Coding — Lot 3: Technical Challenges
-
-**Goal:** Identify technical risks specific to AI-assisted development.
-
-Ask via AskUserQuestion:
-```
-question: "Quels defis techniques anticipez-vous ?"
-header: "Defis"
-multiSelect: true
-options:
-  - label: "Regles metier complexes"
-    description: "Calculs, validations ou workflows difficiles a specifier"
-  - label: "Volume de donnees"
-    description: "Grandes quantites de donnees a gerer ou migrer"
-  - label: "Integrations externes"
-    description: "APIs, services tiers ou synchronisation avec d'autres systemes"
-  - label: "Interface riche"
-    description: "Ecrans avec beaucoup d'interactions, graphiques ou visualisations"
-```
-
-**Auto-infer cadrage data (DO NOT ask these — derive from answers):**
-
-```yaml
-cadrage.problem: "{feature_description} — {problem_type}"
-cadrage.asIs: "Aucun systeme en place" | "Processus manuel existant" | "Outil existant a remplacer"
-  → Derived from Lot 1 problem_type
-cadrage.toBe: "Application {application_name} couvrant: {must_have_features joined}"
-cadrage.trigger: "Projet vibe coding initie par le developpeur"
-cadrage.risks:
-  → Map each selected technical challenge to a RISK entry:
-    - "Regles metier complexes" → RISK-001, type: "technical", probability: "medium", impact: "high"
-    - "Volume de donnees" → RISK-002, type: "technical", probability: "low", impact: "medium"
-    - "Integrations externes" → RISK-003, type: "technical", probability: "medium", impact: "medium"
-    - "Interface riche" → RISK-004, type: "technical", probability: "low", impact: "low"
-  → Add mitigation for each: "Specification detaillee dans step-03 + generation iterative"
-cadrage.acceptanceCriteria:
-  - { id: "AC-001", criterion: "Toutes les fonctionnalites must-have implementees et fonctionnelles", validated: false }
-  - { id: "AC-002", criterion: "Application deployable et utilisable", validated: false }
-cadrage.globalScope:
-  mustHave: {must_have_features}
-  shouldHave: [] → Determined later in coverage matrix
-  couldHave: [] → Determined later in coverage matrix
-  outOfScope: []
-```
+See [references/cadrage-vibe-coding.md](../references/cadrage-vibe-coding.md) for the complete 3-lot questionnaire:
+- **Lot 1 (3v):** Problem & Scope — capture core need + must-have features
+- **Lot 2 (4v):** Users & Permissions — access model (solo/team/org) + roles
+- **Lot 3 (5v):** Technical Challenges — risks specific to AI-assisted dev + auto-inferred cadrage data
 
 **After Lot 3:** Go directly to **section 9 (Coverage Matrix)**.
 
@@ -389,73 +266,7 @@ If a feature is in mustHave → it MUST have at least one UC in the correspondin
 
 Use ba-writer to enrich master feature.json. **Follow the STRUCTURE CARDS below exactly.**
 
-> **STRUCTURE CARD: cadrage.stakeholders[]**
-> ```json
-> {
->   "role": "Fleet Manager",
->   "function": "Manages daily fleet operations",
->   "involvement": "decision-maker",
->   "tasks": ["Monitor vehicles", "Approve repairs", "Export reports"],
->   "frequency": "Daily",
->   "painPoints": ["Manual tracking in spreadsheets", "No real-time visibility"]
-> }
-> ```
-> **MANDATORY fields:** `role`, `function`, `involvement`, `tasks`
-> **involvement values:** `approver`, `decision-maker`, `consulted`, `informed`, `end-user`
-> **FORBIDDEN fields:** Do NOT use `expertise`, `systemRole`, `description` (use `function` instead).
-
-> **STRUCTURE CARD: cadrage.applicationRoles[]**
-> ```json
-> {
->   "role": "{App} Admin",
->   "description": "Full access to all modules",
->   "level": "admin",
->   "permissionPattern": "business.{app}.*"
-> }
-> ```
-> **MANDATORY fields:** `role`, `level`, `permissionPattern`
-> **level values:** `admin`, `manager`, `contributor`, `viewer`
-> **FORBIDDEN fields:** Do NOT use `permissions` (use `permissionPattern`), `isDefault`.
-
-> **STRUCTURE CARD: cadrage.risks[]**
-> ```json
-> {
->   "id": "RISK-001",
->   "type": "business|technical|organizational",
->   "description": "CSV data may contain duplicates and errors",
->   "probability": "high|medium|low",
->   "impact": "high|medium|low",
->   "priority": "critical|medium|low",
->   "mitigation": "Data cleaning phase before import, detailed error reports"
-> }
-> ```
-> **MANDATORY fields:** `id` (pattern: RISK-NNN), `type`, `description`, `mitigation`
-> **FORBIDDEN fields:** Do NOT use `risk` (name), `severity`. Use `id` + `description` + `priority`.
-
-> **STRUCTURE CARD: cadrage.acceptanceCriteria[]**
-> ```json
-> { "id": "AC-001", "criterion": "All must-have features delivered and tested", "validated": false }
-> ```
-> **MANDATORY:** This section must NOT be omitted.
-
-> **STRUCTURE CARD: cadrage.coverageMatrix[]**
-> ```json
-> {
->   "item": "User management with CRUD",
->   "category": "mustHave|shouldHave|couldHave|outOfScope|implicit",
->   "module": "Users",
->   "ucRef": "UC-UM-001",
->   "notes": "Foundation module, must be implemented first"
-> }
-> ```
-> **MANDATORY fields:** `item`, `category`, `module`
-> **category values:** `mustHave`, `shouldHave`, `couldHave`, `outOfScope`, `implicit` (camelCase)
-> **FORBIDDEN fields:** Do NOT use `id`, `feature`, `priority`. Use `item` + `category`.
-
-> **STRUCTURE CARD: cadrage.codebaseContext** — Must be a string, NOT an object.
-> ```json
-> "codebaseContext": "Greenfield project, no existing entities. SmartStack 2.1.0 with Extensions DbContext."
-> ```
+See [references/cadrage-structure-cards.md](../references/cadrage-structure-cards.md) for exact JSON formats of: `stakeholders[]`, `applicationRoles[]`, `risks[]`, `acceptanceCriteria[]`, `coverageMatrix[]`, `codebaseContext`.
 
 ```
 ba-writer.enrichSection({

package/templates/skills/business-analyse/steps/step-03a-data.md

@@ -62,6 +62,42 @@ IF module already specified (status = "specified" in master):
   Increment currentModuleIndex, re-check
   IF all modules specified → Load step-04-consolidation.md, STOP
 
+### 1b. Cache Warming for Module Loop (FIRST MODULE ONLY)
+
+> **Performance Optimization:** Pre-load module specification references to reduce redundant reads across all modules.
+> This step runs ONLY for the FIRST module (currentModuleIndex = 0), not repeated for subsequent modules.
+
+```
+IF currentModuleIndex === 0:
+  // Pre-load module specification references (Bucket 3)
+  const moduleRefs = [
+    "~/.claude/skills/business-analyse/references/spec-auto-inference.md",
+    "~/.claude/skills/business-analyse/references/ui-resource-cards.md",
+    "~/.claude/skills/business-analyse/references/ui-dashboard-spec.md",
+    "~/.claude/skills/business-analyse/references/cadrage-vibe-coding.md"
+  ];
+
+  for (const file of moduleRefs) {
+    read(file);  // Pre-load into cache
+  }
+
+  Display: "✓ Cache warmed: module specification references (23KB, 4 files)"
+  Display: "  Expected token savings: 75% reduction in reference reads across module loop"
+  Display: "  Retention: until step-04 (after all modules specified)"
+ELSE:
+  // Subsequent modules use cached references (no re-load)
+  Display: "✓ Using cached module references (from first module)"
+```
+
+**Rationale:**
+
+- Module specification references are read 2-3× PER MODULE (5 modules = 10-15 reads without caching)
+- Pre-loading once at start of module loop eliminates 75% of redundant reads
+- Token savings: ~10,000 tokens for a 5-module application
+- Cache retained until step-04 (when consolidation starts, references no longer needed)
+
+See [references/cache-warming-strategy.md](../references/cache-warming-strategy.md) § Bucket 3 for details.
+
 ### 2. Initialize Module Feature.json
 
 ```
@@ -245,55 +281,12 @@ Display to client:
 
 **Prerequisites:** Entity attributes must be defined (from step 6) OR anticipated from decomposition.
 
-**Inference rules - Entity attribute → SmartTable column:**
-
-| Attribute Type | Column Format | Sortable | Filterable | Notes |
-|---|---|---|---|---|
-| string + unique | text | yes | yes | clickAction: navigate:detail |
-| string | text | yes | yes | — |
-| enum / status | badge | yes | yes (multi-select) | colorMap from lifeCycles if exists |
-| FK:Entity | text (join .name) | yes | yes (entity-select) | Display related entity name |
-| decimal | currency | yes | no | — |
-| int | number | yes | no | — |
-| datetime | date-relative | yes | yes (date-range) | — |
-| bool | boolean | yes | yes (toggle) | — |
-| text (long) | — | no | no | Hidden in table, visible in detail |
-
-**Inference rules - Entity attribute → SmartForm field:**
-
-| Attribute Type | Component | Required from | Notes |
-|---|---|---|---|
-| string | Input | entity.required | — |
-| string (multiline) | TextArea | entity.required | rows: 4 |
-| enum | Select | entity.required | source: enum name |
-| FK:Entity | EntitySelect | entity.required | source: target entity, searchable |
-| decimal | NumberInput | entity.required | — |
-| int | NumberInput | entity.required | — |
-| datetime | DatePicker | entity.required | — |
-| bool | Toggle | — | default: false |
-
-**Auto-generated sections per featureType:**
-
-| featureType | Sections generated |
-|---|---|
-| data-centric | list, create, detail |
-| workflow | list, create, detail, edit |
-| integration | list, detail, config |
-| reporting | dashboard |
-| full-module | list, create, detail, edit, dashboard |
-
-**For each auto-generated section:**
-
-1. **list section:** SmartTable with all non-long-text attributes as columns (convention or columnDefs based on depth), actions = [view, edit, delete], defaultSort = { createdAt, desc }
-2. **create section:** SmartForm with all writable attributes as fields, component inferred from type
-3. **detail section:** DetailCard with all attributes + child SmartTable for each 1:N relationship
-4. **edit section:** Same as create but pre-filled (mode: edit)
-5. **dashboard section:** Trigger 3d (dashboard specification)
-
-**If entity has a status/enum field AND lifeCycles exists:**
-- list section: status column gets `format: badge`, `colorMap: stateMachine:{Entity}`
-- list section: rowActions get `showWhen` conditions based on state machine transitions
-- detail section: add StatusBadge resource + transition action buttons
+See [references/spec-auto-inference.md](../references/spec-auto-inference.md) for complete inference rules:
+- Entity attribute → SmartTable column mapping (9 type rules)
+- Entity attribute → SmartForm field mapping (8 type rules)
+- Auto-generated sections per featureType (5 types)
+- Section generation rules (list, create, detail, edit, dashboard)
+- Status/lifecycle enhancement rules
 
 Write auto-generated sections to `specification.sections[]` via ba-writer.enrichSection()
 

package/templates/skills/business-analyse/steps/step-03b-ui.md

@@ -122,72 +122,9 @@ For EACH section confirmed in 3a, build the `specification.sections[]` structure
 
 4. Build the section object:
 
-> **STRUCTURE CARD: specification.sections[]** — Resources MUST include full depth definitions.
-> ```json
-> {
->   "code": "list",
->   "labels": { "fr": "Liste", "en": "List", "it": "Elenco", "de": "Liste" },
->   "route": "/business/{app}/{module}/list",
->   "icon": "list",
->   "permission": "business.{app}.{module}.read",
->   "wireframe": "{module}-list",
->   "useCases": ["UC-{PREFIX}-001", "UC-{PREFIX}-002"],
->   "businessRules": ["BR-VAL-{PREFIX}-001"],
->   "resources": [
->     {
->       "code": "{module}-grid",
->       "type": "SmartTable",
->       "entity": "{MainEntity}",
->       "permission": "business.{app}.{module}.read",
->       "columns": ["name", "status", "createdAt"],
->       "columnDefs": [
->         { "field": "code", "label": {"fr": "Code", "en": "Code"}, "format": "text", "sortable": true, "filterable": true, "clickAction": "navigate:detail" },
->         { "field": "name", "label": {"fr": "Nom", "en": "Name"}, "format": "text", "sortable": true, "filterable": true },
->         { "field": "status", "label": {"fr": "Statut", "en": "Status"}, "format": "badge", "sortable": true, "filterable": true, "colorMap": "stateMachine:{Entity}" },
->         { "field": "createdAt", "label": {"fr": "Créé le", "en": "Created"}, "format": "date-relative", "sortable": true }
->       ],
->       "actions": ["view", "edit", "delete"],
->       "rowActions": [
->         { "action": "view", "icon": "eye", "permission": "business.{app}.{module}.read" },
->         { "action": "edit", "icon": "edit", "permission": "business.{app}.{module}.update", "showWhen": {"status": ["draft"]} },
->         { "action": "delete", "icon": "trash", "permission": "business.{app}.{module}.delete", "confirm": true }
->       ],
->       "filters": ["status", "dateRange"],
->       "defaultSort": { "field": "createdAt", "direction": "desc" },
->       "defaultPageSize": 20,
->       "emptyState": { "icon": "inbox", "message": {"fr": "Aucun enregistrement", "en": "No records"}, "createAction": true }
->     }
->   ]
-> }
-> ```
->
-> **SmartForm resource example (for create/edit sections):**
-> ```json
-> {
->   "code": "{module}-form",
->   "type": "SmartForm",
->   "entity": "{MainEntity}",
->   "permission": "business.{app}.{module}.create",
->   "fields": [
->     { "name": "code", "component": "Input", "required": true, "validation": "Unique, auto-generated" },
->     { "name": "name", "component": "Input", "required": true },
->     { "name": "type", "component": "Select", "required": true, "source": "EntityTypeEnum" },
->     { "name": "description", "component": "TextArea", "required": false },
->     { "name": "parentId", "component": "EntitySelect", "source": "ParentEntity", "required": true },
->     { "name": "startDate", "component": "DatePicker", "required": true },
->     { "name": "isActive", "component": "Toggle", "default": true }
->   ],
->   "formLayout": {
->     "type": "tabs",
->     "tabs": [
->       { "code": "general", "label": {"fr": "Général", "en": "General"}, "fields": ["code", "name", "type", "description"] },
->       { "code": "details", "label": {"fr": "Détails", "en": "Details"}, "fields": ["parentId", "startDate", "isActive"] }
->     ]
->   }
-> }
-> ```
-> **MANDATORY for SmartTable:** `columnDefs`, `rowActions`, `defaultSort`, `emptyState`
-> **MANDATORY for SmartForm:** `fields` with `component` type, `formLayout`
+See [references/ui-resource-cards.md](../references/ui-resource-cards.md) for exact JSON formats of `specification.sections[]` (SmartTable + SmartForm resources).
+**MANDATORY for SmartTable:** `columnDefs`, `rowActions`, `defaultSort`, `emptyState`
+**MANDATORY for SmartForm:** `fields` with `component` type, `formLayout`
 
 5. Write `specification.sections[]` via ba-writer.enrichSection()
 
@@ -218,39 +155,9 @@ Example for a list section:
 
 Store in specification.uiWireframes[] (**MANDATORY** for every section):
 
-> **STRUCTURE CARD: specification.uiWireframes[]** — ALL fields below are MANDATORY.
-> ```json
-> {
->   "screen": "{module}-{section}",
->   "section": "{section}",
->   "description": "Description of the screen",
->   "mockupFormat": "ascii",
->   "mockup": "╔═══...",
->   "elements": ["DataGrid", "FilterBar", "Pagination", "CreateButton"],
->   "actions": ["filter", "sort", "create", "view-detail"],
->   "permissionsRequired": ["business.{app}.{module}.read"],
->   "componentMapping": [
->     { "wireframeElement": "DataGrid", "reactComponent": "SmartTable" },
->     { "wireframeElement": "FilterBar", "reactComponent": "SmartFilter" },
->     { "wireframeElement": "CreateButton", "reactComponent": "Button" }
->   ],
->   "layout": {
->     "type": "page",
->     "regions": [
->       { "id": "toolbar", "position": "top", "components": [
->         { "type": "FilterBar", "resourceRef": "{module}-filters" },
->         { "type": "ActionMenu", "resourceRef": "{module}-actions", "permission": "business.{app}.{module}.create" }
->       ]},
->       { "id": "content", "position": "main", "span": 12, "components": [
->         { "type": "SmartTable", "resourceRef": "{module}-grid" }
->       ]}
->     ]
->   }
-> }
-> ```
-> **REQUIRED fields:** `screen`, `mockup`, `elements`, `section`, `componentMapping`, `layout` are ALL mandatory.
-> A wireframe without `componentMapping` or `layout` will FAIL validation in step 9.
-> **layout.regions[].components[].resourceRef** MUST match a `sections[].resources[].code`.
+See [references/ui-resource-cards.md](../references/ui-resource-cards.md) for exact JSON format of `specification.uiWireframes[]`.
+**REQUIRED fields:** `screen`, `mockup`, `elements`, `section`, `componentMapping`, `layout` are ALL mandatory.
+A wireframe without `componentMapping` or `layout` will FAIL validation in step 9.
 
 Ask client to validate each mockup via AskUserQuestion (batch 2-3 mockups at once if possible).
 
@@ -313,85 +220,12 @@ For each section, identify what resources/components are needed:
 
 ### 3d. Dashboard Specification (if section = dashboard)
 
-When a "dashboard" section is selected, capture structured KPI and chart data **in addition** to the standard ASCII mockup.
-
-1. **Ask client for KPIs** via AskUserQuestion (batch):
-   - KPI name and metric description
-   - Visualization type: `kpi-card`, `bar`, `line`, `pie`, `area`, `donut`, `stacked-bar`
-   - Data source entity
-   - Format: `number`, `currency`, `percent`, `duration`
-   - Thresholds (warning/critical) if applicable
-
-2. **Ask client for filters:**
-   - Date range filter? Default period? (day/week/month/quarter/year)
-   - Entity-based filters? (status, category, etc.)
-
-3. **Ask client for refresh mode:**
-   - Static (load on page open)
-   - Polling (periodic refresh)
-   - SignalR (real-time push)
-
-4. **Store in specification.dashboards[]:**
-
-```json
-{
-  "code": "{module}-dashboard",
-  "title": "{Module} Dashboard",
-  "description": "Vue d'ensemble des métriques {module}",
-  "linkedUCs": ["UC-XXX"],
-  "refreshMode": "static",
-  "defaultPeriod": "month",
-  "kpis": [
-    {
-      "code": "total-items",
-      "label": "Total Items",
-      "metric": "COUNT(entity)",
-      "format": "number",
-      "visualization": "kpi-card",
-      "dataSource": "Entity",
-      "thresholds": { "warning": 100, "critical": 50 }
-    },
-    {
-      "code": "items-by-status",
-      "label": "Items by Status",
-      "metric": "COUNT(entity) GROUP BY status",
-      "format": "number",
-      "visualization": "pie",
-      "dataSource": "Entity",
-      "dimensions": ["status"]
-    }
-  ],
-  "filters": [
-    { "field": "dateRange", "type": "dateRange", "label": "Période" },
-    { "field": "status", "type": "multiselect", "label": "Statut" }
-  ],
-  "permissionsRequired": ["business.{app}.{module}.read"]
-}
-```
-
-5. **ALSO generate the standard ASCII mockup** for the dashboard with KPI cards + chart placeholders:
-
-```
-╔═══════════════════════════════════════════════════════════════╗
-║  {Module} > Dashboard              Période: [Ce mois ▾]     ║
-╠═══════════════════════════════════════════════════════════════╣
-║  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐    ║
-║  │ KPI #1   │  │ KPI #2   │  │ KPI #3   │  │ KPI #4   │    ║
-║  │  1,234   │  │  567     │  │  89.2%   │  │  12,400  │    ║
-║  │  ↑ +12%  │  │  ↓ -3%  │  │  → 0%   │  │  ↑ +5%   │    ║
-║  └──────────┘  └──────────┘  └──────────┘  └──────────┘    ║
-╠═══════════════════════════════════════════════════════════════╣
-║  ┌─────────────────────────┐  ┌─────────────────────────┐    ║
-║  │  [Bar Chart]            │  │  [Pie Chart]            │    ║
-║  │  Items by Month         │  │  Items by Status        │    ║
-║  │  ████                   │  │      ████████           │    ║
-║  │  ████ ████              │  │   ███      ███          │    ║
-║  │  ████ ████ ████         │  │  ██   42%    ██         │    ║
-║  └─────────────────────────┘  └─────────────────────────┘    ║
-╚═══════════════════════════════════════════════════════════════╝
-```
-
-Store the mockup in specification.wireframes[] AS WELL (for visual reference).
+See [references/ui-dashboard-spec.md](../references/ui-dashboard-spec.md) for the complete dashboard capture process:
+- Ask client for KPIs (name, visualization type, format, thresholds)
+- Ask client for filters (date range, entity-based)
+- Ask client for refresh mode (static/polling/SignalR)
+- Store in `specification.dashboards[]` with full JSON template
+- Generate standard ASCII mockup with KPI cards + chart placeholders
 
 ---
 

package/templates/skills/business-analyse/steps/step-03c-compile.md

@@ -161,7 +161,7 @@ Module → Sections → Resources (levels 3-4-5 of the hierarchy).
 
 #### 8f. SeedData Core
 
-5 MANDATORY typed arrays — each with structured objects, NOT flat strings or objects.
+7 MANDATORY typed arrays — each with structured objects, NOT flat strings or objects.
 
 > **STRUCTURE CARD: specification.seedDataCore**
 > ```json
@@ -169,6 +169,16 @@ Module → Sections → Resources (levels 3-4-5 of the hierarchy).
 >   "navigationModules": [
 >     { "code": "{module}", "label": "{Module Name}", "icon": "list", "route": "/business/{app}/{module}", "parentCode": "{app}", "sort": 1 }
 >   ],
+>   "navigationSections": [
+>     { "code": "list", "label": "Liste", "icon": "List", "route": "/business/{app}/{module}/list", "parentCode": "{module}", "permission": "business.{app}.{module}.read", "sort": 1 },
+>     { "code": "detail", "label": "Détail", "icon": "FileText", "route": "/business/{app}/{module}/detail/:id", "parentCode": "{module}", "permission": "business.{app}.{module}.read", "sort": 2 },
+>     { "code": "create", "label": "Créer", "icon": "Plus", "route": "/business/{app}/{module}/create", "parentCode": "{module}", "permission": "business.{app}.{module}.create", "sort": 3 }
+>   ],
+>   "navigationResources": [
+>     { "code": "{module}-grid", "type": "SmartTable", "entity": "{Entity}", "parentCode": "list", "permission": "business.{app}.{module}.read" },
+>     { "code": "{module}-form", "type": "SmartForm", "entity": "{Entity}", "parentCode": "create", "permission": "business.{app}.{module}.create" },
+>     { "code": "{module}-detail-card", "type": "DetailCard", "entity": "{Entity}", "parentCode": "detail", "permission": "business.{app}.{module}.read" }
+>   ],
 >   "navigationTranslations": [
 >     { "moduleCode": "{module}", "language": "fr", "label": "..." },
 >     { "moduleCode": "{module}", "language": "en", "label": "..." },
@@ -189,9 +199,68 @@ Module → Sections → Resources (levels 3-4-5 of the hierarchy).
 >   ]
 > }
 > ```
-> **MANDATORY:** All 5 arrays must be present. Each element must be an object, NOT a string.
+> **MANDATORY:** All 7 arrays must be present. Each element must be an object, NOT a string.
+> **CRITICAL:** `navigationSections` and `navigationResources` are DERIVED from `specification.sections[]` — use the transform algorithm below (section 8f-bis).
 > **FORBIDDEN:** Do NOT use `navigationModule` (singular string), `permissions` as flat string array, `rolePermissions` as flat object, `permissionsConstants` as comma-separated string.
 
+#### 8f-bis. Transform Sections into Navigation SeedData
+
+> **CRITICAL:** `navigationSections` and `navigationResources` must be generated from `specification.sections[]`.
+> This ensures the navigation hierarchy (Module → Section → Resource) is complete in the database.
+
+**Transform algorithm:**
+
+```javascript
+// 1. Transform specification.sections[] into navigationSections
+const navigationSections = specification.sections.map((section, index) => ({
+  code: section.code,                    // e.g., "list", "detail", "dashboard"
+  label: section.labels.fr,              // Default language (fr)
+  icon: section.icon,                    // Lucide icon name
+  route: section.route,                  // Full route path
+  parentCode: metadata.module,           // Module code (parent)
+  permission: section.permission,        // Required permission
+  sort: index + 1                        // Display order (1-based)
+}));
+
+// 2. Transform specification.sections[].resources[] into navigationResources
+const navigationResources = specification.sections.flatMap(section =>
+  section.resources.map(resource => ({
+    code: resource.code,                 // e.g., "employees-grid"
+    type: resource.type,                 // e.g., "SmartTable", "SmartForm"
+    entity: resource.entity,             // e.g., "Employee"
+    parentCode: section.code,            // Section code (parent)
+    permission: resource.permission      // Optional (can inherit from section)
+  }))
+);
+```
+
+**Write to seedDataCore:**
+
+```
+ba-writer.enrichSection({
+  feature_id,
+  section: "specification",
+  data: {
+    seedDataCore: {
+      navigationModules: [ ... ],
+      navigationSections: navigationSections,     // DERIVED
+      navigationResources: navigationResources,   // DERIVED
+      navigationTranslations: [ ... ],
+      permissions: [ ... ],
+      rolePermissions: [ ... ],
+      permissionConstants: [ ... ]
+    }
+  }
+})
+```
+
+**Validation:**
+
+- EVERY section in `specification.sections[]` MUST appear in `navigationSections`
+- EVERY resource in `specification.sections[].resources[]` MUST appear in `navigationResources`
+- Total count: `navigationSections.length === specification.sections.length`
+- Total count: `navigationResources.length === sum(sections[].resources.length)`
+
 #### 8g. Gherkin Scenarios
 
 BDD acceptance tests per UC.