superkit-mcp-server 1.1.4 → 1.2.0

package/skills/meta/compound-docs/SKILL.md

@@ -1,133 +1,133 @@
----
-name: compound-docs
-description: Document solved problems for knowledge persistence
----
-
-# Compound Documentation Skill
-
-Manages solution documentation in `docs/solutions/` for knowledge persistence across sessions.
-
-## Overview
-
-When you solve a problem, document it so the solution can be found and reused later.
-
-## What do you want to do?
-
-1. **Document a solution** → Use `/compound` workflow
-2. **Find existing solutions** → See "Searching Solutions" below
-3. **Promote to pattern** → See "Pattern Promotion" below
-4. **Validate schema** → See "YAML Validation" below
-
----
-
-## Instrumentation
-
-```bash
-# Log usage when using this skill
-Call MCP `call_tool_logger_manager` { action: "logSkill", name: "compound-docs", outcome: "manual" }
-```
-
-## Searching Solutions
-
-```bash
-# Search by keyword
-grep -r "keyword" docs/solutions/
-
-# Search by tag
-grep -l "tags:.*performance" docs/solutions/**/*.md
-
-# Search by problem type
-ls docs/solutions/performance-issues/
-```
-
-## Pattern Promotion
-
-When an issue occurs 3+ times:
-
-1. Search for similar solutions:
-   ```bash
-   grep -r "similar terms" docs/solutions/
-   ```
-
-2. Add to critical patterns:
-   ```bash
-   # Edit docs/solutions/patterns/critical-patterns.md
-   ```
-
-3. Format:
-   ```markdown
-   ### Pattern #{N}: {Name}
-   
-   **Problem:** {What goes wrong}
-   
-   **❌ WRONG:**
-   ```code
-   {incorrect}
-   ```
-   
-   **✅ CORRECT:**
-   ```code
-   {correct}
-   ```
-   ```
-
-## YAML Validation
-
-All solutions must have valid frontmatter:
-
-```yaml
----
-date: "YYYY-MM-DD"
-problem_type: "{from schema.yaml}"
-severity: "critical|high|medium|low"
-symptoms:
-  - "symptom 1"
-root_cause: "{from schema.yaml}"
-tags:
-  - tag1
----
-```
-
-See `docs/solutions/schema.yaml` for valid enum values.
-
-## Documenting Failures & Learnings
-
-When documenting solutions, capture the full journey:
-
-### What to Include
-- ✅ Failed attempts with explanations
-- ✅ Incorrect assumptions and corrections
-- ✅ Key insights from mistakes
-- ✅ Course corrections and why
-- ✅ Time investment (helps prioritize future similar issues)
-
-### Example Pattern
-```markdown
-## Investigation Steps
-
-| Attempt | Hypothesis | Result |
-|---------|------------|--------|
-| 1. Check API logs | API might be timing out | ❌ No timeouts found |
-| 2. Review database queries | N+1 query suspected | ❌ Queries were optimized |
-| 3. Check cache invalidation | Cache might be stale | ✅ Found cache not clearing |
-
-## Lessons Learned
-
-### Mistakes Made
-- **Assumption:** Assumed the API was the bottleneck
-  - **Why wrong:** Didn't check cache layer first
-  - **Correction:** Should always check cache before API
-
-### Key Breakthrough
-- **Insight:** Realized cache invalidation logic was only running on UPDATE, not DELETE
-  - **Impact:** Led directly to the solution
-```
-
-> [!TIP]
-> **Document the journey, not just the destination.** Future readers learn from understanding WHY failed approaches didn't work.
-
-## References
-
-- Schema: `docs/solutions/schema.yaml`
-- Template: `docs/solutions/templates/solution-template.md`
-- Patterns: `docs/solutions/patterns/critical-patterns.md`
+---
+name: compound-docs
+description: Document solved problems for knowledge persistence
+---
+
+# Compound Documentation Skill
+
+Manages solution documentation in `docs/solutions/` for knowledge persistence across sessions.
+
+## Overview
+
+When you solve a problem, document it so the solution can be found and reused later.
+
+## What do you want to do?
+
+1. **Document a solution** → Use `/compound` workflow
+2. **Find existing solutions** → See "Searching Solutions" below
+3. **Promote to pattern** → See "Pattern Promotion" below
+4. **Validate schema** → See "YAML Validation" below
+
+---
+
+## Instrumentation
+
+```bash
+# Log usage when using this skill
+Call MCP `call_tool_logger_manager` { action: "logSkill", name: "compound-docs", outcome: "manual" }
+```
+
+## Searching Solutions
+
+```bash
+# Search by keyword
+grep -r "keyword" docs/solutions/
+
+# Search by tag
+grep -l "tags:.*performance" docs/solutions/**/*.md
+
+# Search by problem type
+ls docs/solutions/performance-issues/
+```
+
+## Pattern Promotion
+
+When an issue occurs 3+ times:
+
+1. Search for similar solutions:
+   ```bash
+   grep -r "similar terms" docs/solutions/
+   ```
+
+2. Add to critical patterns:
+   ```bash
+   # Edit docs/solutions/patterns/critical-patterns.md
+   ```
+
+3. Format:
+   ```markdown
+   ### Pattern #{N}: {Name}
+   
+   **Problem:** {What goes wrong}
+   
+   **❌ WRONG:**
+   ```code
+   {incorrect}
+   ```
+   
+   **✅ CORRECT:**
+   ```code
+   {correct}
+   ```
+   ```
+
+## YAML Validation
+
+All solutions must have valid frontmatter:
+
+```yaml
+---
+date: "YYYY-MM-DD"
+problem_type: "{from schema.yaml}"
+severity: "critical|high|medium|low"
+symptoms:
+  - "symptom 1"
+root_cause: "{from schema.yaml}"
+tags:
+  - tag1
+---
+```
+
+See `docs/solutions/schema.yaml` for valid enum values.
+
+## Documenting Failures & Learnings
+
+When documenting solutions, capture the full journey:
+
+### What to Include
+- ✅ Failed attempts with explanations
+- ✅ Incorrect assumptions and corrections
+- ✅ Key insights from mistakes
+- ✅ Course corrections and why
+- ✅ Time investment (helps prioritize future similar issues)
+
+### Example Pattern
+```markdown
+## Investigation Steps
+
+| Attempt | Hypothesis | Result |
+|---------|------------|--------|
+| 1. Check API logs | API might be timing out | ❌ No timeouts found |
+| 2. Review database queries | N+1 query suspected | ❌ Queries were optimized |
+| 3. Check cache invalidation | Cache might be stale | ✅ Found cache not clearing |
+
+## Lessons Learned
+
+### Mistakes Made
+- **Assumption:** Assumed the API was the bottleneck
+  - **Why wrong:** Didn't check cache layer first
+  - **Correction:** Should always check cache before API
+
+### Key Breakthrough
+- **Insight:** Realized cache invalidation logic was only running on UPDATE, not DELETE
+  - **Impact:** Led directly to the solution
+```
+
+> [!TIP]
+> **Document the journey, not just the destination.** Future readers learn from understanding WHY failed approaches didn't work.
+
+## References
+
+- Schema: `docs/solutions/schema.yaml`
+- Template: `docs/solutions/templates/solution-template.md`
+- Patterns: `docs/solutions/patterns/critical-patterns.md`

package/skills/meta/debug/SKILL.md

@@ -1,40 +1,40 @@
----
-name: debug
-description: Systematic debugging with structured reproduction and root cause analysis.
-last_updated: 2025-12-20
----
-
-# Debug Skill
-
-## Overview
-
-Don't guess; verify. This skill guides you through the systematic process of identifying, reproducing, and fixing bugs.
-
-## When To Use
-
-- **Users report a bug**
-- **You encounter an unexpected error**
-- **Tests are failing inexplicably**
-
-## Instrumentation
-
-```bash
-# Log usage when using this skill
-Call MCP `call_tool_logger_manager` { action: "logSkill", name: "debug", outcome: "manual" }
-```
-
-## What do you want to do?
-
-1. **Reproduce an issue** → `workflows/reproduce-issue.md`
-2. **Find Root Cause** → `workflows/root-cause-analysis.md`
-3. **Create Bug Report** → `templates/bug-report.template.md`
-4. **Research Error Messages** → `references/common-errors.md`
-
-## The Golden Rule of Debugging
-
-> **"If you haven't reproduced it, you haven't fixed it."**
-
-Always implement a reproduction case (test or script) BEFORE attempting a fix. Highly recommended to use the template at `docs/templates/repro-script-template.sh` and store artifacts in `scripts/repro/`.
-
-> [!NOTE]
-> No top-level `debug/` folder exists. Use `skills/debug/` for guidance and `scripts/repro/` for artifacts.
+---
+name: debug
+description: Systematic debugging with structured reproduction and root cause analysis.
+last_updated: 2025-12-20
+---
+
+# Debug Skill
+
+## Overview
+
+Don't guess; verify. This skill guides you through the systematic process of identifying, reproducing, and fixing bugs.
+
+## When To Use
+
+- **Users report a bug**
+- **You encounter an unexpected error**
+- **Tests are failing inexplicably**
+
+## Instrumentation
+
+```bash
+# Log usage when using this skill
+Call MCP `call_tool_logger_manager` { action: "logSkill", name: "debug", outcome: "manual" }
+```
+
+## What do you want to do?
+
+1. **Reproduce an issue** → `workflows/reproduce-issue.md`
+2. **Find Root Cause** → `workflows/root-cause-analysis.md`
+3. **Create Bug Report** → `templates/bug-report.template.md`
+4. **Research Error Messages** → `references/common-errors.md`
+
+## The Golden Rule of Debugging
+
+> **"If you haven't reproduced it, you haven't fixed it."**
+
+Always implement a reproduction case (test or script) BEFORE attempting a fix. Highly recommended to use the template at `docs/templates/repro-script-template.sh` and store artifacts in `scripts/repro/`.
+
+> [!NOTE]
+> No top-level `debug/` folder exists. Use `skills/debug/` for guidance and `scripts/repro/` for artifacts.

package/skills/meta/debug/templates/bug-report.template.md

@@ -1,31 +1,31 @@
-# Bug Report: {Short Description}
-
-## Overview
-- **Impact**: {High/Medium/Low}
-- **Frequency**: {Always/Intermittent/Once}
-- **Component**: {Part of the system}
-
-## Reproduction Steps
-1. Navigate to '...'
-2. Click on '...'
-3. See error '...'
-
-## Expected Behavior
-{What should happen?}
-
-## Actual Behavior
-{What actually happens?}
-
-## Environment
-- **Browser**: {e.g. Chrome 120}
-- **OS**: {e.g. macOS Sonoma}
-- **User Role**: {e.g. Admin/User}
-
-## Logs / Errors
-```
-{Paste logs here}
-```
-
-## Possible Root Cause
-- {Hypothesis 1}
-- {Hypothesis 2}
+# Bug Report: {Short Description}
+
+## Overview
+- **Impact**: {High/Medium/Low}
+- **Frequency**: {Always/Intermittent/Once}
+- **Component**: {Part of the system}
+
+## Reproduction Steps
+1. Navigate to '...'
+2. Click on '...'
+3. See error '...'
+
+## Expected Behavior
+{What should happen?}
+
+## Actual Behavior
+{What actually happens?}
+
+## Environment
+- **Browser**: {e.g. Chrome 120}
+- **OS**: {e.g. macOS Sonoma}
+- **User Role**: {e.g. Admin/User}
+
+## Logs / Errors
+```
+{Paste logs here}
+```
+
+## Possible Root Cause
+- {Hypothesis 1}
+- {Hypothesis 2}

package/skills/meta/debug/workflows/reproduce-issue.md

@@ -1,20 +1,20 @@
-# Reproduction Workflow
-
-## 1. Isolate the Variable
-- Can you reproduce it in a different browser?
-- Can you reproduce it with a different user?
-- Can you reproduce it locally vs prod?
-
-## 2. Create Minimal Reproduction
-Try to strip away all unnecessary complexity.
-
-**Frontend:**
-- Create a test case in a relevant `.test.tsx` file that mimics the user interaction.
-
-**Backend:**
-- Create a script in `scripts/repro/` that triggers the API call.
-
-## 3. Scripts
-Use these scripts to help:
-- `./scripts/push-env.sh` (Sync environment variables)
-- `npm run test` (Run unit tests)
+# Reproduction Workflow
+
+## 1. Isolate the Variable
+- Can you reproduce it in a different browser?
+- Can you reproduce it with a different user?
+- Can you reproduce it locally vs prod?
+
+## 2. Create Minimal Reproduction
+Try to strip away all unnecessary complexity.
+
+**Frontend:**
+- Create a test case in a relevant `.test.tsx` file that mimics the user interaction.
+
+**Backend:**
+- Create a script in `scripts/repro/` that triggers the API call.
+
+## 3. Scripts
+Use these scripts to help:
+- `./scripts/push-env.sh` (Sync environment variables)
+- `npm run test` (Run unit tests)