@atlashub/smartstack-cli 1.13.2 → 1.14.1

package/templates/commands/mcp-integration.md

@@ -1,330 +0,0 @@
----
-description: SmartStack MCP Integration Guide
----
-
-# SmartStack MCP Integration
-
-This document describes how SmartStack CLI commands integrate with the **SmartStack MCP Server** for consistent, structured operations across all development environments.
-
----
-
-## Overview
-
-The SmartStack MCP Server provides four main tools:
-
-| MCP Tool | CLI Commands Using It | Purpose |
-|----------|----------------------|---------|
-| `validate_conventions` | `/validate` | Check naming conventions |
-| `check_migrations` | `/efcore:conflicts`, `/efcore:scan`, `/efcore:db-status` | Migration analysis |
-| `scaffold_extension` | `/controller:create`, `/application:create` | Code generation |
-| `api_docs` | (future) `/docs:api` | API documentation |
-
----
-
-## MCP Tools Reference
-
-### 1. validate_conventions
-
-**Description:** Validate SmartStack conventions for SQL schemas, table prefixes, migration naming, service interfaces, and namespace structure.
-
-**Parameters:**
-
-```typescript
-{
-  path?: string;           // Project path (default: auto-detect)
-  checks: Array<'tables' | 'migrations' | 'services' | 'namespaces' | 'all'>;
-}
-```
-
-**Response:**
-
-```typescript
-interface ValidationResult {
-  valid: boolean;
-  errors: ValidationIssue[];
-  warnings: ValidationIssue[];
-  summary: string;
-}
-```
-
-**Used by:** `/validate`, `/validate:tables`, `/validate:migrations`, etc.
-
----
-
-### 2. check_migrations
-
-**Description:** Analyze EF Core migrations for conflicts, ordering issues, and ModelSnapshot discrepancies between branches.
-
-**Parameters:**
-
-```typescript
-{
-  projectPath?: string;    // EF Core project path
-  branch?: string;         // Git branch to check (default: current)
-  compareBranch?: string;  // Branch to compare against
-}
-```
-
-**Response:**
-
-```typescript
-interface MigrationCheckResult {
-  hasConflicts: boolean;
-  migrations: MigrationInfo[];
-  conflicts: MigrationConflict[];
-  suggestions: string[];
-}
-
-interface MigrationInfo {
-  name: string;
-  context: string;      // core, extensions
-  version: string;      // 1.0.0, 1.2.0
-  sequence: string;     // 001, 002
-  description: string;
-  file: string;
-  applied: boolean;
-}
-
-interface MigrationConflict {
-  type: 'order' | 'snapshot' | 'dependency' | 'naming';
-  description: string;
-  files: string[];
-  resolution: string;
-}
-```
-
-**Used by:** `/efcore:conflicts`, `/efcore:scan`, `/efcore:db-status`
-
----
-
-### 3. scaffold_extension
-
-**Description:** Generate code to extend SmartStack: services, entities, controllers, or React components.
-
-**Parameters:**
-
-```typescript
-{
-  type: 'service' | 'entity' | 'controller' | 'component';
-  name: string;          // e.g., "UserProfile", "Order"
-  options?: {
-    namespace?: string;
-    baseEntity?: string;
-    methods?: string[];
-    outputPath?: string;
-  }
-}
-```
-
-**Response:**
-
-```typescript
-interface ScaffoldResult {
-  success: boolean;
-  files: GeneratedFile[];
-  instructions: string[];
-}
-
-interface GeneratedFile {
-  path: string;
-  content: string;
-  type: 'created' | 'modified';
-}
-```
-
-**Used by:** `/controller:create`, `/application:create`
-
----
-
-### 4. api_docs
-
-**Description:** Get API documentation from Swagger/OpenAPI or by parsing controller files.
-
-**Parameters:**
-
-```typescript
-{
-  endpoint?: string;     // Filter by path, e.g., "/api/users"
-  format?: 'markdown' | 'json' | 'openapi';
-  controller?: string;   // Filter by controller name
-}
-```
-
-**Used by:** Future `/docs:api` command
-
----
-
-## Convention Alignment
-
-### Migration Naming
-
-Both CLI and MCP use the same format:
-
-```
-{context}_v{version}_{sequence}_{Description}
-```
-
-| Component | Values | Example |
-|-----------|--------|---------|
-| context | `core`, `extensions` | `core` |
-| version | Semver | `1.2.0` |
-| sequence | 3-digit | `001` |
-| Description | PascalCase | `AddUserRoles` |
-
-**Full example:** `core_v1.2.0_001_AddUserRoles`
-
-### Table Prefixes
-
-Valid prefixes enforced by `validate_conventions`:
-
-- `auth_` - Authentication
-- `nav_` - Navigation
-- `usr_` - User data
-- `ai_` - AI features
-- `cfg_` - Configuration
-- `wkf_` - Workflow
-- `support_` - Support
-- `entra_` - Entra ID
-- `ref_` - Reference data
-- `loc_` - Localization
-- `lic_` - Licensing
-
-### Service Pattern
-
-```
-Interface:      I{Name}Service
-Implementation: {Name}Service
-```
-
-### Namespaces
-
-```
-SmartStack.Domain.*
-SmartStack.Application.*
-SmartStack.Infrastructure.*
-SmartStack.Api.*
-```
-
----
-
-## Command to MCP Mapping
-
-### /efcore:conflicts
-
-```
-1. Get current branch
-2. CALL mcp__smartstack__check_migrations({
-     branch: currentBranch,
-     compareBranch: "develop"
-   })
-3. Display conflicts from response
-4. Exit 1 if hasConflicts is true
-```
-
-### /efcore:scan
-
-```
-1. List all worktrees
-2. FOR each branch:
-   CALL mcp__smartstack__check_migrations({
-     branch: branchName,
-     compareBranch: "develop"
-   })
-3. Aggregate results
-4. Calculate merge order by risk level
-5. Display summary
-```
-
-### /validate
-
-```
-1. CALL mcp__smartstack__validate_conventions({
-     checks: ["all"]
-   })
-2. Display errors and warnings
-3. Exit 1 if not valid
-```
-
-### /controller:create
-
-```
-1. Parse arguments (area, module, entity)
-2. CALL mcp__smartstack__scaffold_extension({
-     type: "controller",
-     name: moduleName,
-     options: { namespace: "SmartStack.Api.Controllers.{area}" }
-   })
-3. Write generated files
-4. Add permissions
-5. Create migration if needed
-```
-
----
-
-## Benefits of MCP Integration
-
-1. **Single Source of Truth**
-   - Convention rules defined once in MCP config
-   - No duplication between CLI and other tools
-
-2. **Consistency**
-   - Same logic in CLI, CI/CD, IDE
-   - Identical results everywhere
-
-3. **Structured Output**
-   - Typed responses instead of text parsing
-   - Easier automation and scripting
-
-4. **Maintainability**
-   - Update logic in one place (MCP)
-   - All commands automatically benefit
-
-5. **Extensibility**
-   - Add new checks/features in MCP
-   - Available to all consumers immediately
-
----
-
-## CI/CD Integration
-
-```yaml
-# GitHub Actions example
-jobs:
-  validate:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Validate conventions
-        run: |
-          OUTPUT=$(claude-code "/validate --json")
-          if [ "$(echo $OUTPUT | jq '.valid')" != "true" ]; then
-            echo "::error::Convention violations detected"
-            exit 1
-          fi
-
-      - name: Check migration conflicts
-        run: |
-          OUTPUT=$(claude-code "/efcore:conflicts --json")
-          if [ "$(echo $OUTPUT | jq '.hasConflicts')" = "true" ]; then
-            echo "::error::Migration conflicts detected"
-            exit 1
-          fi
-```
-
----
-
-## Fallback Behavior
-
-When MCP is unavailable, commands fall back to:
-
-1. **Local bash scripts** for simple operations
-2. **Manual template generation** for scaffolding
-3. **Warning message** indicating degraded mode
-
-To check MCP availability:
-
-```bash
-# MCP health check
-claude-code --mcp-status smartstack
-```

package/templates/commands/notification.md

@@ -1,129 +0,0 @@
-# /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 +0,0 @@
----
-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/quickstart.md

@@ -1,154 +0,0 @@
----
-description: "Quick start guide for SmartStack CLI"
----
-
-# SmartStack Quick Start Guide
-
-## Installation (3 steps)
-
-### Step 1: Install SmartStack CLI
-```bash
-npm install -g @atlashub/smartstack-cli
-```
-
-### Step 2: Activate License
-```bash
-smartstack license activate <your-license-key>
-```
-
-### Step 3: Install Templates
-```bash
-smartstack install
-```
-
-## Verify Setup
-
-Run the doctor command to verify everything is configured:
-```bash
-smartstack doctor
-```
-
-Expected output:
-```
-✓ License valid
-✓ Node.js v20.x.x
-✓ Claude Code CLI installed
-✓ MCP: context7 available
-✓ MCP: smartstack available
-✓ SmartStack Commands installed
-```
-
-## MCP Servers
-
-SmartStack requires two MCP servers for full functionality:
-
-### Check MCP Status
-```bash
-smartstack check-mcp
-```
-
-### Install Missing MCPs
-```bash
-smartstack check-mcp --install
-```
-
-Or manually:
-```bash
-claude mcp add context7
-claude mcp add smartstack
-```
-
-## Create Your First Project
-
-```bash
-# Create a new SmartStack project
-smartstack init MyProject
-
-# Navigate to the project
-cd MyProject
-
-# Start backend
-dotnet run --project src/MyProject.Api
-
-# Start frontend (in another terminal)
-cd web/myproject-web
-npm install
-npm run dev
-```
-
-## Ralph Automation
-
-Ralph Weegund is an AI-powered iterative development loop.
-
-### Setup Ralph
-```bash
-# Verify Ralph prerequisites
-smartstack ralph start
-
-# Initialize Ralph in your project (if not done by init)
-smartstack ralph init
-```
-
-### Use Ralph in Claude Code
-```
-/ralph-loop "Implement user authentication with JWT"
-```
-
-### Monitor Ralph
-```bash
-# Check status
-smartstack ralph status
-
-# View logs
-smartstack ralph logs
-
-# View reports
-smartstack ralph report --list
-```
-
-## Common Commands
-
-| Command | Description |
-|---------|-------------|
-| `smartstack doctor` | Full system diagnostic |
-| `smartstack check-mcp` | Verify MCP servers |
-| `smartstack status` | Show installation status |
-| `smartstack ralph start` | Prepare Ralph for use |
-| `/gitflow` | GitFlow workflow |
-| `/apex` | APEX methodology |
-| `/ralph-loop` | Start automation loop |
-
-## Troubleshooting
-
-### "License required" error
-```bash
-smartstack license activate <key>
-```
-
-### "MCP server not found"
-```bash
-smartstack check-mcp --install
-```
-
-### "Ralph not configured"
-```bash
-smartstack ralph init
-```
-
-### Full diagnostic
-```bash
-smartstack doctor --verbose
-```
-
-## Next Steps
-
-1. **Explore Commands**: `smartstack docs commands`
-2. **Learn GitFlow**: `smartstack docs gitflow`
-3. **Try APEX**: `/apex "Build a feature"`
-4. **Use Ralph**: `/ralph-loop "Your task"`
-
-## Resources
-
-- Documentation: https://docs.smartstack.app
-- Support: https://github.com/atlashub/smartstack-cli/issues
-- Website: https://smartstack.app

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

@@ -1,18 +0,0 @@
----
-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