@atlashub/smartstack-cli 3.39.0 → 3.41.0

package/templates/skills/controller/steps/step-03-generate.md

@@ -1,189 +1,189 @@
----
-name: step-03-generate
-description: Generate controller using MCP scaffold_extension with NavRoute
-next_step: steps/step-04-perms.md
----
-
-# Step 3: Generate Controller
-
-## MANDATORY EXECUTION RULES
-
-- ALWAYS use MCP `scaffold_extension` tool - NEVER use templates
-- ALWAYS generate Controller + DTOs as a unit
-- ALWAYS include NavRoute attribute for frontend/backend sync
-- YOU ARE AN ORCHESTRATOR calling MCP, not a generator
-- MCP is the SOURCE OF TRUTH for code generation
-
-## YOUR TASK
-
-Call the SmartStack MCP `scaffold_extension` tool (TWO calls):
-1. Generate DTOs (Response, Create, Update)
-2. Generate API Controller with NavRoute attribute
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{area}` | Controller folder (Admin, Business, Support, User) |
-| `{module}` | kebab-case module identifier |
-| `{entity}` | Entity name (PascalCase) |
-| `{permission_path}` | Complete navigation path (navRoute) |
-| `{controller_type}` | crud, readonly, custom, auth |
-
----
-
-## EXECUTION SEQUENCE
-
-### 1. Derive Entity Name
-
-Convert `{module}` to PascalCase for entity name:
-
-```
-module: "products"        → entityName: "Product"
-module: "order-items"     → entityName: "OrderItem"
-module: "user-profiles"   → entityName: "UserProfile"
-```
-
-### 2. Determine Table Prefix
-
-Based on navigation context extracted from `{permission_path}`:
-
-| Application | Table Prefix | Controller Folder |
-|-------------|--------------|-------------------|
-| administration | `auth_` or `cfg_` | `Administration` |
-| support | `support_` | `Support` |
-| {application} | `ref_` or domain-specific | `{ApplicationPascal}` |
-| myspace | `usr_` | `MySpace` |
-
-### 3. Call MCP scaffold_extension (TWO CALLS)
-
-See `references/mcp-scaffold-workflow.md` for complete MCP workflow, error handling, and post-generation checks.
-
-**Call 1: Generate DTOs**
-```javascript
-mcp__smartstack__scaffold_extension({
-  type: "dto",
-  name: "{entityName}",
-  options: {
-    navRoute: "{permission_path}",
-    schema: "core",
-    dryRun: false
-  }
-});
-```
-
-**Call 2: Generate Controller**
-```javascript
-mcp__smartstack__scaffold_extension({
-  type: "controller",
-  name: "{entityName}",
-  options: {
-    navRoute: "{permission_path}",  // MANDATORY for NavRoute attribute
-    navRouteSuffix: null,
-    dryRun: false
-  }
-});
-```
-
-### 4. Parse MCP Responses
-
-**From first call (DTOs):**
-- `Application/{Application}/{Module}/DTOs/{entityName}ResponseDto.cs`
-- `Application/{Application}/{Module}/DTOs/Create{entityName}Dto.cs`
-- `Application/{Application}/{Module}/DTOs/Update{entityName}Dto.cs`
-
-**From second call (Controller):**
-- `Api/Controllers/{area}/{entityName}Controller.cs` with **[NavRoute]** attribute
-
-### 5. Present Output to User
-
-```markdown
-## Controller Generated via MCP
-
-### API Layer
-- `Controllers/{area}/{entityName}Controller.cs`
-  - **NavRoute: `{permission_path}`** ✅
-  - Endpoints: GET /api/{module}, POST, PUT, DELETE
-
-### Application Layer (DTOs)
-- `{entityName}ResponseDto.cs`
-- `Create{entityName}Dto.cs`
-- `Update{entityName}Dto.cs`
-
-### ✅ NavRoute Integration
-- [NavRoute("{permission_path}")] attribute present
-- Frontend/backend sync enabled
-- Permission-based navigation ready
-
-Next: step-04-perms.md
-```
-
----
-
-## MCP RESPONSE HANDLING
-
-### Success Case
-
-**After Call 1 (DTOs):**
-- Display all generated DTO files
-- Verify DTOs match entity properties
-- Continue to Call 2
-
-**After Call 2 (Controller):**
-- Display controller file with NavRoute
-- Show frontend/backend sync enabled
-- Proceed to step-04-perms.md
-
-### Error Case
-
-**If Call 1 (DTOs) fails:**
-- Display error message
-- Suggest checking entity name format (must be PascalCase)
-- Verify entity properties are defined
-- Do NOT proceed to Call 2
-
-**If Call 2 (Controller) fails:**
-- Display error message
-- Note that DTOs were generated successfully
-- Suggest checking navRoute format
-- Do NOT proceed to step-04-perms.md
-
----
-
-## NAVROUTE VALIDATION
-
-Verify NavRoute is present (from `references/mcp-scaffold-workflow.md`):
-
-```javascript
-if (!controllerContent.includes('[NavRoute(')) {
-  console.error(`NavRoute attribute NOT FOUND`);
-  console.error(`Expected: [NavRoute("${permission_path}")]`);
-  STOP;
-}
-```
-
-Without NavRoute:
-- ❌ Frontend routes hardcoded
-- ❌ No automatic permission sync
-- ❌ Manual navigation required
-
----
-
-## SUCCESS METRICS
-
-- MCP scaffold_extension called twice (DTOs, then Controller)
-- DTOs generated (ResponseDto, CreateDto, UpdateDto)
-- Controller generated with **[NavRoute]** attribute
-- NavRoute matches permission_path
-- Controller references DTOs correctly
-- Proceeded to step-04-perms.md
-
----
-
-## NEXT STEP:
-
-After controller generation complete, proceed to `./step-04-perms.md`
+---
+name: step-03-generate
+description: Generate controller using MCP scaffold_extension with NavRoute
+next_step: steps/step-04-perms.md
+---
+
+# Step 3: Generate Controller
+
+## MANDATORY EXECUTION RULES
+
+- ALWAYS use MCP `scaffold_extension` tool - NEVER use templates
+- ALWAYS generate Controller + DTOs as a unit
+- ALWAYS include NavRoute attribute for frontend/backend sync
+- YOU ARE AN ORCHESTRATOR calling MCP, not a generator
+- MCP is the SOURCE OF TRUTH for code generation
+
+## YOUR TASK
+
+Call the SmartStack MCP `scaffold_extension` tool (TWO calls):
+1. Generate DTOs (Response, Create, Update)
+2. Generate API Controller with NavRoute attribute
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+| Variable | Description |
+|----------|-------------|
+| `{area}` | Controller folder (Admin, Business, Support, User) |
+| `{module}` | kebab-case module identifier |
+| `{entity}` | Entity name (PascalCase) |
+| `{permission_path}` | Complete navigation path (navRoute) |
+| `{controller_type}` | crud, readonly, custom, auth |
+
+---
+
+## EXECUTION SEQUENCE
+
+### 1. Derive Entity Name
+
+Convert `{module}` to PascalCase for entity name:
+
+```
+module: "products"        → entityName: "Product"
+module: "order-items"     → entityName: "OrderItem"
+module: "user-profiles"   → entityName: "UserProfile"
+```
+
+### 2. Determine Table Prefix
+
+Based on navigation context extracted from `{permission_path}`:
+
+| Application | Table Prefix | Controller Folder |
+|-------------|--------------|-------------------|
+| administration | `auth_` or `cfg_` | `Administration` |
+| support | `support_` | `Support` |
+| {application} | `ref_` or domain-specific | `{ApplicationPascal}` |
+| myspace | `usr_` | `MySpace` |
+
+### 3. Call MCP scaffold_extension (TWO CALLS)
+
+See `references/mcp-scaffold-workflow.md` for complete MCP workflow, error handling, and post-generation checks.
+
+**Call 1: Generate DTOs**
+```javascript
+mcp__smartstack__scaffold_extension({
+  type: "dto",
+  name: "{entityName}",
+  options: {
+    navRoute: "{permission_path}",
+    schema: "core",
+    dryRun: false
+  }
+});
+```
+
+**Call 2: Generate Controller**
+```javascript
+mcp__smartstack__scaffold_extension({
+  type: "controller",
+  name: "{entityName}",
+  options: {
+    navRoute: "{permission_path}",  // MANDATORY for NavRoute attribute
+    navRouteSuffix: null,
+    dryRun: false
+  }
+});
+```
+
+### 4. Parse MCP Responses
+
+**From first call (DTOs):**
+- `Application/{Application}/{Module}/DTOs/{entityName}ResponseDto.cs`
+- `Application/{Application}/{Module}/DTOs/Create{entityName}Dto.cs`
+- `Application/{Application}/{Module}/DTOs/Update{entityName}Dto.cs`
+
+**From second call (Controller):**
+- `Api/Controllers/{area}/{entityName}Controller.cs` with **[NavRoute]** attribute
+
+### 5. Present Output to User
+
+```markdown
+## Controller Generated via MCP
+
+### API Layer
+- `Controllers/{area}/{entityName}Controller.cs`
+  - **NavRoute: `{permission_path}`** ✅
+  - Endpoints: GET /api/{module}, POST, PUT, DELETE
+
+### Application Layer (DTOs)
+- `{entityName}ResponseDto.cs`
+- `Create{entityName}Dto.cs`
+- `Update{entityName}Dto.cs`
+
+### ✅ NavRoute Integration
+- [NavRoute("{permission_path}")] attribute present
+- Frontend/backend sync enabled
+- Permission-based navigation ready
+
+Next: step-04-perms.md
+```
+
+---
+
+## MCP RESPONSE HANDLING
+
+### Success Case
+
+**After Call 1 (DTOs):**
+- Display all generated DTO files
+- Verify DTOs match entity properties
+- Continue to Call 2
+
+**After Call 2 (Controller):**
+- Display controller file with NavRoute
+- Show frontend/backend sync enabled
+- Proceed to step-04-perms.md
+
+### Error Case
+
+**If Call 1 (DTOs) fails:**
+- Display error message
+- Suggest checking entity name format (must be PascalCase)
+- Verify entity properties are defined
+- Do NOT proceed to Call 2
+
+**If Call 2 (Controller) fails:**
+- Display error message
+- Note that DTOs were generated successfully
+- Suggest checking navRoute format
+- Do NOT proceed to step-04-perms.md
+
+---
+
+## NAVROUTE VALIDATION
+
+Verify NavRoute is present (from `references/mcp-scaffold-workflow.md`):
+
+```javascript
+if (!controllerContent.includes('[NavRoute(')) {
+  console.error(`NavRoute attribute NOT FOUND`);
+  console.error(`Expected: [NavRoute("${permission_path}")]`);
+  STOP;
+}
+```
+
+Without NavRoute:
+- ❌ Frontend routes hardcoded
+- ❌ No automatic permission sync
+- ❌ Manual navigation required
+
+---
+
+## SUCCESS METRICS
+
+- MCP scaffold_extension called twice (DTOs, then Controller)
+- DTOs generated (ResponseDto, CreateDto, UpdateDto)
+- Controller generated with **[NavRoute]** attribute
+- NavRoute matches permission_path
+- Controller references DTOs correctly
+- Proceeded to step-04-perms.md
+
+---
+
+## NEXT STEP:
+
+After controller generation complete, proceed to `./step-04-perms.md`

package/templates/skills/controller/steps/step-04-perms.md

@@ -1,80 +1,80 @@
----
-name: step-04-perms
-description: Synchronize permissions in Permissions.cs and PermissionConfiguration.cs
-next_step: steps/step-05-validate.md
----
-
-# Step 4: Synchronize Permissions
-
-## YOUR TASK:
-
-Add permissions to both Permissions.cs (constants) and PermissionConfiguration.cs (database seeds).
-
-**CRITICAL: Both files MUST be in sync. Missing permissions = runtime 403 errors.**
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Update Permissions.cs & PermissionConfiguration.cs
-
-See [references/permission-sync-templates.md](../references/permission-sync-templates.md) for the C# templates:
-- **Permissions.cs**: Nested class with 4 constants (View, Create, Update, Delete) + path-to-class mapping
-- **PermissionConfiguration.cs**: 4 HasData Permission entries with deterministic GUIDs
-
-### 3. Generate Migration (Required)
-
-**After updating PermissionConfiguration:**
-
-```
-IMPORTANT: New HasData entries require a migration!
-
-Suggest command:
-/efcore:migration Add{module}Permissions
-```
-
-**If auto_mode:**
-- Inform user that migration is needed
-- Do NOT auto-run migration (user decision)
-
-### 4. Validation Check
-
-**Verify sync between files:**
-
-| Permission Code | In Permissions.cs | In PermissionConfiguration.cs |
-|-----------------|-------------------|------------------------------|
-| `{permission_path}.read` | ✅ | ✅ |
-| `{permission_path}.create` | ✅ | ✅ |
-| `{permission_path}.update` | ✅ | ✅ |
-| `{permission_path}.delete` | ✅ | ✅ |
-
-### 5. Generate Postman Tests (if postman_mode)
-
-**If {postman_mode} = true:**
-
-See [references/permission-sync-templates.md](../references/permission-sync-templates.md) § "Postman API Test Template" for the JSON test collection template (200 OK + 403 Forbidden tests).
-
----
-
-## OUTPUT FORMAT:
-
-```
-Permissions Synchronized:
-
-| File | Changes |
-|------|---------|
-| Permissions.cs | Added {module} class with 4 constants |
-| PermissionConfiguration.cs | Added 4 permission seeds |
-| Postman Collection | Added {test_count} tests |
-
-⚠️ MIGRATION REQUIRED:
-Run: /efcore:migration Add{module}Permissions
-
--> Validating build...
-```
-
----
-
-## NEXT STEP:
-
-After permissions synced, proceed to `./step-05-validate.md`
+---
+name: step-04-perms
+description: Synchronize permissions in Permissions.cs and PermissionConfiguration.cs
+next_step: steps/step-05-validate.md
+---
+
+# Step 4: Synchronize Permissions
+
+## YOUR TASK:
+
+Add permissions to both Permissions.cs (constants) and PermissionConfiguration.cs (database seeds).
+
+**CRITICAL: Both files MUST be in sync. Missing permissions = runtime 403 errors.**
+
+---
+
+## EXECUTION SEQUENCE:
+
+### 1. Update Permissions.cs & PermissionConfiguration.cs
+
+See [references/permission-sync-templates.md](../references/permission-sync-templates.md) for the C# templates:
+- **Permissions.cs**: Nested class with 4 constants (View, Create, Update, Delete) + path-to-class mapping
+- **PermissionConfiguration.cs**: 4 HasData Permission entries with deterministic GUIDs
+
+### 3. Generate Migration (Required)
+
+**After updating PermissionConfiguration:**
+
+```
+IMPORTANT: New HasData entries require a migration!
+
+Suggest command:
+/efcore migration Add{module}Permissions
+```
+
+**If auto_mode:**
+- Inform user that migration is needed
+- Do NOT auto-run migration (user decision)
+
+### 4. Validation Check
+
+**Verify sync between files:**
+
+| Permission Code | In Permissions.cs | In PermissionConfiguration.cs |
+|-----------------|-------------------|------------------------------|
+| `{permission_path}.read` | ✅ | ✅ |
+| `{permission_path}.create` | ✅ | ✅ |
+| `{permission_path}.update` | ✅ | ✅ |
+| `{permission_path}.delete` | ✅ | ✅ |
+
+### 5. Generate Postman Tests (if postman_mode)
+
+**If {postman_mode} = true:**
+
+See [references/permission-sync-templates.md](../references/permission-sync-templates.md) § "Postman API Test Template" for the JSON test collection template (200 OK + 403 Forbidden tests).
+
+---
+
+## OUTPUT FORMAT:
+
+```
+Permissions Synchronized:
+
+| File | Changes |
+|------|---------|
+| Permissions.cs | Added {module} class with 4 constants |
+| PermissionConfiguration.cs | Added 4 permission seeds |
+| Postman Collection | Added {test_count} tests |
+
+⚠️ MIGRATION REQUIRED:
+Run: /efcore migration Add{module}Permissions
+
+-> Validating build...
+```
+
+---
+
+## NEXT STEP:
+
+After permissions synced, proceed to `./step-05-validate.md`