@atlashub/smartstack-cli 4.9.0 → 4.11.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "4.9.0",
+  "version": "4.11.0",
   "description": "SmartStack Claude Code automation toolkit - GitFlow, EF Core migrations, prompts and more",
   "author": {
     "name": "SmartStack",

package/templates/skills/apex/references/frontend-route-wiring-app-tsx.md

@@ -52,6 +52,16 @@ const applicationRoutes: ApplicationRouteExtensions = {
 
 Routes are automatically injected into BOTH standard (`/{application}/...`) and tenant-prefixed (`/t/:slug/{application}/...`) route trees by `mergeRoutes()`. No manual duplication needed.
 
+#### Custom Applications (Pattern A)
+
+Custom application keys (any key **not** in the built-in list: `administration`, `support`, `user`, `api`) are fully supported in `applicationRoutes`. `mergeRoutes()` automatically:
+
+1. Creates a new route entry wrapped in `<AppLayout />`
+2. Injects it into **both** standard (`/{app-key}/...`) and tenant-prefixed (`/t/:slug/{app-key}/...`) trees, inside `TenantRouteWrapper > RouteGuard > LicenseGuard`
+3. Generates automatic parent redirect routes (e.g., `employees` → `employees/management`)
+
+No need to use Pattern B for custom applications — Pattern A handles everything automatically.
+
 ### Pattern B: JSX Routes
 
 **If App.tsx contains:** `<Route path="/{application}" element={<{Layout} />}>`
@@ -117,7 +127,7 @@ For each application, you MUST add:
 
 The `to` prop is resolved relative to the **parent route** (`/{application}`), so always use the full path from the application root.
 
-> Note: `scaffold_routes` with `outputFormat: "clientRoutes"` generates these redirects automatically.
+> Note: `scaffold_routes` with `outputFormat: "applicationRoutes"` generates these redirects automatically.
 
 ---
 

package/templates/skills/apex/references/post-checks.md

@@ -1118,7 +1118,7 @@ if [ -n "$PAGE_FILES" ]; then
   # Extract navigate targets (relative paths like '../leave-types', './create', etc.)
   NAV_TARGETS=$(grep -oP "navigate\(['\"]([^'\"]+)['\"]" $PAGE_FILES 2>/dev/null | grep -oP "['\"][^'\"]+['\"]" | tr -d "'" | tr -d '"' | sort -u)
   # Extract route paths from App.tsx or route config
-  APP_FILES=$(find web/ -name "App.tsx" -o -name "routes.tsx" -o -name "clientRoutes*.tsx" 2>/dev/null)
+  APP_FILES=$(find web/ -name "App.tsx" -o -name "routes.tsx" -o -name "applicationRoutes*.tsx" -o -name "clientRoutes*.tsx" 2>/dev/null)
   if [ -n "$APP_FILES" ] && [ -n "$NAV_TARGETS" ]; then
     ROUTE_PATHS=$(grep -oP "path:\s*['\"]([^'\"]+)['\"]" $APP_FILES 2>/dev/null | grep -oP "['\"][^'\"]+['\"]" | tr -d "'" | tr -d '"' | sort -u)
     for TARGET in $NAV_TARGETS; do

package/templates/skills/apex/references/smartstack-layers.md

@@ -278,7 +278,7 @@ var sectionRoute = $"{moduleRoute}/{ToKebabCase(sectionCode)}";
 | Action | Tool |
 |--------|------|
 | API client | MCP `scaffold_api_client` |
-| Routes | MCP `scaffold_routes` (outputFormat: `clientRoutes`) |
+| Routes | MCP `scaffold_routes` (outputFormat: `applicationRoutes`) |
 | Complex pages | /ui-components skill + `smartstack-frontend.md` patterns |
 | Validate routes | MCP `validate_frontend_routes` |
 

package/templates/skills/apex/steps/step-03-execute.md

@@ -298,7 +298,7 @@ test({module}): backend unit and integration tests
 
 For each module:
 - **API client:** MCP scaffold_api_client
-- **Routes:** MCP scaffold_routes (outputFormat: 'clientRoutes') → generates lazy imports + Suspense
+- **Routes:** MCP scaffold_routes (outputFormat: 'applicationRoutes') → generates lazy imports + Suspense
 - **Wire Routes to App.tsx (BLOCKING):** After scaffold_routes, routes MUST be wired into App.tsx:
   → Read App.tsx and detect the routing pattern
   → **Pattern A** (`applicationRoutes: ApplicationRouteExtensions`): add routes to `applicationRoutes['{application_kebab}'][]` with RELATIVE paths
@@ -377,7 +377,7 @@ For each entity:
   Task: "Execute Layer 3 frontend for entity {EntityName}:
     **MANDATORY: Read references/smartstack-frontend.md FIRST**
     - API client: MCP scaffold_api_client
-    - Routes: MCP scaffold_routes (outputFormat: 'clientRoutes')
+    - Routes: MCP scaffold_routes (outputFormat: 'applicationRoutes')
     - Wire Routes to App.tsx (BLOCKING): After scaffold_routes, wire into App.tsx:
       → Read App.tsx, detect Pattern A (applicationRoutes) or Pattern B (JSX Route)
       → Pattern A: add to applicationRoutes['{application_kebab}'][] with RELATIVE paths

package/templates/skills/application/references/frontend-i18n-and-output.md

@@ -48,7 +48,7 @@ Display generated frontend code organized by category:
 
 ### Routes
 - Updated `navRoutes.generated.ts`
-- Generated `clientRoutes.generated.tsx`
+- Generated `applicationRoutes.generated.tsx`
 - Wired routes in `App.tsx` (standard + tenant blocks)
 
 ### i18n

package/templates/skills/application/references/frontend-route-wiring-app-tsx.md

@@ -48,6 +48,16 @@ const applicationRoutes: ApplicationRouteExtensions = {
 
 Routes are automatically injected into BOTH standard (`/{application}/...`) and tenant-prefixed (`/t/:slug/{application}/...`) route trees by `mergeRoutes()`. No manual duplication needed.
 
+#### Custom Applications (Pattern A)
+
+Custom application keys (any key **not** in the built-in list: `administration`, `support`, `user`, `api`) are fully supported in `applicationRoutes`. `mergeRoutes()` automatically:
+
+1. Creates a new route entry wrapped in `<AppLayout />`
+2. Injects it into **both** standard (`/{app-key}/...`) and tenant-prefixed (`/t/:slug/{app-key}/...`) trees, inside `TenantRouteWrapper > RouteGuard > LicenseGuard`
+3. Generates automatic parent redirect routes (e.g., `employees` → `employees/management`)
+
+No need to use Pattern B for custom applications — Pattern A handles everything automatically.
+
 ### Pattern B: JSX Routes
 
 **If App.tsx contains:** `<Route path="/{application}" element={<{Layout} />}>`

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

@@ -87,7 +87,7 @@ Verify routes are actually wired into App.tsx (not just generated in standalone
 3. Verify the route also appears inside the **tenant-prefixed** block (`/t/:slug/...`)
 4. Verify the page component is imported (lazy-loaded) at the top of the file
 
-**If routes are only in `clientRoutes.generated.tsx` or `routes/index.tsx` but NOT in App.tsx, the routes will NOT work at runtime — page will be BLANK.**
+**If routes are only in `applicationRoutes.generated.tsx` or `routes/index.tsx` but NOT in App.tsx, the routes will NOT work at runtime — page will be BLANK.**
 
 Run validation:
 ```

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

@@ -103,12 +103,12 @@ Args:
   options:
     includeGuards: true
     generateRegistry: true
-    outputFormat: "clientRoutes"
+    outputFormat: "applicationRoutes"
 ```
 
 This generates:
 - `navRoutes.generated.ts` - Route registry (NavRoute to API/web path mapping)
-- `clientRoutes.generated.tsx` - Route fragments grouped by context with page imports
+- `applicationRoutes.generated.tsx` - Route fragments grouped by context with page imports
 
 ### 4. Wire Routes to App.tsx (BLOCKING)