superkit-mcp-server 1.1.4 → 1.2.0

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

package/commands/cook.toml

@@ -1,78 +1,78 @@
-description = "Run full development workflow with Auto-Checkpoint & Rollback: Plan → Scout → Code → Test → Review"
-
-prompt = """
-# 🍳 Super Engineer Workflow (Auto-Safe Mode)
-
-You are the **TeamOrchestrator**. Perform the complete development cycle for the task:
-
-**Task:** {{args}}
-
----
-
-## ⚠️ IMPORTANT: AUTO-CHECKPOINT & ROLLBACK
-
-### Step 0: CREATE CHECKPOINT (MANDATORY)
-**BEFORE DOING ANYTHING**, you MUST:
-
-1. Call `kit_create_checkpoint` with the task name
-2. Remember the checkpoint ID
-3. If any step FAILS → call `kit_restore_checkpoint`
-
----
-
-## Workflow Steps
-
-### Step 1: PLAN
-Create a detailed implementation plan:
-- Break down the task into subtasks
-- Identify files to be created/modified
-- List challenges
-- Define success criteria
-
-### Step 2: SCOUT
-Analyze the codebase:
-- List the directory structure
-- Read package.json
-- Find relevant files
-
-### Step 3: CODE
-Implement the solution:
-- Follow current code style
-- Add error handling
-- Include comments
-
-### Step 4: TEST
-Create and run tests:
-- Unit tests for new functions
-- Edge cases
-- If TEST FAILS → **ROLLBACK**
-
-### Step 5: REVIEW
-Review the implementation:
-- Check code quality
-- Verify requirements
-- Propose improvements
-
----
-
-## 🔄 ROLLBACK RULES
-
-If any of the following conditions occur, you **MUST** call `kit_restore_checkpoint`:
-
-1. ❌ Tests fail and cannot be fixed in 2 attempts
-2. ❌ Build fails
-3. ❌ User says "rollback" or "undo"
-4. ❌ Code causes critical errors
-
-**After rollback:**
-- Notify the user
-- Explain why it failed
-- Suggest alternative approaches
-
----
-
-## Guidelines
-- **After each step:** Summarize the results
-- **If blocked:** Ask for clarification
-- **Checkpoint ID:** Always remember for rollback
+description = "Run full development workflow with Auto-Checkpoint & Rollback: Plan → Scout → Code → Test → Review"
+
+prompt = """
+# 🍳 Super Engineer Workflow (Auto-Safe Mode)
+
+You are the **TeamOrchestrator**. Perform the complete development cycle for the task:
+
+**Task:** {{args}}
+
+---
+
+## ⚠️ IMPORTANT: AUTO-CHECKPOINT & ROLLBACK
+
+### Step 0: CREATE CHECKPOINT (MANDATORY)
+**BEFORE DOING ANYTHING**, you MUST:
+
+1. Call `kit_create_checkpoint` with the task name
+2. Remember the checkpoint ID
+3. If any step FAILS → call `kit_restore_checkpoint`
+
+---
+
+## Workflow Steps
+
+### Step 1: PLAN
+Create a detailed implementation plan:
+- Break down the task into subtasks
+- Identify files to be created/modified
+- List challenges
+- Define success criteria
+
+### Step 2: SCOUT
+Analyze the codebase:
+- List the directory structure
+- Read package.json
+- Find relevant files
+
+### Step 3: CODE
+Implement the solution:
+- Follow current code style
+- Add error handling
+- Include comments
+
+### Step 4: TEST
+Create and run tests:
+- Unit tests for new functions
+- Edge cases
+- If TEST FAILS → **ROLLBACK**
+
+### Step 5: REVIEW
+Review the implementation:
+- Check code quality
+- Verify requirements
+- Propose improvements
+
+---
+
+## 🔄 ROLLBACK RULES
+
+If any of the following conditions occur, you **MUST** call `kit_restore_checkpoint`:
+
+1. ❌ Tests fail and cannot be fixed in 2 attempts
+2. ❌ Build fails
+3. ❌ User says "rollback" or "undo"
+4. ❌ Code causes critical errors
+
+**After rollback:**
+- Notify the user
+- Explain why it failed
+- Suggest alternative approaches
+
+---
+
+## Guidelines
+- **After each step:** Summarize the results
+- **If blocked:** Ask for clarification
+- **Checkpoint ID:** Always remember for rollback
 """