@atlashub/smartstack-cli 1.13.2 → 1.14.1

package/templates/skills/workflow/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: workflow
 description: |
-  Cree et configure des workflows automatises SmartStack.
-  Utiliser ce skill quand:
-  - L'utilisateur veut automatiser des actions (emails, webhooks)
-  - L'utilisateur mentionne "workflow", "automatisation", "trigger"
-  - Creation d'un processus metier avec etapes
-  - Integration d'emails transactionnels
+  Creates and configures automated SmartStack workflows.
+  Use this skill when:
+  - User wants to automate actions (emails, webhooks)
+  - User mentions "workflow", "automation", "trigger"
+  - Creating a business process with steps
+  - Integrating transactional emails
   Types: SendEmail, Wait, Condition, Webhook
 ---
 
@@ -14,16 +14,16 @@ description: |
 
 > **Architecture:** Trigger → Steps → Actions (Email/Wait/Condition/Webhook)
 
-**Référence:** [_shared.md](../_shared.md) pour services communs
+**Reference:** [_shared.md](../_shared.md) for common services
 
-## QUAND CE SKILL S'ACTIVE
+## WHEN THIS SKILL ACTIVATES
 
-| Declencheur | Exemple |
-|-------------|---------|
-| Demande explicite | "Cree un workflow pour l'inscription" |
-| Email automatique | "Envoie un email quand un ticket est cree" |
-| Enchainement | "Apres 24h sans reponse, envoyer un rappel" |
-| Mots-cles | "workflow", "trigger", "automatisation", "email template" |
+| Trigger | Example |
+|---------|---------|
+| Explicit request | "Create a workflow for registration" |
+| Automatic email | "Send an email when a ticket is created" |
+| Chaining | "After 24h without response, send a reminder" |
+| Keywords | "workflow", "trigger", "automation", "email template" |
 
 ## FLOW
 
@@ -35,7 +35,7 @@ IWorkflowService.TriggerAsync(code, variables)
 Workflow Steps: SendEmail → Wait → Condition → Webhook
 ```
 
-## TRIGGERS DISPONIBLES
+## AVAILABLE TRIGGERS
 
 ### User Events
 | Trigger | Variables |
@@ -52,17 +52,17 @@ Workflow Steps: SendEmail → Wait → Condition → Webhook
 | `ticket.resolved/assigned` | ticketId, ticketNumber, assigneeName |
 | `ticket.sla-warning/breached` | ticketId, deadline, remainingMinutes |
 
-### Ajouter un Trigger
+### Add a Trigger
 ```csharp
 // WorkflowTriggerConfiguration.cs - GetSeedData()
 new { Id = Guid.Parse("..."), Code = "entity.event", Name = "Entity Event",
     AvailableVariablesJson = JsonSerializer.Serialize(new[]{ ... }), ... }
 
-// Declenchement
-await _workflowService.TriggerAsync("entity.event", new Dictionary<string, object>{...}, language: "fr");
+// Trigger
+await _workflowService.TriggerAsync("entity.event", new Dictionary<string, object>{...}, language: "en");
 ```
 
-## TYPES DE STEPS
+## STEP TYPES
 
 ### 1. SendEmail
 ```csharp
@@ -81,7 +81,7 @@ WorkflowStep.CreateConditionStep("Check premium", JsonSerializer.Serialize(new {
     condition = "{{userType}} == 'Premium'",
     trueStepOrder = 3, falseStepOrder = 4
 }), order: 2);
-// Operateurs: ==, !=, >, <, contains, &&, ||
+// Operators: ==, !=, >, <, contains, &&, ||
 ```
 
 ### 4. Webhook
@@ -97,10 +97,10 @@ WorkflowStep.CreateWebhookStep("Notify CRM", JsonSerializer.Serialize(new {
 ## WORKFLOW CREATION
 
 ```csharp
-// 1. Creer workflow
+// 1. Create workflow
 var workflow = Workflow.Create("welcome-sequence", "Welcome Sequence", description, triggerId, null, false, 10);
 
-// 2. Ajouter steps
+// 2. Add steps
 workflow.AddStep(WorkflowStep.CreateEmailStep("Welcome", templateId, 1));
 workflow.AddStep(WorkflowStep.CreateWaitStep("Wait 24h", 1440, 2));
 workflow.AddStep(WorkflowStep.CreateEmailStep("Follow-up", followUpTemplateId, 3));
@@ -109,16 +109,16 @@ workflow.AddStep(WorkflowStep.CreateEmailStep("Follow-up", followUpTemplateId, 3
 builder.HasData(new { Id = ..., Code = "welcome-sequence", TriggerId = ..., IsActive = true, ... });
 ```
 
-## DECLENCHEMENT
+## TRIGGERING
 
 ```csharp
-// Dans Service ou Controller
+// In Service or Controller
 await _workflowService.TriggerAsync("user.registered", new Dictionary<string, object>
 {
     ["userId"] = user.Id,
     ["email"] = user.Email,
     ["confirmUrl"] = GenerateConfirmUrl(user.Id)
-}, language: "fr", ct);
+}, language: "en", ct);
 ```
 
 ## EMAIL TEMPLATES
@@ -129,10 +129,10 @@ EmailTemplate: Code, Name, Category, IsActive, Translations[]
 EmailTemplateTranslation: LanguageCode, Subject, HtmlBody, TextBody
 ```
 
-### Syntaxe (Handlebars)
+### Syntax (Handlebars)
 ```html
-<h1>Bienvenue {{userName}}!</h1>
-{{#if isPremium}}<p>Merci Premium!</p>{{else}}<p>Offres Premium...</p>{{/if}}
+<h1>Welcome {{userName}}!</h1>
+{{#if isPremium}}<p>Thank you Premium member!</p>{{else}}<p>Premium offers...</p>{{/if}}
 {{#each items}}<li>{{this.name}}</li>{{/each}}
 ```
 
@@ -148,31 +148,31 @@ workflowsApi.execute(workflowId, variables)
 ## CHECKLIST
 
 ```
-□ Trigger identifie (existant ou nouveau dans WorkflowTriggerConfiguration.cs)
-□ Workflow cree: Code unique, Trigger lie, Priority (10=standard, 20+=prioritaire)
+□ Trigger identified (existing or new in WorkflowTriggerConfiguration.cs)
+□ Workflow created: Unique code, Linked trigger, Priority (10=standard, 20+=priority)
 □ Steps: SendEmail+templateId, Wait+delayMinutes, Condition+expression, Webhook+url
-□ Email templates crees (si SendEmail)
-□ Declenchement ajoute dans code source
+□ Email templates created (if SendEmail)
+□ Trigger added to source code
 □ Tests: trigger, emails, variables
 ```
 
-## REGLES ABSOLUES
+## ABSOLUTE RULES
 
 | DO | DON'T |
 |----|-------|
-| IWorkflowService.TriggerAsync | Execution directe |
-| Toutes variables du trigger | URLs hardcodees dans templates |
-| Specifier langue pour emails | Secrets dans variables |
-| Codes kebab-case uniques | Boucles infinies (A→B→A) |
-| Logger executions | Oublier email templates |
-
-## FICHIERS CLES
-
-| Fichier | Role |
-|---------|------|
-| `Domain/Communications/Workflow.cs` | Entite workflow |
-| `Domain/Communications/WorkflowStep.cs` | Entite step |
-| `Domain/Communications/WorkflowTrigger.cs` | Entite trigger |
+| IWorkflowService.TriggerAsync | Direct execution |
+| All trigger variables | Hardcoded URLs in templates |
+| Specify language for emails | Secrets in variables |
+| Unique kebab-case codes | Infinite loops (A→B→A) |
+| Log executions | Forget email templates |
+
+## KEY FILES
+
+| File | Role |
+|------|------|
+| `Domain/Communications/Workflow.cs` | Workflow entity |
+| `Domain/Communications/WorkflowStep.cs` | Step entity |
+| `Domain/Communications/WorkflowTrigger.cs` | Trigger entity |
 | `Application/Common/Interfaces/IWorkflowService.cs` | Interface |
 | `Infrastructure/Services/Workflow/WorkflowExecutionService.cs` | Implementation |
 | `Infrastructure/.../WorkflowConfiguration.cs` | EF Config + Seed |

package/templates/commands/ai-prompt.md

@@ -1,315 +0,0 @@
-# /ai-prompt - Gestion Prompts IA SmartStack
-
-> **Synergie Skill/Commande:**
-> - **Skill** (`templates/skills/ai-prompt/`) → Invocation automatique par Claude
-> - **Commande** (`/ai-prompt`) → Invocation manuelle par l'utilisateur
-
----
-
-## ARGUMENTS
-
-```
-/ai-prompt <action> [options]
-```
-
-| Action | Description |
-|--------|-------------|
-| `create` | Creer un nouveau prompt avec blocks |
-| `schema` | Creer un schema de validation |
-| `integrate` | Integrer l'IA dans un service existant |
-| `test` | Tester un prompt avec des variables |
-
----
-
-## WORKFLOW
-
-### /ai-prompt create
-
-Cree un nouveau prompt avec ses blocks.
-
-**Questions:**
-1. Code du prompt ? (kebab-case)
-2. Nom descriptif ?
-3. Description ?
-4. Type ? (Analyzer, Generator, Classifier, Assistant)
-5. Blocks a creer ? (System, User, Examples)
-6. Schema de validation ? (oui/non)
-
-**Actions:**
-1. Creer le prompt via API ou seed
-2. Ajouter les blocks
-3. Creer le schema si requis
-4. Lier le schema au prompt
-
-### /ai-prompt schema
-
-Cree un schema de validation JSON.
-
-**Questions:**
-1. Code du schema ?
-2. Nom ?
-3. Proprietes requises ?
-4. Type .NET associe ?
-
-**Actions:**
-1. Generer le JSON Schema
-2. Creer le DTO C# correspondant
-3. Ajouter dans la base de donnees
-
-### /ai-prompt integrate
-
-Integre l'execution IA dans un service existant.
-
-**Questions:**
-1. Quel service modifier ?
-2. Quelle methode ajouter ? (Analyze, Generate, Classify)
-3. Quel prompt utiliser ?
-4. Retour type ?
-
-**Actions:**
-1. Injecter `IAiCompletionService`
-2. Creer la methode d'execution
-3. Ajouter la validation du resultat
-4. Logger l'execution
-
-### /ai-prompt test
-
-Teste un prompt avec des variables.
-
-**Questions:**
-1. Quel prompt tester ?
-2. Variables a injecter ?
-
-**Actions:**
-1. Afficher le prompt rendu
-2. Executer contre le provider
-3. Afficher le resultat et les metriques
-
----
-
-## TEMPLATES
-
-### Template Prompt Block System
-
-```csharp
-new CreateBlockRequest
-{
-    BlockType = PromptBlockType.System,
-    Label = "Instructions",
-    Content = @"Tu es un expert en $DOMAIN.
-Analyse le contenu fourni et retourne:
-- $OUTPUT_1
-- $OUTPUT_2
-- $OUTPUT_3
-
-Reponds UNIQUEMENT en JSON valide correspondant au schema fourni.",
-    DisplayOrder = 1,
-    IsRequired = true
-}
-```
-
-### Template Prompt Block User
-
-```csharp
-new CreateBlockRequest
-{
-    BlockType = PromptBlockType.User,
-    Label = "Input",
-    Content = "Contenu: {{content}}\nContexte: {{context}}",
-    DisplayOrder = 2,
-    IsRequired = true
-}
-```
-
-### Template JSON Schema
-
-```json
-{
-    "$schema": "http://json-schema.org/draft-07/schema#",
-    "type": "object",
-    "required": ["$PROP_1", "$PROP_2"],
-    "properties": {
-        "$PROP_1": {
-            "type": "string",
-            "description": "$DESCRIPTION_1"
-        },
-        "$PROP_2": {
-            "type": "integer",
-            "minimum": 1,
-            "maximum": 10,
-            "description": "$DESCRIPTION_2"
-        },
-        "$PROP_3": {
-            "type": "array",
-            "items": { "type": "string" },
-            "maxItems": 5,
-            "description": "$DESCRIPTION_3"
-        }
-    }
-}
-```
-
-### Template DTO Result
-
-```csharp
-// Application/AI/{Entity}AnalysisResult.cs
-
-public class {Entity}AnalysisResult
-{
-    [JsonPropertyName("$PROP_1")]
-    public string $Prop1 { get; set; } = string.Empty;
-
-    [JsonPropertyName("$PROP_2")]
-    public int $Prop2 { get; set; }
-
-    [JsonPropertyName("$PROP_3")]
-    public List<string> $Prop3 { get; set; } = new();
-}
-```
-
-### Template Service Integration
-
-```csharp
-public async Task<{Entity}AnalysisResult?> Analyze{Entity}Async(
-    Guid entityId,
-    CancellationToken ct)
-{
-    var entity = await _context.{Entity}s.FindAsync(entityId);
-    if (entity == null) return null;
-
-    try
-    {
-        var result = await _aiCompletionService
-            .ExecutePromptByCodeWithValidationAsync<{Entity}AnalysisResult>(
-                "{entity}-analyzer",
-                new Dictionary<string, object>
-                {
-                    ["content"] = entity.Content,
-                    ["context"] = entity.Context ?? ""
-                },
-                cancellationToken: ct);
-
-        if (result.Success && result.IsValid)
-        {
-            _logger.LogInformation(
-                "{Entity} {EntityId} analyzed in {Ms}ms: {Result}",
-                entityId,
-                result.ExecutionTimeMs,
-                result.Data.$Prop1);
-
-            return result.Data;
-        }
-
-        if (!result.Success)
-        {
-            _logger.LogError(
-                "AI analysis failed for {Entity} {EntityId}: {Error}",
-                entityId, result.Error);
-        }
-        else if (!result.IsValid)
-        {
-            _logger.LogWarning(
-                "AI response invalid for {Entity} {EntityId}: {Errors}",
-                entityId, string.Join(", ", result.ValidationErrors));
-        }
-
-        return null;
-    }
-    catch (Exception ex)
-    {
-        _logger.LogError(ex, "Exception analyzing {Entity} {EntityId}", entityId);
-        return null;
-    }
-}
-```
-
-### Template Controller Endpoint
-
-```csharp
-[HttpPost("{id}/analyze")]
-[RequirePermission(Permissions.$Module.$Entity.Update)]
-[ProducesResponseType(typeof({Entity}AnalysisResult), StatusCodes.Status200OK)]
-[ProducesResponseType(StatusCodes.Status400BadRequest)]
-[ProducesResponseType(StatusCodes.Status404NotFound)]
-public async Task<ActionResult<{Entity}AnalysisResult>> Analyze{Entity}(
-    Guid id,
-    CancellationToken ct)
-{
-    var result = await _service.Analyze{Entity}Async(id, ct);
-
-    if (result == null)
-        return BadRequest(new { message = "Analysis failed" });
-
-    return Ok(result);
-}
-```
-
-### Template Frontend Button
-
-```tsx
-import { Sparkles, Loader2 } from 'lucide-react';
-
-interface AiAnalyzeButtonProps {
-  entityId: string;
-  onResult: (result: AnalysisResult) => void;
-}
-
-export function AiAnalyzeButton({ entityId, onResult }: AiAnalyzeButtonProps) {
-  const [loading, setLoading] = useState(false);
-
-  const handleAnalyze = async () => {
-    setLoading(true);
-    try {
-      const result = await {module}Api.analyze(entityId);
-      onResult(result);
-      toast.success('Analyse terminee');
-    } catch (error) {
-      toast.error('Erreur lors de l\'analyse');
-    } finally {
-      setLoading(false);
-    }
-  };
-
-  return (
-    <button
-      onClick={handleAnalyze}
-      disabled={loading}
-      className="inline-flex items-center gap-2 px-4 py-2 bg-purple-600 text-white rounded-lg hover:bg-purple-700 disabled:opacity-50"
-    >
-      {loading ? (
-        <Loader2 className="w-4 h-4 animate-spin" />
-      ) : (
-        <Sparkles className="w-4 h-4" />
-      )}
-      Analyser avec IA
-    </button>
-  );
-}
-```
-
----
-
-## FICHIERS CLES
-
-| Fichier | Role |
-|---------|------|
-| `Domain/AI/Prompts/Prompt.cs` | Entite prompt |
-| `Domain/AI/Schemas/OutputSchema.cs` | Schema validation |
-| `Application/Common/Interfaces/IAiCompletionService.cs` | Interface |
-| `Infrastructure/Services/AI/AiCompletionService.cs` | Implementation |
-| `Infrastructure/Services/AI/PromptService.cs` | Gestion prompts |
-
----
-
-## REGLES
-
-1. **TOUJOURS** creer un schema de validation pour les reponses structurees
-2. **TOUJOURS** creer le DTO C# correspondant au schema
-3. **TOUJOURS** logger les executions avec tokens et duree
-4. **TOUJOURS** gerer les erreurs (API down, validation)
-5. **JAMAIS** exposer les prompts systeme au frontend
-6. **JAMAIS** hardcoder les cles API
-
----
-
-User: $ARGUMENTS

package/templates/commands/apex/1-analyze.md

@@ -1,100 +0,0 @@
----
-description: Analyze phase - gather all context and create analysis report
-argument-hint: <task-description>
----
-
-You are an analysis specialist. Your mission is to gather ALL relevant context before implementation.
-
-**You need to ULTRA THINK before launching agents.**
-
-## Workflow
-
-1. **SETUP TASK FOLDER**: Create organized workspace in .claude/tasks
-   - Find next task number: Check `.claude/tasks/` for existing folders
-   - Parse task description to create kebab-case name
-   - Create `.claude/tasks/nn-task-name/` folder structure
-   - **EXAMPLE**: "Add user authentication" → `.claude/tasks/01-add-user-authentication/`
-   - **CRITICAL**: Always use `.claude/tasks/` directory for task storage
-
-2. **ULTRA THINK**: Plan analysis strategy
-   - **CRITICAL**: Know EXACTLY what to search for before launching agents
-   - Identify key concepts, files, patterns to find
-   - Determine which sources need analysis (codebase/docs/web)
-   - List specific questions each agent should answer
-
-3. **LAUNCH PARALLEL ANALYSIS**: Gather context from all sources
-   - **Codebase exploration** (`explore-codebase` agent):
-     - Find similar implementations to use as examples
-     - Locate files that need modification
-     - Identify existing patterns and conventions
-     - Search for related utilities and helpers
-
-   - **Documentation exploration** (`explore-docs` agent):
-     - Search library docs for APIs and patterns
-     - Find best practices for tools being used
-     - Gather code examples from official docs
-
-   - **Web research** (`websearch` agent):
-     - Research latest approaches and solutions
-     - Find community examples and patterns
-     - Gather architectural guidance
-
-   - **CRITICAL**: Launch ALL agents in parallel in a single message
-
-4. **SYNTHESIZE FINDINGS**: Create comprehensive analysis report
-   - Combine findings from all agents
-   - Organize by topic/concern
-   - Include file paths with line numbers (e.g., `src/auth.ts:42`)
-   - List relevant examples found in codebase
-   - Document key patterns and conventions to follow
-   - Note any dependencies or prerequisites
-
-5. **SAVE ANALYSIS**: Write to `analyze.md`
-   - Save to `.claude/tasks/nn-task-name/analyze.md`
-   - **Structure**:
-     ```markdown
-     # Task: [Description]
-
-     ## Codebase Context
-     [Findings from codebase exploration]
-
-     ## Documentation Insights
-     [Key information from docs]
-
-     ## Research Findings
-     [Web research results]
-
-     ## Key Files
-     - `path/to/file.ts:line` - Purpose
-
-     ## Patterns to Follow
-     [Existing conventions]
-
-     ## Dependencies
-     [Prerequisites and related systems]
-     ```
-
-6. **REPORT**: Summarize to user
-   - Confirm task folder created
-   - Highlight key findings
-   - Note any concerns or blockers discovered
-   - Suggest next step: Run the following command to create implementation plan:
-     ```
-     /apex:plan <task-folder>
-     ```
-
-## Execution Rules
-
-- **PARALLEL EXECUTION**: All agents must run simultaneously for speed
-- **ULTRA THINK FIRST**: Never launch agents without clear search strategy
-- **COMPREHENSIVE**: Gather more context than seems necessary
-- **ORGANIZED**: Structure findings for easy planning phase
-- **FILE REFERENCES**: Always include file paths with line numbers
-
-## Priority
-
-Context depth > Speed. Missing context causes failed implementations.
-
----
-
-User: $ARGUMENTS