@atlashub/smartstack-cli 4.81.0 → 5.0.0

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

@@ -1,174 +0,0 @@
----
-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

@@ -1,189 +0,0 @@
----
-name: step-05-frontend
-description: Generate frontend code using MCP tools (component, API client, routes, i18n)
-prev_step: steps/step-04-backend.md
-next_step: steps/step-06-migration.md
----
-
-# Step 5: Frontend Generation
-
-## MANDATORY EXECUTION RULES
-
-- ALWAYS use MCP tools for frontend generation
-- ALWAYS generate i18n for 4 languages (fr, en, it, de)
-- ALWAYS use nested routes (not flat)
-- YOU ARE AN ORCHESTRATOR calling MCP, not a generator
-
-## YOUR TASK
-
-Use MCP tools to generate:
-1. React component (scaffold_extension type: component)
-2. TypeScript API client (scaffold_api_client)
-3. Route configuration (scaffold_routes)
-4. i18n files (scaffold_translations for UI)
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{full_path}` | Complete navigation path (navRoute) |
-| `{entity_name}` | PascalCase entity name |
-| `{entity_code}` | kebab-case code |
-| `{labels}` | Object with fr, en, it, de |
-| `{api_route}` | API endpoint path |
-| `{application_kebab}` | kebab-case route segment for application (PascalCase → kebab-case, e.g., `HumanResources` → `human-resources`) |
-| `{module_kebab}` | kebab-case route segment for module (PascalCase → kebab-case, e.g., `TimeManagement` → `time-management`) |
-
----
-
-## ROUTE NAMING RULE
-
-See [references/frontend-route-naming.md](../references/frontend-route-naming.md) for:
-- Kebab-case transformation rules
-- Forbidden patterns (concatenated words)
-- Required patterns (hyphens in multi-word segments)
-- Verification against navigation seed data
-
----
-
-## EXECUTION SEQUENCE
-
-### 1. Generate Frontend Pages (conventions-compliant)
-
-```
-Tool: mcp__smartstack__scaffold_extension
-Args:
-  type: "page"
-  name: "{entity_name}"
-  options:
-    navRoute: "{full_path}"
-    outputPath: "web/src/pages/{application}/{module}"
-    dryRun: false
-```
-
-This generates (all natively compliant with /ui-components conventions):
-- `{EntityName}Page.tsx` — List page wrapper with i18n
-- `{EntityName}ListView.tsx` — EntityCard grid + DataTable + ViewToggle + responsive + loading/error/empty states
-- `{EntityName}DetailPage.tsx` — Detail page with back button + pill tabs + info cards
-- `use{EntityName}Preferences.ts` — Preferences hook (viewMode, sorting, filters, columns)
-- i18n files for 4 languages (fr, en, it, de)
-
-> **Note:** The `type: "page"` scaffold already includes CSS variables, EntityCard, responsive grid,
-> semantic HTML, memo/useCallback, and all ui-components conventions. No manual corrections needed.
-
-### 2. Generate API Client
-
-```
-Tool: mcp__smartstack__scaffold_api_client
-Args:
-  navRoute: "{full_path}"
-  name: "{entity_name}"
-  methods: ["getAll", "getById", "create", "update", "delete"]
-  options:
-    includeTypes: true
-    includeHook: true
-```
-
-This generates:
-- `services/api/{entityCode}Api.ts` - API service
-- `types/{entityName}.types.ts` - TypeScript interfaces
-- `hooks/use{EntityName}Api.ts` - React Query hook (optional)
-
-### 3. Generate Route Configuration
-
-```
-Tool: mcp__smartstack__scaffold_routes
-Args:
-  source: "controllers"
-  scope: "all"
-  options:
-    includeGuards: true
-    generateRegistry: true
-    outputFormat: "componentRegistry"
-```
-
-This generates:
-- `navRoutes.generated.ts` — Route registry (NavRoute to API/web path mapping)
-- `componentRegistry.generated.ts` — PageRegistry.register() calls for DynamicRouter
-
-### 4. Verify PageRegistry Registration
-
-After `scaffold_routes` generates the files:
-
-1. **Verify `componentRegistry.generated.ts`** contains `PageRegistry.register()` calls
-   for each new page component
-2. **Verify `main.tsx`** imports `./extensions/componentRegistry.generated`
-   (this should already be present — check once)
-3. **Verify navigation seed data** has `ComponentKey` values matching the registered keys
-   (e.g., seed Route="/administration/users" → ComponentKey="administration.users")
-
-No manual App.tsx wiring is needed — DynamicRouter resolves routes automatically
-from the API menu response + PageRegistry at runtime.
-
-Verification:
-```
-Tool: mcp__smartstack__validate_frontend_routes
-Args:
-  scope: "routes"
-```
-
-### 5-6. Verify i18n & Present Output
-
-See [references/frontend-i18n-and-output.md](../references/frontend-i18n-and-output.md) for:
-- i18n structure (4 language files)
-- Customization of labels from feature context
-- Output formatting by category (Pages, Components, API Client, Routes, i18n)
-
----
-
-## ROUTING RULES
-
-See [references/frontend-verification.md](../references/frontend-verification.md) for detailed routing rules with code examples:
-- **Rule 1:** Routes MUST be inside the AppLayout wrapper
-- **Rule 2:** Use NESTED routes (not flat) — flat routes bypass layout and break the shell
-
----
-
-## POST-GENERATION VERIFICATION (MANDATORY)
-
-**Before proceeding to step-06, run all 7 checks on generated frontend files.**
-
-See [references/frontend-verification.md](../references/frontend-verification.md) for the complete checklist:
-1. CSS Variables (BLOCKING) — no hardcoded Tailwind colors
-2. API Client (BLOCKING) — use configured client, not raw axios
-3. EntityCard — use EntityCard component for grid/card views
-4. i18n (BLOCKING) — exactly 4 language files with identical keys
-5. Route (BLOCKING) — inside Layout wrapper, nested, correct path convention
-6. States — loading, error, empty states present
-7. TypeScript Build (BLOCKING) — `npx tsc --noEmit` passes for generated files
-
----
-
-## SUCCESS METRICS
-
-- React component generated
-- API client generated with types
-- PageRegistry entries generated (componentRegistry.generated.ts)
-- navRoutes.generated.ts updated
-- Navigation seed data has matching componentKeys
-- i18n files created (4 languages)
-- Post-generation verification passed
-- Proceeded to step-06-migration.md
-
-## FAILURE MODES
-
-- Component generation failed (check entity name)
-- API client generation failed (check navRoute)
-- Route configuration failed (check existing routes)
-- Hardcoded colors detected → Fix before continuing
-- Missing language files → Generate all 4 before continuing
-
----
-
-## NEXT STEP
-
-After displaying frontend code, proceed to `./step-06-migration.md`

package/templates/skills/application/steps/step-06-migration.md

@@ -1,189 +0,0 @@
----
-name: step-06-migration
-description: Create EF Core migration and finalize application setup
-prev_step: steps/step-05-frontend.md
-next_step: steps/step-07-tests.md
----
-
-# Step 6: Migration & Finalization
-
-## MANDATORY EXECUTION RULES
-
-- ALWAYS use MCP `suggest_migration` to get proper migration name
-- ALWAYS use `/efcore migration` skill for migration creation
-- NEVER use raw SQL in migrations
-- YOU ARE AN ORCHESTRATOR, finalizing the application setup
-
-## YOUR TASK
-
-1. Get suggested migration name from MCP
-2. Create the EF Core migration
-3. Provide final checklist to user
-
----
-
-## AVAILABLE STATE
-
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{entity_name}` | PascalCase entity name |
-| `{full_path}` | Complete navigation path |
-| `{level}` | Navigation level |
-| `{labels}` | Translated labels |
-
----
-
-## EXECUTION SEQUENCE
-
-### 0. Pre-Migration Build Verification (BLOCKING)
-
-See [references/migration-checklist-troubleshooting.md](../references/migration-checklist-troubleshooting.md) for:
-- Build verification command
-- Common compilation causes
-- Fix strategies
-- Quick recovery commands
-
-### 1. Get Migration Name Suggestion
-
-```
-Tool: mcp__smartstack__suggest_migration
-Args:
-  description: "Add {entity_name} with navigation and permissions"
-  context: "{db_context}"   # "core" or "extensions" based on project type
-```
-
-Response example (core project):
-```
-Migration name: core_v1.2.0_003_Add{EntityName}WithNavigationAndPermissions
-Command: dotnet ef migrations add core_v1.2.0_003_Add{EntityName}WithNavigationAndPermissions --context CoreDbContext -o Persistence/Migrations
-```
-
-Response example (client project):
-```
-Migration name: extensions_v1.0.0_001_Add{EntityName}ModuleEntities
-Command: dotnet ef migrations add extensions_v1.0.0_001_Add{EntityName}ModuleEntities --context ExtensionsDbContext -o Persistence/Migrations
-```
-
-### 2. Create Migration
-
-Use the /efcore migration skill or direct command:
-
-**For core projects:**
-```bash
-cd Infrastructure
-dotnet ef migrations add {suggested_migration_name} --context CoreDbContext -o Persistence/Migrations
-```
-
-**For client projects (ExtensionsDbContext):**
-```bash
-cd Infrastructure
-dotnet ef migrations add {suggested_migration_name} --context ExtensionsDbContext -o Persistence/Migrations
-```
-
-> **CRITICAL:** Always use `-o Persistence/Migrations` to ensure ALL migrations are in the SAME directory.
-> NEVER create subdirectories under `Migrations/` (e.g., `Migrations/Extensions/`).
-> All migrations for a given DbContext MUST share the same namespace to avoid EF Core errors.
-
-### 3. Verify Migration Content
-
-See [references/migration-checklist-troubleshooting.md](../references/migration-checklist-troubleshooting.md) for complete migration content verification checklist.
-
-### 4. Apply Migration
-
-**For core projects:**
-```bash
-dotnet ef database update --context CoreDbContext
-```
-
-**For client projects:**
-```bash
-dotnet ef database update --context ExtensionsDbContext
-```
-
-### 5. Present Final Checklist
-
-```markdown
-## Application Setup Complete
-
-### Summary
-
-| Item | Status |
-|------|--------|
-| Navigation | ✅ {level}: {full_path} |
-| Translations | ✅ 4 languages (fr, en, it, de) |
-| Permissions | ✅ CRUD + Wildcard |
-| Role Mappings | ✅ PlatformAdmin, TenantAdmin, StandardUser |
-| Entity | ✅ {entity_name} |
-| Service | ✅ I{entity_name}Service |
-| Controller | ✅ {entity_name}Controller |
-| DTOs | ✅ Create, Update, Response |
-| Frontend | ✅ Page, ListView, Hook |
-| API Client | ✅ TypeScript with types |
-| i18n | ✅ 4 languages |
-| Routes | ✅ Nested configuration |
-| Migration | ✅ {migration_name} |
-
-### Final Steps
-
-1. **Verify DbSet registration:**
-   ```csharp
-   // In ICoreDbContext.cs
-   public DbSet<{entity_name}> {entity_name}s => Set<{entity_name}>();
-   ```
-
-2. **Verify DI registration:**
-   ```csharp
-   // In DependencyInjection.cs
-   services.AddScoped<I{entity_name}Service, {entity_name}Service>();
-   ```
-
-3. **Test the application:**
-   ```bash
-   # Backend
-   dotnet run --project Api
-
-   # Frontend
-   cd web && npm run dev
-   ```
-
-4. **Verify navigation:**
-   - Login to the application
-   - Navigate to {full_path}
-   - Verify CRUD operations work
-
-### API Endpoints
-
-| Method | Endpoint | Permission |
-|--------|----------|------------|
-| GET | /api/{entity_code} | {full_path}.read |
-| GET | /api/{entity_code}/{id} | {full_path}.read |
-| POST | /api/{entity_code} | {full_path}.create |
-| PUT | /api/{entity_code}/{id} | {full_path}.update |
-| DELETE | /api/{entity_code}/{id} | {full_path}.delete |
-```
-
----
-
-## TROUBLESHOOTING
-
-See [references/migration-checklist-troubleshooting.md](../references/migration-checklist-troubleshooting.md) for:
-- Common issues and solutions
-- Quick fix commands
-- Database reset procedures
-- Final verification checklist
-
----
-
-## SUCCESS METRICS
-
-- Pre-migration build verification passed
-- Migration name suggested via MCP
-- Migration created and applied
-- All checklist items verified
-- Application functional
-
-## NEXT STEP
-
-After migration is applied and verified, proceed to `./step-07-tests.md` for test generation.