superkit-mcp-server 1.2.2 → 1.2.3

package/commands/README.md

@@ -1,122 +1,122 @@
-# Commands
-
-This directory contains all **custom slash commands** for the Super-Kit extension. Commands are defined as TOML files and automatically loaded by the AI agent client.
-
-## Overview
-
-Commands extend Super-Kit's capabilities by providing specialized prompts for specific tasks. Each command file follows the TOML format with `description` and `prompt` fields.
-
-## Command Categories
-
-| Category | Commands | Purpose |
-|----------|----------|---------|
-| **Planning** | `plan`, `brainstorm` | Create implementation plans |
-| **Coding** | `code`, `fix`, `debug`, `fullstack` | Write and debug code |
-| **Review** | `review`, `review-pr`, `pr` | Code review and PR management |
-| **Documentation** | `docs`, `doc-rules`, `help` | Documentation tasks |
-| **Project** | `project`, `pm`, `status` | Project management |
-| **Git** | `git`, `session` | Git and session management |
-| **Research** | `research`, `scout`, `scout-ext` | Codebase exploration |
-| **Content** | `content`, `copywrite`, `chat` | Content creation |
-| **Database** | `db` | Database operations |
-| **Design** | `design` | UI/UX design tasks |
-| **Testing** | `test` | Testing and QA |
-| **Tools** | `mcp`, `skill`, `screenshot`, `video` | Tool integrations |
-
-## Components
-
-| Component | Purpose | Status |
-|-----------|---------|--------|
-| `ask.toml` | General Q&A with context | ✅ Active |
-| `brainstorm.toml` | Creative ideation | ✅ Active |
-| `chat.toml` | Conversational interactions | ✅ Active |
-| `code.toml` | Code implementation | ✅ Active |
-| `code-preview.toml` | Code preview mode | ✅ Active |
-| `content.toml` | Content creation | ✅ Active |
-| `cook.toml` | Execute plans step-by-step | ✅ Active |
-| `copywrite.toml` | Marketing copy | ✅ Active |
-| `db.toml` | Database operations | ✅ Active |
-| `debug.toml` | Debugging assistance | ✅ Active |
-| `design.toml` | UI/UX design | ✅ Active |
-| `dev-rules.toml` | Development rules loader | ✅ Active |
-| `do.toml` | Quick task execution | ✅ Active |
-| `doc-rules.toml` | Documentation rules | ✅ Active |
-| `docs.toml` | Documentation management | ✅ Active |
-| `fix.toml` | Bug fixing | ✅ Active |
-| `fullstack.toml` | Full-stack development | ✅ Active |
-| `git.toml` | Git operations | ✅ Active |
-| `help.toml` | Help and guidance | ✅ Active |
-| `integrate.toml` | Integration tasks | ✅ Active |
-| `journal.toml` | Session journaling | ✅ Active |
-| `kit-setup.toml` | Project setup wizard | ✅ Active |
-| `mcp.toml` | MCP server management | ✅ Active |
-| `orchestration.toml` | Multi-agent orchestration | ✅ Active |
-| `plan.toml` | Implementation planning | ✅ Active |
-| `pm.toml` | Project management | ✅ Active |
-| `pr.toml` | Pull request creation | ✅ Active |
-| `project.toml` | Project context | ✅ Active |
-| `research.toml` | Research tasks | ✅ Active |
-| `review-pr.toml` | PR review | ✅ Active |
-| `review.toml` | Code review | ✅ Active |
-| `scout-ext.toml` | Extended codebase exploration | ✅ Active |
-| `scout.toml` | Codebase scout | ✅ Active |
-| `screenshot.toml` | Screenshot capture | ✅ Active |
-| `session.toml` | Session management | ✅ Active |
-| `skill.toml` | Skill creation | ✅ Active |
-| `status.toml` | Status reporting | ✅ Active |
-| `team.toml` | Team coordination | ✅ Active |
-| `test.toml` | Testing tasks | ✅ Active |
-| `ticket.toml` | Issue/ticket management | ✅ Active |
-| `use.toml` | Use existing patterns | ✅ Active |
-| `video.toml` | Video processing | ✅ Active |
-| `watzup.toml` | Quick status check | ✅ Active |
-| `workflow.toml` | Workflow management | ✅ Active |
-
-## TOML Structure
-
-Each command file follows this structure:
-
-```toml
-description = "Brief description shown in command list"
-
-prompt = '''
-# Command Name
-
-{{args}} - User input passed to the command
-
-## Instructions
-...
-'''
-```
-
-### String Types
-
-- **Basic string** (`"""..."""`): Processes escape sequences
-- **Literal string** (`'''...'''`): Raw content, no escape processing (preferred for complex prompts with code blocks)
-
-> [!NOTE]
-> Use literal strings (`'''`) when your prompt contains nested markdown code blocks to avoid TOML parsing issues.
-
-## Usage
-
-```bash
-# In Gemini CLI
-/command-name [arguments]
-
-# Examples
-/plan Add user authentication
-/code Implement login form
-/review @src/auth/login.ts
-```
-
-## Changelog
-
-### 2026-01-24
-- Fixed TOML parsing failure in `docs.toml` by switching from basic strings (`"""`) to literal strings (`'''`) - Issue #9
-
----
-
-## References
-
-- [Gemini CLI Commands Documentation](https://ai.google.dev/gemini-api/docs/gemini-cli)
-- [TOML Specification](https://toml.io/en/)
+# Commands
+
+This directory contains all **custom slash commands** for the Super-Kit extension. Commands are defined as TOML files and automatically loaded by the AI agent client.
+
+## Overview
+
+Commands extend Super-Kit's capabilities by providing specialized prompts for specific tasks. Each command file follows the TOML format with `description` and `prompt` fields.
+
+## Command Categories
+
+| Category | Commands | Purpose |
+|----------|----------|---------|
+| **Planning** | `plan`, `brainstorm` | Create implementation plans |
+| **Coding** | `code`, `fix`, `debug`, `fullstack` | Write and debug code |
+| **Review** | `review`, `review-pr`, `pr` | Code review and PR management |
+| **Documentation** | `docs`, `doc-rules`, `help` | Documentation tasks |
+| **Project** | `project`, `pm`, `status` | Project management |
+| **Git** | `git`, `session` | Git and session management |
+| **Research** | `research`, `scout`, `scout-ext` | Codebase exploration |
+| **Content** | `content`, `copywrite`, `chat` | Content creation |
+| **Database** | `db` | Database operations |
+| **Design** | `design` | UI/UX design tasks |
+| **Testing** | `test` | Testing and QA |
+| **Tools** | `mcp`, `skill`, `screenshot`, `video` | Tool integrations |
+
+## Components
+
+| Component | Purpose | Status |
+|-----------|---------|--------|
+| `ask.toml` | General Q&A with context | ✅ Active |
+| `brainstorm.toml` | Creative ideation | ✅ Active |
+| `chat.toml` | Conversational interactions | ✅ Active |
+| `code.toml` | Code implementation | ✅ Active |
+| `code-preview.toml` | Code preview mode | ✅ Active |
+| `content.toml` | Content creation | ✅ Active |
+| `cook.toml` | Execute plans step-by-step | ✅ Active |
+| `copywrite.toml` | Marketing copy | ✅ Active |
+| `db.toml` | Database operations | ✅ Active |
+| `debug.toml` | Debugging assistance | ✅ Active |
+| `design.toml` | UI/UX design | ✅ Active |
+| `dev-rules.toml` | Development rules loader | ✅ Active |
+| `do.toml` | Quick task execution | ✅ Active |
+| `doc-rules.toml` | Documentation rules | ✅ Active |
+| `docs.toml` | Documentation management | ✅ Active |
+| `fix.toml` | Bug fixing | ✅ Active |
+| `fullstack.toml` | Full-stack development | ✅ Active |
+| `git.toml` | Git operations | ✅ Active |
+| `help.toml` | Help and guidance | ✅ Active |
+| `integrate.toml` | Integration tasks | ✅ Active |
+| `journal.toml` | Session journaling | ✅ Active |
+| `kit-setup.toml` | Project setup wizard | ✅ Active |
+| `mcp.toml` | MCP server management | ✅ Active |
+| `orchestration.toml` | Multi-agent orchestration | ✅ Active |
+| `plan.toml` | Implementation planning | ✅ Active |
+| `pm.toml` | Project management | ✅ Active |
+| `pr.toml` | Pull request creation | ✅ Active |
+| `project.toml` | Project context | ✅ Active |
+| `research.toml` | Research tasks | ✅ Active |
+| `review-pr.toml` | PR review | ✅ Active |
+| `review.toml` | Code review | ✅ Active |
+| `scout-ext.toml` | Extended codebase exploration | ✅ Active |
+| `scout.toml` | Codebase scout | ✅ Active |
+| `screenshot.toml` | Screenshot capture | ✅ Active |
+| `session.toml` | Session management | ✅ Active |
+| `skill.toml` | Skill creation | ✅ Active |
+| `status.toml` | Status reporting | ✅ Active |
+| `team.toml` | Team coordination | ✅ Active |
+| `test.toml` | Testing tasks | ✅ Active |
+| `ticket.toml` | Issue/ticket management | ✅ Active |
+| `use.toml` | Use existing patterns | ✅ Active |
+| `video.toml` | Video processing | ✅ Active |
+| `watzup.toml` | Quick status check | ✅ Active |
+| `workflow.toml` | Workflow management | ✅ Active |
+
+## TOML Structure
+
+Each command file follows this structure:
+
+```toml
+description = "Brief description shown in command list"
+
+prompt = '''
+# Command Name
+
+{{args}} - User input passed to the command
+
+## Instructions
+...
+'''
+```
+
+### String Types
+
+- **Basic string** (`"""..."""`): Processes escape sequences
+- **Literal string** (`'''...'''`): Raw content, no escape processing (preferred for complex prompts with code blocks)
+
+> [!NOTE]
+> Use literal strings (`'''`) when your prompt contains nested markdown code blocks to avoid TOML parsing issues.
+
+## Usage
+
+```bash
+# In Gemini CLI
+/command-name [arguments]
+
+# Examples
+/plan Add user authentication
+/code Implement login form
+/review @src/auth/login.ts
+```
+
+## Changelog
+
+### 2026-01-24
+- Fixed TOML parsing failure in `docs.toml` by switching from basic strings (`"""`) to literal strings (`'''`) - Issue #9
+
+---
+
+## References
+
+- [Gemini CLI Commands Documentation](https://ai.google.dev/gemini-api/docs/gemini-cli)
+- [TOML Specification](https://toml.io/en/)

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
 # ---