superkit-mcp-server 1.2.4 → 1.2.5

package/skills/workflows/promote_pattern.md

@@ -1,86 +1,86 @@
----
-description: Promote a recurring issue to a critical pattern.
----
-
-# /promote_pattern - Pattern Promotion
-
-Use this workflow when you have a **Pattern Promotion Todo** (ready-p2-promote-pattern).
-Goal: Synthesize individual solutions into a reusable engineering pattern.
-
-## Workflow
-
-### Step 0: Search & Log
-
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/promote_pattern", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "design pattern"] }
-```
-
-### Step 1: Analyze Sources
-
-Read the solutions referenced in the todo.
-Identify:
-1. What context do they share?
-2. What was the common root cause?
-3. What is the fundamental principle violated?
-
-### Step 2: Synthesize Pattern
-
-You must strictly follow this template.
-
-**Pattern Template:**
-
-1.  **Name**: (Concept Name, e.g., "Single Source of Truth")
-2.  **Context**: (When does this apply? e.g., "When defining constants...")
-3.  **Problem**: (What goes wrong? e.g., "Values drift across files...")
-4.  **Forces**: (Why is this hard? e.g., "Convenience vs Maintenance...")
-5.  **Solution**: (The Rule)
-    *   ❌ **Anti-Pattern**: (Code example of what NOT to do)
-    *   ✅ **Best Practice**: (Code example of what TO do)
-6.  **Consequences**: (Trade-offs)
-
-### Step 3: Update Knowledge Base
-
-1.  Open `docs/solutions/patterns/critical-patterns.md` (or create domain specific file)
-2.  Append the synthesized pattern.
-3.  Add it to the Table of Contents.
-
-### Step 4: Link Back
-
-For each source solution:
-1.  Open the solution file.
-2.  Add a link to the new pattern under "Related Solutions" or "Long-term Prevention".
-
-### Step 5: Close Todo
-
-Move the promotion todo to `todos/archive/` or delete it.
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Pattern Promotion",
-  TaskStatus: "Pattern synthesized and documented. Offering next steps.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Promoted pattern: {Pattern Name}. Updated critical-patterns.md and linked back to source solutions."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ Pattern promoted
-
-Next steps:
-1. /housekeeping - Archive used todos
-2. /compound_health - Check pattern coverage
-```
-
----
-
-## References
-
-- [Critical Patterns](../../docs/solutions/patterns/critical-patterns.md)
+---
+description: Promote a recurring issue to a critical pattern.
+---
+
+# /promote_pattern - Pattern Promotion
+
+Use this workflow when you have a **Pattern Promotion Todo** (ready-p2-promote-pattern).
+Goal: Synthesize individual solutions into a reusable engineering pattern.
+
+## Workflow
+
+### Step 0: Search & Log
+
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/promote_pattern", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "design pattern"] }
+```
+
+### Step 1: Analyze Sources
+
+Read the solutions referenced in the todo.
+Identify:
+1. What context do they share?
+2. What was the common root cause?
+3. What is the fundamental principle violated?
+
+### Step 2: Synthesize Pattern
+
+You must strictly follow this template.
+
+**Pattern Template:**
+
+1.  **Name**: (Concept Name, e.g., "Single Source of Truth")
+2.  **Context**: (When does this apply? e.g., "When defining constants...")
+3.  **Problem**: (What goes wrong? e.g., "Values drift across files...")
+4.  **Forces**: (Why is this hard? e.g., "Convenience vs Maintenance...")
+5.  **Solution**: (The Rule)
+    *   ❌ **Anti-Pattern**: (Code example of what NOT to do)
+    *   ✅ **Best Practice**: (Code example of what TO do)
+6.  **Consequences**: (Trade-offs)
+
+### Step 3: Update Knowledge Base
+
+1.  Open `docs/solutions/patterns/critical-patterns.md` (or create domain specific file)
+2.  Append the synthesized pattern.
+3.  Add it to the Table of Contents.
+
+### Step 4: Link Back
+
+For each source solution:
+1.  Open the solution file.
+2.  Add a link to the new pattern under "Related Solutions" or "Long-term Prevention".
+
+### Step 5: Close Todo
+
+Move the promotion todo to `todos/archive/` or delete it.
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Pattern Promotion",
+  TaskStatus: "Pattern synthesized and documented. Offering next steps.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Promoted pattern: {Pattern Name}. Updated critical-patterns.md and linked back to source solutions."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ Pattern promoted
+
+Next steps:
+1. /housekeeping - Archive used todos
+2. /compound_health - Check pattern coverage
+```
+
+---
+
+## References
+
+- [Critical Patterns](../../docs/solutions/patterns/critical-patterns.md)

package/skills/workflows/release-docs.md

@@ -1,82 +1,82 @@
----
-description: Prepare release documentation. Use before publishing new versions.
----
-
-# /release-docs - Release Documentation
-
-Prepare documentation for a new release.
-
-## Workflow
-
-### Step 0: Search & Log
-
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/release-docs", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "release notes"] }
-```
-
-### Step 1: Update Version
-
-Update version numbers in:
-- [ ] package.json / pyproject.toml
-- [ ] README.md badges
-- [ ] Documentation config
-
-### Step 2: Generate Changelog
-
-Run `npm run changelog:gen` to generate release notes.
-
-### Step 3: Update Documentation
-
-- [ ] Update getting started guide if APIs changed
-- [ ] Add migration guide for breaking changes
-- [ ] Update API reference
-- [ ] Add examples for new features
-
-### Step 4: Review Documentation
-
-```bash
-# Build and preview
-npm run docs:build
-npm run docs:serve
-```
-
-Check:
-- [ ] All code examples work
-- [ ] Links not broken
-- [ ] Screenshots current
-
-### Step 5: Tag Release
-
-```bash
-git tag -a v{X.Y.Z} -m "Release {X.Y.Z}"
-git push origin v{X.Y.Z}
-```
-
-### Step 6: Deploy Docs
-
-Run `/deploy-docs` to publish.
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Release Docs",
-  TaskStatus: "Docs released and deployed. Offering next steps.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Released documentation for v{X.Y.Z}. Generated changelog, updated versions, deployment triggered."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ Docs released
-
-Next steps:
-1. /housekeeping - Cleanup artifacts
-2. Notify Team - Announce the release
-```
+---
+description: Prepare release documentation. Use before publishing new versions.
+---
+
+# /release-docs - Release Documentation
+
+Prepare documentation for a new release.
+
+## Workflow
+
+### Step 0: Search & Log
+
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/release-docs", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "release notes"] }
+```
+
+### Step 1: Update Version
+
+Update version numbers in:
+- [ ] package.json / pyproject.toml
+- [ ] README.md badges
+- [ ] Documentation config
+
+### Step 2: Generate Changelog
+
+Run `npm run changelog:gen` to generate release notes.
+
+### Step 3: Update Documentation
+
+- [ ] Update getting started guide if APIs changed
+- [ ] Add migration guide for breaking changes
+- [ ] Update API reference
+- [ ] Add examples for new features
+
+### Step 4: Review Documentation
+
+```bash
+# Build and preview
+npm run docs:build
+npm run docs:serve
+```
+
+Check:
+- [ ] All code examples work
+- [ ] Links not broken
+- [ ] Screenshots current
+
+### Step 5: Tag Release
+
+```bash
+git tag -a v{X.Y.Z} -m "Release {X.Y.Z}"
+git push origin v{X.Y.Z}
+```
+
+### Step 6: Deploy Docs
+
+Run `/deploy-docs` to publish.
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Release Docs",
+  TaskStatus: "Docs released and deployed. Offering next steps.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Released documentation for v{X.Y.Z}. Generated changelog, updated versions, deployment triggered."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ Docs released
+
+Next steps:
+1. /housekeeping - Cleanup artifacts
+2. Notify Team - Announce the release
+```

package/skills/workflows/report-bug.md

@@ -1,135 +1,135 @@
----
-description: Report bugs with structured reproduction steps. Use when you find a bug that needs tracking.
----
-
-# /report-bug - Structured Bug Reporting
-
-Create detailed bug reports with reproduction steps.
-
-## Workflow
-
-### Step 0: Search Existing Bugs (MANDATORY)
-
-> [!CAUTION]
-> **BLOCKING STEP.** Before reporting a new bug, verify it hasn't already been solved or reported.
-
-**Run the auto-searcher:**
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/report-bug", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "{keyword1}" "{keyword2}"] }
-```
-
-**See also:** `skills/compound-docs/SKILL.md` for advanced searching and checking if similar bugs are already reported.
-
-**If relevant solutions or bug reports found:**
-1. Do NOT file a duplicate report.
-2. Add your new findings (logs, screenshots) to the existing issue if it's still open.
-3. Use `/reproduce-bug` if you can provide a more consistent reproduction for an existing issue.
-4. Execute the update command to track usage if it's a solved problem:
-   ```bash
-   // turbo
-   Call MCP `call_tool_compound_manager` { action: "updateRef", files: ["{paths from search output}"] }
-   ```
-
----
-
-### Step 1: Gather Information and Reproduce
-
-> [!TIP]
-> Use the **debug skill** for structured reproduction workflows.
-
-```bash
-cat skills/debug/SKILL.md
-Call MCP `call_tool_logger_manager` { action: "logSkill", name: "debug", outcome: "workflow" }
-```
-
-- [ ] **What happened:** Observable behavior
-- [ ] **What was expected:** Intended behavior
-- [ ] **How to reproduce:** Step-by-step instructions
-- [ ] **Environment:** OS, browser, versions
-
-### Step 2: Create Bug Report
-
-```markdown
-# Bug: {Brief Description}
-
-## Summary
-{One-line description}
-
-## Environment
-- OS: {operating system}
-- Browser/Runtime: {details}
-- Version: {app version}
-
-## Steps to Reproduce
-1. {Step 1}
-2. {Step 2}
-3. {Step 3}
-
-## Expected Behavior
-{What should happen}
-
-## Actual Behavior
-{What actually happened}
-
-## Screenshots/Logs
-{Attach if applicable}
-
-## Possible Cause
-{Initial hypothesis if any}
-
-## Workaround
-{Temporary fix if known}
-```
-
-### Step 3: File the Report
-
-```bash
-# Create issue
-gh issue create --title "Bug: {description}" --body "$(cat bug-report.md)"
-```
-
-### Step 4: Create Local Todo (MANDATORY)
-
-> [!IMPORTANT]
-> **Do not skip.** GitHub issues can be forgotten. Create a local tracking item.
-
-```bash
-# Create local todo
-Call MCP `call_tool_todo_manager` { action: "create", priority: "p1", title: "Fix: {Bug Title}", description: "TODO description" }
-  "External Tracking: GitHub Issue #{issue_number}.\n\nBug Description:\n(Brief description here)" \
-  "Fix the bug reported in issue #{issue_number}" \
-  "Add regression test"
-```
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Report Bug",
-  TaskStatus: "Bug reported and tracked. Offering next steps.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Reported bug: {Bug Title}. Github Issue #{number}. Local Todo created."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ Bug reported: #{issue_number}
-
-Next steps:
-1. /plan - Create plan to fix the bug
-2. /reproduce-bug - If reproduction steps need refinement
-3. /housekeeping - Cleanup
-```
-
----
-
-## References
-
-- Reproduce bugs: `/reproduce-bug`
-- Plan fix: `/plan`
+---
+description: Report bugs with structured reproduction steps. Use when you find a bug that needs tracking.
+---
+
+# /report-bug - Structured Bug Reporting
+
+Create detailed bug reports with reproduction steps.
+
+## Workflow
+
+### Step 0: Search Existing Bugs (MANDATORY)
+
+> [!CAUTION]
+> **BLOCKING STEP.** Before reporting a new bug, verify it hasn't already been solved or reported.
+
+**Run the auto-searcher:**
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/report-bug", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "{keyword1}" "{keyword2}"] }
+```
+
+**See also:** `skills/compound-docs/SKILL.md` for advanced searching and checking if similar bugs are already reported.
+
+**If relevant solutions or bug reports found:**
+1. Do NOT file a duplicate report.
+2. Add your new findings (logs, screenshots) to the existing issue if it's still open.
+3. Use `/reproduce-bug` if you can provide a more consistent reproduction for an existing issue.
+4. Execute the update command to track usage if it's a solved problem:
+   ```bash
+   // turbo
+   Call MCP `call_tool_compound_manager` { action: "updateRef", files: ["{paths from search output}"] }
+   ```
+
+---
+
+### Step 1: Gather Information and Reproduce
+
+> [!TIP]
+> Use the **debug skill** for structured reproduction workflows.
+
+```bash
+cat skills/debug/SKILL.md
+Call MCP `call_tool_logger_manager` { action: "logSkill", name: "debug", outcome: "workflow" }
+```
+
+- [ ] **What happened:** Observable behavior
+- [ ] **What was expected:** Intended behavior
+- [ ] **How to reproduce:** Step-by-step instructions
+- [ ] **Environment:** OS, browser, versions
+
+### Step 2: Create Bug Report
+
+```markdown
+# Bug: {Brief Description}
+
+## Summary
+{One-line description}
+
+## Environment
+- OS: {operating system}
+- Browser/Runtime: {details}
+- Version: {app version}
+
+## Steps to Reproduce
+1. {Step 1}
+2. {Step 2}
+3. {Step 3}
+
+## Expected Behavior
+{What should happen}
+
+## Actual Behavior
+{What actually happened}
+
+## Screenshots/Logs
+{Attach if applicable}
+
+## Possible Cause
+{Initial hypothesis if any}
+
+## Workaround
+{Temporary fix if known}
+```
+
+### Step 3: File the Report
+
+```bash
+# Create issue
+gh issue create --title "Bug: {description}" --body "$(cat bug-report.md)"
+```
+
+### Step 4: Create Local Todo (MANDATORY)
+
+> [!IMPORTANT]
+> **Do not skip.** GitHub issues can be forgotten. Create a local tracking item.
+
+```bash
+# Create local todo
+Call MCP `call_tool_todo_manager` { action: "create", priority: "p1", title: "Fix: {Bug Title}", description: "TODO description" }
+  "External Tracking: GitHub Issue #{issue_number}.\n\nBug Description:\n(Brief description here)" \
+  "Fix the bug reported in issue #{issue_number}" \
+  "Add regression test"
+```
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Report Bug",
+  TaskStatus: "Bug reported and tracked. Offering next steps.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Reported bug: {Bug Title}. Github Issue #{number}. Local Todo created."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ Bug reported: #{issue_number}
+
+Next steps:
+1. /plan - Create plan to fix the bug
+2. /reproduce-bug - If reproduction steps need refinement
+3. /housekeeping - Cleanup
+```
+
+---
+
+## References
+
+- Reproduce bugs: `/reproduce-bug`
+- Plan fix: `/plan`