mustard-claude 2.0.0

package/dist/generators/commands.js

@@ -0,0 +1,845 @@
+import { getRunCommand, getInstallCommand } from '../services/package-manager.js';
+/**
+ * Mustard commands subfolder
+ * Commands generated by Mustard go in commands/mustard/
+ * User-created commands go directly in commands/
+ */
+export const MUSTARD_COMMANDS_FOLDER = 'mustard';
+/**
+ * Command prefix for Mustard commands
+ */
+export const MUSTARD_COMMAND_PREFIX = 'mtd';
+/**
+ * Generate command files
+ * All generated commands go in the mustard/ subfolder
+ * Pattern: mtd-{category}-{action}
+ */
+export function generateCommands(projectInfo) {
+    const commands = {
+        // Pipeline commands
+        'mtd-pipeline-feature': generatePipelineFeatureCommand(projectInfo),
+        'mtd-pipeline-bugfix': generatePipelineBugfixCommand(projectInfo),
+        'mtd-pipeline-approve': generatePipelineApproveCommand(),
+        'mtd-pipeline-complete': generatePipelineCompleteCommand(),
+        'mtd-pipeline-resume': generatePipelineResumeCommand(),
+        // Git commands
+        'mtd-git-commit': generateGitCommitCommand(),
+        'mtd-git-push': generateGitPushCommand(),
+        'mtd-git-merge': generateGitMergeCommand(),
+        // Validate commands
+        'mtd-validate-build': generateValidateBuildCommand(projectInfo),
+        'mtd-validate-status': generateValidateStatusCommand(projectInfo),
+        // Sync commands
+        'mtd-sync-registry': generateSyncRegistryCommand(),
+        'mtd-sync-dependencies': generateSyncDependenciesCommand(projectInfo),
+        'mtd-sync-context': generateSyncContextCommand(),
+        // Report commands
+        'mtd-report-daily': generateReportDailyCommand(),
+        'mtd-report-weekly': generateReportWeeklyCommand(),
+        // Scan commands
+        'mtd-scan-project': generateScanProjectCommand(),
+        // Task commands (L0 Universal Delegation)
+        'mtd-task-analyze': generateTaskAnalyzeCommand(),
+        'mtd-task-review': generateTaskReviewCommand(),
+        'mtd-task-refactor': generateTaskRefactorCommand(),
+        'mtd-task-docs': generateTaskDocsCommand()
+    };
+    return commands;
+}
+// ============== Pipeline Commands ==============
+function generatePipelineFeatureCommand(projectInfo) {
+    return `# /mtd-pipeline-feature - Feature Pipeline
+
+## Trigger
+
+\`/mtd-pipeline-feature <feature-name>\`
+
+## Description
+
+Starts the full pipeline to implement a new feature.
+
+## Flow
+
+1. **EXPLORE**
+   - Use Task(Explore) to analyze requirements
+   - Map related existing files
+   - Identify patterns to follow
+
+2. **SPEC**
+   - Create spec at \`spec/active/{name}/spec.md\`
+   - List files to create/modify
+   - Define implementation checklist
+
+3. **APPROVE**
+   - Present spec to user
+   - Wait for /mtd-pipeline-approve or feedback
+
+4. **IMPLEMENT**
+   - Delegate to specialized agents
+   - Backend → Frontend → Database (order as needed)
+
+5. **REVIEW**
+   - Validate implementation
+   - Verify checklist
+
+6. **COMPLETE**
+   - Update entity-registry if needed
+   - Move spec to completed/
+
+## Example
+
+\`\`\`
+User: /mtd-pipeline-feature add-partner-email-field
+
+Claude:
+1. Explores codebase to understand Partner
+2. Creates spec with implementation plan
+3. Presents spec for approval
+4. (after /mtd-pipeline-approve) Implements Database → Backend → Frontend
+5. Validates and completes
+\`\`\`
+`;
+}
+function generatePipelineBugfixCommand(projectInfo) {
+    return `# /mtd-pipeline-bugfix - Bug Fix Pipeline
+
+## Trigger
+
+\`/mtd-pipeline-bugfix <error-description>\`
+
+## Description
+
+Starts the pipeline to diagnose and fix a bug.
+
+## Flow
+
+1. **DIAGNOSE**
+   - Use grepai to search related code
+   - Identify root cause
+   - Document findings
+
+2. **SPEC**
+   - Create spec at \`spec/active/{name}/spec.md\`
+   - Describe root cause
+   - Propose fix
+
+3. **APPROVE**
+   - Present diagnosis to user
+   - Wait for /mtd-pipeline-approve
+
+4. **FIX**
+   - Apply minimal fix
+   - Do not make unrelated changes
+
+5. **VALIDATE**
+   - Verify bug is fixed
+   - Verify nothing broke
+
+6. **COMPLETE**
+   - Document solution
+   - Move spec to completed/
+
+## Example
+
+\`\`\`
+User: /mtd-pipeline-bugfix error saving contract
+
+Claude:
+1. Uses grepai to find save code
+2. Identifies root cause
+3. Presents diagnosis
+4. (after /mtd-pipeline-approve) Fixes
+5. Validates and completes
+\`\`\`
+`;
+}
+function generatePipelineApproveCommand() {
+    return `# /mtd-pipeline-approve - Approve Spec
+
+## Trigger
+
+\`/mtd-pipeline-approve\`
+
+## Description
+
+Approves the current spec and enables the implementation phase.
+
+## Prerequisites
+
+- Active pipeline (created via /mtd-pipeline-feature or /mtd-pipeline-bugfix)
+- Spec presented awaiting approval
+
+## Action
+
+1. Marks pipeline as "approved"
+2. Enables implementation start
+3. Claude proceeds automatically
+
+## Alternative Flow
+
+If the spec is not satisfactory, the user can:
+- Give text feedback for adjustments
+- Use /mtd-pipeline-complete to cancel
+
+\`\`\`
+User: /mtd-pipeline-approve
+
+Claude: ✅ Spec approved! Starting implementation...
+\`\`\`
+`;
+}
+function generatePipelineCompleteCommand() {
+    return `# /mtd-pipeline-complete - Finalize Pipeline
+
+## Trigger
+
+\`/mtd-pipeline-complete\`
+
+## Description
+
+Finalizes the current pipeline, either completing or canceling.
+
+## Action
+
+1. Moves spec from \`spec/active/\` to \`spec/completed/\`
+2. Updates entity-registry if needed
+3. Clears pipeline state
+
+## When to Use
+
+- After successful implementation and review
+- To cancel an ongoing pipeline
+- To force close if something went wrong
+
+\`\`\`
+User: /mtd-pipeline-complete
+
+Claude: ✅ Pipeline finalized!
+        Spec moved to spec/completed/{name}/
+        Entity registry updated.
+\`\`\`
+`;
+}
+function generatePipelineResumeCommand() {
+    return `# /mtd-pipeline-resume - Resume Pipeline
+
+## Trigger
+
+\`/mtd-pipeline-resume\`
+
+## Description
+
+Resumes a pipeline that was interrupted.
+
+## Action
+
+1. Finds active pipeline
+2. Identifies last completed phase
+3. Continues from where it stopped
+
+## When to Use
+
+- After restarting Claude session
+- After accidental interruption
+- To continue work from another session
+
+\`\`\`
+User: /mtd-pipeline-resume
+
+Claude: 🔄 Resuming pipeline "add-email-partner"
+        Last phase: IMPLEMENT
+        Continuing with Backend...
+\`\`\`
+`;
+}
+// ============== Git Commands ==============
+function generateGitCommitCommand() {
+    return `# /mtd-git-commit - Simple Commit
+
+## Trigger
+
+\`/mtd-git-commit\`
+
+## Description
+
+Creates a commit with current changes.
+
+## Action
+
+1. Runs \`git status\` to see changes
+2. Runs \`git diff\` to analyze content
+3. Generates commit message based on changes
+4. Runs \`git add\` + \`git commit\`
+
+## Message Format
+
+\`\`\`
+<type>: <short description>
+
+<detailed description if needed>
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+\`\`\`
+
+Types: feat, fix, refactor, docs, chore, test
+`;
+}
+function generateGitPushCommand() {
+    return `# /mtd-git-push - Commit and Push
+
+## Trigger
+
+\`/mtd-git-push\`
+
+## Description
+
+Creates commit and pushes to remote.
+
+## Action
+
+1. Same process as /mtd-git-commit
+2. Adds \`git push\` at the end
+
+## Cautions
+
+- Checks if branch has remote configured
+- Uses \`git push -u origin <branch>\` if needed
+`;
+}
+function generateGitMergeCommand() {
+    return `# /mtd-git-merge - Merge to Main
+
+## Trigger
+
+\`/mtd-git-merge\`
+
+## Description
+
+Merges current branch to main/master.
+
+## Action
+
+1. Checks for uncommitted changes
+2. Switches to main branch
+3. Pulls latest changes
+4. Merges feature branch
+5. Pushes to remote
+
+## Cautions
+
+- Will abort if there are merge conflicts
+- Requires clean working directory
+`;
+}
+// ============== Validate Commands ==============
+function generateValidateBuildCommand(projectInfo) {
+    const hasNode = projectInfo.stacks.some(s => ['react', 'nextjs', 'node'].includes(s.name));
+    const hasDotnet = projectInfo.stacks.some(s => s.name === 'dotnet');
+    const pm = projectInfo.packageManager ?? 'npm';
+    const steps = [];
+    if (hasDotnet) {
+        steps.push('- `dotnet build` - Verifies .NET compiles');
+    }
+    if (hasNode) {
+        steps.push(`- \`${getRunCommand(pm, 'typecheck')}\` - Verifies TypeScript types`);
+        steps.push(`- \`${getRunCommand(pm, 'lint')}\` - Verifies linting (if available)`);
+    }
+    return `# /mtd-validate-build - Build Validation
+
+## Trigger
+
+\`/mtd-validate-build\`
+
+## Description
+
+Runs build and type-check validations.
+
+## Actions
+
+${steps.join('\n') || '- Verify project compilation'}
+
+## Result
+
+- ✅ **Success** - Project compiles and passes type-check
+- ❌ **Failure** - Lists errors found
+`;
+}
+function generateValidateStatusCommand(projectInfo) {
+    return `# /mtd-validate-status - Consolidated Status
+
+## Trigger
+
+\`/mtd-validate-status\`
+
+## Description
+
+Shows consolidated project status.
+
+## Information
+
+1. **Git Status**
+   - Current branch
+   - Modified files
+   - Commits pending push
+
+2. **Pipeline**
+   - Active pipeline (if any)
+   - Current phase
+
+3. **Build**
+   - Last validation result
+
+4. **Entity Registry**
+   - Number of entities
+   - Last update
+`;
+}
+// ============== Sync Commands ==============
+function generateSyncRegistryCommand() {
+    return `# /mtd-sync-registry - Update Entity Registry
+
+## Trigger
+
+\`/mtd-sync-registry\`
+
+## Description
+
+Scans the project and updates entity-registry.json.
+
+## Action
+
+1. Searches database schemas (Drizzle, Prisma, etc)
+2. Searches backend entities (.NET, Node, etc)
+3. Updates \`.claude/entity-registry.json\`
+
+## When to Use
+
+- After creating new entity
+- After importing existing code
+- To sync after manual changes
+`;
+}
+function generateSyncDependenciesCommand(projectInfo) {
+    const pm = projectInfo.packageManager ?? 'npm';
+    const hasDotnet = projectInfo.stacks.some(s => s.name === 'dotnet');
+    return `# /mtd-sync-dependencies - Install Dependencies
+
+## Trigger
+
+\`/mtd-sync-dependencies\`
+
+## Description
+
+Installs dependencies for all projects.
+
+## Actions
+
+${hasDotnet ? '- `dotnet restore` - Restores NuGet packages\n' : ''}- \`${getInstallCommand(pm)}\` - Installs Node dependencies
+
+## Subprojects
+
+If monorepo, runs in all configured subprojects.
+`;
+}
+function generateSyncContextCommand() {
+    return `# /mtd-sync-context - Load Project Context
+
+## Trigger
+
+\`/mtd-sync-context\`
+\`/mtd-sync-context --refresh\`
+
+## Description
+
+Discovers and caches project context for faster implementations.
+
+## What It Does
+
+1. Reads \`.claude/context/*.md\` for user-provided context
+2. Reads \`.claude/CLAUDE.md\` for project rules and conventions
+3. Reads \`.claude/entity-registry.json\` for entity mappings
+4. Uses grepai to discover code patterns (services, repos, components)
+5. Stores all in memory MCP as entities
+
+## When It Runs
+
+- **Automatically** at the start of /mtd-pipeline-feature or /mtd-pipeline-bugfix (if context is missing or stale)
+- **Manually** when you run /mtd-sync-context
+- **Force refresh** with /mtd-sync-context --refresh
+
+## Context Sources
+
+| Source | Entity Type | Content |
+|--------|-------------|---------|
+| \`.claude/context/*.md\` | \`UserContext:*\` | User-provided specs, tips, examples |
+| \`.claude/CLAUDE.md\` | \`ProjectContext\` | Stacks, naming, conventions |
+| \`.claude/entity-registry.json\` | \`EntityRegistry\` | Entity mappings |
+| \`.claude/core/enforcement.md\` | \`EnforcementRules\` | L0-L9 rules |
+| grepai discovery | \`CodePattern:*\` | Services, repos, components |
+
+## Output
+
+\`\`\`
+✅ Context loaded successfully
+
+Project Context:
+- Type: monorepo
+- Stacks: dotnet:9.0, react:19.x
+
+User Context (3 files):
+- architecture.md
+- business-rules.md
+- tips.md
+
+Code Patterns:
+- service (Backend/Services/ContractService.cs)
+- repository (Backend/Repositories/ContractRepository.cs)
+\`\`\`
+
+## Context Refresh Strategy
+
+| Trigger | Action |
+|---------|--------|
+| Context > 24h old | Auto-refresh on /mtd-pipeline-feature or /mtd-pipeline-bugfix |
+| \`/mtd-sync-context --refresh\` | Force full refresh |
+| \`/mtd-sync-registry\` | Refresh only EntityRegistry |
+
+## See Also
+
+- [context/README.md](../context/README.md) - How to create context files
+- [/mtd-pipeline-feature](./mtd-pipeline-feature.md) - Feature pipeline (auto-loads context)
+- [/mtd-pipeline-bugfix](./mtd-pipeline-bugfix.md) - Bugfix pipeline (auto-loads context)
+`;
+}
+// ============== Report Commands ==============
+function generateReportDailyCommand() {
+    return `# /mtd-report-daily - Daily Report
+
+## Trigger
+
+\`/mtd-report-daily\`
+
+## Description
+
+Generates a daily progress report.
+
+## Content
+
+1. **Commits Today**
+   - List of commits made
+   - Files changed
+
+2. **Pipeline Activity**
+   - Features started/completed
+   - Bugs fixed
+
+3. **Pending Items**
+   - Open pipelines
+   - Uncommitted changes
+
+## Output Format
+
+Markdown report suitable for sharing or documentation.
+`;
+}
+function generateReportWeeklyCommand() {
+    return `# /mtd-report-weekly - Weekly Report
+
+## Trigger
+
+\`/mtd-report-weekly\`
+
+## Description
+
+Generates a weekly progress report.
+
+## Content
+
+1. **Week Summary**
+   - Total commits
+   - Features completed
+   - Bugs fixed
+
+2. **Entity Changes**
+   - New entities created
+   - Entities modified
+
+3. **Code Metrics**
+   - Lines added/removed
+   - Files changed
+
+## Output Format
+
+Markdown report suitable for team updates.
+`;
+}
+// ============== Scan Commands ==============
+function generateScanProjectCommand() {
+    return `# /mtd-scan-project - Scan Project
+
+## Trigger
+
+\`/mtd-scan-project\`
+
+## Description
+
+Scans the project structure and updates detection.
+
+## Action
+
+1. Detects technology stacks
+2. Maps folder structure
+3. Identifies naming conventions
+4. Updates project state
+
+## When to Use
+
+- After major structural changes
+- When adding new technology
+- To refresh project detection
+`;
+}
+// ============== Task Commands (L0 Universal Delegation) ==============
+function generateTaskAnalyzeCommand() {
+    return `# /mtd-task-analyze - Code Analysis
+
+> Analyzes code in a **separate Task context** (L0 Universal Delegation).
+
+## Trigger
+
+\`/mtd-task-analyze <scope>\`
+
+## Description
+
+Analyzes code in a separate Task(Explore) context.
+Use for any code exploration that doesn't fit feature/bugfix pipelines.
+
+## L0 Enforcement
+
+**CRITICAL**: This command enforces L0 Universal Delegation:
+- Parent context does NOT read code
+- Parent context ONLY coordinates and presents results
+- ALL analysis happens in Task(Explore) context
+
+## Flow
+
+1. **DELEGATE** 🔍
+   - Create Task(Explore) with analysis scope
+   - Never analyze directly in parent context
+
+2. **REPORT**
+   - Present findings to user
+
+## Implementation
+
+\`\`\`javascript
+Task({
+  subagent_type: "Explore",
+  model: "haiku",
+  description: \`🔍 Analyze: \${scope}\`,
+  prompt: \`
+    # 🔍 CODE ANALYSIS TASK
+    ## Scope: \${scope}
+    ## Instructions
+    1. Use grepai_search for semantic search
+    2. Read relevant files
+    3. Document patterns found
+    4. Report findings clearly
+  \`
+})
+\`\`\`
+
+## Examples
+
+\`\`\`bash
+/mtd-task-analyze authentication flow
+/mtd-task-analyze "database schema"
+/mtd-task-analyze error handling patterns
+\`\`\`
+`;
+}
+function generateTaskReviewCommand() {
+    return `# /mtd-task-review - Code Review
+
+> Performs code review in a **separate Task context** (L0 Universal Delegation).
+
+## Trigger
+
+\`/mtd-task-review <scope>\`
+
+## Description
+
+Reviews code quality in a separate Task(general-purpose) context.
+Use for QA, SOLID validation, security checks.
+
+## L0 Enforcement
+
+**CRITICAL**: This command enforces L0 Universal Delegation:
+- Parent context does NOT read code
+- Parent context ONLY coordinates and presents results
+- ALL review happens in Task(general-purpose) context
+
+## Flow
+
+1. **DELEGATE** 🔎
+   - Create Task(general-purpose) with review prompt
+   - Never review directly in parent context
+
+2. **REPORT**
+   - Present findings with severity levels
+
+## Implementation
+
+\`\`\`javascript
+Task({
+  subagent_type: "general-purpose",
+  model: "opus",
+  description: \`🔎 Review: \${scope}\`,
+  prompt: \`
+    # 🔎 CODE REVIEW TASK
+    ## Scope: \${scope}
+    ## Checklist
+    - [ ] SOLID principles
+    - [ ] Error handling
+    - [ ] Security concerns
+    - [ ] Performance issues
+    ## Output: [Severity] File:Line - Issue - Suggestion
+  \`
+})
+\`\`\`
+
+## Examples
+
+\`\`\`bash
+/mtd-task-review src/services/payment
+/mtd-task-review "Contract entity"
+/mtd-task-review "security in auth module"
+\`\`\`
+`;
+}
+function generateTaskRefactorCommand() {
+    return `# /mtd-task-refactor - Code Refactoring
+
+> Refactors code in **separate Task contexts** (L0 Universal Delegation).
+
+## Trigger
+
+\`/mtd-task-refactor <scope>\`
+
+## Description
+
+Refactors code using Plan → Approve → Implement flow.
+Uses separate Task contexts for planning and execution.
+
+## L0 Enforcement
+
+**CRITICAL**: This command enforces L0 Universal Delegation:
+- Parent context does NOT read code
+- Parent context does NOT plan or implement
+- ALL work happens in Task(Plan) and Task(general-purpose) contexts
+
+## Flow
+
+1. **PLAN** 📋
+   - Create Task(Plan) to analyze scope
+   - Propose refactoring strategy
+
+2. **APPROVE**
+   - Present plan to user
+   - Wait for approval
+
+3. **IMPLEMENT** ⚙️
+   - Create Task(general-purpose) to execute
+   - Apply changes incrementally
+
+4. **VALIDATE**
+   - Run build/tests
+
+## Implementation
+
+\`\`\`javascript
+// Phase 1: Plan
+Task({
+  subagent_type: "Plan",
+  model: "sonnet",
+  description: \`📋 Plan refactor: \${scope}\`,
+  prompt: \`# Plan refactoring for \${scope}...\`
+})
+
+// Phase 2: Execute (after approval)
+Task({
+  subagent_type: "general-purpose",
+  model: "opus",
+  description: \`⚙️ Execute refactor: \${scope}\`,
+  prompt: \`# Execute approved plan...\`
+})
+\`\`\`
+
+## Examples
+
+\`\`\`bash
+/mtd-task-refactor "extract PaymentService"
+/mtd-task-refactor "rename User to Account"
+/mtd-task-refactor "split large component"
+\`\`\`
+`;
+}
+function generateTaskDocsCommand() {
+    return `# /mtd-task-docs - Documentation Generation
+
+> Generates documentation in a **separate Task context** (L0 Universal Delegation).
+
+## Trigger
+
+\`/mtd-task-docs <scope>\`
+
+## Description
+
+Generates documentation in a separate Task(general-purpose) context.
+Use for API docs, README updates, or technical documentation.
+
+## L0 Enforcement
+
+**CRITICAL**: This command enforces L0 Universal Delegation:
+- Parent context does NOT read code
+- Parent context does NOT generate documentation
+- ALL work happens in Task(general-purpose) context
+
+## Flow
+
+1. **DELEGATE** 📊
+   - Create Task(general-purpose) with docs prompt
+   - Never generate docs in parent context
+
+2. **PRESENT**
+   - Show generated documentation
+   - Ask for approval before saving
+
+## Implementation
+
+\`\`\`javascript
+Task({
+  subagent_type: "general-purpose",
+  model: "sonnet",
+  description: \`📊 Docs: \${scope}\`,
+  prompt: \`
+    # 📊 DOCUMENTATION TASK
+    ## Scope: \${scope}
+    ## Instructions
+    1. Use grepai to find relevant code
+    2. Generate appropriate documentation
+    3. Indicate where to save
+  \`
+})
+\`\`\`
+
+## Examples
+
+\`\`\`bash
+/mtd-task-docs "API endpoints"
+/mtd-task-docs "Contract entity"
+/mtd-task-docs "update README"
+\`\`\`
+`;
+}
+//# sourceMappingURL=commands.js.map