@atlashub/smartstack-cli 1.5.0 → 1.5.2

package/templates/commands/notification.md

@@ -1,129 +1,129 @@
-# /notification - Integration Notifications SmartStack
-
-> **Synergie Skill/Commande:**
-> - **Skill** (`templates/skills/notification/`) → Invocation automatique par Claude
-> - **Commande** (`/notification`) → Invocation manuelle par l'utilisateur
-
----
-
-## ARGUMENTS
-
-```
-/notification <action> [options]
-```
-
-| Action | Description |
-|--------|-------------|
-| `add` | Ajouter une notification dans un service existant |
-| `type` | Creer un nouveau type de notification |
-| `hook` | Creer le hook frontend avec SignalR |
-
----
-
-## WORKFLOW
-
-### /notification add
-
-Ajoute l'envoi de notification dans un service existant.
-
-**Questions:**
-1. Quel service modifier ? (liste des services)
-2. Quelle methode ? (Create, Update, Delete, etc.)
-3. Qui notifier ? (createur, assigne, role, liste)
-4. Quel type de notification ? (existant ou nouveau)
-
-**Actions:**
-1. Injecter `INotificationService` si pas present
-2. Ajouter l'appel `SendNotificationAsync` dans la methode
-3. Logger l'envoi de notification
-
-### /notification type
-
-Cree un nouveau type de notification.
-
-**Questions:**
-1. Nom du type ? (ex: `ProductCreated`)
-2. Categorie ? (Support, Admin, System, SLA)
-3. Description ?
-
-**Actions:**
-1. Ajouter dans `NotificationType.cs`
-2. Creer migration EF Core
-
-### /notification hook
-
-Cree le hook frontend pour recevoir les notifications en temps reel.
-
-**Questions:**
-1. Quel module ?
-2. Quel type d'entite ?
-
-**Actions:**
-1. Creer `use{Module}Notifications.ts`
-2. Integrer `useSignalR`
-3. Configurer les callbacks
-
----
-
-## TEMPLATES
-
-### Template SendNotification
-
-```csharp
-await _notificationService.SendNotificationAsync(
-    userId: $USER_ID,
-    type: NotificationType.$TYPE,
-    title: "$TITLE",
-    message: $"$MESSAGE",
-    relatedEntityType: "$ENTITY_TYPE",
-    relatedEntityId: $ENTITY_ID,
-    actionUrl: $"/$MODULE/$ENTITY_ID",
-    cancellationToken: ct);
-
-_logger.LogInformation(
-    "Notification sent to {UserId}: {Type}",
-    $USER_ID, NotificationType.$TYPE);
-```
-
-### Template Hook
-
-```typescript
-// hooks/use{Module}Notifications.ts
-import { useSignalR } from '@/hooks/useSignalR';
-import { useQueryClient } from '@tanstack/react-query';
-import { toast } from 'sonner';
-
-export function use{Module}Notifications() {
-  const queryClient = useQueryClient();
-
-  useSignalR({
-    onNotification: (notification) => {
-      if (notification.relatedEntityType === '{Entity}') {
-        queryClient.invalidateQueries(['{module}']);
-        toast.info(notification.title, {
-          description: notification.message,
-          action: notification.actionUrl ? {
-            label: 'Voir',
-            onClick: () => window.location.href = notification.actionUrl,
-          } : undefined,
-        });
-      }
-    },
-  });
-}
-```
-
----
-
-## FICHIERS CLES
-
-| Fichier | Role |
-|---------|------|
-| `Domain/Support/Enums/NotificationType.cs` | Types de notification |
-| `Application/Common/Interfaces/INotificationService.cs` | Interface |
-| `Infrastructure/Services/Support/NotificationService.cs` | Implementation |
-| `web/src/hooks/useSignalR.ts` | Hook SignalR |
-
----
-
-User: $ARGUMENTS
+# /notification - Integration Notifications SmartStack
+
+> **Synergie Skill/Commande:**
+> - **Skill** (`templates/skills/notification/`) → Invocation automatique par Claude
+> - **Commande** (`/notification`) → Invocation manuelle par l'utilisateur
+
+---
+
+## ARGUMENTS
+
+```
+/notification <action> [options]
+```
+
+| Action | Description |
+|--------|-------------|
+| `add` | Ajouter une notification dans un service existant |
+| `type` | Creer un nouveau type de notification |
+| `hook` | Creer le hook frontend avec SignalR |
+
+---
+
+## WORKFLOW
+
+### /notification add
+
+Ajoute l'envoi de notification dans un service existant.
+
+**Questions:**
+1. Quel service modifier ? (liste des services)
+2. Quelle methode ? (Create, Update, Delete, etc.)
+3. Qui notifier ? (createur, assigne, role, liste)
+4. Quel type de notification ? (existant ou nouveau)
+
+**Actions:**
+1. Injecter `INotificationService` si pas present
+2. Ajouter l'appel `SendNotificationAsync` dans la methode
+3. Logger l'envoi de notification
+
+### /notification type
+
+Cree un nouveau type de notification.
+
+**Questions:**
+1. Nom du type ? (ex: `ProductCreated`)
+2. Categorie ? (Support, Admin, System, SLA)
+3. Description ?
+
+**Actions:**
+1. Ajouter dans `NotificationType.cs`
+2. Creer migration EF Core
+
+### /notification hook
+
+Cree le hook frontend pour recevoir les notifications en temps reel.
+
+**Questions:**
+1. Quel module ?
+2. Quel type d'entite ?
+
+**Actions:**
+1. Creer `use{Module}Notifications.ts`
+2. Integrer `useSignalR`
+3. Configurer les callbacks
+
+---
+
+## TEMPLATES
+
+### Template SendNotification
+
+```csharp
+await _notificationService.SendNotificationAsync(
+    userId: $USER_ID,
+    type: NotificationType.$TYPE,
+    title: "$TITLE",
+    message: $"$MESSAGE",
+    relatedEntityType: "$ENTITY_TYPE",
+    relatedEntityId: $ENTITY_ID,
+    actionUrl: $"/$MODULE/$ENTITY_ID",
+    cancellationToken: ct);
+
+_logger.LogInformation(
+    "Notification sent to {UserId}: {Type}",
+    $USER_ID, NotificationType.$TYPE);
+```
+
+### Template Hook
+
+```typescript
+// hooks/use{Module}Notifications.ts
+import { useSignalR } from '@/hooks/useSignalR';
+import { useQueryClient } from '@tanstack/react-query';
+import { toast } from 'sonner';
+
+export function use{Module}Notifications() {
+  const queryClient = useQueryClient();
+
+  useSignalR({
+    onNotification: (notification) => {
+      if (notification.relatedEntityType === '{Entity}') {
+        queryClient.invalidateQueries(['{module}']);
+        toast.info(notification.title, {
+          description: notification.message,
+          action: notification.actionUrl ? {
+            label: 'Voir',
+            onClick: () => window.location.href = notification.actionUrl,
+          } : undefined,
+        });
+      }
+    },
+  });
+}
+```
+
+---
+
+## FICHIERS CLES
+
+| Fichier | Role |
+|---------|------|
+| `Domain/Support/Enums/NotificationType.cs` | Types de notification |
+| `Application/Common/Interfaces/INotificationService.cs` | Interface |
+| `Infrastructure/Services/Support/NotificationService.cs` | Implementation |
+| `web/src/hooks/useSignalR.ts` | Hook SignalR |
+
+---
+
+User: $ARGUMENTS

package/templates/commands/oneshot.md

@@ -1,57 +1,57 @@
----
-description: Ultra-fast feature implementation - Explore then Code then Test
-argument-hint: <feature-description>
----
-
-You are a rapid implementation specialist. Implement features at maximum speed using the OneShot methodology.
-
-**You need to always ULTRA THINK.**
-
-## Workflow
-
-1. **EXPLORE**: Quick context gathering (5-10 minutes max)
-   - Launch **1-2 parallel subagents maximum** to find relevant files
-   - Prefer `explore-codebase` agent for codebase search
-   - Use `explore-docs` agent ONLY if library-specific knowledge needed
-   - Find files to use as **examples** or **edit targets**
-   - **CRITICAL**: Be surgical - know exactly what to search for
-   - **NO PLANNING PHASE** - gather context and move directly to coding
-
-2. **CODE**: Implement immediately following existing patterns
-   - Start coding as soon as you have basic context
-   - Follow existing codebase style:
-     - Prefer clear variable/method names over comments
-     - Match existing patterns and conventions
-   - **CRITICAL RULES**:
-     - Stay **STRICTLY IN SCOPE** - change only what's needed
-     - NO comments unless absolutely necessary
-     - NO refactoring beyond the feature requirements
-   - Run autoformatting scripts when done
-   - Fix reasonable linter warnings as you go
-
-3. **TEST**: Validate with ESLint and TypeScript
-   - **First check package.json** for available scripts:
-     - Look for: `lint`, `typecheck`, `format`
-     - Run: `npm run lint && npm run typecheck` (or equivalent)
-   - **CRITICAL**: Code must pass linting and type checks
-   - If checks fail: fix errors immediately and re-run
-   - **STAY IN SCOPE**: Don't run full test suite unless explicitly requested
-   - For major changes only: run relevant tests with `npm test -- <pattern>`
-
-## Execution Rules
-
-- **SPEED IS PRIORITY**: Move fast, break nothing
-- **NO PLANNING**: Trust your exploration and code directly
-- **PARALLEL AGENTS**: Max 2 agents during explore phase
-- **MINIMAL TESTS**: Lint + typecheck only (unless user requests more)
-- **STAY FOCUSED**: Implement exactly what's requested, nothing more
-- Never exceed task boundaries
-- If stuck or uncertain: ask user immediately instead of over-exploring
-
-## Priority
-
-Speed > Completeness. Ship fast, iterate later.
-
----
-
-User: $ARGUMENTS
+---
+description: Ultra-fast feature implementation - Explore then Code then Test
+argument-hint: <feature-description>
+---
+
+You are a rapid implementation specialist. Implement features at maximum speed using the OneShot methodology.
+
+**You need to always ULTRA THINK.**
+
+## Workflow
+
+1. **EXPLORE**: Quick context gathering (5-10 minutes max)
+   - Launch **1-2 parallel subagents maximum** to find relevant files
+   - Prefer `explore-codebase` agent for codebase search
+   - Use `explore-docs` agent ONLY if library-specific knowledge needed
+   - Find files to use as **examples** or **edit targets**
+   - **CRITICAL**: Be surgical - know exactly what to search for
+   - **NO PLANNING PHASE** - gather context and move directly to coding
+
+2. **CODE**: Implement immediately following existing patterns
+   - Start coding as soon as you have basic context
+   - Follow existing codebase style:
+     - Prefer clear variable/method names over comments
+     - Match existing patterns and conventions
+   - **CRITICAL RULES**:
+     - Stay **STRICTLY IN SCOPE** - change only what's needed
+     - NO comments unless absolutely necessary
+     - NO refactoring beyond the feature requirements
+   - Run autoformatting scripts when done
+   - Fix reasonable linter warnings as you go
+
+3. **TEST**: Validate with ESLint and TypeScript
+   - **First check package.json** for available scripts:
+     - Look for: `lint`, `typecheck`, `format`
+     - Run: `npm run lint && npm run typecheck` (or equivalent)
+   - **CRITICAL**: Code must pass linting and type checks
+   - If checks fail: fix errors immediately and re-run
+   - **STAY IN SCOPE**: Don't run full test suite unless explicitly requested
+   - For major changes only: run relevant tests with `npm test -- <pattern>`
+
+## Execution Rules
+
+- **SPEED IS PRIORITY**: Move fast, break nothing
+- **NO PLANNING**: Trust your exploration and code directly
+- **PARALLEL AGENTS**: Max 2 agents during explore phase
+- **MINIMAL TESTS**: Lint + typecheck only (unless user requests more)
+- **STAY FOCUSED**: Implement exactly what's requested, nothing more
+- Never exceed task boundaries
+- If stuck or uncertain: ask user immediately instead of over-exploring
+
+## Priority
+
+Speed > Completeness. Ship fast, iterate later.
+
+---
+
+User: $ARGUMENTS

package/templates/commands/quick-search.md

@@ -1,72 +1,72 @@
----
-description: Lightning-fast search to answer specific questions - optimized for speed
-argument-hint: <question>
-allowed-tools: Grep, Glob, Read
-model: haiku
----
-
-You are a rapid search specialist. Answer questions at maximum speed using direct search tools.
-
-## Workflow
-
-1. **IDENTIFY**: Parse the question
-
-   - Extract key search terms
-   - Determine target file types or patterns
-   - **CRITICAL**: Be surgical - know exactly what to search
-
-2. **SEARCH**: Direct tool usage (NO agents)
-
-   - Use `Grep` for code content search with specific patterns
-   - Use `Glob` for file name/path patterns
-   - Launch searches **in parallel** when possible
-   - **SPEED RULE**: Max 2-3 search iterations total
-
-3. **READ**: Targeted file reading
-
-   - `Read` only the most relevant files found
-   - **CRITICAL**: Max 3-5 files - be selective
-   - Scan for the specific answer needed
-
-4. **ANSWER**: Direct response
-   - Immediate answer to the question
-   - Include file references with line numbers (`file.ts:42`)
-   - **NO**: Long explanations or architectural context
-   - **YES**: Concise answer with evidence
-
-## Execution Rules
-
-- **SPEED FIRST**: Answer in under 30 seconds
-- **NO AGENTS**: Use direct tools only (Grep, Glob, Read)
-- **PARALLEL SEARCH**: Run independent searches simultaneously
-- **MINIMAL READING**: Read only what's absolutely necessary
-- **NO DEEP ANALYSIS**: Surface-level answers with citations
-- **STOP EARLY**: Once you have the answer, respond immediately
-
-## Search Patterns
-
-**Finding implementations**:
-
-```
-Grep: pattern="class FooBar" or "function fooBar"
-```
-
-**Finding configs**:
-
-```
-Glob: pattern="**/config.{js,ts,json}"
-```
-
-**Finding imports/usage**:
-
-```
-Grep: pattern="from ['\"].*moduleName['\"]"
-```
-
-## Priority
-
-Speed > Completeness. Fast answers beat perfect answers.
-
----
-
-User: $ARGUMENTS
+---
+description: Lightning-fast search to answer specific questions - optimized for speed
+argument-hint: <question>
+allowed-tools: Grep, Glob, Read
+model: haiku
+---
+
+You are a rapid search specialist. Answer questions at maximum speed using direct search tools.
+
+## Workflow
+
+1. **IDENTIFY**: Parse the question
+
+   - Extract key search terms
+   - Determine target file types or patterns
+   - **CRITICAL**: Be surgical - know exactly what to search
+
+2. **SEARCH**: Direct tool usage (NO agents)
+
+   - Use `Grep` for code content search with specific patterns
+   - Use `Glob` for file name/path patterns
+   - Launch searches **in parallel** when possible
+   - **SPEED RULE**: Max 2-3 search iterations total
+
+3. **READ**: Targeted file reading
+
+   - `Read` only the most relevant files found
+   - **CRITICAL**: Max 3-5 files - be selective
+   - Scan for the specific answer needed
+
+4. **ANSWER**: Direct response
+   - Immediate answer to the question
+   - Include file references with line numbers (`file.ts:42`)
+   - **NO**: Long explanations or architectural context
+   - **YES**: Concise answer with evidence
+
+## Execution Rules
+
+- **SPEED FIRST**: Answer in under 30 seconds
+- **NO AGENTS**: Use direct tools only (Grep, Glob, Read)
+- **PARALLEL SEARCH**: Run independent searches simultaneously
+- **MINIMAL READING**: Read only what's absolutely necessary
+- **NO DEEP ANALYSIS**: Surface-level answers with citations
+- **STOP EARLY**: Once you have the answer, respond immediately
+
+## Search Patterns
+
+**Finding implementations**:
+
+```
+Grep: pattern="class FooBar" or "function fooBar"
+```
+
+**Finding configs**:
+
+```
+Glob: pattern="**/config.{js,ts,json}"
+```
+
+**Finding imports/usage**:
+
+```
+Grep: pattern="from ['\"].*moduleName['\"]"
+```
+
+## Priority
+
+Speed > Completeness. Fast answers beat perfect answers.
+
+---
+
+User: $ARGUMENTS

package/templates/commands/ralph-loop/cancel-ralph.md

@@ -1,18 +1,18 @@
----
-description: "Cancel active Ralph Loop"
-allowed-tools: ["Bash(test -f .claude/ralph-loop.local.md:*)", "Bash(rm .claude/ralph-loop.local.md)", "Read(.claude/ralph-loop.local.md)"]
-hide-from-slash-command-tool: "true"
----
-
-# Cancel Ralph
-
-To cancel the Ralph loop:
-
-1. Check if `.claude/ralph-loop.local.md` exists using Bash: `test -f .claude/ralph-loop.local.md && echo "EXISTS" || echo "NOT_FOUND"`
-
-2. **If NOT_FOUND**: Say "No active Ralph loop found."
-
-3. **If EXISTS**:
-   - Read `.claude/ralph-loop.local.md` to get the current iteration number from the `iteration:` field
-   - Remove the file using Bash: `rm .claude/ralph-loop.local.md`
-   - Report: "Cancelled Ralph loop (was at iteration N)" where N is the iteration value
+---
+description: "Cancel active Ralph Loop"
+allowed-tools: ["Bash(test -f .claude/ralph-loop.local.md:*)", "Bash(rm .claude/ralph-loop.local.md)", "Read(.claude/ralph-loop.local.md)"]
+hide-from-slash-command-tool: "true"
+---
+
+# Cancel Ralph
+
+To cancel the Ralph loop:
+
+1. Check if `.claude/ralph-loop.local.md` exists using Bash: `test -f .claude/ralph-loop.local.md && echo "EXISTS" || echo "NOT_FOUND"`
+
+2. **If NOT_FOUND**: Say "No active Ralph loop found."
+
+3. **If EXISTS**:
+   - Read `.claude/ralph-loop.local.md` to get the current iteration number from the `iteration:` field
+   - Remove the file using Bash: `rm .claude/ralph-loop.local.md`
+   - Report: "Cancelled Ralph loop (was at iteration N)" where N is the iteration value