@atlashub/smartstack-cli 3.38.0 → 3.39.0

package/templates/skills/application/steps/step-04-backend.md

@@ -1,174 +1,174 @@
----
-name: step-04-backend
-description: Generate backend code using MCP scaffold_extension
-prev_step: steps/step-03-roles.md
-next_step: steps/step-05-frontend.md
----
-
-# Step 4: Backend Generation
-
-## MANDATORY EXECUTION RULES
-
-- ALWAYS use MCP `scaffold_extension` tool - NEVER use templates
-- ALWAYS generate Entity + Service + Controller as a unit
-- NEVER skip controller generation - API is required
-- YOU ARE AN ORCHESTRATOR calling MCP, not a generator
-- **NEVER use Write on appsettings*.json** - ALWAYS use Edit (see _resources/config-safety.md)
-- **Replace secret VALUES with `<CONFIGURE_HERE>`** - NEVER delete keys or sections
-
-## YOUR TASK
-
-Call the SmartStack MCP `scaffold_extension` tool with type "feature" to generate:
-1. Domain Entity with EF Configuration
-2. Application Service (Interface + Implementation)
-3. API Controller with NavRoute attribute
-4. DTOs (Response, Create, Update)
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{level}` | application, module, or section |
-| `{code}` | kebab-case identifier |
-| `{full_path}` | Complete navigation path (navRoute) |
-| `{labels}` | Object with fr, en, it, de |
-
----
-
-## EXECUTION SEQUENCE
-
-### 1. Derive Entity Name
-
-Convert `{code}` to PascalCase for entity name:
-
-```
-code: "products"        → entityName: "Product"
-code: "order-items"     → entityName: "OrderItem"
-code: "user-profiles"   → entityName: "UserProfile"
-```
-
-### 2. Determine Table Prefix and Controller Folder
-
-See [references/backend-table-prefix-mapping.md](../references/backend-table-prefix-mapping.md) for:
-- Table prefix priority (feature.json vs. fallback)
-- Application-to-prefix mapping table
-- Feature.json detection and extraction
-- Controller folder organization
-- Store `{controller_folder}` from the mapping
-
-### 3. Call MCP scaffold_extension
-
-```
-Tool: mcp__smartstack__scaffold_extension
-Args:
-  type: "feature"
-  name: "{entityName}"  # PascalCase
-  options:
-    navRoute: "{full_path}"
-    tablePrefix: "{prefix}"
-    schema: "core"
-    withDtos: true
-    withValidation: true
-    withRepository: false  # Use service pattern
-    skipComponent: true    # Frontend in next step
-    dryRun: false
-```
-
-### 4. Parse MCP Response
-
-The tool generates (paths organized by navRoute hierarchy `{application}.{module}`):
-- `Domain/{Application}/{Module}/{EntityName}.cs` - Entity with BaseEntity
-- `Infrastructure/Persistence/Configurations/{Application}/{Module}/{EntityName}Configuration.cs` - EF Config
-- `Application/Common/Interfaces/I{EntityName}Service.cs` - Service Interface
-- `Infrastructure/Services/{Application}/{Module}/{EntityName}Service.cs` - Service Implementation
-- `Api/Controllers/{controller_folder}/{Application}/{EntityName}Controller.cs` - REST Controller
-- `Application/{Application}/{Module}/DTOs/{EntityName}ResponseDto.cs` - Response DTO
-- `Application/{Application}/{Module}/DTOs/Create{EntityName}Dto.cs` - Create request
-- `Application/{Application}/{Module}/DTOs/Update{EntityName}Dto.cs` - Update request
-
-### 5-7. Present Output, Entity Seeding & Store Info
-
-See [references/backend-seeding-and-dto-output.md](../references/backend-seeding-and-dto-output.md) for:
-- Output formatting by layer (Domain, Infrastructure, Application, API)
-- Entity seeding questions and responses
-- Entity info storage for frontend generation
-
----
-
-## CONTROLLER NAVROUTE AND FOLDER HIERARCHY
-
-See [references/backend-controller-hierarchy.md](../references/backend-controller-hierarchy.md) for the complete reference:
-- Controller file organization (Admin/Business/Support/User folders)
-- Context-to-folder mapping table
-- NavRoute attribute C# template with RequirePermission
-
----
-
-## MCP RESPONSE HANDLING
-
-### Success Case
-
-If MCP returns successfully:
-- Display all generated files
-- Show DbSet and DI registration instructions
-- Ask about entity seeding (section 6)
-- Store entity info for frontend
-- Proceed to step-05-frontend.md
-
-### Error Case
-
-If MCP call fails:
-- Display error message
-- Suggest checking entity name format
-- Do NOT proceed automatically
-
----
-
-## POST-GENERATION VERIFICATION (MANDATORY)
-
-**Before proceeding to step-05, run ALL checks.**
-
-See [references/backend-verification.md](../references/backend-verification.md) for the complete verification checklist:
-
-| Check | Type | What |
-|-------|------|------|
-| 1. Backend Build | BLOCKING | `dotnet build --no-restore` must succeed |
-| 2. DbSet Registration | BLOCKING | `DbSet<{EntityName}>` in DbContext |
-| 3. DI Registration | BLOCKING | `I{EntityName}Service` in DependencyInjection.cs |
-| 4. RequirePermission | BLOCKING | All HTTP actions have `[RequirePermission]` |
-| 5. Entity Configuration | BLOCKING | Table prefix, HasKey, HasIndex |
-| 5b. Seeding Infrastructure | BLOCKING (first entity) | SeedConstants + DevDataSeeder + DI |
-| 5c. SqlObjects Directory | BLOCKING (first entity) | SqlObjectHelper + Functions/ + .csproj EmbeddedResource |
-| 6. Convention Validation | RECOMMENDED | `mcp__smartstack__validate_conventions` |
-
-IF any BLOCKING check fails: Fix before proceeding to step-05.
-
----
-
-## SUCCESS METRICS
-
-- MCP scaffold_extension called successfully
-- Entity, Service, Controller generated
-- DTOs generated
-- NavRoute attribute included
-- Entity seeding offered to user (SeedData.cs + DevDataSeeder if accepted)
-- Entity info stored for frontend
-- Post-generation verification passed (all 7 checks: 5 original + 5b Seeding + 5c SqlObjects)
-- Proceeded to step-05-frontend.md
-
-## FAILURE MODES
-
-- MCP call failed (display error, stop)
-- Invalid entity name (must be PascalCase)
-- Invalid navRoute format
-
----
-
-## NEXT STEP
-
-After backend code is generated and entity seeding is handled,
-proceed to `./step-05-frontend.md`
+---
+name: step-04-backend
+description: Generate backend code using MCP scaffold_extension
+prev_step: steps/step-03-roles.md
+next_step: steps/step-05-frontend.md
+---
+
+# Step 4: Backend Generation
+
+## MANDATORY EXECUTION RULES
+
+- ALWAYS use MCP `scaffold_extension` tool - NEVER use templates
+- ALWAYS generate Entity + Service + Controller as a unit
+- NEVER skip controller generation - API is required
+- YOU ARE AN ORCHESTRATOR calling MCP, not a generator
+- **NEVER use Write on appsettings*.json** - ALWAYS use Edit (see _resources/config-safety.md)
+- **Replace secret VALUES with `<CONFIGURE_HERE>`** - NEVER delete keys or sections
+
+## YOUR TASK
+
+Call the SmartStack MCP `scaffold_extension` tool with type "feature" to generate:
+1. Domain Entity with EF Configuration
+2. Application Service (Interface + Implementation)
+3. API Controller with NavRoute attribute
+4. DTOs (Response, Create, Update)
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+| Variable | Description |
+|----------|-------------|
+| `{level}` | application, module, section, or resource |
+| `{code}` | kebab-case identifier |
+| `{full_path}` | Complete navigation path (navRoute) |
+| `{labels}` | Object with fr, en, it, de |
+
+---
+
+## EXECUTION SEQUENCE
+
+### 1. Derive Entity Name
+
+Convert `{code}` to PascalCase for entity name:
+
+```
+code: "products"        → entityName: "Product"
+code: "order-items"     → entityName: "OrderItem"
+code: "user-profiles"   → entityName: "UserProfile"
+```
+
+### 2. Determine Table Prefix and Controller Folder
+
+See [references/backend-table-prefix-mapping.md](../references/backend-table-prefix-mapping.md) for:
+- Table prefix priority (feature.json vs. fallback)
+- Application-to-prefix mapping table
+- Feature.json detection and extraction
+- Controller folder organization
+- Store `{controller_folder}` from the mapping
+
+### 3. Call MCP scaffold_extension
+
+```
+Tool: mcp__smartstack__scaffold_extension
+Args:
+  type: "feature"
+  name: "{entityName}"  # PascalCase
+  options:
+    navRoute: "{full_path}"
+    tablePrefix: "{prefix}"
+    schema: "core"
+    withDtos: true
+    withValidation: true
+    withRepository: false  # Use service pattern
+    skipComponent: true    # Frontend in next step
+    dryRun: false
+```
+
+### 4. Parse MCP Response
+
+The tool generates (paths organized by navRoute hierarchy `{application}.{module}`):
+- `Domain/{Application}/{Module}/{EntityName}.cs` - Entity with BaseEntity
+- `Infrastructure/Persistence/Configurations/{Application}/{Module}/{EntityName}Configuration.cs` - EF Config
+- `Application/Common/Interfaces/I{EntityName}Service.cs` - Service Interface
+- `Infrastructure/Services/{Application}/{Module}/{EntityName}Service.cs` - Service Implementation
+- `Api/Controllers/{controller_folder}/{Application}/{EntityName}Controller.cs` - REST Controller
+- `Application/{Application}/{Module}/DTOs/{EntityName}ResponseDto.cs` - Response DTO
+- `Application/{Application}/{Module}/DTOs/Create{EntityName}Dto.cs` - Create request
+- `Application/{Application}/{Module}/DTOs/Update{EntityName}Dto.cs` - Update request
+
+### 5-7. Present Output, Entity Seeding & Store Info
+
+See [references/backend-seeding-and-dto-output.md](../references/backend-seeding-and-dto-output.md) for:
+- Output formatting by layer (Domain, Infrastructure, Application, API)
+- Entity seeding questions and responses
+- Entity info storage for frontend generation
+
+---
+
+## CONTROLLER NAVROUTE AND FOLDER HIERARCHY
+
+See [references/backend-controller-hierarchy.md](../references/backend-controller-hierarchy.md) for the complete reference:
+- Controller file organization (Admin/Business/Support/User folders)
+- Context-to-folder mapping table
+- NavRoute attribute C# template with RequirePermission
+
+---
+
+## MCP RESPONSE HANDLING
+
+### Success Case
+
+If MCP returns successfully:
+- Display all generated files
+- Show DbSet and DI registration instructions
+- Ask about entity seeding (section 6)
+- Store entity info for frontend
+- Proceed to step-05-frontend.md
+
+### Error Case
+
+If MCP call fails:
+- Display error message
+- Suggest checking entity name format
+- Do NOT proceed automatically
+
+---
+
+## POST-GENERATION VERIFICATION (MANDATORY)
+
+**Before proceeding to step-05, run ALL checks.**
+
+See [references/backend-verification.md](../references/backend-verification.md) for the complete verification checklist:
+
+| Check | Type | What |
+|-------|------|------|
+| 1. Backend Build | BLOCKING | `dotnet build --no-restore` must succeed |
+| 2. DbSet Registration | BLOCKING | `DbSet<{EntityName}>` in DbContext |
+| 3. DI Registration | BLOCKING | `I{EntityName}Service` in DependencyInjection.cs |
+| 4. RequirePermission | BLOCKING | All HTTP actions have `[RequirePermission]` |
+| 5. Entity Configuration | BLOCKING | Table prefix, HasKey, HasIndex |
+| 5b. Seeding Infrastructure | BLOCKING (first entity) | SeedConstants + DevDataSeeder + DI |
+| 5c. SqlObjects Directory | BLOCKING (first entity) | SqlObjectHelper + Functions/ + .csproj EmbeddedResource |
+| 6. Convention Validation | RECOMMENDED | `mcp__smartstack__validate_conventions` |
+
+IF any BLOCKING check fails: Fix before proceeding to step-05.
+
+---
+
+## SUCCESS METRICS
+
+- MCP scaffold_extension called successfully
+- Entity, Service, Controller generated
+- DTOs generated
+- NavRoute attribute included
+- Entity seeding offered to user (SeedData.cs + DevDataSeeder if accepted)
+- Entity info stored for frontend
+- Post-generation verification passed (all 7 checks: 5 original + 5b Seeding + 5c SqlObjects)
+- Proceeded to step-05-frontend.md
+
+## FAILURE MODES
+
+- MCP call failed (display error, stop)
+- Invalid entity name (must be PascalCase)
+- Invalid navRoute format
+
+---
+
+## NEXT STEP
+
+After backend code is generated and entity seeding is handled,
+proceed to `./step-05-frontend.md`

package/templates/skills/application/steps/step-05-frontend.md

@@ -131,7 +131,7 @@ See [references/frontend-i18n-and-output.md](../references/frontend-i18n-and-out
 ## ROUTING RULES
 
 See [references/frontend-verification.md](../references/frontend-verification.md) for detailed routing rules with code examples:
-- **Rule 1:** Routes MUST be inside Layout wrappers (BusinessLayout, AdminLayout, UserLayout)
+- **Rule 1:** Routes MUST be inside the AppLayout wrapper
 - **Rule 2:** Use NESTED routes (not flat) — flat routes bypass layout and break the shell
 
 ---

package/templates/skills/application/templates-frontend.md

@@ -543,15 +543,15 @@ const applicationRoutes: ApplicationRouteExtensions = {
 
 | Application key | Injected into Layout | Standard path | Tenant path |
 |-----------------|---------------------|---------------|-------------|
-| `administration` | `AdminLayout` | `/administration/...` | `/t/:slug/administration/...` |
-| `{application}` | `{Application}Layout` | `/{application}/...` | `/t/:slug/{application}/...` |
-| `myspace` | `UserLayout` | `/myspace/...` | `/t/:slug/myspace/...` |
+| `administration` | `AppLayout` | `/administration/...` | `/t/:slug/administration/...` |
+| `{application}` | `AppLayout` | `/{application}/...` | `/t/:slug/{application}/...` |
+| `myspace` | `AppLayout` | `/myspace/...` | `/t/:slug/myspace/...` |
 
 ### Pattern B: JSX Routes (inside Layout wrapper)
 
 > **Legacy pattern** — only used if App.tsx was manually restructured with JSX `<Route>` elements.
 
-SmartStack layouts (`AdminLayout`, `BusinessLayout`, `UserLayout`) provide the application shell: **header with AvatarMenu**, sidebar, navigation. They render child pages via React Router's `<Outlet />`.
+The unified `AppLayout` provides the application shell: **header with AvatarMenu**, sidebar, navigation. It renders child pages via React Router's `<Outlet />`.
 
 **If routes are placed OUTSIDE the layout wrapper, the shell (header, sidebar, AvatarMenu) will NOT render. The page appears "naked" without any navigation.**
 
@@ -559,9 +559,9 @@ SmartStack layouts (`AdminLayout`, `BusinessLayout`, `UserLayout`) provide the a
 
 1. Open `App.tsx`
 2. Find the existing layout route for the target application:
-   - `administration` → `<Route path="/administration" element={<AdminLayout />}>`
-   - `{application}` → `<Route path="/{application}" element={<{Application}Layout />}>`
-   - `myspace` → `<Route path="/myspace" element={<UserLayout />}>`
+   - `administration` → `<Route path="/administration" element={<AppLayout />}>`
+   - `{application}` → `<Route path="/{application}" element={<AppLayout />}>`
+   - `myspace` → `<Route path="/myspace" element={<AppLayout />}>`
 3. Add the new routes **INSIDE** that `<Route>` block
 4. If a tenant-prefixed block exists (`/t/:slug/...`), add the routes there too