superkit-mcp-server 1.2.3 → 1.2.4

package/commands/ask.toml

@@ -1,72 +1,72 @@
-# Ask - Ask About Codebase
-# Usage: /ask <question>
-# Ask questions about the codebase, AI will search and answer
-
-description = "Ask questions about the codebase, AI will search and answer"
-
-prompt = """
-{{#if args}}
-# ❓ Ask About Codebase
-
-**Question:** {{args}}
-
-## Instructions:
-
-1. **Search the codebase** to find relevant files and code
-2. **Analyze** the code structure and patterns
-3. **Answer** the question based on actual code
-
-## Search Strategy:
-- Look for files related to the question keywords
-- Read relevant source files
-- Check imports and dependencies
-- Look at tests for usage examples
-
-## Answer Format:
-
-### 📋 Answer
-[Direct answer to the question]
-
-### 📁 Relevant Files
-- `file1.ts` - [description]
-- `file2.ts` - [description]
-
-### 💡 Code Examples
-```typescript
-// relevant code snippets
-```
-
-### 🔗 Related
-- [other related concepts or files]
-
----
-
-Now search the codebase and answer: "{{args}}"
-{{else}}
-# ❓ Ask About Codebase
-
-Ask any question about the codebase and get AI-powered answers.
-
-## Usage:
-```
-/ask <your question>
-```
-
-## Examples:
-```
-/ask How does authentication work?
-/ask Where is the user model defined?
-/ask What API endpoints are available?
-/ask How do I add a new route?
-/ask Where are database queries made?
-```
-
-## What it does:
-1. Searches codebase for relevant files
-2. Analyzes code structure and patterns
-3. Provides answer based on actual code
-4. Shows relevant code snippets
-
-Ask your question!
-{{/if}}
-"""
+# Ask - Ask About Codebase
+# Usage: /ask <question>
+# Ask questions about the codebase, AI will search and answer
+
+description = "Ask questions about the codebase, AI will search and answer"
+
+prompt = """
+{{#if args}}
+# ❓ Ask About Codebase
+
+**Question:** {{args}}
+
+## Instructions:
+
+1. **Search the codebase** to find relevant files and code
+2. **Analyze** the code structure and patterns
+3. **Answer** the question based on actual code
+
+## Search Strategy:
+- Look for files related to the question keywords
+- Read relevant source files
+- Check imports and dependencies
+- Look at tests for usage examples
+
+## Answer Format:
+
+### 📋 Answer
+[Direct answer to the question]
+
+### 📁 Relevant Files
+- `file1.ts` - [description]
+- `file2.ts` - [description]
+
+### 💡 Code Examples
+```typescript
+// relevant code snippets
+```
+
+### 🔗 Related
+- [other related concepts or files]
+
+---
+
+Now search the codebase and answer: "{{args}}"
+{{else}}
+# ❓ Ask About Codebase
+
+Ask any question about the codebase and get AI-powered answers.
+
+## Usage:
+```
+/ask <your question>
+```
+
+## Examples:
+```
+/ask How does authentication work?
+/ask Where is the user model defined?
+/ask What API endpoints are available?
+/ask How do I add a new route?
+/ask Where are database queries made?
+```
+
+## What it does:
+1. Searches codebase for relevant files
+2. Analyzes code structure and patterns
+3. Provides answer based on actual code
+4. Shows relevant code snippets
+
+Ask your question!
+{{/if}}
+"""

package/commands/brainstorm.toml

@@ -1,120 +1,120 @@
-description = "Trade-off analysis before coding (Brainstormer Agent)"
-
-prompt = """
-# 💡 BRAINSTORMER AGENT
-
-Brainstorm topic:
-
-**Question:** {{args}}
-
-## CONTEXT REQUESTED
-Before analysis, context is needed:
-- **Team:** Skills, experience level?
-- **Timeline:** Deadline? MVP or full product?
-- **Budget:** Constraints?
-- **Constraints:** Technical, business?
-
-(If no context is provided, it will base analysis on assumptions and list them)
-
----
-
-## OUTPUT FORMAT
-
-### 📋 Problem Understanding
-- Problem to solve
-- Constraints identified
-- Assumptions made
-
----
-
-### 🔄 Approaches Analysis
-
-#### Approach A: [Name]
-| Aspect | Analysis |
-|--------|----------|
-| **Description** | [How it works] |
-| **Pros** | • [Pro 1] • [Pro 2] • [Pro 3] |
-| **Cons** | • [Con 1] • [Con 2] |
-| **Effort** | Low / Medium / High |
-| **Risk** | Low / Medium / High |
-| **Time to MVP** | [Estimate] |
-
-#### Approach B: [Name]
-[Same structure]
-
-#### Approach C: [Name]
-[Same structure]
-
----
-
-### 📊 Trade-off Matrix
-
-| Criteria | A | B | C |
-|----------|---|---|---|
-| Speed | ⭐⭐⭐ | ⭐⭐ | ⭐ |
-| Scale | ⭐ | ⭐⭐⭐ | ⭐⭐ |
-| Cost | ⭐⭐⭐ | ⭐⭐ | ⭐ |
-| Team Fit | ⭐⭐ | ⭐⭐⭐ | ⭐ |
-
----
-
-### ✅ Success Criteria
-Measurable criteria to validate decision:
-- [ ] [Metric 1] e.g., "p95 latency <200ms"
-- [ ] [Metric 2] e.g., "Ship MVP in 6 weeks"
-- [ ] [Metric 3] e.g., "80% test coverage"
-
----
-
-### ⚠️ YAGNI Assessment
-**Overengineering check:**
-
-> Is this solution over-engineered for current needs?
-
-- [ ] Building for 10x scale when 2x is enough
-- [ ] Premature optimization
-- [ ] Unnecessary abstractions
-
-**Verdict:** [Keep simple / Proceed / Simplify]
-
----
-
-### ❓ Open Questions
-Questions to answer BEFORE proceeding:
-1. [Question 1]
-2. [Question 2]
-3. [Question 3]
-
-⚠️ **Don't skip these!**
-
----
-
-### 🎯 Recommendation
-**Recommended:** [Approach X]
-
-**Reasoning:**
-[Why this approach fits best given context]
-
-**When NOT to use:**
-[Scenarios where this would be wrong choice]
-
----
-
-### 🚀 Next Steps
-```bash
-# Ready to proceed? Run:
-/plan [implementation based on chosen approach]
-```
-
----
-
-> **Key Takeaway:** Brainstormer doesn't write code. It saves you from writing the wrong code. 10 minutes of brainstorming prevents weeks of refactoring.
-"""
-
-# ---
-# USAGE:
-# /brainstorm REST vs GraphQL for mobile app
-# /brainstorm Redis cache vs DB optimization vs CDN
-# /brainstorm Monolith vs microservices
-# /brainstorm WebSockets vs polling for dashboard
+description = "Trade-off analysis before coding (Brainstormer Agent)"
+
+prompt = """
+# 💡 BRAINSTORMER AGENT
+
+Brainstorm topic:
+
+**Question:** {{args}}
+
+## CONTEXT REQUESTED
+Before analysis, context is needed:
+- **Team:** Skills, experience level?
+- **Timeline:** Deadline? MVP or full product?
+- **Budget:** Constraints?
+- **Constraints:** Technical, business?
+
+(If no context is provided, it will base analysis on assumptions and list them)
+
+---
+
+## OUTPUT FORMAT
+
+### 📋 Problem Understanding
+- Problem to solve
+- Constraints identified
+- Assumptions made
+
+---
+
+### 🔄 Approaches Analysis
+
+#### Approach A: [Name]
+| Aspect | Analysis |
+|--------|----------|
+| **Description** | [How it works] |
+| **Pros** | • [Pro 1] • [Pro 2] • [Pro 3] |
+| **Cons** | • [Con 1] • [Con 2] |
+| **Effort** | Low / Medium / High |
+| **Risk** | Low / Medium / High |
+| **Time to MVP** | [Estimate] |
+
+#### Approach B: [Name]
+[Same structure]
+
+#### Approach C: [Name]
+[Same structure]
+
+---
+
+### 📊 Trade-off Matrix
+
+| Criteria | A | B | C |
+|----------|---|---|---|
+| Speed | ⭐⭐⭐ | ⭐⭐ | ⭐ |
+| Scale | ⭐ | ⭐⭐⭐ | ⭐⭐ |
+| Cost | ⭐⭐⭐ | ⭐⭐ | ⭐ |
+| Team Fit | ⭐⭐ | ⭐⭐⭐ | ⭐ |
+
+---
+
+### ✅ Success Criteria
+Measurable criteria to validate decision:
+- [ ] [Metric 1] e.g., "p95 latency <200ms"
+- [ ] [Metric 2] e.g., "Ship MVP in 6 weeks"
+- [ ] [Metric 3] e.g., "80% test coverage"
+
+---
+
+### ⚠️ YAGNI Assessment
+**Overengineering check:**
+
+> Is this solution over-engineered for current needs?
+
+- [ ] Building for 10x scale when 2x is enough
+- [ ] Premature optimization
+- [ ] Unnecessary abstractions
+
+**Verdict:** [Keep simple / Proceed / Simplify]
+
+---
+
+### ❓ Open Questions
+Questions to answer BEFORE proceeding:
+1. [Question 1]
+2. [Question 2]
+3. [Question 3]
+
+⚠️ **Don't skip these!**
+
+---
+
+### 🎯 Recommendation
+**Recommended:** [Approach X]
+
+**Reasoning:**
+[Why this approach fits best given context]
+
+**When NOT to use:**
+[Scenarios where this would be wrong choice]
+
+---
+
+### 🚀 Next Steps
+```bash
+# Ready to proceed? Run:
+/plan [implementation based on chosen approach]
+```
+
+---
+
+> **Key Takeaway:** Brainstormer doesn't write code. It saves you from writing the wrong code. 10 minutes of brainstorming prevents weeks of refactoring.
+"""
+
+# ---
+# USAGE:
+# /brainstorm REST vs GraphQL for mobile app
+# /brainstorm Redis cache vs DB optimization vs CDN
+# /brainstorm Monolith vs microservices
+# /brainstorm WebSockets vs polling for dashboard
 # ---

package/commands/chat.toml

@@ -1,77 +1,77 @@
-# Chat - Chat Mode Reference
-# Usage: /chat
-# Reference for chat shortcuts and commands
-
-description = "Reference for chat shortcuts and commands"
-
-
-
-prompt = """
-# 💬 Super-Kit Chat Reference
-
-Quick reference for chat mode features in Super-Kit CLI.
-
-## Built-in Features
-
-Super-Kit CLI already supports these in chat:
-
-### File Operations
-```
-@file.ts          # Read a file into context
-Read file.ts      # Natural language also works
-```
-
-### Search
-```
-Search for auth    # Find files
-Where is login    # Natural language search
-```
-
-### Commands
-```
-/plan             # Create plan
-/cook             # Execute with checkpoint
-/scout            # Search codebase
-/code             # Implement features
-...               # All super-kit commands
-```
-
-## Tips
-
-### Adding Context
-- Mention file names and AI will read them
-- Use "Read [file]" or "Show me [file]"
-- Reference line numbers: "line 50 of app.ts"
-
-### Multi-turn Conversations
-- AI remembers conversation history
-- Reference previous messages
-- Build on earlier answers
-
-### Controlling Output
-- "Be concise" for shorter answers
-- "Explain in detail" for longer
-- "Show code only" for just code
-
-## Super-Kit Chat Commands
-
-| Command | Description |
-|---------|-------------|
-| `/chat` | Show this help |
-| `/chat mode` | Explain AI modes |
-| `/chat tips` | Show power user tips |
-| `/ask <question>` | Ask about codebase |
-| `/watzup` | Project status |
-| `/session save` | Save current context |
-
-## Keyboard Shortcuts
-
-- `Ctrl+C` - Cancel current operation
-- `Ctrl+D` - Exit Super-Kit CLI
-- `Up/Down` - Navigate history
-
-That's it! Start chatting naturally with AI.
-"""
-
-# ---
-# USAGE:
+# Chat - Chat Mode Reference
+# Usage: /chat
+# Reference for chat shortcuts and commands
+
+description = "Reference for chat shortcuts and commands"
+
+
+
+prompt = """
+# 💬 Super-Kit Chat Reference
+
+Quick reference for chat mode features in Super-Kit CLI.
+
+## Built-in Features
+
+Super-Kit CLI already supports these in chat:
+
+### File Operations
+```
+@file.ts          # Read a file into context
+Read file.ts      # Natural language also works
+```
+
+### Search
+```
+Search for auth    # Find files
+Where is login    # Natural language search
+```
+
+### Commands
+```
+/plan             # Create plan
+/cook             # Execute with checkpoint
+/scout            # Search codebase
+/code             # Implement features
+...               # All super-kit commands
+```
+
+## Tips
+
+### Adding Context
+- Mention file names and AI will read them
+- Use "Read [file]" or "Show me [file]"
+- Reference line numbers: "line 50 of app.ts"
+
+### Multi-turn Conversations
+- AI remembers conversation history
+- Reference previous messages
+- Build on earlier answers
+
+### Controlling Output
+- "Be concise" for shorter answers
+- "Explain in detail" for longer
+- "Show code only" for just code
+
+## Super-Kit Chat Commands
+
+| Command | Description |
+|---------|-------------|
+| `/chat` | Show this help |
+| `/chat mode` | Explain AI modes |
+| `/chat tips` | Show power user tips |
+| `/ask <question>` | Ask about codebase |
+| `/watzup` | Project status |
+| `/session save` | Save current context |
+
+## Keyboard Shortcuts
+
+- `Ctrl+C` - Cancel current operation
+- `Ctrl+D` - Exit Super-Kit CLI
+- `Up/Down` - Navigate history
+
+That's it! Start chatting naturally with AI.
+"""
+
+# ---
+# USAGE:

package/commands/code-preview.toml

@@ -1,38 +1,38 @@
-description = "Preview code changes without applying (Dry Run mode)"
-
-prompt = """
-# 👁️ Code Preview Agent (Dry Run)
-
-**Request:** {{args}}
-
-## IMPORTANT - DRY RUN MODE
-
-You are in **DRY RUN** mode. This means:
-1. ❌ **DO NOT** write to actual files
-2. ❌ **DO NOT** use write_file, edit, or any file writing tools
-3. ✅ **ONLY** display proposed changes in unified diff format
-
-## Output Format
-
-Display proposed changes as:
-
-### File: `path/to/file.ts`
-```diff
-- old line
-+ new line
-```
-
-## After Preview
-
-After the user views the diff:
-- If the user says "apply", "ok", "lgtm" → Run `/code` to apply
-- If the user says "no", "cancel" → Stop
-- If the user requests changes → Update the diff
-
-## Guidelines
-
-1. Read current files first
-2. Create proposed changes
-3. Display diff ONLY ON CONSOLE
-4. DO NOT WRITE TO FILE
+description = "Preview code changes without applying (Dry Run mode)"
+
+prompt = """
+# 👁️ Code Preview Agent (Dry Run)
+
+**Request:** {{args}}
+
+## IMPORTANT - DRY RUN MODE
+
+You are in **DRY RUN** mode. This means:
+1. ❌ **DO NOT** write to actual files
+2. ❌ **DO NOT** use write_file, edit, or any file writing tools
+3. ✅ **ONLY** display proposed changes in unified diff format
+
+## Output Format
+
+Display proposed changes as:
+
+### File: `path/to/file.ts`
+```diff
+- old line
++ new line
+```
+
+## After Preview
+
+After the user views the diff:
+- If the user says "apply", "ok", "lgtm" → Run `/code` to apply
+- If the user says "no", "cancel" → Stop
+- If the user requests changes → Update the diff
+
+## Guidelines
+
+1. Read current files first
+2. Create proposed changes
+3. Display diff ONLY ON CONSOLE
+4. DO NOT WRITE TO FILE
 """

package/commands/code.toml

@@ -1,29 +1,29 @@
-description = "Write and edit code (Coder Agent)"
-
-prompt = """
-# 💻 Coder Agent
-
-Implement:
-
-**Task:** {{args}}
-
-## Pre-flight
-1. Review plan (if any)
-2. Check existing patterns
-3. Identify integration points
-
-## Implementation Guidelines
-- Follow project style guide
-- TypeScript best practices
-- Proper error handling
-- JSDoc comments for functions
-
-## Code Quality
-- Clean, readable
-- Single responsibility
-- Proper naming
-- No magic numbers
-
-## Output
-Code changes with explanations.
+description = "Write and edit code (Coder Agent)"
+
+prompt = """
+# 💻 Coder Agent
+
+Implement:
+
+**Task:** {{args}}
+
+## Pre-flight
+1. Review plan (if any)
+2. Check existing patterns
+3. Identify integration points
+
+## Implementation Guidelines
+- Follow project style guide
+- TypeScript best practices
+- Proper error handling
+- JSDoc comments for functions
+
+## Code Quality
+- Clean, readable
+- Single responsibility
+- Proper naming
+- No magic numbers
+
+## Output
+Code changes with explanations.
 """