@atlashub/smartstack-cli 3.38.0 → 3.39.0

package/templates/skills/application/steps/step-03-roles.md

@@ -1,182 +1,182 @@
----
-name: step-03-roles
-description: Generate application roles and role-permission mappings using MCP scaffold_role_permissions (with fallback)
-prev_step: steps/step-02-permissions.md
-next_step: steps/step-03b-provider.md
----
-
-# Step 3: Application Roles & Role-Permission Mapping
-
-## MANDATORY EXECUTION RULES
-
-- For **client projects** (`seeding_strategy = "provider"`): Generate ApplicationRolesSeedData.cs and module role mappings
-- For **core projects** (`seeding_strategy = "hasdata"`): Use RolePermissionConfiguration.cs
-- PREFER MCP `scaffold_role_permissions` tool as the primary method
-- If MCP is unavailable or the call fails, use the FALLBACK PROCEDURE below
-- ALWAYS assign permissions to default roles
-- NEVER leave permissions without role assignments
-- ALWAYS WRITE generated code to the actual files
-
-## YOUR TASK
-
-For **client projects**:
-1. **ApplicationRolesSeedData.cs** (once per application) — defines the 4 application-scoped roles
-2. **{Module}RolePermissionSeedData.cs** (per module) — maps permissions to roles by Code
-
-For **core projects**:
-1. RolePermissionConfiguration.cs HasData() entries
-2. Default role assignments (SuperAdmin, PlatformAdmin, TenantAdmin, StandardUser)
-3. Application-scoped role assignments (Admin, Manager, Contributor, Viewer)
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{full_path}` | Complete navigation path (navRoute) |
-| `{level}` | application, module, or section |
-| `{permission_guids}` | GUIDs for generated permissions |
-| `{mcp_available}` | Boolean - MCP connectivity status |
-| `{project_type}` | "core" or "client" |
-| `{seeding_strategy}` | "hasdata" or "provider" |
-
----
-
-## EXECUTION SEQUENCE (MCP Primary)
-
-### 1. Determine Default Role Assignments
-
-See [references/roles-client-project-handling.md](../references/roles-client-project-handling.md) for:
-- Default role mapping table by application prefix
-- ApplicationRolesSeedData.cs requirements (once per application)
-- {Module}RolePermissionSeedData.cs requirements (per module)
-
-### 2. Call MCP scaffold_role_permissions
-
-```
-Tool: mcp__smartstack__scaffold_role_permissions
-Args:
-  navRoute: "{full_path}"
-  roles:
-    platformAdmin: ["read", "create", "update", "delete"]  # Adjust based on context
-    tenantAdmin: ["read", "create", "update"]              # Adjust based on context
-    standardUser: ["read"]                                  # Adjust based on context
-  includeWildcard: true
-```
-
-### 3. Parse MCP Response
-
-The tool returns:
-- RolePermissionConfiguration.cs HasData() entries
-- Permission ID variable references
-- Role ID variable references
-
-### 4. Write Code to Files
-
-**CRITICAL:** WRITE the generated code to the actual RolePermissionConfiguration.cs file.
-
-### 5. Present Summary
-
-```markdown
-## Role-Permission Mappings
-
-| Role | Permissions |
-|------|-------------|
-| SuperAdmin | `{full_path}.*` (via wildcard) |
-| PlatformAdmin | `{full_path}.read`, `.create`, `.update`, `.delete` |
-| TenantAdmin | `{full_path}.read`, `.create`, `.update` |
-| StandardUser | `{full_path}.read` |
-```
-
-### 6. Confirm with User (Optional)
-
-```yaml
-questions:
-  - header: "Role Access"
-    question: "Adjust role permissions for {full_path}?"
-    options:
-      - label: "Keep defaults (Recommended)"
-        description: "PlatformAdmin: CRUD, TenantAdmin: CRU, StandardUser: R"
-      - label: "All roles full access"
-        description: "All roles get full CRUD access"
-      - label: "Custom"
-        description: "I'll specify custom permissions"
-    multiSelect: false
-```
-
----
-
-## MCP RESPONSE HANDLING
-
-### Success Case
-
-If MCP returns successfully:
-- Write RolePermission HasData code to file
-- Show role-permission summary table
-- Proceed to step-04-backend.md
-
-### Error Case
-
-If MCP call fails or `{mcp_available}` = false:
-- Log the error for reference
-- Proceed to FALLBACK PROCEDURE below
-- Do NOT stop the workflow
-
----
-
-## CLIENT PROJECT HANDLING
-
-> **Condition:** `{seeding_strategy}` = "provider"
-
-See [references/roles-client-project-handling.md](../references/roles-client-project-handling.md) for:
-- ApplicationRolesSeedData.cs creation (once per application)
-- {Module}RolePermissionSeedData.cs creation (per module)
-- Role code naming and GUID generation rules
-- Detection of existing ApplicationRolesSeedData.cs
-
----
-
-## FALLBACK PROCEDURE (When MCP Unavailable)
-
-See [references/roles-fallback-procedure.md](../references/roles-fallback-procedure.md) for the complete 7-step fallback:
-- **F1:** Read existing RolePermissionConfiguration.cs to determine state
-- **F2:** Read role GUIDs (system-level and application-scoped)
-- **F3:** Determine default mappings based on application prefix
-- **F4:** Generate RolePermission HasData entries using permission GUIDs
-- **F5:** Write code to RolePermissionConfiguration.cs (CRITICAL: WRITE not display)
-- **F6:** Present summary
-- **F7:** Offer user adjustment option
-
----
-
-## SUCCESS METRICS
-
-**For client projects:**
-- ApplicationRolesSeedData.cs created (once per application)
-- {Module}RolePermissionSeedData.cs created with role-permission mappings
-- All 4 application roles defined with valid Code values
-- Proceeded to step-03b-provider.md
-
-**For core projects:**
-- Role-permission mappings generated (via MCP or fallback)
-- RolePermissionConfiguration.cs WRITTEN with new entries
-- All default roles have appropriate access
-- Proceeded to step-04-backend.md
-
-## FAILURE MODES
-
-- Permission GUIDs not available from step-02 (return to step-02)
-- Role GUIDs not found in project (ask user, use well-known defaults)
-- Invalid navRoute format (return to step-00)
-
----
-
-## NEXT STEP
-
-After role-permission mappings are generated (via MCP or fallback) and written to files,
-proceed to `./step-03b-provider.md`
-
-> **Note:** step-03b will automatically skip if `{seeding_strategy}` = "hasdata" and proceed directly to step-04-backend.
+---
+name: step-03-roles
+description: Generate application roles and role-permission mappings using MCP scaffold_role_permissions (with fallback)
+prev_step: steps/step-02-permissions.md
+next_step: steps/step-03b-provider.md
+---
+
+# Step 3: Application Roles & Role-Permission Mapping
+
+## MANDATORY EXECUTION RULES
+
+- For **client projects** (`seeding_strategy = "provider"`): Generate ApplicationRolesSeedData.cs and module role mappings
+- For **core projects** (`seeding_strategy = "hasdata"`): Use RolePermissionConfiguration.cs
+- PREFER MCP `scaffold_role_permissions` tool as the primary method
+- If MCP is unavailable or the call fails, use the FALLBACK PROCEDURE below
+- ALWAYS assign permissions to default roles
+- NEVER leave permissions without role assignments
+- ALWAYS WRITE generated code to the actual files
+
+## YOUR TASK
+
+For **client projects**:
+1. **ApplicationRolesSeedData.cs** (once per application) — defines the 4 application-scoped roles
+2. **{Module}RolePermissionSeedData.cs** (per module) — maps permissions to roles by Code
+
+For **core projects**:
+1. RolePermissionConfiguration.cs HasData() entries
+2. Default role assignments (SuperAdmin, PlatformAdmin, TenantAdmin, StandardUser)
+3. Application-scoped role assignments (Admin, Manager, Contributor, Viewer)
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+| Variable | Description |
+|----------|-------------|
+| `{full_path}` | Complete navigation path (navRoute) |
+| `{level}` | application, module, section, or resource |
+| `{permission_guids}` | GUIDs for generated permissions |
+| `{mcp_available}` | Boolean - MCP connectivity status |
+| `{project_type}` | "core" or "client" |
+| `{seeding_strategy}` | "hasdata" or "provider" |
+
+---
+
+## EXECUTION SEQUENCE (MCP Primary)
+
+### 1. Determine Default Role Assignments
+
+See [references/roles-client-project-handling.md](../references/roles-client-project-handling.md) for:
+- Default role mapping table by application prefix
+- ApplicationRolesSeedData.cs requirements (once per application)
+- {Module}RolePermissionSeedData.cs requirements (per module)
+
+### 2. Call MCP scaffold_role_permissions
+
+```
+Tool: mcp__smartstack__scaffold_role_permissions
+Args:
+  navRoute: "{full_path}"
+  roles:
+    platformAdmin: ["read", "create", "update", "delete"]  # Adjust based on context
+    tenantAdmin: ["read", "create", "update"]              # Adjust based on context
+    standardUser: ["read"]                                  # Adjust based on context
+  includeWildcard: true
+```
+
+### 3. Parse MCP Response
+
+The tool returns:
+- RolePermissionConfiguration.cs HasData() entries
+- Permission ID variable references
+- Role ID variable references
+
+### 4. Write Code to Files
+
+**CRITICAL:** WRITE the generated code to the actual RolePermissionConfiguration.cs file.
+
+### 5. Present Summary
+
+```markdown
+## Role-Permission Mappings
+
+| Role | Permissions |
+|------|-------------|
+| SuperAdmin | `{full_path}.*` (via wildcard) |
+| PlatformAdmin | `{full_path}.read`, `.create`, `.update`, `.delete` |
+| TenantAdmin | `{full_path}.read`, `.create`, `.update` |
+| StandardUser | `{full_path}.read` |
+```
+
+### 6. Confirm with User (Optional)
+
+```yaml
+questions:
+  - header: "Role Access"
+    question: "Adjust role permissions for {full_path}?"
+    options:
+      - label: "Keep defaults (Recommended)"
+        description: "PlatformAdmin: CRUD, TenantAdmin: CRU, StandardUser: R"
+      - label: "All roles full access"
+        description: "All roles get full CRUD access"
+      - label: "Custom"
+        description: "I'll specify custom permissions"
+    multiSelect: false
+```
+
+---
+
+## MCP RESPONSE HANDLING
+
+### Success Case
+
+If MCP returns successfully:
+- Write RolePermission HasData code to file
+- Show role-permission summary table
+- Proceed to step-04-backend.md
+
+### Error Case
+
+If MCP call fails or `{mcp_available}` = false:
+- Log the error for reference
+- Proceed to FALLBACK PROCEDURE below
+- Do NOT stop the workflow
+
+---
+
+## CLIENT PROJECT HANDLING
+
+> **Condition:** `{seeding_strategy}` = "provider"
+
+See [references/roles-client-project-handling.md](../references/roles-client-project-handling.md) for:
+- ApplicationRolesSeedData.cs creation (once per application)
+- {Module}RolePermissionSeedData.cs creation (per module)
+- Role code naming and GUID generation rules
+- Detection of existing ApplicationRolesSeedData.cs
+
+---
+
+## FALLBACK PROCEDURE (When MCP Unavailable)
+
+See [references/roles-fallback-procedure.md](../references/roles-fallback-procedure.md) for the complete 7-step fallback:
+- **F1:** Read existing RolePermissionConfiguration.cs to determine state
+- **F2:** Read role GUIDs (system-level and application-scoped)
+- **F3:** Determine default mappings based on application prefix
+- **F4:** Generate RolePermission HasData entries using permission GUIDs
+- **F5:** Write code to RolePermissionConfiguration.cs (CRITICAL: WRITE not display)
+- **F6:** Present summary
+- **F7:** Offer user adjustment option
+
+---
+
+## SUCCESS METRICS
+
+**For client projects:**
+- ApplicationRolesSeedData.cs created (once per application)
+- {Module}RolePermissionSeedData.cs created with role-permission mappings
+- All 4 application roles defined with valid Code values
+- Proceeded to step-03b-provider.md
+
+**For core projects:**
+- Role-permission mappings generated (via MCP or fallback)
+- RolePermissionConfiguration.cs WRITTEN with new entries
+- All default roles have appropriate access
+- Proceeded to step-04-backend.md
+
+## FAILURE MODES
+
+- Permission GUIDs not available from step-02 (return to step-02)
+- Role GUIDs not found in project (ask user, use well-known defaults)
+- Invalid navRoute format (return to step-00)
+
+---
+
+## NEXT STEP
+
+After role-permission mappings are generated (via MCP or fallback) and written to files,
+proceed to `./step-03b-provider.md`
+
+> **Note:** step-03b will automatically skip if `{seeding_strategy}` = "hasdata" and proceed directly to step-04-backend.

package/templates/skills/application/steps/step-03b-provider.md

@@ -1,133 +1,133 @@
----
-name: step-03b-provider
-description: Generate IClientSeedDataProvider implementation for client projects
-prev_step: steps/step-03-roles.md
-next_step: steps/step-04-backend.md
----
-
-# Step 3b: Client Seed Data Provider (Client Projects Only)
-
-## CONDITION D'EXECUTION
-
-> This step executes ONLY if `{seeding_strategy}` = "provider" (client project).
-> If `{seeding_strategy}` = "hasdata", skip directly to step-04-backend.md.
-
-## MANDATORY EXECUTION RULES
-
-- ONLY execute for client projects (`{seeding_strategy}` = "provider")
-- ALWAYS use factory methods (`NavigationModule.Create(...)`, etc.) - NEVER `new Entity()`
-- ALWAYS implement idempotence (check existence before inserting)
-- ALWAYS register the provider in DI
-- ALWAYS consume the SeedData classes created in steps 01-03
-
-## YOUR TASK
-
-Generate the `IClientSeedDataProvider` implementation that wires the SeedData files
-created in steps 01, 02, 03 into the SmartStack Core seeding pipeline.
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{level}` | application, module, or section |
-| `{code}` | kebab-case identifier |
-| `{full_path}` | Complete navigation path |
-| `{labels}` | Object with fr, en, it, de |
-| `{descriptions}` | Object with fr, en, it, de |
-| `{icon}` | Lucide icon name |
-| `{display_order}` | Numeric display order |
-| `{navigation_guid}` | GUID of the navigation entity |
-| `{permission_guids}` | GUIDs for generated permissions |
-| `{project_type}` | "client" (guaranteed at this step) |
-| `{seeding_strategy}` | "provider" (guaranteed at this step) |
-
----
-
-## FILES TO GENERATE
-
-See [references/provider-template.md](../references/provider-template.md) for the complete implementation:
-- **ApplicationRolesSeedData.cs** (once per application) — defines application-scoped roles (Admin, Manager, Contributor, Viewer)
-- **Provider class** (`{AppPascalName}SeedDataProvider.cs`) with 4 seed methods (Navigation, Roles, Permissions, RolePermissions)
-- **DI registration** pattern for `Infrastructure/DependencyInjection.cs`
-- **7 critical rules** (factory methods, idempotence, execution order, SaveChangesAsync order, deterministic GUIDs, FK by Code, Order property)
-
----
-
-## EXECUTION SEQUENCE
-
-### 1. Read SeedData files from steps 01-03
-
-Identify all SeedData files created in previous steps:
-
-```
-Glob: **/Persistence/Seeding/Data/{Domain}/*SeedData.cs
-Glob: **/Persistence/Seeding/Data/ApplicationRolesSeedData.cs
-```
-
-Expected files:
-- `ApplicationRolesSeedData.cs` (application-level, once per app)
-- `{Module}NavigationSeedData.cs` (from step 01)
-- `{Module}NavigationTranslationSeedData.cs` (from step 01)
-- `{Module}PermissionSeedData.cs` (from step 02)
-- `{Module}RolePermissionSeedData.cs` (from step 03)
-
-### 2. Generate Provider Class
-
-Using the SeedData files as data sources, generate the `{AppPascalName}SeedDataProvider.cs` following the pattern above.
-
-Adapt the template:
-- Replace `{AppPascalName}` with the PascalCase application name
-- Replace `{app_code}` with the kebab-case application code
-- Fill in the actual navigation, permission, and role-permission creation logic
-  using the helper methods from the SeedData classes
-
-### 3. Register in DI
-
-Find and update `Infrastructure/DependencyInjection.cs`:
-
-```
-Glob: **/Infrastructure/DependencyInjection.cs
-```
-
-Add the `IClientSeedDataProvider` registration.
-
-### 4. Verify
-
-Before proceeding to step-04, verify:
-- [ ] ApplicationRolesSeedData.cs created (once per application)
-- [ ] Provider generated with 4 methods (SeedNavigationAsync, SeedRolesAsync, SeedPermissionsAsync, SeedRolePermissionsAsync)
-- [ ] Execution order: Navigation → Roles → Permissions → RolePermissions
-- [ ] Registered in DI (`services.AddScoped<IClientSeedDataProvider, ...>()`)
-- [ ] Consumes SeedData classes from steps 01-03 + ApplicationRolesSeedData
-- [ ] Idempotent (check existence before insert)
-- [ ] Uses factory methods (no `new Entity()`)
-
----
-
-## SUCCESS METRICS
-
-- ApplicationRolesSeedData.cs created (application-level)
-- Provider class generated with all 4 seed methods (Navigation, Roles, Permissions, RolePermissions)
-- Correct execution order enforced
-- DI registration added
-- SeedData classes from steps 01-03 + ApplicationRolesSeedData properly consumed
-- All methods are idempotent
-- Factory methods used throughout
-- Proceeded to step-04-backend.md
-
-## FAILURE MODES
-
-- SeedData files not found from previous steps (return to step-01)
-- DependencyInjection.cs not found (ask user for DI registration location)
-- Missing IClientSeedDataProvider interface (verify SmartStack.Application reference)
-
----
-
-## NEXT STEP
-
-After generating the provider and registering it in DI,
-proceed to `./step-04-backend.md`
+---
+name: step-03b-provider
+description: Generate IClientSeedDataProvider implementation for client projects
+prev_step: steps/step-03-roles.md
+next_step: steps/step-04-backend.md
+---
+
+# Step 3b: Client Seed Data Provider (Client Projects Only)
+
+## CONDITION D'EXECUTION
+
+> This step executes ONLY if `{seeding_strategy}` = "provider" (client project).
+> If `{seeding_strategy}` = "hasdata", skip directly to step-04-backend.md.
+
+## MANDATORY EXECUTION RULES
+
+- ONLY execute for client projects (`{seeding_strategy}` = "provider")
+- ALWAYS use factory methods (`NavigationModule.Create(...)`, etc.) - NEVER `new Entity()`
+- ALWAYS implement idempotence (check existence before inserting)
+- ALWAYS register the provider in DI
+- ALWAYS consume the SeedData classes created in steps 01-03
+
+## YOUR TASK
+
+Generate the `IClientSeedDataProvider` implementation that wires the SeedData files
+created in steps 01, 02, 03 into the SmartStack Core seeding pipeline.
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+| Variable | Description |
+|----------|-------------|
+| `{level}` | application, module, section, or resource |
+| `{code}` | kebab-case identifier |
+| `{full_path}` | Complete navigation path |
+| `{labels}` | Object with fr, en, it, de |
+| `{descriptions}` | Object with fr, en, it, de |
+| `{icon}` | Lucide icon name |
+| `{display_order}` | Numeric display order |
+| `{navigation_guid}` | GUID of the navigation entity |
+| `{permission_guids}` | GUIDs for generated permissions |
+| `{project_type}` | "client" (guaranteed at this step) |
+| `{seeding_strategy}` | "provider" (guaranteed at this step) |
+
+---
+
+## FILES TO GENERATE
+
+See [references/provider-template.md](../references/provider-template.md) for the complete implementation:
+- **ApplicationRolesSeedData.cs** (once per application) — defines application-scoped roles (Admin, Manager, Contributor, Viewer)
+- **Provider class** (`{AppPascalName}SeedDataProvider.cs`) with 4 seed methods (Navigation, Roles, Permissions, RolePermissions)
+- **DI registration** pattern for `Infrastructure/DependencyInjection.cs`
+- **7 critical rules** (factory methods, idempotence, execution order, SaveChangesAsync order, deterministic GUIDs, FK by Code, Order property)
+
+---
+
+## EXECUTION SEQUENCE
+
+### 1. Read SeedData files from steps 01-03
+
+Identify all SeedData files created in previous steps:
+
+```
+Glob: **/Persistence/Seeding/Data/{Domain}/*SeedData.cs
+Glob: **/Persistence/Seeding/Data/ApplicationRolesSeedData.cs
+```
+
+Expected files:
+- `ApplicationRolesSeedData.cs` (application-level, once per app)
+- `{Module}NavigationSeedData.cs` (from step 01)
+- `{Module}NavigationTranslationSeedData.cs` (from step 01)
+- `{Module}PermissionSeedData.cs` (from step 02)
+- `{Module}RolePermissionSeedData.cs` (from step 03)
+
+### 2. Generate Provider Class
+
+Using the SeedData files as data sources, generate the `{AppPascalName}SeedDataProvider.cs` following the pattern above.
+
+Adapt the template:
+- Replace `{AppPascalName}` with the PascalCase application name
+- Replace `{app_code}` with the kebab-case application code
+- Fill in the actual navigation, permission, and role-permission creation logic
+  using the helper methods from the SeedData classes
+
+### 3. Register in DI
+
+Find and update `Infrastructure/DependencyInjection.cs`:
+
+```
+Glob: **/Infrastructure/DependencyInjection.cs
+```
+
+Add the `IClientSeedDataProvider` registration.
+
+### 4. Verify
+
+Before proceeding to step-04, verify:
+- [ ] ApplicationRolesSeedData.cs created (once per application)
+- [ ] Provider generated with 4 methods (SeedNavigationAsync, SeedRolesAsync, SeedPermissionsAsync, SeedRolePermissionsAsync)
+- [ ] Execution order: Navigation → Roles → Permissions → RolePermissions
+- [ ] Registered in DI (`services.AddScoped<IClientSeedDataProvider, ...>()`)
+- [ ] Consumes SeedData classes from steps 01-03 + ApplicationRolesSeedData
+- [ ] Idempotent (check existence before insert)
+- [ ] Uses factory methods (no `new Entity()`)
+
+---
+
+## SUCCESS METRICS
+
+- ApplicationRolesSeedData.cs created (application-level)
+- Provider class generated with all 4 seed methods (Navigation, Roles, Permissions, RolePermissions)
+- Correct execution order enforced
+- DI registration added
+- SeedData classes from steps 01-03 + ApplicationRolesSeedData properly consumed
+- All methods are idempotent
+- Factory methods used throughout
+- Proceeded to step-04-backend.md
+
+## FAILURE MODES
+
+- SeedData files not found from previous steps (return to step-01)
+- DependencyInjection.cs not found (ask user for DI registration location)
+- Missing IClientSeedDataProvider interface (verify SmartStack.Application reference)
+
+---
+
+## NEXT STEP
+
+After generating the provider and registering it in DI,
+proceed to `./step-04-backend.md`