superkit-mcp-server 1.1.3 → 1.2.0

package/commands/use.toml

@@ -0,0 +1,106 @@
+# Custom Assistants
+# Usage: /use <assistant> <message>
+# Chat with specialized AI assistants
+
+description = "Use specific tools or workflows"
+
+
+
+prompt = """
+{{#if args}}
+# 🤖 Custom Assistant Mode
+
+Parse the input: {{args}}
+
+The FIRST word is the assistant name, the REST is the user message.
+
+## Available Assistants:
+
+### 1. **coder** - Expert Programmer
+- Write clean, efficient, well-documented code
+- Follow best practices and design patterns
+- Provide complete, working solutions
+
+### 2. **reviewer** - Code Review Specialist  
+- Analyze code for bugs and security issues
+- Check performance and best practices
+- Suggest specific improvements with examples
+
+### 3. **architect** - System Design Expert
+- System design and architecture decisions
+- Database schema design
+- API design patterns
+- Scalability considerations
+- Use mermaid diagrams when helpful
+
+### 4. **debugger** - Bug Hunter
+- Analyze the root cause of errors
+- Explain why bugs happen
+- Provide exact fixes
+- Suggest prevention strategies
+
+### 5. **docs** - Documentation Writer
+- README files
+- API documentation
+- User guides
+- Clear language with helpful examples
+
+### 6. **brainstormer** - Trade-off Analyst
+- Evaluate multiple approaches with pros/cons
+- YAGNI assessment
+- Recommendation with reasoning
+- Saves you from writing wrong code
+
+### 7. **researcher** - Deep Research Expert
+- Multi-source research (docs, GitHub, articles)
+- Best practices extraction
+- Security concerns identification
+- Structured reports with citations
+
+### 8. **content** - Marketing Content Writer
+- Landing pages, hero sections, CTAs
+- Social media (Twitter threads, LinkedIn)
+- Email campaigns
+- A/B variants and CRO optimization
+
+---
+
+**Instructions:**
+1. Identify which assistant the user wants (first word)
+2. Adopt that assistant's persona and expertise
+3. Respond to the user's message using that specialized perspective
+4. If assistant name not recognized, suggest available options
+
+Now, respond as the requested assistant to the user's message.
+{{else}}
+# 🤖 Custom Assistants
+
+Use specialized AI assistants for different tasks.
+
+## Usage:
+```
+/use <assistant> <your message>
+```
+
+## Available Assistants:
+
+| Assistant | Expertise |
+|-----------|-----------|
+| `coder` | Expert programmer, clean code |
+| `reviewer` | Code review, security, performance |
+| `architect` | System design, databases, APIs |
+| `debugger` | Bug analysis, root cause, fixes |
+| `docs` | Documentation, README, guides |
+
+## Examples:
+```
+/use coder Write a function to debounce API calls
+/use reviewer Check this code for security issues: [code]
+/use architect Design a schema for a blog platform
+/use debugger Why is this error happening: TypeError...
+/use docs Write a README for my CLI tool
+```
+
+Choose an assistant and ask your question!
+{{/if}}
+"""

package/commands/video.toml

@@ -0,0 +1,84 @@
+# `/video` - Video Analysis to Code
+
+description = "Analyze video to generate code or design (Video Agent)"
+
+prompt = """
+# 🎬 VIDEO ANALYSIS AGENT
+
+Analyze video and generate output:
+
+**Input:** {{args}}
+
+## WORKFLOW
+
+### 1. VIDEO UNDERSTANDING
+- Identify video type (tutorial, demo, design, animation)
+- Identify key frames
+- Understand flow and transitions
+
+### 2. ANALYSIS TYPE
+
+#### UI/UX Demo
+- Extract design system (colors, typography, spacing)
+- Component breakdown
+- Interaction patterns
+- Responsive considerations
+
+#### Tutorial/Walkthrough
+- Step-by-step instructions
+- Key code snippets
+- Best practices mentioned
+- Timestamps and references
+
+#### Animation/Motion
+- Animation timeline
+- CSS/JavaScript animation code
+- Framer Motion / GSAP equivalents
+
+### 3. CODE GENERATION
+
+```[language]
+// Generated code based on video analysis
+```
+
+### 4. DESIGN TOKENS (if applicable)
+```css
+:root {
+  /* Colors */
+  --primary: #...;
+  --secondary: #...;
+  
+  /* Typography */
+  --font-heading: '...';
+  --font-body: '...';
+  
+  /* Spacing */
+  --spacing-xs: ...;
+}
+```
+
+### 5. COMPONENT STRUCTURE
+```
+ComponentName/
+├── index.tsx
+├── styles.css
+└── types.ts
+```
+
+## OUTPUT
+- Clean, production-ready code
+- Design tokens extracted
+- Animation timing functions
+- Responsive breakpoints
+
+## LIMITATIONS
+⚠️ Note: Video analysis accuracy depends on video quality and clarity.
+For complex videos, may need multiple passes or clarification.
+"""
+
+# ---
+# USAGE:
+# /video Analyze this UI demo and recreate the design
+# /video Extract animation patterns from this motion design
+# /video Convert this tutorial walkthrough into step-by-step guide
+# ---

package/commands/watzup.toml

@@ -0,0 +1,71 @@
+# Watzup - Project Status Overview
+# Usage: /watzup
+# Quick overview of project status
+
+description = "Check recent activity and status"
+
+
+
+prompt = """
+# 📊 Project Status Check
+
+Analyze the current project and provide a comprehensive status report.
+
+## Gather Information:
+
+1. **Git Status**
+   - Current branch
+   - Uncommitted changes
+   - Recent commits (last 5)
+   - Ahead/behind origin
+
+2. **Package Info** (if package.json exists)
+   - Name and version
+   - Dependencies count
+   - Scripts available
+   - Outdated packages (if possible)
+
+3. **Code Health**
+   - Scan for TODO/FIXME comments
+   - Count files by type (.ts, .js, .tsx, etc.)
+   - Estimate lines of code
+
+4. **Build/Test Status**
+   - Check if build script exists
+   - Check if test script exists
+   - Note any obvious issues
+
+## Output Format:
+
+```
+📊 PROJECT STATUS: [Project Name]
+═══════════════════════════════════
+
+🌿 Git Status
+   Branch: [branch]
+   Changes: [count] uncommitted files
+   Last commit: [message]
+
+📦 Dependencies
+   Production: [count]
+   Dev: [count]
+   
+📝 Code Stats
+   Files: [count]
+   TODOs: [count]
+   FIXMEs: [count]
+
+🔧 Available Scripts
+   - npm run build
+   - npm run test
+   - ...
+
+⚠️ Issues Found
+   - [any issues]
+
+✅ Quick Actions
+   - [suggested next steps]
+```
+
+Start the analysis now!
+"""

package/commands/workflow.toml

@@ -0,0 +1,14 @@
+description = "View primary workflow guide (/cook)"
+
+prompt = """
+You are a Workflow Guide. Read and explain the primary workflow.
+
+@{.agent/workflows/primary-workflow.md}
+
+Based on the workflow above, help the user with: {{args}}
+
+If no specific question, explain:
+1. The /cook workflow steps
+2. Quick workflows (feature, bugfix, refactor)
+3. When to use which command
+"""

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "superkit-mcp-server",
-    "version": "1.1.3",
+    "version": "1.2.0",
     "type": "module",
     "description": "An MCP server for exploring and loading Super-Kit AI agent resources.",
     "main": "build/index.js",
@@ -13,8 +13,10 @@
         "dev": "tsc --watch"
     },
     "dependencies": {
+        "@iarna/toml": "^2.2.5",
         "@modelcontextprotocol/sdk": "^1.4.1",
         "playwright": "^1.58.2",
+        "toml": "^3.0.0",
         "zod": "^3.23.8"
     },
     "devDependencies": {
@@ -26,7 +28,7 @@
         "build/",
         "agents/",
         "skills/",
-        "workflows/",
+        "commands/",
         "SUPERKIT.md",
         "README.md",
         "ARCHITECTURE.md"

package/{workflows → skills/workflows}/README.md

@@ -1,7 +1,7 @@
 # Compound Engineering Workflows
 
-> **Quick Start:** New to this project? Read [critical-patterns.md](../docs/solutions/patterns/critical-patterns.md) first.
-> **Technical Architecture:** For the complete system architecture, see [docs/architecture/compound-system.md](../docs/architecture/compound-system.md).
+> **Quick Start:** New to this project? Read [critical-patterns.md](../../docs/solutions/patterns/critical-patterns.md) first.
+> **Technical Architecture:** For the complete system architecture, see [docs/architecture/compound-system.md](../../docs/architecture/compound-system.md).
 
 ## Purpose
 
@@ -164,7 +164,7 @@ ls plans/*.md 2>/dev/null
 ## Directory Structure
 
 ```
-.agent/workflows/     # You are here - all workflow commands
+skills/workflows/     # You are here - all workflow definitions
 docs/solutions/       # Persistent knowledge base
 ├── patterns/         # Critical patterns (READ FIRST)
 ├── schema.yaml       # Solution validation schema

package/{workflows → skills/workflows}/development-rules.md

@@ -1,3 +1,8 @@
+---
+name: development-rules
+description: Code quality standards, testing targets, and pre-commit procedures to adhere to during development.
+---
+
 # Development Rules
 
 ## Code Quality Standards

package/{workflows → skills/workflows}/documentation-management.md

@@ -1,3 +1,8 @@
+---
+name: documentation-management
+description: Guidelines on when and where to update documentation, covering READMEs, API docs, and comments.
+---
+
 # Documentation Management
 
 ## When to Update Docs

package/{workflows → skills/workflows}/orchestration-protocol.md

@@ -1,3 +1,8 @@
+---
+name: orchestration-protocol
+description: Best practices and patterns for agent coordination, including sequential, parallel, and hybrid models.
+---
+
 # Orchestration Protocol
 
 ## Agent Coordination Patterns

package/{workflows → skills/workflows}/primary-workflow.md

@@ -1,3 +1,8 @@
+---
+name: primary-workflow
+description: Information about the primary workflow commands, including /cook for complex features and other quick tasks.
+---
+
 # Primary Workflow
 
 ## The `/cook` Workflow