@atlashub/smartstack-cli 1.13.2 → 1.14.0

package/templates/commands/explain.md

@@ -1,186 +0,0 @@
----
-description: Deep explanation of code features with tracing, analysis, and visual diagrams
-allowed-tools: Read, Glob, Grep, Task
-argument-hint: <feature-or-topic>
----
-
-You are a code archaeologist. Your mission is to deeply understand a specific feature or code area, trace through all relevant files, and explain it with absolute clarity.
-
-## Workflow
-
-1. **UNDERSTAND THE QUESTION**: Parse what needs explaining
-   - Identify the feature/topic/function to explain
-   - Determine scope (single feature vs system interaction)
-   - **CRITICAL**: Ask clarifying questions if topic is ambiguous
-
-2. **ULTRA THINK - TRACE THE CODE**: Deep analysis phase
-   - Find entry point (where does this feature start?)
-   - Trace execution flow through all files
-   - Map dependencies and relationships
-   - Read files in logical order (not alphabetical)
-   - **MUST**: Follow the actual code path, not assumptions
-   - Document decisions and trade-offs found in code
-
-3. **COLLECT EVIDENCE**: Gather concrete examples
-   - Extract relevant code snippets
-   - Identify configuration that affects behavior
-   - Find tests that demonstrate usage
-   - Note comments explaining "why" decisions
-   - **STAY FOCUSED**: Only collect what's relevant to the question
-
-4. **SYNTHESIZE UNDERSTANDING**: Connect the pieces
-   - How do files interact?
-   - What's the data flow?
-   - What design patterns are used?
-   - What are the key decisions and why?
-   - What constraints shaped this implementation?
-
-5. **CREATE CLEAR OUTPUT**: Present findings
-   - Start with objective statement
-   - List files in logical reading order
-   - Provide ASCII diagram of relationships
-   - Explain key decisions with code examples
-   - **PRIORITY**: Clarity over completeness
-
-## Output Format
-
-```markdown
-## Explanation: [Feature/Topic]
-
-### Objective
-[2-3 sentences explaining what this feature does and why it exists]
-
-### Files to Read (in order)
-1. `path/to/entry-point.ts` - Where the feature starts
-2. `path/to/core-logic.ts` - Main implementation
-3. `path/to/dependencies.ts` - Supporting functionality
-4. `path/to/config.ts` - Configuration affecting behavior
-
-### Architecture Diagram
-```
-┌─────────────────┐
-│   Entry Point   │ Feature starts here
-└────────┬────────┘
-         │
-         ▼
-┌─────────────────┐
-│   Core Logic    │ Main implementation
-└────────┬────────┘
-         │
-         ├──────────┐
-         ▼          ▼
-┌──────────┐  ┌──────────┐
-│ Helper A │  │ Helper B │ Supporting functions
-└──────────┘  └──────────┘
-```
-
-### Key Decisions
-
-#### Decision 1: [What was decided]
-**Why**: [Reasoning found in code/comments]
-**Trade-off**: [What was sacrificed]
-
-**Code example**:
-```language
-// Concrete example from codebase showing this decision
-```
-
-#### Decision 2: [Another decision]
-**Why**: [Reasoning]
-**Alternative considered**: [What wasn't chosen and why]
-
-### Data Flow
-
-```
-User Input
-    │
-    ▼
-Validation (file:line)
-    │
-    ▼
-Processing (file:line)
-    │
-    ├─→ Side Effect A (file:line)
-    │
-    ▼
-Final Output (file:line)
-```
-
-### Implementation Details
-
-**Pattern Used**: [e.g., Factory, Repository, Observer]
-
-**Key Functions**:
-- `functionName()` in `file.ts:123` - What it does
-- `otherFunction()` in `file.ts:456` - Its role
-
-**Configuration**:
-- `CONFIG_VAR` affects [behavior]
-- Default values set in `config.ts:789`
-
-### Complexity Points
-
-**Where it gets tricky**:
-1. [Complex area 1] - Why it's complex and how it's handled
-2. [Complex area 2] - Edge cases and solutions
-
-### Summary
-
-[3-4 sentences tying everything together - the "aha!" moment explanation]
-```
-
-## Analysis Techniques
-
-### Tracing Entry Points
-```bash
-# Find where feature is called/imported
-grep -r "featureName" --include="*.ts"
-
-# Find route handlers
-grep -r "router\." --include="*.ts"
-
-# Find React components
-glob "**/*ComponentName*.tsx"
-```
-
-### Understanding Dependencies
-- Read imports at top of each file
-- Trace backward from exports
-- Check for dependency injection
-- Look for factory/builder patterns
-
-### Reading Order Priority
-1. Entry point (route/handler/component)
-2. Core business logic
-3. Data models/types
-4. Helper utilities
-5. Configuration
-
-## Execution Rules
-
-- **MUST**: Read files in logical execution order
-- **MUST**: Create ASCII diagrams showing relationships
-- **MUST**: Include file:line references for all key code
-- **NEVER**: Assume patterns without verification
-- **NEVER**: Skip the ultra thinking phase
-- **CRITICAL**: Explain the "why" behind decisions, not just "what"
-- Use parallel `Task` agents for broad searches
-- Focus deeply once key files are identified
-
-## Ultra Thinking Checklist
-
-Before writing output, verify you can answer:
-- [ ] Where does this feature start executing?
-- [ ] What's the complete file dependency chain?
-- [ ] What design patterns are used and why?
-- [ ] What are the key trade-offs made?
-- [ ] How does data transform through the flow?
-- [ ] What would break if X file was removed?
-
-## Priority
-
-Understanding > Speed. Take time to truly comprehend before explaining.
-
----
-
-User: $ARGUMENTS

package/templates/commands/feature-full.md

@@ -1,267 +0,0 @@
-# /feature-full - Creation Feature Complete OneShot
-
-> **Synergie Skill/Commande:**
-> - **Skill** (`templates/skills/feature-full/`) → Invocation automatique par Claude
-> - **Commande** (`/feature-full`) → Invocation manuelle par l'utilisateur
->
-> Ce skill orchestre tous les autres skills pour une experience de developpement optimale.
-
----
-
-## ARGUMENTS
-
-```
-/feature-full <entity> [options]
-```
-
-| Option | Description |
-|--------|-------------|
-| `--area` | Zone de navigation (platform, business, personal) |
-| `--module` | Module parent |
-| `--notifications` | Activer les notifications (defaut: oui) |
-| `--workflows` | Activer les workflows/emails (defaut: non) |
-| `--ai` | Activer l'assistance IA (defaut: non) |
-| `--crud` | Operations CRUD (defaut: all) |
-
----
-
-## WORKFLOW ONESHOT
-
-### PHASE 1: ANALYSE (2 min)
-
-```
-AskUserQuestion: {
-  questions: [
-    {
-      header: "Entity",
-      question: "Quel est le nom de l'entite principale ?",
-      options: [
-        { label: "Saisie libre", description: "Ex: Product, Order, Customer" }
-      ]
-    },
-    {
-      header: "Area",
-      question: "Dans quelle zone de navigation ?",
-      options: [
-        { label: "platform", description: "Administration systeme" },
-        { label: "business", description: "Fonctionnalites metier" },
-        { label: "personal", description: "Espace personnel" }
-      ]
-    },
-    {
-      header: "Integrations",
-      question: "Quelles integrations activer ?",
-      multiSelect: true,
-      options: [
-        { label: "Notifications", description: "In-app + SignalR (Recommended)" },
-        { label: "Workflows", description: "Emails automatiques" },
-        { label: "AI", description: "Assistance IA" }
-      ]
-    }
-  ]
-}
-```
-
-### PHASE 2: GENERATION (30 min)
-
-Execute automatiquement dans l'ordre :
-
-```
-1. DOMAIN LAYER
-   → Entity + Enums + Factory Methods
-   → /application templates-backend
-
-2. APPLICATION LAYER
-   → Interface + DTOs + Permissions
-   → /application templates-backend
-
-3. INFRASTRUCTURE LAYER
-   → EF Core Configuration + Service
-   → /application templates-backend
-   → /efcore:migration
-
-4. API LAYER
-   → Controller + Authorize + Swagger
-   → /controller:create
-
-5. WEB LAYER
-   → Pages + Hooks + i18n + Routes
-   → /application templates-frontend
-   → /ui-components
-
-6. NOTIFICATIONS (si active)
-   → NotificationType + Service injection
-   → /notification add
-
-7. WORKFLOWS (si active)
-   → Trigger + Workflow + Template
-   → /workflow create
-
-8. AI (si active)
-   → Prompt + Schema + Service
-   → /ai-prompt create
-
-9. VALIDATION
-   → dotnet build
-   → npm run build
-   → npm run lint
-```
-
-### PHASE 3: RESUME (1 min)
-
-Affiche le resume de tout ce qui a ete cree.
-
----
-
-## EXEMPLE COMPLET
-
-```bash
-/feature-full Product --area business --notifications --workflows --ai
-```
-
-**Genere automatiquement :**
-
-| Layer | Fichiers |
-|-------|----------|
-| Domain | `Product.cs`, `ProductStatus.cs` |
-| Application | `IProductService.cs`, `ProductDto.cs`, `Permissions.cs` |
-| Infrastructure | `ProductConfiguration.cs`, `ProductService.cs`, `PermissionConfiguration.cs` |
-| API | `ProductsController.cs` |
-| Web | `ProductsPage.tsx`, `useProducts.ts`, `productsApi.ts`, i18n (4 langues) |
-| Notifications | `NotificationType.ProductCreated`, SignalR integration |
-| Workflows | `product.created` trigger, email template |
-| AI | `product-analyzer` prompt, `ProductAnalysisResult` |
-
----
-
-## TEMPLATES ORCHESTRATION
-
-### Template Execution Order
-
-```typescript
-// 1. Domain
-await generateDomainLayer(entity, config);
-
-// 2. Application
-await generateApplicationLayer(entity, config);
-
-// 3. Infrastructure
-await generateInfrastructureLayer(entity, config);
-await runCommand('/efcore:migration', `Add${entity}`);
-
-// 4. API
-await runCommand('/controller:create', entity);
-
-// 5. Web
-await generateWebLayer(entity, config);
-
-// 6. Integrations
-if (config.notifications) {
-  await runCommand('/notification', `add ${entity}`);
-}
-if (config.workflows) {
-  await runCommand('/workflow', `create ${entity}.created`);
-}
-if (config.ai) {
-  await runCommand('/ai-prompt', `create ${entity}-analyzer`);
-}
-
-// 7. Validation
-await runCommand('dotnet', 'build');
-await runCommand('npm', 'run build');
-await runCommand('npm', 'run lint');
-```
-
----
-
-## CHECKLIST AUTOMATIQUE
-
-```
-DOMAIN LAYER
-  ✓ Entity {Entity}.cs avec Factory Method
-  ✓ Enum {Entity}Status.cs
-  ✓ IAuditableEntity implemente
-
-APPLICATION LAYER
-  ✓ Interface I{Entity}Service.cs
-  ✓ DTOs: {Entity}Dto, Create/Update Requests
-  ✓ Permissions dans Permissions.cs
-  ✓ Permissions dans PermissionConfiguration.cs
-
-INFRASTRUCTURE LAYER
-  ✓ {Entity}Configuration.cs (EF Core)
-  ✓ {Entity}Service.cs implementation
-  ✓ DbSet<{Entity}> dans ApplicationDbContext
-  ✓ DI registration
-  ✓ Migration EF Core
-
-API LAYER
-  ✓ {Entity}Controller.cs
-  ✓ [Authorize] + [RequirePermission]
-  ✓ [ProducesResponseType]
-  ✓ Logging
-
-WEB LAYER
-  ✓ {module}Api.ts
-  ✓ use{Module}.ts (avec SignalR si notifications)
-  ✓ {Module}Page.tsx
-  ✓ {Module}Form.tsx
-  ✓ {Module}DetailPage.tsx
-  ✓ i18n: fr, en, it, de
-  ✓ Routes dans App.tsx
-
-NOTIFICATIONS (si active)
-  ✓ NotificationType ajoute
-  ✓ SendNotificationAsync dans service
-  ✓ useSignalR dans hook
-
-WORKFLOWS (si active)
-  ✓ Trigger cree
-  ✓ Workflow cree
-  ✓ Email template
-  ✓ TriggerAsync dans service
-
-AI (si active)
-  ✓ Prompt cree
-  ✓ OutputSchema
-  ✓ DTO Result
-  ✓ ExecutePromptAsync dans service
-  ✓ Bouton IA frontend
-
-VALIDATION
-  ✓ dotnet build OK
-  ✓ npm run build OK
-  ✓ npm run lint OK
-```
-
----
-
-## REGLES ABSOLUES
-
-1. **TOUJOURS** suivre l'ordre des phases
-2. **TOUJOURS** valider chaque phase avant la suivante
-3. **TOUJOURS** utiliser les skills specialises
-4. **TOUJOURS** respecter l'architecture en couches
-5. **TOUJOURS** creer les 4 langues i18n
-6. **TOUJOURS** ajouter les permissions dans les 2 fichiers
-7. **JAMAIS** sauter une phase
-8. **JAMAIS** generer du code sans validation
-9. **JAMAIS** oublier les integrations demandees
-
----
-
-## SKILLS ORCHESTRES
-
-| Skill | Phase | Action |
-|-------|-------|--------|
-| `/application` | 1-5 | Generation full-stack |
-| `/controller` | 4 | Controller API |
-| `/ui-components` | 5 | Composants UI |
-| `/notification` | 6 | Notifications |
-| `/workflow` | 7 | Workflows/Emails |
-| `/ai-prompt` | 8 | IA |
-| `/efcore:migration` | 3 | Migration DB |
-
----
-
-User: $ARGUMENTS

package/templates/commands/gitflow/1-init.md

@@ -1,188 +0,0 @@
----
-description: Phase 1 - Initialize GitFlow structure with versioning and EF Core configuration
-agent: gitflow-init
-model: sonnet
----
-
-# GitFlow Init
-
-**Arguments:** `$ARGUMENTS`
-
-> **Ref:** Fonctions partagées dans [_shared.md](_shared.md)
-
----
-
-## Détection du Mode
-
-| Condition | Mode |
-|-----------|------|
-| `$ARGUMENTS` contient URL (`https://` ou `git@`) | **MODE A: Clone** |
-| Pas dans un repo git ET pas d'URL | **MODE C: Interactive** |
-| Dans un repo git existant | **MODE B: Existing** |
-
----
-
-## MODE A: Clone (URL détectée)
-
-### Workflow Obligatoire
-
-**NE CRÉER AUCUN DOSSIER** avant confirmation utilisateur.
-
-#### 1. Extraire nom suggéré
-```bash
-SUGGESTED_NAME=$(basename "$REPO_URL" .git)
-```
-
-#### 2. Demander emplacement
-Question: "Où créer ce projet?" | Options: `C:/Dev`, `Répertoire courant`, `Chemin personnalisé`
-
-#### 3. Demander nom projet
-Question: "Nom du dossier projet?" | Options: `{SUGGESTED_NAME} (Recommandé)`, `Nom personnalisé`
-
-#### 4. Confirmer
-Afficher récapitulatif complet avec chemin final: `{TARGET_FOLDER}/{PROJECT_NAME}/`
-
-#### 5. Créer structure (après confirmation)
-
-```bash
-mkdir -p "$PROJECT_BASE" && cd "$PROJECT_BASE"
-git clone --bare "$REPO_URL" .bare
-echo "gitdir: ./.bare" > .git
-cd .bare && git config core.bare false && git config core.worktree ".." && cd ..
-mkdir -p features releases hotfixes
-git worktree add "01-Main" main
-git worktree add "02-Develop" develop
-cd "02-Develop"
-mkdir -p .claude/gitflow/{plans,logs,migrations,backup,cache}
-```
-
-**Structure résultante:**
-```
-{project}/
-├── .bare/           # Bare repository
-├── 01-Main/         # main branch
-├── 02-Develop/      # develop branch ← WORKING DIR
-├── features/        # Feature worktrees
-├── releases/        # Release worktrees
-└── hotfixes/        # Hotfix worktrees
-```
-
----
-
-## MODE B: Existing Repository
-
-### 1. Vérifier structure existante
-
-Si `.claude/gitflow/config.json` existe:
-- Options: `Migrate` (màj config) | `Reset` (backup + recréer) | `Skip`
-
-### 2. Analyser le repo
-
-**Détections:**
-- Branches: main/master, develop
-- Version: `*.csproj` > `Directory.Build.props` > `VERSION` > dernier tag > `0.1.0`
-- EF Core: références dans csproj
-
-### 3. Générer plan
-
-Créer `.claude/gitflow/plans/init_{DATE}.md` puis exécuter avec `--exec`
-
-### 4. Demander style worktree
-
-Options:
-- `Organized (Recommandé)`: 01-Main/, 02-Develop/, features/, etc.
-- `Adjacent`: ../worktrees/ (legacy)
-- `Skip`: pas de worktrees
-
----
-
-## MODE C: Interactive (pas de repo)
-
-**Flow:** Location → Repository URL → Project Name → Confirmation → Create
-
-Même structure que MODE A mais avec questions préalables pour URL et emplacement.
-
----
-
-## Configuration Langue & Azure DevOps
-
-### Langue (v1.5)
-Question: "Langue pour descriptions?" | Options: `English (Recommended)`, `Français`
-
-> **Note:** Prefixes (`feature/`, `feat:`) restent TOUJOURS en anglais. Seul le contenu descriptif change.
-
-### Azure DevOps (optionnel)
-Si Azure CLI détecté, proposer configuration: organization, project, reviewers
-
----
-
-## Config.json Template
-
-```json
-{
-  "version": "1.5.0",
-  "initMode": "organized",
-  "language": { "code": "en" },
-  "naming": { "normalize": true, "maxLength": 50, "separator": "-" },
-  "repository": { "name": "", "defaultBranch": "main", "remoteUrl": "" },
-  "versioning": { "strategy": "semver", "current": "0.1.0", "tagPrefix": "v" },
-  "git": { "branches": { "main": "main", "develop": "develop" } },
-  "worktrees": {
-    "enabled": true, "mode": "organized",
-    "permanent": { "main": "../01-Main", "develop": "../02-Develop" },
-    "structure": { "features": "../features/", "releases": "../releases/", "hotfixes": "../hotfixes/" }
-  },
-  "database": { "enabled": true, "server": "localhost", "authType": "windows" },
-  "azureDevOps": { "enabled": false },
-  "efcore": { "enabled": false, "crossBranch": { "enabled": true, "blockOnConflict": true } }
-}
-```
-
-**Sections optionnelles (si activées):**
-
-| Section | Champs additionnels |
-|---------|---------------------|
-| `language` | `descriptions: { add, update, fix, refactor, remove, improve }` |
-| `database` | `username, password, namePrefix` (si authType=sql) |
-| `azureDevOps` | `organization, project, defaultReviewers, workItemTypes, linkWorkItems` |
-| `efcore` | `contexts[], generateScript, scriptOutputPath` |
-
----
-
-## Database Auto-Config (v1.3)
-
-Convention nommage DB par branche:
-
-| Type | Pattern | Exemple |
-|------|---------|---------|
-| develop | `{prefix}_Dev` | `SmartStack_Dev` |
-| feature/* | `{prefix}_feat_{name}` | `SmartStack_feat_user_auth` |
-| hotfix/* | `{prefix}_fix_{name}` | `SmartStack_fix_login` |
-| release/* | `{prefix}_rel_{version}` | `SmartStack_rel_1_3_0` |
-
----
-
-## Résumé Final
-
-```
-GITFLOW INITIALIZED
-- Repository: {name} | Remote: {url}
-- Structure: {organized|adjacent} | Worktrees: {enabled|disabled}
-- Working Dir: {path}/02-Develop
-
-→ Prochain: /gitflow:10-start feature {name}
-```
-
----
-
-## Modes CLI
-
-| Commande | Action |
-|----------|--------|
-| `/gitflow:1-init {url}` | Clone avec structure organisée |
-| `/gitflow:1-init` | Interactive ou existing repo |
-| `/gitflow:1-init --exec` | Exécuter plan existant |
-| `/gitflow:1-init --yes` | Sans confirmation |
-| `/gitflow:1-init --migrate` | Forcer migration config |
-| `/gitflow:1-init --organized` | Forcer structure organisée |
-| `/gitflow:1-init --adjacent` | Forcer structure legacy |