@su-record/vibe 2.6.42 → 2.6.44

package/skills/core-capabilities/SKILL.md

@@ -1,164 +1,164 @@
----
-name: core-capabilities
-description: "Core framework capabilities overview. Auto-activates when working on core projects, asking about available features, or needing workflow guidance."
-triggers: [core, capabilities, features, workflow, framework guide]
-priority: 50
----
-# Core Capabilities
-
-Complete guide to core's scenario-driven development framework.
-
-## Core Workflow
-
-```
-/vibe.spec → /vibe.run → /vibe.verify → /vibe.review
-```
-
-## Slash Commands
-
-| Command | Purpose |
-|---------|---------|
-| `/vibe.spec "feature"` | Create SPEC with PTCF structure + 8 parallel research |
-| `/vibe.spec "feature" split` | Create multiple SPECs for large scope features |
-| `/vibe.run "feature"` | Implement based on SPEC |
-| `/vibe.run "feature" ultrawork` | Maximum performance mode |
-| `/vibe.verify "feature"` | BDD scenario verification |
-| `/vibe.review` | Parallel code review (13+ agents) |
-| `/vibe.analyze` | Project analysis |
-| `/vibe.reason "problem"` | Systematic reasoning |
-| `/vibe.utils --e2e` | Playwright E2E testing |
-| `/vibe.utils --diagram` | Generate diagrams |
-| `/vibe.utils --ui "description"` | UI preview |
-| `/vibe.utils --continue` | Session restore (load previous context) |
-| `/vibe.utils --compound` | Document solutions |
-
-## Built-in Tools
-
-### Semantic Code Analysis
-
-```bash
-node -e "import('@su-record/vibe/tools').then(t => t.TOOL_NAME({...}))"
-```
-
-| Tool | Purpose |
-|------|---------|
-| `findSymbol` | Find symbol definitions |
-| `findReferences` | Find all references |
-| `analyzeComplexity` | Code complexity analysis |
-| `validateCodeQuality` | Quality validation |
-
-### Memory Management
-
-| Tool | Purpose |
-|------|---------|
-| `startSession` | Start session (restore previous context) |
-| `autoSaveContext` | Save current state |
-| `saveMemory` | Save important decisions |
-| `recallMemory` | Recall saved memory |
-| `listMemories` | List saved memories |
-
-## Orchestrator
-
-### Background Agents
-
-```bash
-node -e "import('@su-record/vibe/orchestrator').then(o =>
-  o.launchBackgroundAgent({ prompt: '...', agentName: '...' })
-)"
-```
-
-## Multi-LLM Research (v2.5.0)
-
-GPT/Gemini are automatically called within `/vibe.spec`:
-
-```text
-/vibe.spec "feature"
-      ↓
-[Claude] Draft SPEC
-      ↓
-[Parallel Research] 8 parallel tasks:
-  - 4x Bash: GPT/Gemini (best practices + security)
-  - 4x Task: Claude agents (docs, patterns, advisories)
-      ↓
-[SPEC Review] GPT + Gemini parallel review
-      ↓
-[Claude] Finalize SPEC
-```
-
-| Phase | Method | Tasks |
-|-------|--------|-------- |
-| Research | `llm-orchestrate.js` via Bash | GPT best practices, GPT security, Gemini best practices, Gemini security |
-| Research | Task tool (Claude agents) | framework-docs, codebase-patterns, best-practices, security-advisory |
-| SPEC Review | `llm-orchestrate.js` via Bash | SPEC quality validation |
-| Docs | context7 MCP | Latest library documentation |
-
-**Setup:**
-```bash
-vibe gpt auth       # Enable GPT
-vibe gemini auth    # Enable Gemini
-vibe status         # Check current settings
-```
-
-## ULTRAWORK Mode
-
-Add `ultrawork` or `ulw` for maximum performance:
-
-- Parallel subagent exploration (3+ concurrent)
-- Background agents preparing next phase
-- Phase pipelining (no wait between phases)
-- Boulder Loop (auto-progress until complete)
-- Auto-retry on errors (max 3 times)
-- Auto-compress at 70%+ context
-
-## Review Agents (13+)
-
-| Category | Agents |
-|----------|--------|
-| Security | security-reviewer, data-integrity-reviewer |
-| Performance | performance-reviewer, complexity-reviewer |
-| Architecture | architecture-reviewer, simplicity-reviewer |
-| Language | python, typescript, rails, react reviewers |
-| Context | git-history, test-coverage reviewers |
-
-## Project Structure
-
-```
-# Global (~/.claude/)
-~/.claude/
-├── commands/          # Slash commands
-├── agents/            # Sub-agents
-├── skills/            # Auto-activated guides
-└── core/
-    ├── rules/         # Coding rules
-    ├── languages/     # Language guides
-    └── templates/     # Templates
-
-# Global (%APPDATA%/core/ or ~/.config/vibe/)
-core/
-├── hooks/scripts/     # Hook scripts (llm-orchestrate.js)
-├── gpt.json           # GPT credentials
-└── gemini.json        # Gemini credentials
-
-# Project (.claude/)
-.claude/
-├── settings.local.json  # Hooks config (personal, gitignored)
-└── core/
-    ├── specs/           # SPEC documents
-    ├── features/        # BDD scenarios
-    ├── config.json      # Project config
-    └── constitution.md  # Project rules
-```
-
-## Context Management
-
-- Session start: Auto-restore previous context
-- 70/80/90%: Auto-save checkpoints
-- Context overflow: Use `saveMemory` → `/new`
-
-## Without Commands
-
-Even without `/vibe.*` commands, you can:
-
-1. Call tools directly via node commands
-2. Reference skills for guidance
-3. Apply coding rules from `~/.claude/vibe/rules/` (global)
+---
+name: core-capabilities
+description: "Core framework capabilities overview. Auto-activates when working on core projects, asking about available features, or needing workflow guidance."
+triggers: [core, capabilities, features, workflow, framework guide]
+priority: 50
+---
+# Core Capabilities
+
+Complete guide to core's scenario-driven development framework.
+
+## Core Workflow
+
+```
+/vibe.spec → /vibe.run → /vibe.verify → /vibe.review
+```
+
+## Slash Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/vibe.spec "feature"` | Create SPEC with PTCF structure + 8 parallel research |
+| `/vibe.spec "feature" split` | Create multiple SPECs for large scope features |
+| `/vibe.run "feature"` | Implement based on SPEC |
+| `/vibe.run "feature" ultrawork` | Maximum performance mode |
+| `/vibe.verify "feature"` | BDD scenario verification |
+| `/vibe.review` | Parallel code review (13+ agents) |
+| `/vibe.analyze` | Project analysis |
+| `/vibe.reason "problem"` | Systematic reasoning |
+| `/vibe.utils --e2e` | Playwright E2E testing |
+| `/vibe.utils --diagram` | Generate diagrams |
+| `/vibe.utils --ui "description"` | UI preview |
+| `/vibe.utils --continue` | Session restore (load previous context) |
+| `/vibe.utils --compound` | Document solutions |
+
+## Built-in Tools
+
+### Semantic Code Analysis
+
+```bash
+node -e "import('{{CORE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index.js').then(t => t.TOOL_NAME({...}))"
+```
+
+| Tool | Purpose |
+|------|---------|
+| `findSymbol` | Find symbol definitions |
+| `findReferences` | Find all references |
+| `analyzeComplexity` | Code complexity analysis |
+| `validateCodeQuality` | Quality validation |
+
+### Memory Management
+
+| Tool | Purpose |
+|------|---------|
+| `startSession` | Start session (restore previous context) |
+| `autoSaveContext` | Save current state |
+| `saveMemory` | Save important decisions |
+| `recallMemory` | Recall saved memory |
+| `listMemories` | List saved memories |
+
+## Orchestrator
+
+### Background Agents
+
+```bash
+node -e "import('{{CORE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').then(o =>
+  o.launchBackgroundAgent({ prompt: '...', agentName: '...' })
+)"
+```
+
+## Multi-LLM Research (v2.5.0)
+
+GPT/Gemini are automatically called within `/vibe.spec`:
+
+```text
+/vibe.spec "feature"
+      ↓
+[Claude] Draft SPEC
+      ↓
+[Parallel Research] 8 parallel tasks:
+  - 4x Bash: GPT/Gemini (best practices + security)
+  - 4x Task: Claude agents (docs, patterns, advisories)
+      ↓
+[SPEC Review] GPT + Gemini parallel review
+      ↓
+[Claude] Finalize SPEC
+```
+
+| Phase | Method | Tasks |
+|-------|--------|-------- |
+| Research | `llm-orchestrate.js` via Bash | GPT best practices, GPT security, Gemini best practices, Gemini security |
+| Research | Task tool (Claude agents) | framework-docs, codebase-patterns, best-practices, security-advisory |
+| SPEC Review | `llm-orchestrate.js` via Bash | SPEC quality validation |
+| Docs | context7 MCP | Latest library documentation |
+
+**Setup:**
+```bash
+vibe gpt auth       # Enable GPT
+vibe gemini auth    # Enable Gemini
+vibe status         # Check current settings
+```
+
+## ULTRAWORK Mode
+
+Add `ultrawork` or `ulw` for maximum performance:
+
+- Parallel subagent exploration (3+ concurrent)
+- Background agents preparing next phase
+- Phase pipelining (no wait between phases)
+- Boulder Loop (auto-progress until complete)
+- Auto-retry on errors (max 3 times)
+- Auto-compress at 70%+ context
+
+## Review Agents (13+)
+
+| Category | Agents |
+|----------|--------|
+| Security | security-reviewer, data-integrity-reviewer |
+| Performance | performance-reviewer, complexity-reviewer |
+| Architecture | architecture-reviewer, simplicity-reviewer |
+| Language | python, typescript, rails, react reviewers |
+| Context | git-history, test-coverage reviewers |
+
+## Project Structure
+
+```
+# Global (~/.claude/)
+~/.claude/
+├── commands/          # Slash commands
+├── agents/            # Sub-agents
+├── skills/            # Auto-activated guides
+└── core/
+    ├── rules/         # Coding rules
+    ├── languages/     # Language guides
+    └── templates/     # Templates
+
+# Global (%APPDATA%/core/ or ~/.config/vibe/)
+core/
+├── hooks/scripts/     # Hook scripts (llm-orchestrate.js)
+├── gpt.json           # GPT credentials
+└── gemini.json        # Gemini credentials
+
+# Project (.claude/)
+.claude/
+├── settings.local.json  # Hooks config (personal, gitignored)
+└── core/
+    ├── specs/           # SPEC documents
+    ├── features/        # BDD scenarios
+    ├── config.json      # Project config
+    └── constitution.md  # Project rules
+```
+
+## Context Management
+
+- Session start: Auto-restore previous context
+- 70/80/90%: Auto-save checkpoints
+- Context overflow: Use `saveMemory` → `/new`
+
+## Without Commands
+
+Even without `/vibe.*` commands, you can:
+
+1. Call tools directly via node commands
+2. Reference skills for guidance
+3. Apply coding rules from `~/.claude/vibe/rules/` (global)

package/skills/parallel-research/SKILL.md

@@ -1,80 +1,80 @@
----
-name: parallel-research
-description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
-triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
-priority: 60
----
-# 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
+---
+name: parallel-research
+description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
+triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
+priority: 60
+---
+# 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('{{CORE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').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