@su-record/vibe 2.4.4 → 2.4.6

package/skills/multi-llm-orchestration.md

@@ -1,97 +1,97 @@
----
-description: Multi-LLM collaboration guide. Auto-activates for architecture review, design decisions, debugging, UI/UX consultation, complex problem solving, or when a different perspective is needed.
----
-# Multi-LLM Orchestration
-
-Guide for using GPT/Gemini as sub-agents in Claude Code.
-
-## When to Use GPT (mcp__vibe-gpt)
-
-| Situation | Reason |
-|-----------|--------|
-| Architecture design/review | Get different perspective on design |
-| Complex debugging | Fresh eyes on the problem |
-| Algorithm optimization | Alternative algorithm suggestions |
-| Security review | Cross-check vulnerabilities |
-| Technology decisions | Compare pros/cons |
-
-### Usage
-
-```
-mcp__vibe-gpt__gpt_chat({
-  prompt: "Review this auth architecture: [code/description]",
-  model: "gpt-5.2-codex"  // coding specialized
-})
-```
-
-### Recommended Models
-
-| Model | Use Case |
-|-------|----------|
-| gpt-5.2 | General purpose (default) |
-| gpt-5.2-codex | Coding specialized |
-| gpt-5.1-codex-mini | Quick responses needed |
-
-## When to Use Gemini (mcp__vibe-gemini)
-
-| Situation | Reason |
-|-----------|--------|
-| UI/UX design consultation | User experience perspective |
-| Design system advice | Component structuring |
-| Accessibility (a11y) review | Accessibility guidelines |
-| User flow design | UX optimization |
-
-### Usage
-
-```
-mcp__vibe-gemini__gemini_chat({
-  prompt: "Suggest UX improvements for this login form: [description]"
-})
-```
-
-## When NOT to Use
-
-- Simple implementation (Claude alone is sufficient)
-- File read/write (use Claude's tools)
-- Quick response needed (API latency exists)
-- Tasks requiring project context (Claude has the context)
-
-## Collaboration Patterns
-
-### Pattern 1: Design Cross-check
-
-```
-Claude: Draft design
-    ↓
-GPT: Architecture review (mcp__vibe-gpt__gpt_analyze_architecture)
-    ↓
-Claude: Incorporate feedback into final design
-```
-
-### Pattern 2: Debugging Collaboration
-
-```
-Claude: Attempt problem analysis
-    ↓
-If stuck, ask GPT (mcp__vibe-gpt__gpt_debug)
-    ↓
-Claude: Apply GPT's suggestions
-```
-
-### Pattern 3: UI/UX Consultation
-
-```
-Claude: Implement feature
-    ↓
-Gemini: Suggest UX improvements (mcp__vibe-gemini__gemini_chat)
-    ↓
-Claude: Apply UX feedback
-```
-
-## API Key Setup
-
-```bash
-vibe gpt <api-key>      # Enable GPT
-vibe gemini <api-key>   # Enable Gemini
-vibe status             # Check current settings
-```
+---
+description: Multi-LLM collaboration guide. Auto-activates for architecture review, design decisions, debugging, UI/UX consultation, complex problem solving, or when a different perspective is needed.
+---
+# Multi-LLM Orchestration
+
+Guide for using GPT/Gemini as sub-agents in Claude Code.
+
+## When to Use GPT (mcp__vibe-gpt)
+
+| Situation | Reason |
+|-----------|--------|
+| Architecture design/review | Get different perspective on design |
+| Complex debugging | Fresh eyes on the problem |
+| Algorithm optimization | Alternative algorithm suggestions |
+| Security review | Cross-check vulnerabilities |
+| Technology decisions | Compare pros/cons |
+
+### Usage
+
+```
+mcp__vibe-gpt__gpt_chat({
+  prompt: "Review this auth architecture: [code/description]",
+  model: "gpt-5.2-codex"  // coding specialized
+})
+```
+
+### Recommended Models
+
+| Model | Use Case |
+|-------|----------|
+| gpt-5.2 | General purpose (default) |
+| gpt-5.2-codex | Coding specialized |
+| gpt-5.1-codex-mini | Quick responses needed |
+
+## When to Use Gemini (mcp__vibe-gemini)
+
+| Situation | Reason |
+|-----------|--------|
+| UI/UX design consultation | User experience perspective |
+| Design system advice | Component structuring |
+| Accessibility (a11y) review | Accessibility guidelines |
+| User flow design | UX optimization |
+
+### Usage
+
+```
+mcp__vibe-gemini__gemini_chat({
+  prompt: "Suggest UX improvements for this login form: [description]"
+})
+```
+
+## When NOT to Use
+
+- Simple implementation (Claude alone is sufficient)
+- File read/write (use Claude's tools)
+- Quick response needed (API latency exists)
+- Tasks requiring project context (Claude has the context)
+
+## Collaboration Patterns
+
+### Pattern 1: Design Cross-check
+
+```
+Claude: Draft design
+    ↓
+GPT: Architecture review (mcp__vibe-gpt__gpt_analyze_architecture)
+    ↓
+Claude: Incorporate feedback into final design
+```
+
+### Pattern 2: Debugging Collaboration
+
+```
+Claude: Attempt problem analysis
+    ↓
+If stuck, ask GPT (mcp__vibe-gpt__gpt_debug)
+    ↓
+Claude: Apply GPT's suggestions
+```
+
+### Pattern 3: UI/UX Consultation
+
+```
+Claude: Implement feature
+    ↓
+Gemini: Suggest UX improvements (mcp__vibe-gemini__gemini_chat)
+    ↓
+Claude: Apply UX feedback
+```
+
+## API Key Setup
+
+```bash
+vibe gpt <api-key>      # Enable GPT
+vibe gemini <api-key>   # Enable Gemini
+vibe status             # Check current settings
+```

package/skills/parallel-research.md

@@ -1,77 +1,77 @@
----
-description: Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions.
----
-# Parallel Research
-
-Parallel research patterns for solving complex problems.
-
-## When Parallel Research is Needed
-
-| Situation | Reason |
-|-----------|--------|
-| New technology adoption | Need best practices |
-| Security-related features | Multi-angle review needed |
-| Architecture design | Multiple perspectives needed |
-| Technology selection | Comparison analysis needed |
-| Complex bugs | Explore multiple causes |
-
-## Research Agents (4 Parallel)
-
-| Agent | Role | Tools |
-|-------|------|-------|
-| best-practices | Search best practices | Web Search, context7 |
-| framework-docs | Search official docs | context7 |
-| codebase-patterns | Analyze existing code patterns | Grep, Glob |
-| security-advisory | Search security advisories | Web Search |
-
-## Usage Methods
-
-### Method 1: Direct Orchestrator Call
-
-```bash
-node -e "import('@su-record/vibe/orchestrator').then(o =>
-  o.research('passkey authentication', ['React', 'Supabase'])
-  .then(r => console.log(r.content[0].text))
-)"
-```
-
-### Method 2: Use /vibe.spec
-
-```
-/vibe.spec "feature-name"
-→ Parallel research runs automatically after requirements confirmed
-```
-
-### Method 3: Parallel Task Tool Execution
-
-```
-Task 1: "Search React auth best practices"
-Task 2: "Search Supabase Auth official docs" (concurrent)
-Task 3: "Analyze existing auth code patterns" (concurrent)
-Task 4: "Search auth security vulnerabilities" (concurrent)
-```
-
-## Using Research Results
-
-```
-Parallel research complete
-    ↓
-Synthesize results
-    ↓
-Reflect in SPEC Context section
-OR
-Reference during implementation
-```
-
-## When Research is NOT Needed
-
-- Simple CRUD operations
-- Already familiar patterns
-- Similar code exists in project
-- Time-critical (supplement with review later)
-
-## Notes
-
-- Research runs **after requirements confirmed**
-- Split overly broad topics
-- Research results are references, not absolute truth
+---
+description: Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions.
+---
+# Parallel Research
+
+Parallel research patterns for solving complex problems.
+
+## When Parallel Research is Needed
+
+| Situation | Reason |
+|-----------|--------|
+| New technology adoption | Need best practices |
+| Security-related features | Multi-angle review needed |
+| Architecture design | Multiple perspectives needed |
+| Technology selection | Comparison analysis needed |
+| Complex bugs | Explore multiple causes |
+
+## Research Agents (4 Parallel)
+
+| Agent | Role | Tools |
+|-------|------|-------|
+| best-practices | Search best practices | Web Search, context7 |
+| framework-docs | Search official docs | context7 |
+| codebase-patterns | Analyze existing code patterns | Grep, Glob |
+| security-advisory | Search security advisories | Web Search |
+
+## Usage Methods
+
+### Method 1: Direct Orchestrator Call
+
+```bash
+node -e "import('@su-record/vibe/orchestrator').then(o =>
+  o.research('passkey authentication', ['React', 'Supabase'])
+  .then(r => console.log(r.content[0].text))
+)"
+```
+
+### Method 2: Use /vibe.spec
+
+```
+/vibe.spec "feature-name"
+→ Parallel research runs automatically after requirements confirmed
+```
+
+### Method 3: Parallel Task Tool Execution
+
+```
+Task 1: "Search React auth best practices"
+Task 2: "Search Supabase Auth official docs" (concurrent)
+Task 3: "Analyze existing auth code patterns" (concurrent)
+Task 4: "Search auth security vulnerabilities" (concurrent)
+```
+
+## Using Research Results
+
+```
+Parallel research complete
+    ↓
+Synthesize results
+    ↓
+Reflect in SPEC Context section
+OR
+Reference during implementation
+```
+
+## When Research is NOT Needed
+
+- Simple CRUD operations
+- Already familiar patterns
+- Similar code exists in project
+- Time-critical (supplement with review later)
+
+## Notes
+
+- Research runs **after requirements confirmed**
+- Split overly broad topics
+- Research results are references, not absolute truth