@su-record/vibe 2.7.8 → 2.7.10

package/skills/context7-usage/SKILL.md

@@ -1,105 +1,105 @@
----
-name: context7-usage
-description: "Context7 plugin for latest library documentation. Auto-activates when docs, documentation, latest version, official docs, API reference, or library help is needed."
-triggers: [docs, documentation, latest version, official docs, API reference, library help, context7]
-priority: 60
----
-
-# Context7 Usage
-
-Guide for searching latest library/framework documentation using Context7 plugin with subagent isolation.
-
-## Why Subagent Approach?
-
-| Approach | Problem |
-|----------|---------|
-| Direct plugin call | Docs content fills main context, causing bloat |
-| Subagent isolation | Docs queried in separate context, only results returned |
-
-**Benefits:**
-
-- Prevents context bloat during long coding sessions
-- Solves knowledge cutoff problem with latest docs
-- Main context stays focused on implementation
-
-## When to Use
-
-| Situation | Example |
-|-----------|---------|
-| Latest API check | "React 19 use() hook usage" |
-| Version differences | "Next.js 15 changes" |
-| Official docs needed | "Prisma schema syntax" |
-| Migration guide | "Vue 2 → Vue 3 migration" |
-
-## How It Works
-
-```
-User asks library question
-    ↓
-Skill detects docs need
-    ↓
-Spawn docs-researcher subagent (haiku)
-    ↓
-Subagent calls context7 in isolated context
-    ↓
-Returns only relevant info to main context
-```
-
-## Usage
-
-### Automatic (Recommended)
-
-Just ask library/API questions naturally:
-
-```
-"How do I use React 19 use() hook?"
-"What's new in Next.js 15?"
-"Prisma many-to-many relation syntax"
-```
-
-The skill auto-detects and spawns a docs-researcher subagent.
-
-### Manual Command
-
-```
-/context7:docs <library> [query]
-```
-
-Examples:
-
-```
-/context7:docs react hooks
-/context7:docs next.js app router
-/context7:docs prisma relations
-```
-
-## Implementation Pattern
-
-When you detect a library/API documentation need, spawn a subagent:
-
-```
-Task tool call:
-- subagent_type: Explore
-- model: haiku
-- prompt: "Use context7 to find [library] documentation about [topic]. Return only the relevant API usage examples and key points."
-```
-
-The subagent handles the context7 calls and returns a summary, keeping main context clean.
-
-## Fallback Chain
-
-```
-context7 plugin not installed
-    ↓
-Prompt user: /plugin install context7
-    ↓
-If still unavailable: Web Search for official docs
-```
-
-## Installation
-
-If context7 is not installed, guide user:
-
-```bash
-/plugin install context7
-```
+---
+name: context7-usage
+description: "Context7 plugin for latest library documentation. Auto-activates when docs, documentation, latest version, official docs, API reference, or library help is needed."
+triggers: [docs, documentation, latest version, official docs, API reference, library help, context7]
+priority: 60
+---
+
+# Context7 Usage
+
+Guide for searching latest library/framework documentation using Context7 plugin with subagent isolation.
+
+## Why Subagent Approach?
+
+| Approach | Problem |
+|----------|---------|
+| Direct plugin call | Docs content fills main context, causing bloat |
+| Subagent isolation | Docs queried in separate context, only results returned |
+
+**Benefits:**
+
+- Prevents context bloat during long coding sessions
+- Solves knowledge cutoff problem with latest docs
+- Main context stays focused on implementation
+
+## When to Use
+
+| Situation | Example |
+|-----------|---------|
+| Latest API check | "React 19 use() hook usage" |
+| Version differences | "Next.js 15 changes" |
+| Official docs needed | "Prisma schema syntax" |
+| Migration guide | "Vue 2 → Vue 3 migration" |
+
+## How It Works
+
+```
+User asks library question
+    ↓
+Skill detects docs need
+    ↓
+Spawn docs-researcher subagent (haiku)
+    ↓
+Subagent calls context7 in isolated context
+    ↓
+Returns only relevant info to main context
+```
+
+## Usage
+
+### Automatic (Recommended)
+
+Just ask library/API questions naturally:
+
+```
+"How do I use React 19 use() hook?"
+"What's new in Next.js 15?"
+"Prisma many-to-many relation syntax"
+```
+
+The skill auto-detects and spawns a docs-researcher subagent.
+
+### Manual Command
+
+```
+/context7:docs <library> [query]
+```
+
+Examples:
+
+```
+/context7:docs react hooks
+/context7:docs next.js app router
+/context7:docs prisma relations
+```
+
+## Implementation Pattern
+
+When you detect a library/API documentation need, spawn a subagent:
+
+```
+Task tool call:
+- subagent_type: Explore
+- model: haiku
+- prompt: "Use context7 to find [library] documentation about [topic]. Return only the relevant API usage examples and key points."
+```
+
+The subagent handles the context7 calls and returns a summary, keeping main context clean.
+
+## Fallback Chain
+
+```
+context7 plugin not installed
+    ↓
+Prompt user: /plugin install context7
+    ↓
+If still unavailable: Web Search for official docs
+```
+
+## Installation
+
+If context7 is not installed, guide user:
+
+```bash
+/plugin install context7
+```

package/skills/core-capabilities/SKILL.md

@@ -1,164 +1,48 @@
----
-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('{{VIBE_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('{{VIBE_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%/vibe/ 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
+
+## Pre-check (K1)
+
+> Need to call VIBE tools directly or understand orchestrator patterns? For slash commands and workflow, check CLAUDE.md first — it covers `/vibe.spec`, `/vibe.run`, `/vibe.review`, etc.
+
+## Direct Tool Invocation (Not in CLAUDE.md)
+
+Call built-in tools without slash commands:
+
+```bash
+# Semantic code analysis
+node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index.js').then(t => t.findSymbol({symbol: 'UserService'}))"
+node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index.js').then(t => t.analyzeComplexity({filePath: 'src/service.ts'}))"
+
+# Background agent via orchestrator
+node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').then(o => o.launchBackgroundAgent({prompt: '...', agentName: '...'}))"
+
+# Parallel research
+node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').then(o => o.research('topic', ['React']).then(r => console.log(r.content[0].text)))"
+```
+
+## Available Tools
+
+| Category | Tools |
+|----------|-------|
+| Code Analysis | `findSymbol`, `findReferences`, `analyzeComplexity`, `validateCodeQuality` |
+| Memory | `startSession`, `autoSaveContext`, `saveMemory`, `recallMemory`, `listMemories` |
+
+## Context Thresholds
+
+| Threshold | Action |
+|-----------|--------|
+| 70% | `autoSaveContext` checkpoint |
+| 80% | Warning + save |
+| 90% | Critical — `saveMemory` → `/new` → `/vibe.utils --continue` |
+
+## Done Criteria (K4)
+
+- [ ] Tool call executed successfully (non-empty result)
+- [ ] Context saved before reaching 90% threshold