superkit-mcp-server 1.2.4 → 1.2.5

package/skills/meta/session-resume/SKILL.md

@@ -1,96 +1,96 @@
----
-name: session-resume
-description: Resume context from previous session
----
-
-# Session Resume Skill
-
-Helps agents quickly understand where work left off when starting a new session.
-
-## When To Use
-
-- At the **start of any new conversation**
-- When context seems missing
-- When user asks "what were we working on?"
-
-## Instrumentation
-
-```bash
-# Log usage when using this skill
-Call MCP `call_tool_logger_manager` { action: "logSkill", name: "session-resume", outcome: "manual" }
-```
-
----
-
-## Quick Resume Checklist
-
-### 1. Check Active Work
-
-```bash
-# Ready todos (highest priority)
-ls todos/*-ready-*.md 2>/dev/null | head -5
-
-# In-progress plans
-ls plans/*.md 2>/dev/null
-
-# Recent solutions (for context)
-ls -t docs/solutions/**/*.md 2>/dev/null | head -3
-```
-
-### 2. Check Recent Git Activity
-
-```bash
-# Recent commits
-git log --oneline -5
-
-# Uncommitted changes
-git status --short
-```
-
-### 3. Summarize Context
-
-After gathering info, summarize:
-
-### 4. Check System Health
-
-```bash
-Call MCP `call_tool_compound_manager` { action: "dashboard" }
-```
-
-Review health grade and recommendations before starting work.
-
-### 5. Final Summary
-
-```
-📍 Session Context:
-
-**Active Work:**
-- {X} ready todos waiting
-- Plan in progress: {plan name if any}
-
-**Recent Activity:**
-- Last commit: {subject}
-- {Changed files if uncommitted}
-
-**Suggested Next Steps:**
-1. {Most logical next action}
-2. {Alternative}
-```
-
----
-
-## Automatic Triggers
-
-Consider running this skill when you see:
-- User starts with "continue", "resume", "where were we"
-- First message in a new session
-- User seems to lack context
-
----
-
-## References
-
-- Todos: `todos/`
-- Plans: `plans/`
-- Solutions: `docs/solutions/`
-- Workflows: `skills/workflows/`
+---
+name: session-resume
+description: Resume context from previous session
+---
+
+# Session Resume Skill
+
+Helps agents quickly understand where work left off when starting a new session.
+
+## When To Use
+
+- At the **start of any new conversation**
+- When context seems missing
+- When user asks "what were we working on?"
+
+## Instrumentation
+
+```bash
+# Log usage when using this skill
+Call MCP `call_tool_logger_manager` { action: "logSkill", name: "session-resume", outcome: "manual" }
+```
+
+---
+
+## Quick Resume Checklist
+
+### 1. Check Active Work
+
+```bash
+# Ready todos (highest priority)
+ls todos/*-ready-*.md 2>/dev/null | head -5
+
+# In-progress plans
+ls plans/*.md 2>/dev/null
+
+# Recent solutions (for context)
+ls -t docs/solutions/**/*.md 2>/dev/null | head -3
+```
+
+### 2. Check Recent Git Activity
+
+```bash
+# Recent commits
+git log --oneline -5
+
+# Uncommitted changes
+git status --short
+```
+
+### 3. Summarize Context
+
+After gathering info, summarize:
+
+### 4. Check System Health
+
+```bash
+Call MCP `call_tool_compound_manager` { action: "dashboard" }
+```
+
+Review health grade and recommendations before starting work.
+
+### 5. Final Summary
+
+```
+📍 Session Context:
+
+**Active Work:**
+- {X} ready todos waiting
+- Plan in progress: {plan name if any}
+
+**Recent Activity:**
+- Last commit: {subject}
+- {Changed files if uncommitted}
+
+**Suggested Next Steps:**
+1. {Most logical next action}
+2. {Alternative}
+```
+
+---
+
+## Automatic Triggers
+
+Consider running this skill when you see:
+- User starts with "continue", "resume", "where were we"
+- First message in a new session
+- User seems to lack context
+
+---
+
+## References
+
+- Todos: `todos/`
+- Plans: `plans/`
+- Solutions: `docs/solutions/`
+- Workflows: `skills/workflows/`

package/skills/meta/tailwind/SKILL.md

@@ -1,139 +1,139 @@
-# Tailwind CSS Skill
-
-## Overview
-Tailwind CSS v4 patterns, design systems, and responsive design.
-
-## Core Concepts
-
-### 1. Utility-First Approach
-```html
-<!-- Instead of writing CSS -->
-<div class="flex items-center gap-4 p-6 bg-white rounded-xl shadow-lg">
-  <img class="size-16 rounded-full" src="avatar.jpg" alt="">
-  <div>
-    <h3 class="text-lg font-semibold text-gray-900">John Doe</h3>
-    <p class="text-gray-500">Developer</p>
-  </div>
-</div>
-```
-
-### 2. Responsive Design
-```html
-<!-- Mobile-first approach -->
-<div class="
-  grid grid-cols-1 gap-4
-  sm:grid-cols-2
-  md:grid-cols-3
-  lg:grid-cols-4
-">
-  <!-- Cards -->
-</div>
-
-<!-- Container widths -->
-<div class="container mx-auto px-4 sm:px-6 lg:px-8">
-  <!-- Content -->
-</div>
-```
-
-### 3. Dark Mode
-```html
-<div class="bg-white dark:bg-gray-900">
-  <h1 class="text-gray-900 dark:text-white">Title</h1>
-  <p class="text-gray-600 dark:text-gray-300">Description</p>
-</div>
-```
-
-### 4. State Variants
-```html
-<button class="
-  bg-blue-500 
-  hover:bg-blue-600 
-  focus:ring-2 focus:ring-blue-500 focus:ring-offset-2
-  active:bg-blue-700
-  disabled:opacity-50 disabled:cursor-not-allowed
-  transition-colors duration-200
-">
-  Submit
-</button>
-```
-
-## Component Patterns
-
-### Card Component
-```html
-<div class="
-  bg-white rounded-2xl shadow-md
-  overflow-hidden
-  hover:shadow-xl transition-shadow duration-300
-">
-  <img class="w-full h-48 object-cover" src="..." alt="">
-  <div class="p-6">
-    <h3 class="text-xl font-bold mb-2">Card Title</h3>
-    <p class="text-gray-600 line-clamp-2">Description...</p>
-  </div>
-</div>
-```
-
-### Form Input
-```html
-<div class="space-y-2">
-  <label class="block text-sm font-medium text-gray-700">Email</label>
-  <input 
-    type="email"
-    class="
-      w-full px-4 py-2 
-      border border-gray-300 rounded-lg
-      focus:ring-2 focus:ring-blue-500 focus:border-blue-500
-      placeholder:text-gray-400
-    "
-    placeholder="you@example.com"
-  >
-</div>
-```
-
-### Button Variants
-```html
-<!-- Primary -->
-<button class="px-4 py-2 bg-blue-600 text-white rounded-lg hover:bg-blue-700">
-  Primary
-</button>
-
-<!-- Secondary -->
-<button class="px-4 py-2 bg-gray-100 text-gray-900 rounded-lg hover:bg-gray-200">
-  Secondary
-</button>
-
-<!-- Outline -->
-<button class="px-4 py-2 border-2 border-blue-600 text-blue-600 rounded-lg hover:bg-blue-50">
-  Outline
-</button>
-```
-
-## Custom Design System
-
-### tailwind.config.js
-```javascript
-module.exports = {
-  theme: {
-    extend: {
-      colors: {
-        primary: {
-          50: '#eff6ff',
-          500: '#3b82f6',
-          600: '#2563eb',
-          700: '#1d4ed8',
-        },
-      },
-      fontFamily: {
-        sans: ['Inter', 'sans-serif'],
-      },
-    },
-  },
-};
-```
-
-## Best Practices
-- Use `@apply` sparingly (prefer utilities in HTML)
-- Extract components instead of `@apply`
-- Use arbitrary values `[]` for one-off designs
-- Enable JIT mode for development
+# Tailwind CSS Skill
+
+## Overview
+Tailwind CSS v4 patterns, design systems, and responsive design.
+
+## Core Concepts
+
+### 1. Utility-First Approach
+```html
+<!-- Instead of writing CSS -->
+<div class="flex items-center gap-4 p-6 bg-white rounded-xl shadow-lg">
+  <img class="size-16 rounded-full" src="avatar.jpg" alt="">
+  <div>
+    <h3 class="text-lg font-semibold text-gray-900">John Doe</h3>
+    <p class="text-gray-500">Developer</p>
+  </div>
+</div>
+```
+
+### 2. Responsive Design
+```html
+<!-- Mobile-first approach -->
+<div class="
+  grid grid-cols-1 gap-4
+  sm:grid-cols-2
+  md:grid-cols-3
+  lg:grid-cols-4
+">
+  <!-- Cards -->
+</div>
+
+<!-- Container widths -->
+<div class="container mx-auto px-4 sm:px-6 lg:px-8">
+  <!-- Content -->
+</div>
+```
+
+### 3. Dark Mode
+```html
+<div class="bg-white dark:bg-gray-900">
+  <h1 class="text-gray-900 dark:text-white">Title</h1>
+  <p class="text-gray-600 dark:text-gray-300">Description</p>
+</div>
+```
+
+### 4. State Variants
+```html
+<button class="
+  bg-blue-500 
+  hover:bg-blue-600 
+  focus:ring-2 focus:ring-blue-500 focus:ring-offset-2
+  active:bg-blue-700
+  disabled:opacity-50 disabled:cursor-not-allowed
+  transition-colors duration-200
+">
+  Submit
+</button>
+```
+
+## Component Patterns
+
+### Card Component
+```html
+<div class="
+  bg-white rounded-2xl shadow-md
+  overflow-hidden
+  hover:shadow-xl transition-shadow duration-300
+">
+  <img class="w-full h-48 object-cover" src="..." alt="">
+  <div class="p-6">
+    <h3 class="text-xl font-bold mb-2">Card Title</h3>
+    <p class="text-gray-600 line-clamp-2">Description...</p>
+  </div>
+</div>
+```
+
+### Form Input
+```html
+<div class="space-y-2">
+  <label class="block text-sm font-medium text-gray-700">Email</label>
+  <input 
+    type="email"
+    class="
+      w-full px-4 py-2 
+      border border-gray-300 rounded-lg
+      focus:ring-2 focus:ring-blue-500 focus:border-blue-500
+      placeholder:text-gray-400
+    "
+    placeholder="you@example.com"
+  >
+</div>
+```
+
+### Button Variants
+```html
+<!-- Primary -->
+<button class="px-4 py-2 bg-blue-600 text-white rounded-lg hover:bg-blue-700">
+  Primary
+</button>
+
+<!-- Secondary -->
+<button class="px-4 py-2 bg-gray-100 text-gray-900 rounded-lg hover:bg-gray-200">
+  Secondary
+</button>
+
+<!-- Outline -->
+<button class="px-4 py-2 border-2 border-blue-600 text-blue-600 rounded-lg hover:bg-blue-50">
+  Outline
+</button>
+```
+
+## Custom Design System
+
+### tailwind.config.js
+```javascript
+module.exports = {
+  theme: {
+    extend: {
+      colors: {
+        primary: {
+          50: '#eff6ff',
+          500: '#3b82f6',
+          600: '#2563eb',
+          700: '#1d4ed8',
+        },
+      },
+      fontFamily: {
+        sans: ['Inter', 'sans-serif'],
+      },
+    },
+  },
+};
+```
+
+## Best Practices
+- Use `@apply` sparingly (prefer utilities in HTML)
+- Extract components instead of `@apply`
+- Use arbitrary values `[]` for one-off designs
+- Enable JIT mode for development

package/skills/meta/testing/SKILL.md

@@ -1,43 +1,43 @@
----
-name: testing
-description: Unified testing commands and patterns across frontend and backend.
-last_updated: 2025-12-20
----
-
-# Testing Skill
-
-## Overview
-
-Guidance and templates for testing in {PROJECT_NAME}. Covers React Component testing (Vitest/RTL) and Backend testing (Python/Pytest).
-
-## When To Use
-
-- **Writing new code**: Every new feature needs tests.
-- **Fixing bugs**: Create a reproduction test first.
-- **Refactoring**: Ensure green tests before and after.
-
-## Instrumentation
-
-```bash
-# Log usage when using this skill
-Call MCP `call_tool_logger_manager` { action: "logSkill", name: "testing", outcome: "manual" }
-```
-
-## What do you want to do?
-
-1. **Test React Components** → `workflows/run-frontend-tests.md`
-2. **Test Backend/API** → `workflows/run-backend-tests.md`
-3. **Write a New Test** → `templates/component-test.template.tsx`
-4. **Fix Test Failures** → `references/vitest-patterns.md`
-
-## Quick Commands
-
-```bash
-# Frontend (Unit/Integration)
-npm test
-npm test -- -t "ComponentName"  # Run specific test
-
-# Backend (API)
-pytest
-pytest -k "test_name"
-```
+---
+name: testing
+description: Unified testing commands and patterns across frontend and backend.
+last_updated: 2025-12-20
+---
+
+# Testing Skill
+
+## Overview
+
+Guidance and templates for testing in {PROJECT_NAME}. Covers React Component testing (Vitest/RTL) and Backend testing (Python/Pytest).
+
+## When To Use
+
+- **Writing new code**: Every new feature needs tests.
+- **Fixing bugs**: Create a reproduction test first.
+- **Refactoring**: Ensure green tests before and after.
+
+## Instrumentation
+
+```bash
+# Log usage when using this skill
+Call MCP `call_tool_logger_manager` { action: "logSkill", name: "testing", outcome: "manual" }
+```
+
+## What do you want to do?
+
+1. **Test React Components** → `workflows/run-frontend-tests.md`
+2. **Test Backend/API** → `workflows/run-backend-tests.md`
+3. **Write a New Test** → `templates/component-test.template.tsx`
+4. **Fix Test Failures** → `references/vitest-patterns.md`
+
+## Quick Commands
+
+```bash
+# Frontend (Unit/Integration)
+npm test
+npm test -- -t "ComponentName"  # Run specific test
+
+# Backend (API)
+pytest
+pytest -k "test_name"
+```

package/skills/meta/testing/references/vitest-patterns.md

@@ -1,45 +1,45 @@
-# Vitest & Testing Library Patterns
-
-## Common Mocking Patterns
-
-### Mocking a Module
-```tsx
-vi.mock('next/navigation', () => ({
-  useRouter: () => ({
-    push: vi.fn(),
-    replace: vi.fn(),
-  }),
-}));
-```
-
-### Mocking a Component
-```tsx
-vi.mock('./ChildComponent', () => ({
-  ChildComponent: () => <div data-testid="child-mock">Mocked Child</div>,
-}));
-```
-
-## Async Testing
-
-Wait for element to appear:
-```tsx
-await waitFor(() => {
-  expect(screen.getByText('Loaded')).toBeInTheDocument();
-});
-```
-
-Verify element disappears:
-```tsx
-await waitFor(() => {
-  expect(screen.queryByText('Loading...')).not.toBeInTheDocument();
-});
-```
-
-## User Interaction
-
-Use `fireEvent` for simple events, or `userEvent` (if setup) for complex ones.
-
-```tsx
-fireEvent.change(input, { target: { value: 'New Value' } });
-fireEvent.click(button);
-```
+# Vitest & Testing Library Patterns
+
+## Common Mocking Patterns
+
+### Mocking a Module
+```tsx
+vi.mock('next/navigation', () => ({
+  useRouter: () => ({
+    push: vi.fn(),
+    replace: vi.fn(),
+  }),
+}));
+```
+
+### Mocking a Component
+```tsx
+vi.mock('./ChildComponent', () => ({
+  ChildComponent: () => <div data-testid="child-mock">Mocked Child</div>,
+}));
+```
+
+## Async Testing
+
+Wait for element to appear:
+```tsx
+await waitFor(() => {
+  expect(screen.getByText('Loaded')).toBeInTheDocument();
+});
+```
+
+Verify element disappears:
+```tsx
+await waitFor(() => {
+  expect(screen.queryByText('Loading...')).not.toBeInTheDocument();
+});
+```
+
+## User Interaction
+
+Use `fireEvent` for simple events, or `userEvent` (if setup) for complex ones.
+
+```tsx
+fireEvent.change(input, { target: { value: 'New Value' } });
+fireEvent.click(button);
+```