@atlashub/smartstack-cli 3.36.0 → 3.38.0

package/templates/skills/apex/references/examine-build-validation.md

@@ -0,0 +1,87 @@
+# Examine Build & Migration Validation
+
+> **Loaded by:** step-04-examine.md (sections 4-5)
+> **Purpose:** Build verification, migration validation, database testing procedures.
+
+---
+
+## Build Verification
+
+```bash
+# Cleanup corrupted EF Core design-time artifacts (Roslyn BuildHost bug on Windows/WSL)
+for d in src/*/bin?Debug bin?Debug; do [ -d "$d" ] && echo "Removing corrupted artifact: $d" && rm -rf "$d"; done
+
+# Backend
+dotnet clean && dotnet restore && dotnet build
+
+# Post-build cleanup (WSL Roslyn recreates literal bin\Debug folders after each build)
+for d in src/*/bin?Debug bin?Debug; do [ -d "$d" ] && rm -rf "$d"; done
+
+# Frontend (if applicable)
+npm run typecheck
+```
+
+**BLOCKING:** Both must pass. If failure, classify error per `references/error-classification.md`:
+- Category A (missing package) → `dotnet add package` → rebuild
+- Category B (assembly conflict) → resolve version → rebuild
+- Category C (DI missing) → fix DI registration → rebuild
+- Category D (migration broken) → fix migration → rebuild
+- Category E (config) → fix config → rebuild
+- Category F (source code) → fix code → rebuild
+
+---
+
+## Migration Validation (if needs_migration)
+
+### Pending Model Changes Check
+
+```bash
+INFRA_PROJECT=$(ls src/*Infrastructure*/*.csproj 2>/dev/null | head -1)
+API_PROJECT=$(ls src/*Api*/*.csproj 2>/dev/null | head -1)
+
+dotnet ef migrations has-pending-model-changes \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$API_PROJECT"
+```
+
+**BLOCKING** if pending changes detected → migration is missing.
+
+### Migration Application Test (SQL Server LocalDB)
+
+```bash
+DB_NAME="SmartStack_Apex_Examine_$(date +%s)"
+CONN_STRING="Server=(localdb)\\MSSQLLocalDB;Database=$DB_NAME;Integrated Security=true;TrustServerCertificate=true;Connect Timeout=120;"
+
+dotnet ef database update \
+  --connection "$CONN_STRING" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$API_PROJECT"
+```
+
+**BLOCKING** if migration fails on SQL Server. Common issues:
+- SQLite-only syntax in migrations (fix: regenerate migration)
+- Column type mismatches (fix: update EF configuration)
+- Missing foreign key targets (fix: reorder migrations)
+
+### Integration Tests on Real SQL Server
+
+```bash
+# Integration tests use DatabaseFixture → real SQL Server LocalDB
+# This validates: LINQ→SQL, multi-tenant isolation, soft delete, EF configs
+INT_TEST_PROJECT=$(ls tests/*Tests.Integration*/*.csproj 2>/dev/null | head -1)
+if [ -n "$INT_TEST_PROJECT" ]; then
+  dotnet test "$INT_TEST_PROJECT" --no-build --verbosity normal
+fi
+```
+
+Tests running against SQL Server catch issues that SQLite misses:
+- Case sensitivity in string comparisons
+- Date/time function differences
+- IDENTITY vs AUTOINCREMENT behavior
+- Global query filter translation to T-SQL
+
+### Cleanup
+
+```bash
+sqlcmd -S "(localdb)\MSSQLLocalDB" -Q "IF DB_ID('$DB_NAME') IS NOT NULL BEGIN ALTER DATABASE [$DB_NAME] SET SINGLE_USER WITH ROLLBACK IMMEDIATE; DROP DATABASE [$DB_NAME]; END" 2>/dev/null
+```

package/templates/skills/apex/references/execution-frontend-gates.md

@@ -0,0 +1,177 @@
+# Frontend Compliance Gate — 5 Mandatory Checks
+
+> **Loaded by:** step-03-execute.md (FRONTEND COMPLIANCE GATE section)
+> **Condition:** MANDATORY before any frontend commit
+> **Purpose:** Automated checks that catch the most common failures in generated code.
+
+---
+
+## Gate 1: CSS Variables (Theme System)
+
+Check for hardcoded Tailwind colors — MUST use CSS variables.
+
+```bash
+ALL_PAGES=$(find src/pages/ src/components/ -name "*.tsx" 2>/dev/null | grep -v node_modules | grep -v "\.test\.")
+if [ -n "$ALL_PAGES" ]; then
+  HARDCODED=$(grep -Pn '(bg|text|border)-(?!\[)(red|blue|green|gray|white|black|slate|zinc|neutral|stone)-' $ALL_PAGES 2>/dev/null)
+  if [ -n "$HARDCODED" ]; then
+    echo "FAIL: Hardcoded Tailwind colors found — must use CSS variables"
+    echo "$HARDCODED"
+  else
+    echo "PASS: CSS variables"
+  fi
+fi
+```
+
+**If hardcoded colors found, replace BEFORE committing:**
+
+| Old | New |
+|-----|-----|
+| `bg-white` | `bg-[var(--bg-card)]` |
+| `bg-gray-50` | `bg-[var(--bg-primary)]` |
+| `text-gray-900` | `text-[var(--text-primary)]` |
+| `text-gray-500/600` | `text-[var(--text-secondary)]` |
+| `border-gray-200` | `border-[var(--border-color)]` |
+| `bg-blue-600` / `text-blue-600` | `bg-[var(--color-accent-500)]` / `text-[var(--color-accent-500)]` |
+| `hover:bg-blue-700` | `hover:bg-[var(--color-accent-600)]` |
+| `text-red-500` | `text-[var(--error-text)]` |
+| `bg-green-500` | `bg-[var(--success-bg)]` |
+
+---
+
+## Gate 2: Forms as Pages (ZERO Modals/Drawers/Slide-overs)
+
+Check for modal/dialog/drawer/slide-over imports and inline form patterns — FORBIDDEN.
+
+```bash
+PAGE_FILES=$(find src/pages/ -name "*.tsx" 2>/dev/null)
+if [ -n "$PAGE_FILES" ]; then
+  FAIL=false
+
+  # 2a. Component imports
+  MODAL_IMPORTS=$(grep -Pn "import.*(?:Modal|Dialog|Drawer|Popup|Sheet|SlideOver|Overlay)" $PAGE_FILES 2>/dev/null)
+  if [ -n "$MODAL_IMPORTS" ]; then
+    echo "FAIL: Modal/Dialog/Drawer component imports — forms MUST be full pages"
+    echo "$MODAL_IMPORTS"
+    FAIL=true
+  fi
+
+  # 2b. State variables for inline forms (catches drawers/slide-overs without imports)
+  MODAL_STATE=$(grep -Pn "useState.*(?:isOpen|showModal|showDialog|showCreate|showEdit|showForm|isCreating|isEditing|showDrawer|showPanel|showSlideOver|selectedEntity|editingEntity)" $PAGE_FILES 2>/dev/null)
+  if [ -n "$MODAL_STATE" ]; then
+    echo "FAIL: Inline form state detected — forms MUST be separate page components with own routes"
+    echo "$MODAL_STATE"
+    FAIL=true
+  fi
+
+  if [ "$FAIL" = true ]; then
+    echo "Fix: Create EntityCreatePage.tsx (route: /create) and EntityEditPage.tsx (route: /:id/edit)"
+    echo "See smartstack-frontend.md section 3b"
+  else
+    echo "PASS: No modals/drawers"
+  fi
+fi
+```
+
+**If modals/drawers found:** Replace with separate `EntityCreatePage.tsx` (route: `/{module}/create`) and `EntityEditPage.tsx` (route: `/{module}/:id/edit`). See `smartstack-frontend.md` section 3b.
+
+---
+
+## Gate 3: I18n File Structure
+
+Verify translation files exist as separate JSON per language.
+
+```bash
+if [ ! -d "src/i18n/locales" ]; then
+  echo "FAIL: Missing src/i18n/locales/ directory — create it with 4 languages"
+else
+  for LANG in fr en it de; do
+    JSON_FILES=$(find "src/i18n/locales/$LANG" -name "*.json" 2>/dev/null | wc -l)
+    if [ "$JSON_FILES" -eq 0 ]; then
+      echo "FAIL: No JSON files in src/i18n/locales/$LANG/"
+    else
+      echo "PASS: $LANG ($JSON_FILES files)"
+    fi
+  done
+fi
+```
+
+**If i18n structure wrong:** Create `src/i18n/locales/{fr,en,it,de}/{module}.json` following the template in `smartstack-frontend.md` section 2. NEVER embed translations in a single `.ts` file.
+
+**Correct structure:**
+```
+src/i18n/locales/
+├── fr/{module}.json    ← French (primary)
+├── en/{module}.json    ← English
+├── it/{module}.json    ← Italian
+└── de/{module}.json    ← German
+```
+
+Each file MUST contain: `title`, `description`, `actions`, `labels`, `columns`, `form`, `errors`, `validation`, `messages`, `empty`.
+
+---
+
+## Gate 4: Lazy Loading
+
+Check for static page imports in route/App files.
+
+```bash
+APP_TSX=$(find src/ -name "App.tsx" -not -path "*/node_modules/*" 2>/dev/null | head -1)
+ROUTE_FILES=$(find src/routes/ -name "*.tsx" -o -name "*.ts" 2>/dev/null)
+if [ -n "$APP_TSX" ]; then
+  STATIC_IMPORTS=$(grep -Pn "^import .+ from '@/pages/" "$APP_TSX" $ROUTE_FILES 2>/dev/null)
+  if [ -n "$STATIC_IMPORTS" ]; then
+    echo "FAIL: Static page imports in App.tsx/routes — MUST use React.lazy()"
+    echo "$STATIC_IMPORTS"
+  else
+    echo "PASS: Lazy loading"
+  fi
+fi
+```
+
+---
+
+## Gate 5: useTranslation in Pages
+
+Verify pages use i18n.
+
+```bash
+PAGE_FILES=$(find src/pages/ -name "*.tsx" 2>/dev/null | grep -v "\.test\." | grep -v node_modules)
+if [ -n "$PAGE_FILES" ]; then
+  TOTAL=$(echo "$PAGE_FILES" | wc -l)
+  WITH_I18N=$(grep -l "useTranslation" $PAGE_FILES 2>/dev/null | wc -l)
+  if [ "$WITH_I18N" -eq 0 ]; then
+    echo "FAIL: No pages use useTranslation — all text must be translated"
+  else
+    echo "PASS: $WITH_I18N/$TOTAL pages use useTranslation"
+  fi
+fi
+```
+
+---
+
+## Explicit I18n File Creation
+
+When creating i18n files, generate EXACTLY this structure:
+
+```
+src/i18n/locales/
+├── fr/{module}.json    ← French (primary)
+├── en/{module}.json    ← English
+├── it/{module}.json    ← Italian
+└── de/{module}.json    ← German
+```
+
+Each file MUST contain these keys: `title`, `description`, `actions`, `labels`, `columns`, `form`, `errors`, `validation`, `messages`, `empty`. See `smartstack-frontend.md` section 2 for the complete JSON template.
+
+---
+
+## ALL 5 Gates MUST PASS
+
+**Before creating the frontend commit:**
+1. Do NOT commit frontend changes until ALL checks pass
+2. If ANY gate fails, fix the issues first
+3. When delegating to `/ui-components` skill, include explicit instructions:
+   - "CSS: Use CSS variables ONLY — `bg-[var(--bg-card)]`, `text-[var(--text-primary)]`. NEVER use hardcoded Tailwind colors."
+   - "Forms: Create/Edit forms are FULL PAGES with own routes (e.g., `/create`, `/:id/edit`). NEVER use modals/dialogs."
+   - "I18n: ALL text must use `t('namespace:key', 'Fallback')`. Generate JSON files in `src/i18n/locales/`."

package/templates/skills/apex/references/execution-frontend-patterns.md

@@ -0,0 +1,105 @@
+# Frontend Patterns — Economy Mode Guidelines
+
+> **Loaded by:** step-03-execute.md (Layer 1 section: economy_mode frontend tasks)
+> **Purpose:** Quick reference for frontend creation in sequential (economy) mode.
+> **Detailed patterns:** See `smartstack-frontend.md` (referenced from smartstack-layers.md)
+
+---
+
+## Frontend Tasks — Sequential Execution (economy_mode)
+
+For each frontend task in the plan (Layer 1):
+
+1. **API Client:** `MCP scaffold_api_client` → API client + types + React Query hook
+2. **Routes:** `MCP scaffold_routes` with `outputFormat: 'clientRoutes'` for lazy imports
+3. **Pages:** **INVOKE `/ui-components` skill** (read SKILL.md + ALL patterns) — MANDATORY for ALL page types
+
+---
+
+## Required Page Types Per Module
+
+Create ALL 4 page types per module:
+- `ListPage.tsx` — entity list with SmartTable/EntityCard
+- `DetailPage.tsx` — entity detail view
+- `EntityCreatePage.tsx` (route: `/create`) — FULL PAGE form, NEVER modal
+- `EntityEditPage.tsx` (route: `/:id/edit`) — FULL PAGE form, NEVER modal
+
+**Wire ALL routes in App.tsx:** `index` (ListPage), `:id` (DetailPage), `create` (CreatePage), `:id/edit` (EditPage)
+
+---
+
+## Foreign Key (FK) Fields — CRITICAL
+
+Any Guid FK property (e.g., EmployeeId, DepartmentId) MUST use `EntityLookup` component:
+- **NEVER** a `<select>` dropdown
+- **NEVER** a `<input type="text">`
+- **A `<select>` loaded from API state is NOT a substitute for EntityLookup**
+
+See `smartstack-frontend.md` section 6 for the full EntityLookup pattern. Backend GetAll endpoints MUST support `?search=` parameter (enables EntityLookup on frontend).
+
+---
+
+## Forms: ZERO Modals/Popups/Drawers/Slide-overs
+
+**ALL forms are full pages with their own URL:**
+- Create forms: route `/{module}/create`
+- Edit forms: route `/{module}/:id/edit`
+- NEVER embed forms as drawers, panels, or slide-overs
+- Back button with `navigate(-1)` on every form page
+
+---
+
+## Detail Pages: Tab Behavior (CRITICAL)
+
+**Tabs MUST switch content LOCALLY via `setActiveTab()` — NEVER `navigate()` to another page.**
+
+Sub-resource data (e.g., employee's leaves) loads inline via API call filtered by parent entity ID. See `smartstack-frontend.md` section 3 "Tab Behavior Rules".
+
+---
+
+## Tests (MANDATORY)
+
+Generate form tests as co-located files:
+- `EntityCreatePage.test.tsx` (next to CreatePage.tsx)
+- `EntityEditPage.test.tsx` (next to EditPage.tsx)
+
+Cover: rendering, validation, submit, pre-fill, navigation, errors. See `smartstack-frontend.md` section 8 for test templates.
+
+---
+
+## Section-Level Routes (if sections exist)
+
+**SECTION PERMISSIONS:** After calling `MCP generate_permissions` for the module navRoute (2 segments: `{app}.{module}`), also call it for EACH section navRoute (3 segments: `{app}.{module}.{section}`)
+
+**SECTION ROUTES:** After generating module routes, add section child routes to the module's `children` array. Wire `PermissionGuard` for section routes with section-level permissions.
+
+---
+
+## Sub-Resource Handling
+
+If a section controller has sub-resource endpoints (e.g., `[HttpGet("types")]` for LeaveTypes inside LeavesController), you MUST EITHER:
+1. Create dedicated frontend pages for the sub-resource (ListPage, CreatePage, EditPage) with routes wired in App.tsx, OR
+2. NOT include any `navigate()` button that links to those sub-resource pages
+
+**Prefer separate controllers** with `[NavRoute(..., Suffix = "types")]` — see `smartstack-api.md` Sub-Resource Pattern. A dead link (navigate to a route with no page) is a BLOCKING issue (POST-CHECK 42).
+
+---
+
+## I18n (Translations)
+
+Generate i18n JSON files for all 4 languages (fr, en, it, de):
+- Location: `src/i18n/locales/{lang}/{module}.json`
+- Keys: `actions`, `labels`, `errors`, `validation`, `columns`, `form`, `messages`, `empty`
+- ALL `t()` calls MUST use namespace prefix + fallback: `t('ns:key', 'Default text')`
+
+**CRITICAL:** After creating i18n JSON files, register EACH new namespace in the i18n config file (config.ts/index.ts/i18n.ts). Unregistered namespaces → `useTranslation(['module'])` returns empty strings at runtime. POST-CHECK 45 validates this.
+
+---
+
+## Folder Structure
+
+MUST use: `src/pages/{App}/{Module}/` hierarchy (NOT flat).
+
+All pages must follow: **hooks → useEffect(load) → loading state → error state → content**
+
+Use **CSS variables ONLY** for styling — hardcoded Tailwind colors are BLOCKING (POST-CHECK 13).

package/templates/skills/apex/references/execution-layer1-rules.md

@@ -0,0 +1,96 @@
+# Layer 1: Execution Rules — Application + API + Seed Data
+
+> **Loaded by:** step-03-execute.md (section: Layer 1)
+> **Purpose:** Critical rules for Layer 1 execution — NavRoute, permissions, validators, code generation, frontend patterns.
+
+---
+
+## NavRoute and Permission Kebab-Case (CRITICAL)
+
+**ALL NavRoute segments and permission codes MUST use kebab-case for multi-word identifiers.**
+
+Root cause (test-apex-007): Controllers had `[NavRoute("humanresources.employees")]` instead of `[NavRoute("human-resources.employees")]`. This mismatched seed data routes and permission codes, causing 404s and permission denials at runtime.
+
+**Rules:**
+- NavRoute: `human-resources.employees` (NEVER `humanresources.employees`)
+- Permissions: `human-resources.employees.read` (segments MATCH NavRoute exactly)
+- Seed data codes: `human-resources` (NEVER `humanresources`)
+- C# class names stay PascalCase (`HumanResourcesController`) — only route/permission strings use kebab-case
+- POST-CHECKs 41 + 48 validate this. Fix BEFORE committing.
+
+---
+
+## Controller Route Attribute (BLOCKING)
+
+**Controllers with `[NavRoute]` must NOT have `[Route]` attribute.**
+
+Root cause (test-apex-007): ALL 7 controllers had BOTH `[Route("api/...")]` AND `[NavRoute("...")]`. In SmartStack, `[NavRoute]` resolves routes dynamically from Navigation entities in the database at startup. Having `[Route]` alongside causes route conflicts → all endpoints return 404.
+
+**Rules:**
+- `[NavRoute("app.module")]` is the ONLY route attribute needed on controllers
+- **FORBIDDEN:** `[Route("api/human-resources/employees")]` alongside `[NavRoute]`
+- **FORBIDDEN:** `[Route("api/[controller]")]` alongside `[NavRoute]`
+- If generating via MCP `scaffold_extension` with `navRoute` option → output is correct (NavRoute only)
+- If generating via `/controller` skill → verify NO `[Route]` is added
+- POST-CHECK 50 validates this. Fix BEFORE committing.
+
+---
+
+## Validators DI Registration (CRITICAL)
+
+After creating validators, they MUST be registered in DI. Without registration, `[FromBody]` DTOs are never validated.
+
+```csharp
+In DependencyInjection.cs (or ServiceCollectionExtensions.cs):
+  services.AddValidatorsFromAssemblyContaining<Create{Entity}DtoValidator>();
+```
+
+POST-CHECK 46 validates this. If validators exist but no DI registration → BLOCKING.
+
+---
+
+## Date Fields — Use DateOnly (CRITICAL)
+
+**ALL date-only fields in DTOs MUST use `DateOnly`, NEVER `string`.**
+
+Root cause (test-apex-007): WorkLog DTO had `string Date` instead of `DateOnly Date`. This causes: no date validation, inconsistent date formats, parsing errors.
+
+**Type mapping for DTOs:**
+
+| Domain type | DTO type | Example |
+|-------------|----------|---------|
+| `DateTime` | `DateTime` | `CreatedAt`, `UpdatedAt` |
+| Date-only field | `DateOnly` | `Date`, `StartDate`, `EndDate`, `BirthDate` |
+| `string` for date | **FORBIDDEN** | Never use `string` for dates |
+| `DateTime` for date-only | **Avoid** | Use `DateOnly` when no time component needed |
+
+POST-CHECK 47 validates this. If a DTO has `string` type for a property named `*Date*` → BLOCKING.
+
+---
+
+## Code Generation (if entities have codePattern != "manual")
+
+For each entity with auto-generated code pattern (from feature.json or step-02 decisions):
+
+```
+1. Create CodePatternConfig for the entity (strategy, prefix, digits from codePattern)
+2. Register ICodeGenerator<TEntity> in DependencyInjection.cs (Infrastructure layer)
+   → See references/code-generation.md for DI registration pattern
+3. Update CreateDto: REMOVE Code property (auto-generated, not user-provided)
+4. Update CreateDtoValidator: REMOVE Code regex rule (not in DTO anymore)
+5. Update service CreateAsync: inject ICodeGenerator<TEntity>, call NextCodeAsync()
+   → Code is auto-generated BEFORE entity creation
+   → See references/code-generation.md for service integration pattern
+6. Keep Code in ResponseDto (returned to frontend after creation)
+7. Keep Code in UpdateDto ONLY if code is mutable (rare — discuss with user)
+```
+
+**CRITICAL:** If `codePattern.strategy == "manual"` (or no codePattern), keep the current behavior: Code stays in CreateDto, user provides it, validator has regex rule.
+
+---
+
+## Sequential vs Parallel Execution
+
+**If economy_mode:** Execute each item from the plan sequentially using skills and MCP.
+
+**If NOT economy_mode:** See `references/agent-teams-protocol.md` for parallel team-based execution with exec-backend and exec-frontend teammates.

package/templates/skills/apex/references/initialization-challenge-flow.md

@@ -0,0 +1,110 @@
+# Initialization — Challenge Flow & Hierarchy Definition
+
+> **Loaded by:** step-00-init.md (sections 4-5)
+> **Purpose:** Detailed flow for challenging user hierarchy assumptions and defining the 4-level navigation structure.
+
+---
+
+## Challenge Questions Reference
+
+> **Complete question templates with validation:**
+> Load `references/challenge-questions.md` for the actual YAML question blocks and validation logic.
+
+---
+
+## 4-Level Navigation Hierarchy (BLOCKING RULE)
+
+SmartStack uses a **4-level navigation hierarchy:**
+- **Level 1: Application** — e.g., "HumanResources", "ProjectManagement"
+- **Level 2: Module** — e.g., "Employees", "Timesheet"
+- **Level 3: Section** — e.g., "List", "Dashboard", "Approval"
+- **Level 4: Resource** — e.g., "Export", "Settings" (optional)
+
+**BLOCKING RULE:** Every module MUST have at least one section. A module without sections produces an incomplete navigation tree, broken seed data, and missing frontend routes.
+
+---
+
+## Step 4: Validate Application Level (4a)
+
+Load application question from `references/challenge-questions.md` section 4a.
+
+**If `{app_name}` was clearly inferred from the task description:**
+- Skip question, use inferred value
+
+**If unclear:**
+- Present question with best guess as recommended option
+- Options:
+  1. "Inferred app name (Recommended)" + description
+  2. "New application" + option to create
+  3. "Existing application" + option to select from scanned projects
+- If "New application": collect `{app_name}`, `{app_code}`, `{app_icon}`, `{app_labels}` (4 langs)
+- If "Existing application": scan `**/Seeding/Data/**/NavigationApplicationSeedData.cs` and present discovered apps
+
+---
+
+## Step 4b: Validate Module Level
+
+Load module question from `references/challenge-questions.md` section 4b.
+
+**If `{module_code}` was clearly inferred:**
+- Skip question
+
+**If unclear:**
+- Present question with best guess(es) as options
+- Options:
+  1. "Inferred module code (Recommended)" + from task description
+  2. "Alternative suggestions" + based on keywords
+- User selects or enters custom value
+- Store as `{module_code}` (kebab-case)
+
+---
+
+## Step 4c: Define Sections (MANDATORY — at least one)
+
+Load section questions from `references/challenge-questions.md` section 4c.
+
+**BLOCKING VALIDATION:** Sections list MUST contain at least one entry before proceeding.
+
+Infer section suggestions from:
+1. Task description (extract nouns/concepts that suggest functional sub-areas)
+2. PRD/feature.json if available (module.sections)
+3. Common patterns: "list" (default for simple CRUD), "dashboard", "settings", "reports"
+
+**Question format:**
+```yaml
+question: "What sections should the module '{module_code}' contain?
+           (Select at least one — use 'Other' to add custom sections)"
+options:
+  - label: "<inferred section 1>"
+    description: "Primary functional area based on module purpose"
+  - label: "<inferred section 2>"
+    description: "Secondary functional area"
+  - label: "<inferred section 3>"
+    description: "Additional area inferred from context"
+multiSelect: true
+```
+
+**Validation (BLOCKING):**
+```
+IF {sections}.length == 0:
+  DISPLAY: "Every module must have at least one section."
+  → Re-ask the sections question
+  → DO NOT proceed to next step
+```
+
+**Store for each section:**
+```yaml
+sections:
+  - code: "section-kebab"
+    labels: { fr: "...", en: "...", it: "...", de: "..." }
+    icon: "LucideIconName"
+    displayOrder: 10
+```
+
+---
+
+## Delegate Mode Skip (if -d)
+
+When `/ralph-loop` invokes `/apex -d {prd_path}`, ALL hierarchy is extracted from the PRD file:
+- Skip sections 2-4 (no interactive questions)
+- Jump directly to section 3 (MCP verify)