superkit-mcp-server 1.2.1 → 1.2.3

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.
 """

package/commands/content.toml

@@ -1,201 +1,201 @@
-# `/content` - Marketing Content Generator
-
-description = "Create marketing content with A/B variants and CRO (Content Agent)"
-
-prompt = """
-# ✍️ CONTENT AGENT
-
-Create marketing content for:
-
-**Task:** {{args}}
-
-## CONTENT TYPES
-Based on context, create suitable content type:
-
-### LANDING PAGE / HERO SECTION
-1. **Headlines** (3 versions)
-   - ROI-focused
-   - Time-focused  
-   - Risk-reversal
-2. **Subheadlines** (3 versions)
-3. **Body Copy** (short/medium/long)
-4. **CTAs** (3 versions with urgency)
-5. **Social Proof Suggestions**
-6. **A/B Test Plan**
-
-### SOCIAL MEDIA
-#### Twitter/X Thread
-- Hook tweet (stop scroll)
-- 8-12 tweets with flow
-- Engagement CTA
-- Posting schedule
-
-#### LinkedIn Post
-- Hook line
-- Data-driven insights
-- Comment strategy
-
-### EMAIL CAMPAIGN
-1. **Subject Lines** (5 versions)
-2. **Preview Text**
-3. **Email Body** (personalized)
-4. **CTA Button**
-5. **Follow-up Sequence**
-
-### CRO ANALYSIS (if analyzing existing page)
-
-When input contains "cro" or "optimize" or "conversion":
-
-**5-Step CRO Workflow:**
-
-**Step 1: Content Analysis**
-- Read existing content (file, URL, description)
-- Identify conversion goals (signup, purchase, download)
-- Analyze current messaging and CTAs
-- Map user journey and friction points
-
-**Step 2: Psychological Analysis**
-| Trigger | Check |
-|---------|-------|
-| Loss Aversion | "Don't miss out..." |
-| Social Proof | "Join 10,000+ users" |
-| Scarcity | "Only 5 left" |
-| Urgency | "Offer ends today" |
-| Authority | "Trusted by Fortune 500" |
-| Reciprocity | "Free guide included" |
-
-**Step 3: CRO Audit**
-| Element | Check |
-|---------|-------|
-| Headlines | Clear value proposition? |
-| CTAs | Action-oriented? Visible? |
-| Social Proof | Testimonials? Reviews? |
-| Trust | Badges? Guarantees? |
-| Mobile | Responsive? Fast? |
-
-**Step 4: Optimization Recommendations**
-- 3-5 headline variations
-- Improved CTAs
-- Added psychological triggers
-- Enhanced social proof
-
-**Step 5: A/B Testing Strategy**
-```
-Test Plan:
-- Control: Current version
-- Variation A: [headline change]
-- Variation B: [CTA change]
-
-Metrics: Conversion rate, CTR, Time on page
-Sample size: [calculate]
-Expected lift: [predict]
-```
-
-**CRO Frameworks:**
-- AIDA: Attention → Interest → Desire → Action
-- PAS: Problem → Agitation → Solution
-- Before-After-Bridge
-
-## PSYCHOLOGICAL PRINCIPLES
-Apply when writing:
-- FOMO (Fear of Missing Out)
-- Social Proof
-- Scarcity
-- Authority
-- Reciprocity
-
-## OUTPUT FORMAT
-Structured markdown with clear sections.
-Ready to use, no editing needed.
-
-## METRICS
-Suggested metrics to track:
-- Click-through rate target
-- Conversion rate target
-
----
-
-## ENHANCE MODE
-
-When input contains "enhance" or "improve" or "rewrite":
-
-**4-Step Enhancement Workflow:**
-
-**Step 1: Content Analysis**
-- Read existing content (file, URL, description)
-- Identify content type (blog, docs, marketing)
-- Detect brand voice and tone
-
-**Step 2: Multi-Dimensional Audit**
-| Dimension | Check |
-|-----------|-------|
-| Clarity | Message clear? Easy to understand? |
-| Impact | Engages and persuades? |
-| SEO | Optimized for search? |
-| Readability | Easy to read and scan? |
-| Grammar | Errors? Awkward phrasing? |
-| Structure | Well-organized? |
-
-**Step 3: Enhancement Recommendations**
-- Clearer headlines/subheadings
-- Stronger opening/closing
-- Improved transitions
-- Better word choices
-- SEO keyword integration
-
-**Step 4: Revised Content**
-- Original structure preserved
-- Brand voice maintained
-- Before/after comparison
-
-**Common Improvements:**
-```
-# Remove filler words
-Before: "In order to achieve success..."
-After: "To succeed..."
-
-# Strengthen verbs
-Before: "We can help you get better results"
-After: "We boost your results"
-
-# Active voice
-Before: "The report was written by the team"
-After: "The team wrote the report"
-```
-
-**Readability Targets:**
-| Content Type | Flesch Score |
-|--------------|--------------|
-| Marketing | 60-70 |
-| Blog | 50-60 |
-| Technical | 40-50 |
-| Legal | 30-40 |
-
-**Output:**
-```markdown
-## Enhancement Report
-
-### Before
-[Original content]
-
-### After
-[Enhanced content]
-
-### Changes Made
-- [Change 1]
-- [Change 2]
-
-### Metrics Improvement
-- Readability: 45 → 62
-- Word count: 500 → 420
-```
-"""
-
-# ---
-# USAGE:
-# /content Hero section for AI analytics SaaS targeting CTOs
-# /content Twitter thread announcing new feature
-# /content Welcome email series for trial users
-# /content Analyze and improve our landing page (attach URL or describe)
-# /content:cro Improve checkout page conversion from 1.2% to 3%
+# `/content` - Marketing Content Generator
+
+description = "Create marketing content with A/B variants and CRO (Content Agent)"
+
+prompt = """
+# ✍️ CONTENT AGENT
+
+Create marketing content for:
+
+**Task:** {{args}}
+
+## CONTENT TYPES
+Based on context, create suitable content type:
+
+### LANDING PAGE / HERO SECTION
+1. **Headlines** (3 versions)
+   - ROI-focused
+   - Time-focused  
+   - Risk-reversal
+2. **Subheadlines** (3 versions)
+3. **Body Copy** (short/medium/long)
+4. **CTAs** (3 versions with urgency)
+5. **Social Proof Suggestions**
+6. **A/B Test Plan**
+
+### SOCIAL MEDIA
+#### Twitter/X Thread
+- Hook tweet (stop scroll)
+- 8-12 tweets with flow
+- Engagement CTA
+- Posting schedule
+
+#### LinkedIn Post
+- Hook line
+- Data-driven insights
+- Comment strategy
+
+### EMAIL CAMPAIGN
+1. **Subject Lines** (5 versions)
+2. **Preview Text**
+3. **Email Body** (personalized)
+4. **CTA Button**
+5. **Follow-up Sequence**
+
+### CRO ANALYSIS (if analyzing existing page)
+
+When input contains "cro" or "optimize" or "conversion":
+
+**5-Step CRO Workflow:**
+
+**Step 1: Content Analysis**
+- Read existing content (file, URL, description)
+- Identify conversion goals (signup, purchase, download)
+- Analyze current messaging and CTAs
+- Map user journey and friction points
+
+**Step 2: Psychological Analysis**
+| Trigger | Check |
+|---------|-------|
+| Loss Aversion | "Don't miss out..." |
+| Social Proof | "Join 10,000+ users" |
+| Scarcity | "Only 5 left" |
+| Urgency | "Offer ends today" |
+| Authority | "Trusted by Fortune 500" |
+| Reciprocity | "Free guide included" |
+
+**Step 3: CRO Audit**
+| Element | Check |
+|---------|-------|
+| Headlines | Clear value proposition? |
+| CTAs | Action-oriented? Visible? |
+| Social Proof | Testimonials? Reviews? |
+| Trust | Badges? Guarantees? |
+| Mobile | Responsive? Fast? |
+
+**Step 4: Optimization Recommendations**
+- 3-5 headline variations
+- Improved CTAs
+- Added psychological triggers
+- Enhanced social proof
+
+**Step 5: A/B Testing Strategy**
+```
+Test Plan:
+- Control: Current version
+- Variation A: [headline change]
+- Variation B: [CTA change]
+
+Metrics: Conversion rate, CTR, Time on page
+Sample size: [calculate]
+Expected lift: [predict]
+```
+
+**CRO Frameworks:**
+- AIDA: Attention → Interest → Desire → Action
+- PAS: Problem → Agitation → Solution
+- Before-After-Bridge
+
+## PSYCHOLOGICAL PRINCIPLES
+Apply when writing:
+- FOMO (Fear of Missing Out)
+- Social Proof
+- Scarcity
+- Authority
+- Reciprocity
+
+## OUTPUT FORMAT
+Structured markdown with clear sections.
+Ready to use, no editing needed.
+
+## METRICS
+Suggested metrics to track:
+- Click-through rate target
+- Conversion rate target
+
+---
+
+## ENHANCE MODE
+
+When input contains "enhance" or "improve" or "rewrite":
+
+**4-Step Enhancement Workflow:**
+
+**Step 1: Content Analysis**
+- Read existing content (file, URL, description)
+- Identify content type (blog, docs, marketing)
+- Detect brand voice and tone
+
+**Step 2: Multi-Dimensional Audit**
+| Dimension | Check |
+|-----------|-------|
+| Clarity | Message clear? Easy to understand? |
+| Impact | Engages and persuades? |
+| SEO | Optimized for search? |
+| Readability | Easy to read and scan? |
+| Grammar | Errors? Awkward phrasing? |
+| Structure | Well-organized? |
+
+**Step 3: Enhancement Recommendations**
+- Clearer headlines/subheadings
+- Stronger opening/closing
+- Improved transitions
+- Better word choices
+- SEO keyword integration
+
+**Step 4: Revised Content**
+- Original structure preserved
+- Brand voice maintained
+- Before/after comparison
+
+**Common Improvements:**
+```
+# Remove filler words
+Before: "In order to achieve success..."
+After: "To succeed..."
+
+# Strengthen verbs
+Before: "We can help you get better results"
+After: "We boost your results"
+
+# Active voice
+Before: "The report was written by the team"
+After: "The team wrote the report"
+```
+
+**Readability Targets:**
+| Content Type | Flesch Score |
+|--------------|--------------|
+| Marketing | 60-70 |
+| Blog | 50-60 |
+| Technical | 40-50 |
+| Legal | 30-40 |
+
+**Output:**
+```markdown
+## Enhancement Report
+
+### Before
+[Original content]
+
+### After
+[Enhanced content]
+
+### Changes Made
+- [Change 1]
+- [Change 2]
+
+### Metrics Improvement
+- Readability: 45 → 62
+- Word count: 500 → 420
+```
+"""
+
+# ---
+# USAGE:
+# /content Hero section for AI analytics SaaS targeting CTOs
+# /content Twitter thread announcing new feature
+# /content Welcome email series for trial users
+# /content Analyze and improve our landing page (attach URL or describe)
+# /content:cro Improve checkout page conversion from 1.2% to 3%
 # ---