@atlashub/smartstack-cli 4.80.0 → 5.0.0

package/templates/skills/_resources/docs-manifest-schema.md

@@ -1,155 +0,0 @@
-# Documentation Manifest Schema
-
-## Purpose
-
-The `docs-manifest.json` file maps code modules to their documentation artifacts. It is the single source of truth for documentation drift detection.
-
-**Location:** Project root (next to `package.json` or `.sln`)
-
-## Schema
-
-```json
-{
-  "version": "1.0",
-  "lastUpdated": "2026-01-30T10:00:00Z",
-  "modules": {
-    "business/{app}/{module}": {
-      "featureId": "FEAT-NNN",
-      "displayName": "Module Display Name",
-      "codeFiles": [
-        "src/SmartStack.Domain/Entities/Business/{Entity}.cs",
-        "src/SmartStack.Application/Features/{Module}/Commands/*.cs",
-        "src/SmartStack.Application/Features/{Module}/Queries/*.cs",
-        "src/SmartStack.Api/Controllers/Business/{Module}Controller.cs"
-      ],
-      "docFiles": [
-        "web/smartstack-web/src/pages/docs/business/{app}/{module}/doc-data.ts",
-        "web/smartstack-web/src/i18n/locales/fr/docs-{app}-{module}.json"
-      ],
-      "baOutputs": [
-        ".business-analyse/business/{app}/modules/{module}/features/FEAT-NNN/"
-      ],
-      "screenshots": {
-        "step1": "/assets/docs/{module}/step-1.png",
-        "step2": "/assets/docs/{module}/step-2.png"
-      },
-      "lastCodeChange": "2026-01-30T10:00:00Z",
-      "lastDocUpdate": "2026-01-30T10:00:00Z",
-      "gitCommitCode": "abc123",
-      "gitCommitDoc": "def456",
-      "status": "synced"
-    }
-  }
-}
-```
-
-## Fields
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `version` | string | Yes | Schema version (always "1.0") |
-| `lastUpdated` | ISO date | Yes | Last time manifest was modified |
-| `modules` | object | Yes | Map of module path → module entry |
-
-### Module Entry
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `featureId` | string | Yes | BA feature ID (FEAT-NNN) |
-| `displayName` | string | Yes | Human-readable module name |
-| `codeFiles` | string[] | Yes | Source code files for this module |
-| `docFiles` | string[] | Yes | Documentation files (doc-data.ts, i18n) |
-| `baOutputs` | string[] | No | Business Analysis output directory |
-| `screenshots` | object | No | Map of stepKey → image path |
-| `lastCodeChange` | ISO date | Yes | Last code modification timestamp |
-| `lastDocUpdate` | ISO date | Yes | Last documentation update timestamp |
-| `gitCommitCode` | string | Yes | Git SHA of last code commit |
-| `gitCommitDoc` | string | Yes | Git SHA of last doc commit |
-| `status` | enum | Yes | `synced`, `drift`, or `missing` |
-
-## Status Values
-
-| Status | Meaning | Action |
-|--------|---------|--------|
-| `synced` | Documentation matches code | No action needed |
-| `drift` | Code changed after last doc update | Run `/documentation` to update |
-| `missing` | Module exists in code but has no documentation | Run `/business-analyse` or `/documentation` to create |
-
-## Usage
-
-### Created by
-- BA skill step-06 (doc-html) after generating documentation
-- Documentation skill after creating/updating a module page
-
-### Read by
-- `docs-context-reader` agent (for context injection)
-- `docs-sync-checker` agent (for drift detection)
-- BA step-04 (validate) for freshness check
-- Drift hook (pre-commit) for commit warnings
-
-### Updated by
-- BA step-06 (on doc generation)
-- Documentation skill (on doc update)
-
-## Drift Detection Logic
-
-```
-IF module.lastCodeChange > module.lastDocUpdate:
-    module.status = "drift"
-ELSE:
-    module.status = "synced"
-```
-
-## Example
-
-```json
-{
-  "version": "1.0",
-  "lastUpdated": "2026-01-30T14:30:00Z",
-  "modules": {
-    "business/support/sla": {
-      "featureId": "FEAT-003",
-      "displayName": "SLA Management",
-      "codeFiles": [
-        "src/SmartStack.Domain/Entities/Business/Sla.cs",
-        "src/SmartStack.Application/Features/Sla/Commands/CreateSlaCommand.cs",
-        "src/SmartStack.Application/Features/Sla/Queries/GetSlaListQuery.cs",
-        "src/SmartStack.Api/Controllers/Business/SlaController.cs"
-      ],
-      "docFiles": [
-        "web/smartstack-web/src/pages/docs/business/support/sla/doc-data.ts",
-        "web/smartstack-web/src/i18n/locales/fr/docs-support-sla.json"
-      ],
-      "baOutputs": [
-        ".business-analyse/business/Support/modules/Sla/features/FEAT-003/"
-      ],
-      "screenshots": {
-        "step1": "/assets/docs/sla/step-1.png",
-        "step2": "/assets/docs/sla/step-2.png",
-        "step3": "/assets/docs/sla/step-3.png"
-      },
-      "lastCodeChange": "2026-01-28T16:00:00Z",
-      "lastDocUpdate": "2026-01-30T14:30:00Z",
-      "gitCommitCode": "a1b2c3d",
-      "gitCommitDoc": "e4f5g6h",
-      "status": "synced"
-    },
-    "business/support/tickets": {
-      "featureId": "FEAT-005",
-      "displayName": "Ticket Management",
-      "codeFiles": [
-        "src/SmartStack.Domain/Entities/Business/Ticket.cs",
-        "src/SmartStack.Api/Controllers/Business/TicketsController.cs"
-      ],
-      "docFiles": [],
-      "baOutputs": [],
-      "screenshots": {},
-      "lastCodeChange": "2026-01-29T10:00:00Z",
-      "lastDocUpdate": "1970-01-01T00:00:00Z",
-      "gitCommitCode": "x7y8z9a",
-      "gitCommitDoc": "",
-      "status": "missing"
-    }
-  }
-}
-```

package/templates/skills/_resources/formatting-guide.md

@@ -1,124 +0,0 @@
-# Formatting Guide - Clickable References & Copyable Commands
-
-This guide defines formatting standards for all command templates.
-
-## File References (clickable)
-
-### Standard format
-
-```markdown
-<!-- Simple file -->
-[filename.ts](path/to/filename.ts)
-
-<!-- File with line -->
-[filename.ts:42](path/to/filename.ts#L42)
-
-<!-- File with line range -->
-[filename.ts:42-51](path/to/filename.ts#L42-L51)
-
-<!-- Folder -->
-[src/components/](src/components/)
-```
-
-### Concrete examples
-
-| Context | Format | Result |
-|---------|--------|--------|
-| GitFlow Config | `[config.json](.claude/gitflow/config.json)` | [config.json](.claude/gitflow/config.json) |
-| Specific line | `[installer.ts:45](src/lib/installer.ts#L45)` | [installer.ts:45](src/lib/installer.ts#L45) |
-| Range | `[utils.ts:10-25](src/utils.ts#L10-L25)` | [utils.ts:10-25](src/utils.ts#L10-L25) |
-| Folder | `[templates/](templates/)` | [templates/](templates/) |
-
-### Avoid
-
-```markdown
-<!-- INCORRECT -->
-`config.json`
-`.claude/gitflow/config.json`
-The config.json file
-```
-
-## Commands (copyable)
-
-### Claude Code Commands
-
-Always in simple code block:
-
-```markdown
-```
-/gitflow init --exec
-```
-```
-
-### Bash/Shell Commands
-
-With language specified:
-
-```markdown
-```bash
-npm run build
-dotnet ef migrations add Initial
-```
-```
-
-### Multiple commands
-
-```markdown
-```bash
-# Step 1: Build
-npm run build
-
-# Step 2: Test
-npm test
-```
-```
-
-### Avoid
-
-```markdown
-<!-- INCORRECT -->
-Execute `/gitflow init`
-Run the command `npm run build`
-```
-
-## Command Tables
-
-Recommended format for listing commands:
-
-```markdown
-| Command | Description |
-|---------|-------------|
-| `/test-web --quick` | Quick tests |
-| `/test-web --chrome` | E2E tests |
-```
-
-## Paths in Instructions
-
-### Good example
-
-```markdown
-1. Create file [config.json](.claude/test-web/config.json)
-2. Execute:
-   ```
-   /test-web --quick
-   ```
-3. Check report in [reports/](.claude/test-web/reports/)
-```
-
-### Bad example
-
-```markdown
-1. Create file `.claude/test-web/config.json`
-2. Execute `/test-web --quick`
-3. Check report in `.claude/test-web/reports/`
-```
-
-## Summary
-
-| Element | Format | Example |
-|---------|--------|---------|
-| File | `[name](path)` | `[config.json](.claude/config.json)` |
-| File:line | `[name:L](path#LX)` | `[utils.ts:42](src/utils.ts#L42)` |
-| Folder | `[name/](path/)` | `[templates/](templates/)` |
-| Claude Command | ` ``` code ``` ` | `/command --flag` |
-| Bash Command | ` ```bash code ``` ` | `npm run build` |

package/templates/skills/_resources/mcp-validate-documentation-spec.md

@@ -1,181 +0,0 @@
-# MCP Tool Specification: validate_documentation
-
-## Status: FUTURE
-
-> This tool does not yet exist in SmartStack.mcp. This file is a specification for its implementation.
-> Until implemented, use the `docs-sync-checker` agent as a fallback.
-
-## Tool Definition
-
-```typescript
-{
-  name: "mcp__smartstack__validate_documentation",
-  description: "Validate documentation freshness, completeness, and accuracy for SmartStack modules",
-  parameters: {
-    module: {
-      type: "string",
-      description: "Module path (e.g., 'business/support/sla'). Empty for all modules.",
-      required: false
-    },
-    checkType: {
-      type: "string",
-      enum: ["freshness", "completeness", "accuracy", "all"],
-      default: "all",
-      description: "Type of validation to perform"
-    },
-    path: {
-      type: "string",
-      description: "Project path (default: SmartStack.app path from config)",
-      required: false
-    }
-  }
-}
-```
-
-## Check Types
-
-### freshness
-Compare `docs-manifest.json` with git history to detect stale documentation.
-
-**Input:** manifest entries, git log
-**Logic:**
-```
-FOR each module in manifest:
-  lastCodeCommit = git log -1 --format="%aI" -- {codeFiles}
-  IF lastCodeCommit > module.lastDocUpdate:
-    status = "drift"
-    driftDays = daysBetween(module.lastDocUpdate, lastCodeCommit)
-```
-
-**Output:**
-```json
-{
-  "modules": [
-    {
-      "path": "business/support/sla",
-      "status": "drift",
-      "driftDays": 15,
-      "lastCodeChange": "2026-01-28",
-      "lastDocUpdate": "2026-01-13"
-    }
-  ]
-}
-```
-
-### completeness
-Verify that documented modules have all 8 business-first sections.
-
-**Input:** doc-data.ts files, i18n JSON files
-**Logic:**
-```
-FOR each module with documentation:
-  Read doc-data.ts
-  Check presence of:
-    1. overview (valeur métier)
-    2. useCases (cas d'usage)
-    3. benefits (bénéfices concrets) — in i18n
-    4. beforeAfter (avant/après) — in i18n
-    5. features (fonctionnalités)
-    6. steps (comment ça marche)
-    7. faq (FAQ métier) — in i18n
-    8. technicalRef (référence technique)
-  Report missing sections
-```
-
-**Output:**
-```json
-{
-  "modules": [
-    {
-      "path": "business/support/sla",
-      "completeness": "6/8",
-      "missingSections": ["beforeAfter", "faq"],
-      "i18nComplete": { "fr": true, "en": false, "it": false, "de": false }
-    }
-  ]
-}
-```
-
-### accuracy
-Compare documented permissions, endpoints, and entities against actual code.
-
-**Input:** doc-data.ts, controllers, PermissionConfiguration.cs, entities
-**Logic:**
-```
-FOR each module:
-  documentedPermissions = docData.permissions
-  actualPermissions = scan PermissionConfiguration.cs for module path
-  IF documentedPermissions != actualPermissions:
-    issues.push("permission mismatch")
-
-  documentedEndpoints = docData.apiEndpoints
-  actualEndpoints = scan Controller for [Http*] attributes
-  IF documentedEndpoints != actualEndpoints:
-    issues.push("endpoint mismatch")
-
-  documentedEntities = docData (entity references)
-  actualEntities = scan Domain/Entities for module
-  IF documentedEntities != actualEntities:
-    issues.push("entity mismatch")
-```
-
-**Output:**
-```json
-{
-  "modules": [
-    {
-      "path": "business/support/sla",
-      "accuracy": "partial",
-      "issues": [
-        {
-          "type": "endpoint_mismatch",
-          "documented": ["GET /api/support/sla", "POST /api/support/sla"],
-          "actual": ["GET /api/support/sla", "POST /api/support/sla", "PATCH /api/support/sla/{id}/status"],
-          "message": "Endpoint PATCH /api/support/sla/{id}/status exists in code but not in documentation"
-        }
-      ]
-    }
-  ]
-}
-```
-
-## Combined Output (checkType: "all")
-
-```json
-{
-  "summary": {
-    "totalModules": 5,
-    "synced": 2,
-    "drift": 2,
-    "missing": 1,
-    "overallScore": "60%"
-  },
-  "modules": [
-    {
-      "path": "business/support/sla",
-      "freshness": { "status": "drift", "driftDays": 15 },
-      "completeness": { "score": "6/8", "missingSections": ["beforeAfter", "faq"] },
-      "accuracy": { "status": "partial", "issues": 1 }
-    }
-  ],
-  "recommendations": [
-    "Run `/documentation` for business/support/sla to sync documentation",
-    "Run `/business-analyse` for business/support/tickets to create documentation"
-  ]
-}
-```
-
-## Integration Points
-
-| Consumer | When | Fallback |
-|----------|------|----------|
-| BA step-04 (validate) | During specification validation | Read manifest + git log |
-| Drift hook (pre-commit) | Before commit | Bash script reading manifest |
-
-## Implementation Notes
-
-- Tool should read `docs-manifest.json` from project root
-- Must handle missing manifest gracefully (return "no manifest" status)
-- Git operations should use `--no-pager` flag
-- Performance: cache git log results across modules
-- The tool should be idempotent (no side effects)

package/templates/skills/_shared.md

@@ -1,228 +0,0 @@
-# Skills SmartStack - Shared Functions
-
-> **SmartStack CLI** v{{SMARTSTACK_VERSION}}
-
-## Model Strategy
-
-| Task | Model | Reason |
-|------|-------|--------|
-| Code generation | **Sonnet** | Optimal quality/cost ratio |
-| Security audit | **Opus** | Critical analysis required |
-| Final validation | **Opus** | Architectural decisions |
-
-## SmartStack Architecture
-
-```
-Domain → Application → Infrastructure → API → Web
-```
-
-### Layers
-| Layer | Responsibility | Namespace | Folder Hierarchy |
-|-------|-----------------|-----------|------------------|
-| Domain | Entities, ValueObjects | `SmartStack.Domain.{App}.{Module}` | `Domain/{App}/{Module}/` |
-| Application | Interfaces (Common), DTOs | `SmartStack.Application.Common.Interfaces` / `.{App}.{Module}.DTOs` | `Application/Common/Interfaces/` + `Application/{App}/{Module}/DTOs/` |
-| Infrastructure | Service Impl, EF Core | `SmartStack.Infrastructure.Services.{App}.{Module}` | `Infrastructure/Services/{App}/{Module}/` + `Persistence/Configurations/{App}/{Module}/` |
-| API | Controllers, Middleware | `SmartStack.Api.Controllers` | `Api/Controllers/` |
-| Web | React components, pages | N/A | `pages/{app}/{module}/` + `components/{module}/` |
-
-## Permissions (2 mandatory files)
-
-### 1. Permissions.cs (Application layer)
-```csharp
-public static class {Module}
-{
-    public const string View = "{app}.{module}.view";
-    public const string Create = "{app}.{module}.create";
-    public const string Update = "{app}.{module}.update";
-    public const string Delete = "{app}.{module}.delete";
-}
-```
-
-### 2. PermissionConfiguration.cs (Infrastructure layer)
-```csharp
-builder.HasData(
-    new { Id = nextId++, Path = Permissions.{Module}.View, ... },
-    new { Id = nextId++, Path = Permissions.{Module}.Create, ... },
-    ...
-);
-```
-
-## i18n (4 mandatory languages)
-
-| Language | File | Code |
-|----------|------|------|
-| French | `fr.json` | `fr` |
-| English | `en.json` | `en` |
-| Italian | `it.json` | `it` |
-| German | `de.json` | `de` |
-
-### i18n Structure
-```json
-{
-  "{application}": {
-    "{module}": {
-      "title": "...",
-      "fields": { ... },
-      "actions": { ... },
-      "messages": { ... }
-    }
-  }
-}
-```
-
-## Common Services to Inject
-
-| Service | Usage |
-|---------|-------|
-| `IApplicationDbContext` | DB access |
-| `ICurrentUserService` | Current user |
-| `ILogger<T>` | Logging |
-| `IMapper` | AutoMapper |
-| `IPermissionService` | Permission cache |
-
-## Security Validation
-
-### Critical Logs
-| Event | Level |
-|-------|-------|
-| Failed login | `Critical` |
-| Permission denied | `Critical` |
-| Account locked | `Critical` |
-| Password change | `Warning` |
-| Deletion | `Warning` |
-
-### System Account Protection
-```csharp
-if (entity.UserType == UserType.System || entity.UserType == UserType.LocalAdmin)
-    return BadRequest(new { message = "Cannot modify system accounts" });
-```
-
-## FORBIDDEN: Temporary Files and Scripts (ALL SKILLS)
-
-> **ABSOLUTE PROHIBITION: NEVER create temporary files, scripts, or helper files.**
-
-This includes but is not limited to:
-- `.ps1`, `.sh`, `.bat`, `.cmd` scripts
-- `temp-*`, `tmp-*`, `helper-*` files
-- Any file created solely to discover types, scan DLLs, or read metadata
-
-**How to discover .NET types WITHOUT scripts:**
-| Need | Tool to Use |
-|------|-------------|
-| Find a class/entity | `Grep` for `class {Name}` in `*.cs` files |
-| Find services/interfaces | `Glob` for `**/I*Service.cs` in Application layer |
-| Find NuGet packages | `Read` the `.csproj` file directly |
-| Find existing entities | `Glob` for `**/*.cs` in Domain layer |
-| Validate conventions | MCP `validate_conventions` tool |
-| Cannot find after 2 tries | **ASK the user** |
-
-**If you catch yourself about to create a script file: STOP. Use the tools above instead.**
-
-## Common Validation Checklist
-
-```
-□ Permissions created (Permissions.cs + PermissionConfiguration.cs)
-□ EF Core migration created
-□ i18n 4 languages (fr, en, it, de)
-□ Unit tests
-□ API documentation (ProducesResponseType)
-```
-
-## MCP Prerequisite Guard (BLOCKING)
-
-Skills that depend on SmartStack MCP **MUST** verify connectivity before proceeding. This check is **BLOCKING** - the skill cannot continue without MCP.
-
-### Detection Method
-
-At skill initialization (step-00-init), attempt a minimal MCP call:
-
-```
-mcp__smartstack__validate_conventions({ checks: ["tables"] })
-```
-
-### Decision Matrix
-
-| Result | Action |
-|--------|--------|
-| Success response | Set `mcp_available = true`, continue workflow |
-| Connection error / tool not found | **STOP EXECUTION** - display error below |
-
-### Blocking Error (STOP)
-
-If MCP is not available, display this message and **STOP the skill immediately**:
-
-```
-═══════════════════════════════════════════════════════════════
-  MCP SMARTSTACK NOT AVAILABLE - SKILL BLOCKED
-═══════════════════════════════════════════════════════════════
-
-  The SmartStack MCP server is required for this skill but
-  could not be reached.
-
-  To install:
-    claude mcp add smartstack -- npx --package @atlashub/smartstack-cli smartstack-mcp
-
-  To verify:
-    /mcp healthcheck
-
-  After installation, restart Claude Code and retry.
-
-═══════════════════════════════════════════════════════════════
-```
-
-**DO NOT** offer fallback modes, manual instructions, or degraded execution. The skill MUST stop.
-
-### Skills Requiring MCP
-
-| Skill | MCP Required | Reason |
-|-------|:---:|--------|
-| business-analyse | **YES** | Analysis, specification, validation |
-| application | **YES** | Navigation + code generation |
-| controller | **YES** | Controller scaffolding |
-| business-analyse-develop | **YES** | Iterative code generation |
-| validate | **YES** | Convention validation |
-| efcore | **YES** | Migration management |
-| review-code | **YES** | Code review |
-| gitflow | NO | Git operations only |
-| explore | NO | Code search only |
-| mcp | NO | Self-check skill |
-
-## MCP Tools References
-
-### Outils Core
-
-| Tool | Usage | Used By |
-|------|-------|---------|
-| `mcp__smartstack__validate_conventions` | Valider conventions SmartStack (tables, migrations, services, namespaces, entities, tenants, controllers) | application, controller, business-analyse-develop |
-| `mcp__smartstack__scaffold_extension` | Génération code (feature, entity, service, controller, component, dto, validator, repository) | application, business-analyse-develop |
-| `mcp__smartstack__check_migrations` | Analyser migrations EF Core (conflits, ordre, ModelSnapshot) | application, business-analyse-develop |
-| `mcp__smartstack__api_docs` | Documentation API depuis Swagger/OpenAPI ou controllers | controller |
-| `mcp__smartstack__suggest_migration` | Suggérer nom migration ({context}_v{version}_{sequence}_{Description}) | application, business-analyse-develop |
-| `mcp__smartstack__generate_permissions` | Générer permissions RBAC depuis NavRoute | application, business-analyse-develop |
-
-### Outils Tests
-
-| Tool | Usage | Used By |
-|------|-------|---------|
-| `mcp__smartstack__scaffold_tests` | Générer tests unitaires/intégration/sécurité | application, business-analyse-develop |
-| `mcp__smartstack__analyze_test_coverage` | Analyser couverture de tests du projet | business-analyse-develop |
-| `mcp__smartstack__validate_test_conventions` | Valider conventions de nommage des tests | business-analyse-develop |
-| `mcp__smartstack__suggest_test_scenarios` | Suggérer scénarios de test basés sur le code | business-analyse-develop |
-
-### Outils Frontend
-
-| Tool | Usage | Used By |
-|------|-------|---------|
-| `mcp__smartstack__scaffold_api_client` | Générer client TypeScript avec NavRoute | application, business-analyse-develop |
-| `mcp__smartstack__scaffold_routes` | Générer React Router depuis NavRoute backend | application, business-analyse-develop |
-| `mcp__smartstack__validate_frontend_routes` | Valider synchronisation routes frontend/backend | application, business-analyse-develop |
-| `mcp__smartstack__scaffold_frontend_extension` | Générer infrastructure extension frontend | application |
-| `mcp__smartstack__analyze_extension_points` | Analyser points d'extension dans les pages React | application |
-
-### Outils Documentation
-
-| Tool | Usage | Used By |
-|------|-------|---------|
-| `mcp__smartstack__validate_documentation` | Valider fraîcheur, complétude et exactitude de la documentation (FUTURE - voir `_resources/mcp-validate-documentation-spec.md`) | documentation |
-
-> **Fallback** : En attendant l'implémentation MCP, utiliser l'agent `docs-sync-checker` pour la détection de drift et l'agent `docs-context-reader` pour l'injection de contexte documentation.