superkit-mcp-server 1.1.4 → 1.2.0

package/skills/workflows/cycle.md

@@ -1,144 +1,144 @@
----
-description: Orchestrate the full "plan → review → work → review → compound" lifecycle for small tasks.
----
-
-# /cycle - Unified Small-Task Lifecycle
-
-Orchestrate the full "essential" development lifecycle for small, self-contained tasks. This workflow ensures rigorous quality without friction by chaining the standard workflows together.
-
-> **Why /cycle?** "Quick" tasks often skip steps like planning or review, leading to bugs. /cycle makes it easy to do it right.
-
-## When To Use
-
-- For small, well-defined tasks (15-60 mins)
-- When "just fixing one thing"
-- To ensure you don't skip the "boring" but critical steps
-
----
-
-## Workflow
-
-### Step 0: Search & Log
-
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/cycle", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "unified workflow" "cycle"] }
-```
-
-### Step 1: Planning
-
-Trigger the planning workflow.
-
-```bash
-/plan
-```
-
-*Guidance:* Use the **Minimal** or **Standard** template. Don't over-engineer, but DO capture:
-- Goal
-- Approach
-- Verification plan
-
-### Step 2: Self-Review
-
-Review your own plan immediately.
-
-```bash
-/plan_review
-```
-
-*Guidance:*
-- Did you run `compound-search`?
-- Is the verification plan solid?
-- If yes → **Approved**.
-
-### Step 3: Execution
-
-Execute the plan systematically.
-
-```bash
-/work
-```
-
-*Guidance:*
-- Mark the todo as in-progress: `Call MCP `call_tool_todo_manager` { action: "start", todoId: "todos/{todo}.md`" }
-- Create tests first if possible.
-- Update todos as you go.
-
-### Step 4: Rapid Review
-
-Review the code changes.
-
-```bash
-/review
-```
-
-*Guidance:*
-- Run the **Security** and **Simplicity** passes.
-- Verify tests pass.
-- If self-approving (for non-critical path), be extra critical.
-
-### Step 4.5: Complete Source Todo (CONDITIONAL)
-
-> [!CAUTION]
-> **IF WORKING FROM A TODO:** You must atomically mark it complete.
-
-**If this /cycle was triggered by a todo file:**
-
-```bash
-Call MCP `call_tool_todo_manager` { action: "done", todoId: "todos/{todo-filename}.md" }
-```
-
-**Why:** This script updates YAML status AND renames the file atomically, preventing state drift ([Pattern #10](../../docs/solutions/patterns/critical-patterns.md#pattern-10-atomic-state-transitions)).
-
-**Skip this step if:**
-- Working from a plan file
-- No source todo exists
-- Todo is exploratory work
-
-### Step 5: Capture Knowledge
-
-Don't skip this just because it was small.
-
-```bash
-/compound
-```
-
-*Guidance:*
-- Did you learn a new grep pattern?
-- Did you fix a tricky type error?
-- Document it!
-
-### Step 6: Cleanup
-
-Archive and cleanup.
-
-```bash
-/housekeeping
-```
-
----
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Cycle: {Task Name}",
-  TaskStatus: "Cycle complete. All quality gates passed.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Completed full development cycle for {task}. Passed plan, review, work, and compound stages."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ Cycle complete
-
-Next steps:
-1. /housekeeping - Final check before push
-2. /review - Request peer review if necessary
-3. Continue working
-```
+---
+description: Orchestrate the full "plan → review → work → review → compound" lifecycle for small tasks.
+---
+
+# /cycle - Unified Small-Task Lifecycle
+
+Orchestrate the full "essential" development lifecycle for small, self-contained tasks. This workflow ensures rigorous quality without friction by chaining the standard workflows together.
+
+> **Why /cycle?** "Quick" tasks often skip steps like planning or review, leading to bugs. /cycle makes it easy to do it right.
+
+## When To Use
+
+- For small, well-defined tasks (15-60 mins)
+- When "just fixing one thing"
+- To ensure you don't skip the "boring" but critical steps
+
+---
+
+## Workflow
+
+### Step 0: Search & Log
+
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/cycle", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "unified workflow" "cycle"] }
+```
+
+### Step 1: Planning
+
+Trigger the planning workflow.
+
+```bash
+/plan
+```
+
+*Guidance:* Use the **Minimal** or **Standard** template. Don't over-engineer, but DO capture:
+- Goal
+- Approach
+- Verification plan
+
+### Step 2: Self-Review
+
+Review your own plan immediately.
+
+```bash
+/plan_review
+```
+
+*Guidance:*
+- Did you run `compound-search`?
+- Is the verification plan solid?
+- If yes → **Approved**.
+
+### Step 3: Execution
+
+Execute the plan systematically.
+
+```bash
+/work
+```
+
+*Guidance:*
+- Mark the todo as in-progress: `Call MCP `call_tool_todo_manager` { action: "start", todoId: "todos/{todo}.md`" }
+- Create tests first if possible.
+- Update todos as you go.
+
+### Step 4: Rapid Review
+
+Review the code changes.
+
+```bash
+/review
+```
+
+*Guidance:*
+- Run the **Security** and **Simplicity** passes.
+- Verify tests pass.
+- If self-approving (for non-critical path), be extra critical.
+
+### Step 4.5: Complete Source Todo (CONDITIONAL)
+
+> [!CAUTION]
+> **IF WORKING FROM A TODO:** You must atomically mark it complete.
+
+**If this /cycle was triggered by a todo file:**
+
+```bash
+Call MCP `call_tool_todo_manager` { action: "done", todoId: "todos/{todo-filename}.md" }
+```
+
+**Why:** This script updates YAML status AND renames the file atomically, preventing state drift ([Pattern #10](../../docs/solutions/patterns/critical-patterns.md#pattern-10-atomic-state-transitions)).
+
+**Skip this step if:**
+- Working from a plan file
+- No source todo exists
+- Todo is exploratory work
+
+### Step 5: Capture Knowledge
+
+Don't skip this just because it was small.
+
+```bash
+/compound
+```
+
+*Guidance:*
+- Did you learn a new grep pattern?
+- Did you fix a tricky type error?
+- Document it!
+
+### Step 6: Cleanup
+
+Archive and cleanup.
+
+```bash
+/housekeeping
+```
+
+---
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Cycle: {Task Name}",
+  TaskStatus: "Cycle complete. All quality gates passed.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Completed full development cycle for {task}. Passed plan, review, work, and compound stages."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ Cycle complete
+
+Next steps:
+1. /housekeeping - Final check before push
+2. /review - Request peer review if necessary
+3. Continue working
+```

package/skills/workflows/deploy-docs.md

@@ -1,84 +1,84 @@
----
-description: Deploy documentation updates. Use when publishing docs changes.
----
-
-# /deploy-docs - Documentation Deployment
-
-Deploy documentation to hosting platform.
-
-## Workflow
-
-### Step 0: Search & Log
-
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/deploy-docs", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "deployment"] }
-```
-
-### Step 1: Build Documentation
-
-```bash
-# For most doc systems
-npm run docs:build
-# or
-mkdocs build
-# or
-mdbook build
-```
-
-### Step 2: Preview Locally
-
-```bash
-npm run docs:serve
-# or
-mkdocs serve
-# or
-python -m http.server 8000 -d dist/
-```
-
-### Step 3: Deploy
-
-```bash
-# GitHub Pages
-npm run docs:deploy
-
-# Vercel
-vercel --prod
-
-# Netlify
-netlify deploy --prod
-
-# Manual
-rsync -avz dist/ user@server:/var/www/docs/
-```
-
-### Step 4: Verify
-
-- [ ] Docs accessible at URL
-- [ ] All pages load
-- [ ] Search works
-- [ ] Links not broken
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Deploy Documentation",
-  TaskStatus: "Docs deployed and verified. Offering next steps.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Deployed docs to {target}. Verified accessibility and links."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ Docs deployed
-
-Next steps:
-1. /housekeeping - Cleanup artifacts
-2. /work - Resume development
-```
+---
+description: Deploy documentation updates. Use when publishing docs changes.
+---
+
+# /deploy-docs - Documentation Deployment
+
+Deploy documentation to hosting platform.
+
+## Workflow
+
+### Step 0: Search & Log
+
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/deploy-docs", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "deployment"] }
+```
+
+### Step 1: Build Documentation
+
+```bash
+# For most doc systems
+npm run docs:build
+# or
+mkdocs build
+# or
+mdbook build
+```
+
+### Step 2: Preview Locally
+
+```bash
+npm run docs:serve
+# or
+mkdocs serve
+# or
+python -m http.server 8000 -d dist/
+```
+
+### Step 3: Deploy
+
+```bash
+# GitHub Pages
+npm run docs:deploy
+
+# Vercel
+vercel --prod
+
+# Netlify
+netlify deploy --prod
+
+# Manual
+rsync -avz dist/ user@server:/var/www/docs/
+```
+
+### Step 4: Verify
+
+- [ ] Docs accessible at URL
+- [ ] All pages load
+- [ ] Search works
+- [ ] Links not broken
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Deploy Documentation",
+  TaskStatus: "Docs deployed and verified. Offering next steps.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Deployed docs to {target}. Verified accessibility and links."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ Docs deployed
+
+Next steps:
+1. /housekeeping - Cleanup artifacts
+2. /work - Resume development
+```

package/skills/workflows/development-rules.md

@@ -1,42 +1,42 @@
----
-name: development-rules
-description: Code quality standards, testing targets, and pre-commit procedures to adhere to during development.
----
-
-# Development Rules
-
-## Code Quality Standards
-
-### TypeScript
-- Strict mode enabled
-- No implicit `any`
-- Proper null checks
-
-### Testing
-- Unit tests for new features
-- Integration tests for workflows
-- Coverage target: 80%
-
-### Code Style
-- ESLint + Prettier
-- Max line length: 100
-- Use arrow functions
-
-## Pre-commit Procedures
-
-1. Run tests: `npm test`
-2. Type check: `npm run build`
-3. Lint: `npm run lint`
-4. Update docs if API changed
-
-## Subagent Orchestration
-
-### Sequential (Default)
-```
-Planner → Scout → Coder → Tester → Reviewer → Git
-```
-
-### Parallel (Independent tasks)
-- Multiple file reviews
-- Concurrent doc updates
-- Parallel tests
+---
+name: development-rules
+description: Code quality standards, testing targets, and pre-commit procedures to adhere to during development.
+---
+
+# Development Rules
+
+## Code Quality Standards
+
+### TypeScript
+- Strict mode enabled
+- No implicit `any`
+- Proper null checks
+
+### Testing
+- Unit tests for new features
+- Integration tests for workflows
+- Coverage target: 80%
+
+### Code Style
+- ESLint + Prettier
+- Max line length: 100
+- Use arrow functions
+
+## Pre-commit Procedures
+
+1. Run tests: `npm test`
+2. Type check: `npm run build`
+3. Lint: `npm run lint`
+4. Update docs if API changed
+
+## Subagent Orchestration
+
+### Sequential (Default)
+```
+Planner → Scout → Coder → Tester → Reviewer → Git
+```
+
+### Parallel (Independent tasks)
+- Multiple file reviews
+- Concurrent doc updates
+- Parallel tests