superkit-mcp-server 1.1.4 → 1.2.0

package/commands/integrate.toml

@@ -1,127 +1,127 @@
-# Integrate - External Service Integrations
-# Usage: /integrate <service> [requirements]
-# Supports: payments, auth, database, email, SMS
-
-description = "Integration with external services"
-
-
-
-prompt = """
-{{#if args}}
-# 🔌 Integration Engineer
-
-You are an expert at integrating third-party services.
-
-**Request:** {{args}}
-
-## Workflow:
-
-### 1. Service Detection
-Parse "{{args}}" to identify:
-- Service name
-- Features needed
-- Current stack (check package.json)
-
-### 2. Supported Services
-
-#### 💳 Payments
-| Service | Features |
-|---------|----------|
-| **stripe** | Checkout, subscriptions, webhooks |
-| **polar** | Open-source subscriptions |
-| **sepay** | Vietnam payments |
-| **paypal** | Global payments |
-
-#### 🔐 Authentication
-| Service | Features |
-|---------|----------|
-| **supabase** | Auth, database, realtime |
-| **firebase** | Auth, Firestore, Functions |
-| **auth0** | SSO, MFA, social login |
-| **clerk** | User management, components |
-
-#### 📧 Communication
-| Service | Features |
-|---------|----------|
-| **resend** | Transactional emails |
-| **twilio** | SMS, voice |
-| **nodemailer** | SMTP emails |
-
-#### 🗄️ Database
-| Service | Features |
-|---------|----------|
-| **prisma** | ORM, migrations |
-| **drizzle** | TypeScript ORM |
-| **mongoose** | MongoDB ODM |
-
-### 3. Implementation
-
-1. **Install** packages
-2. **Configure** env vars
-3. **Create** client/service file
-4. **Add** API routes/webhooks
-5. **Build** UI components
-6. **Test** integration
-7. **Document** setup
-
-### 4. Output Format
-
-```markdown
-## Integration: [Service]
-
-### Install
-npm install [packages]
-
-### Environment Variables
-SERVICE_KEY=xxx
-
-### Files Created
-- src/lib/[service].ts
-- src/routes/api/[service]/
-
-### Usage
-[code example]
-```
-
----
-
-Implement: {{args}}
-{{else}}
-# 🔌 Integration Helper
-
-Integrate external services with AI assistance.
-
-## Usage:
-```
-/integrate <service> [requirements]
-```
-
-## Categories:
-
-### 💳 Payments
-- `/integrate stripe subscriptions`
-- `/integrate polar billing`
-- `/integrate sepay vn payments`
-
-### 🔐 Auth
-- `/integrate supabase auth`
-- `/integrate clerk users`
-- `/integrate auth0 sso`
-
-### 📧 Email/SMS
-- `/integrate resend emails`
-- `/integrate twilio sms`
-
-### 🗄️ Database
-- `/integrate prisma postgres`
-- `/integrate drizzle orm`
-
-## Example:
-```
-/integrate stripe Add checkout and subscriptions
-/integrate supabase Add auth with Google OAuth
-```
-
-What service do you want to integrate?
-{{/if}}
-"""
+# Integrate - External Service Integrations
+# Usage: /integrate <service> [requirements]
+# Supports: payments, auth, database, email, SMS
+
+description = "Integration with external services"
+
+
+
+prompt = """
+{{#if args}}
+# 🔌 Integration Engineer
+
+You are an expert at integrating third-party services.
+
+**Request:** {{args}}
+
+## Workflow:
+
+### 1. Service Detection
+Parse "{{args}}" to identify:
+- Service name
+- Features needed
+- Current stack (check package.json)
+
+### 2. Supported Services
+
+#### 💳 Payments
+| Service | Features |
+|---------|----------|
+| **stripe** | Checkout, subscriptions, webhooks |
+| **polar** | Open-source subscriptions |
+| **sepay** | Vietnam payments |
+| **paypal** | Global payments |
+
+#### 🔐 Authentication
+| Service | Features |
+|---------|----------|
+| **supabase** | Auth, database, realtime |
+| **firebase** | Auth, Firestore, Functions |
+| **auth0** | SSO, MFA, social login |
+| **clerk** | User management, components |
+
+#### 📧 Communication
+| Service | Features |
+|---------|----------|
+| **resend** | Transactional emails |
+| **twilio** | SMS, voice |
+| **nodemailer** | SMTP emails |
+
+#### 🗄️ Database
+| Service | Features |
+|---------|----------|
+| **prisma** | ORM, migrations |
+| **drizzle** | TypeScript ORM |
+| **mongoose** | MongoDB ODM |
+
+### 3. Implementation
+
+1. **Install** packages
+2. **Configure** env vars
+3. **Create** client/service file
+4. **Add** API routes/webhooks
+5. **Build** UI components
+6. **Test** integration
+7. **Document** setup
+
+### 4. Output Format
+
+```markdown
+## Integration: [Service]
+
+### Install
+npm install [packages]
+
+### Environment Variables
+SERVICE_KEY=xxx
+
+### Files Created
+- src/lib/[service].ts
+- src/routes/api/[service]/
+
+### Usage
+[code example]
+```
+
+---
+
+Implement: {{args}}
+{{else}}
+# 🔌 Integration Helper
+
+Integrate external services with AI assistance.
+
+## Usage:
+```
+/integrate <service> [requirements]
+```
+
+## Categories:
+
+### 💳 Payments
+- `/integrate stripe subscriptions`
+- `/integrate polar billing`
+- `/integrate sepay vn payments`
+
+### 🔐 Auth
+- `/integrate supabase auth`
+- `/integrate clerk users`
+- `/integrate auth0 sso`
+
+### 📧 Email/SMS
+- `/integrate resend emails`
+- `/integrate twilio sms`
+
+### 🗄️ Database
+- `/integrate prisma postgres`
+- `/integrate drizzle orm`
+
+## Example:
+```
+/integrate stripe Add checkout and subscriptions
+/integrate supabase Add auth with Google OAuth
+```
+
+What service do you want to integrate?
+{{/if}}
+"""

package/commands/journal.toml

@@ -1,137 +1,137 @@
-description = "Journal entry or incident report with institutional knowledge (Journal Writer Agent)"
-
-prompt = """
-# 📓 JOURNAL WRITER AGENT
-
-Write documentation for:
-
-**Context:** {{args}}
-
-## MODE DETECTION
-Based on context, select appropriate mode:
-
-### PROGRESS JOURNAL (default)
-When tracking daily/weekly progress.
-
-### INCIDENT REPORT
-When keywords: "bug", "outage", "down", "crash", "failed", "error", "incident" are present.
-
----
-
-## PROGRESS JOURNAL MODE
-
-### Entry: [Date]
-
-#### What Was Done
-- [Accomplishment 1]
-- [Accomplishment 2]
-
-#### Challenges Encountered
-- [Challenge] → [How solved]
-
-#### Lessons Learned
-- [Key takeaway]
-
-#### Next Steps
-- [ ] [Action item 1]
-- [ ] [Action item 2]
-
----
-
-## INCIDENT REPORT MODE
-
-### 🚨 Incident Report: [Title]
-**Date:** [YYYY-MM-DD HH:MM]
-**Severity:** Critical / High / Medium / Low
-**Duration:** [X hours/minutes]
-**Tags:** #incident #[system] #[type]
-
-#### Timeline
-| Time | Event | Emotion |
-|------|-------|---------|
-| HH:MM | [Initial symptom] | 😱 Panic |
-| HH:MM | [Investigation started] | 🔍 Focus |
-| HH:MM | [Root cause identified] | 💡 Aha! |
-| HH:MM | [Fix deployed] | 🤞 Hope |
-| HH:MM | [Resolution confirmed] | 😮‍💨 Relief |
-
-#### Root Cause
-[Technical explanation of what went wrong]
-
-#### Failed Attempts
-1. [Attempt 1] - Why it didn't work
-2. [Attempt 2] - Why it didn't work
-3. [Attempt 3] - Why it didn't work
-
-(Learning comes from what DIDN'T work!)
-
-#### Final Fix
-```[language]
-// The fix that worked
-```
-
-#### Impact (Be Specific!)
-| Metric | Value |
-|--------|-------|
-| Downtime | X hours |
-| Users affected | Y users |
-| Revenue impact | $X estimated |
-| Support tickets | Z tickets |
-| Data loss | Yes/No |
-
-#### Cost Breakdown
-```
-Revenue lost:     $X
-Engineering time: $Y (Z hours × $rate)
-Support costs:    $W
-Total impact:     $TOTAL
-```
-
-#### Why Monitoring Didn't Catch It
-[Explain gap - this prevents future incidents!]
-
-#### Preventive Measures
-- [ ] [Action 1 to prevent recurrence]
-- [ ] [Action 2 to prevent recurrence]
-- [ ] [New monitoring/alerting]
-
-#### Lessons Learned
-⚠️ **Key Takeaways:**
-1. [Lesson 1]
-2. [Lesson 2]
-3. [Systemic cause, not individual blame]
-
-#### Related Files
-- [File 1 that was modified]
-- [File 2 that was modified]
-
----
-
-## 💡 PRO TIPS
-
-1. **Write immediately** - Emotional context fades fast
-2. **Include failed attempts** - Learning = what didn't work
-3. **Use real language** - "We screwed up" not "encountered issue"
-4. **Show numbers** - $cost, time, impact metrics
-5. **Add code snippets** - Error logs, broken → fixed
-6. **Make searchable** - Use #tags for future lookup
-7. **Blame the system** - Focus on process failures
-
----
-
-## OUTPUT
-Structured markdown, thorough but concise.
-Blame the system, not individuals.
-Include code snippets where relevant.
-Make it searchable with tags.
-
-> **Key Takeaway:** Transform expensive failures into permanent institutional knowledge. Learn once, don't fail repeatedly.
-"""
-
-# ---
-# USAGE:
-# /journal What I accomplished today on the auth feature
-# /journal Found race condition in payment 2hrs before release
-# /journal Production DB outage for 6 hours
-# /journal Weekly status update for team
+description = "Journal entry or incident report with institutional knowledge (Journal Writer Agent)"
+
+prompt = """
+# 📓 JOURNAL WRITER AGENT
+
+Write documentation for:
+
+**Context:** {{args}}
+
+## MODE DETECTION
+Based on context, select appropriate mode:
+
+### PROGRESS JOURNAL (default)
+When tracking daily/weekly progress.
+
+### INCIDENT REPORT
+When keywords: "bug", "outage", "down", "crash", "failed", "error", "incident" are present.
+
+---
+
+## PROGRESS JOURNAL MODE
+
+### Entry: [Date]
+
+#### What Was Done
+- [Accomplishment 1]
+- [Accomplishment 2]
+
+#### Challenges Encountered
+- [Challenge] → [How solved]
+
+#### Lessons Learned
+- [Key takeaway]
+
+#### Next Steps
+- [ ] [Action item 1]
+- [ ] [Action item 2]
+
+---
+
+## INCIDENT REPORT MODE
+
+### 🚨 Incident Report: [Title]
+**Date:** [YYYY-MM-DD HH:MM]
+**Severity:** Critical / High / Medium / Low
+**Duration:** [X hours/minutes]
+**Tags:** #incident #[system] #[type]
+
+#### Timeline
+| Time | Event | Emotion |
+|------|-------|---------|
+| HH:MM | [Initial symptom] | 😱 Panic |
+| HH:MM | [Investigation started] | 🔍 Focus |
+| HH:MM | [Root cause identified] | 💡 Aha! |
+| HH:MM | [Fix deployed] | 🤞 Hope |
+| HH:MM | [Resolution confirmed] | 😮‍💨 Relief |
+
+#### Root Cause
+[Technical explanation of what went wrong]
+
+#### Failed Attempts
+1. [Attempt 1] - Why it didn't work
+2. [Attempt 2] - Why it didn't work
+3. [Attempt 3] - Why it didn't work
+
+(Learning comes from what DIDN'T work!)
+
+#### Final Fix
+```[language]
+// The fix that worked
+```
+
+#### Impact (Be Specific!)
+| Metric | Value |
+|--------|-------|
+| Downtime | X hours |
+| Users affected | Y users |
+| Revenue impact | $X estimated |
+| Support tickets | Z tickets |
+| Data loss | Yes/No |
+
+#### Cost Breakdown
+```
+Revenue lost:     $X
+Engineering time: $Y (Z hours × $rate)
+Support costs:    $W
+Total impact:     $TOTAL
+```
+
+#### Why Monitoring Didn't Catch It
+[Explain gap - this prevents future incidents!]
+
+#### Preventive Measures
+- [ ] [Action 1 to prevent recurrence]
+- [ ] [Action 2 to prevent recurrence]
+- [ ] [New monitoring/alerting]
+
+#### Lessons Learned
+⚠️ **Key Takeaways:**
+1. [Lesson 1]
+2. [Lesson 2]
+3. [Systemic cause, not individual blame]
+
+#### Related Files
+- [File 1 that was modified]
+- [File 2 that was modified]
+
+---
+
+## 💡 PRO TIPS
+
+1. **Write immediately** - Emotional context fades fast
+2. **Include failed attempts** - Learning = what didn't work
+3. **Use real language** - "We screwed up" not "encountered issue"
+4. **Show numbers** - $cost, time, impact metrics
+5. **Add code snippets** - Error logs, broken → fixed
+6. **Make searchable** - Use #tags for future lookup
+7. **Blame the system** - Focus on process failures
+
+---
+
+## OUTPUT
+Structured markdown, thorough but concise.
+Blame the system, not individuals.
+Include code snippets where relevant.
+Make it searchable with tags.
+
+> **Key Takeaway:** Transform expensive failures into permanent institutional knowledge. Learn once, don't fail repeatedly.
+"""
+
+# ---
+# USAGE:
+# /journal What I accomplished today on the auth feature
+# /journal Found race condition in payment 2hrs before release
+# /journal Production DB outage for 6 hours
+# /journal Weekly status update for team
 # ---

package/commands/kit-setup.toml

@@ -1,41 +1,41 @@
-description = "Interactive project setup wizard - create context files for new projects"
-
-prompt = """
-# 🚀 Kit Setup Wizard
-
-Hello! This is the wizard to setup project context for Gemini-Kit.
-
-## I will help you create 3 context files:
-
-1. **product.md** - Product description, users, goals
-2. **tech-stack.md** - Language, framework, database
-3. **guidelines.md** - Code style, commit conventions
-
----
-
-## Step 1: Product Context
-
-Please tell me about your project:
-
-**Questions:**
-1. What are you building? (One-line description)
-2. Who are the primary users? (Developers, End users, Enterprises, etc.)
-3. What is the main goal of the product?
-4. What are the main features?
-
----
-
-When you finish answering, I will:
-1. Create file `.gemini-kit/product.md`
-2. Continue asking about Tech Stack
-3. Continue asking about Guidelines
-4. Complete setup!
-
-**You can answer freely or following the format:**
-```
-Product: [description]
-Users: [who uses it]
-Goals: [goals]
-Features: [main features]
-```
+description = "Interactive project setup wizard - create context files for new projects"
+
+prompt = """
+# 🚀 Kit Setup Wizard
+
+Hello! This is the wizard to setup project context for Gemini-Kit.
+
+## I will help you create 3 context files:
+
+1. **product.md** - Product description, users, goals
+2. **tech-stack.md** - Language, framework, database
+3. **guidelines.md** - Code style, commit conventions
+
+---
+
+## Step 1: Product Context
+
+Please tell me about your project:
+
+**Questions:**
+1. What are you building? (One-line description)
+2. Who are the primary users? (Developers, End users, Enterprises, etc.)
+3. What is the main goal of the product?
+4. What are the main features?
+
+---
+
+When you finish answering, I will:
+1. Create file `.gemini-kit/product.md`
+2. Continue asking about Tech Stack
+3. Continue asking about Guidelines
+4. Complete setup!
+
+**You can answer freely or following the format:**
+```
+Product: [description]
+Users: [who uses it]
+Goals: [goals]
+Features: [main features]
+```
 """