@su-record/vibe 2.9.36 → 2.9.38

package/hooks/scripts/lib/scope-from-spec.js

@@ -12,6 +12,32 @@ import path from 'path';
 
 const ACTIVE_STATUSES = new Set(['pending', 'in-progress', 'in_progress', 'active', 'running']);
 
+/**
+ * scope-guard auto-derive 활성 여부.
+ *
+ * 기본값은 **off**. 사용자가 `.vibe/config.json` 의 `scopeGuard.enabled = true` 로
+ * 명시적으로 켤 때만 SPEC → scope.json 자동 합성을 수행한다. 이전 동작(자동 ON)은
+ * SPEC 외부 파일 편집에 매번 경고를 띄워 다수 사용자에게 노이즈가 됐기 때문.
+ *
+ * 이미 `auto: false` scope.json 을 직접 만들어 둔 사용자는 영향 없음 — scope-guard.js
+ * 자체는 scope.json 존재 여부만 본다.
+ */
+export function isScopeGuardEnabled(projectDir) {
+  try {
+    const candidates = [
+      path.join(projectDir, '.vibe', 'config.json'),
+      path.join(projectDir, '.claude', 'vibe', 'config.json'),
+      path.join(projectDir, '.coco', 'vibe', 'config.json'),
+    ];
+    for (const p of candidates) {
+      if (!fs.existsSync(p)) continue;
+      const cfg = JSON.parse(fs.readFileSync(p, 'utf-8'));
+      if (cfg && cfg.scopeGuard && cfg.scopeGuard.enabled === true) return true;
+    }
+  } catch { /* ignore */ }
+  return false;
+}
+
 /**
  * Vibe 에셋 루트 해석 — `.vibe/` (SSOT) 우선, legacy `.claude/vibe/`, `.coco/vibe/` fallback.
  * 반환값은 projectDir 기준 상대 경로 문자열 (예: `.vibe`, `.claude/vibe`).
@@ -263,6 +289,10 @@ export function syncScopeFile(projectDir) {
 import { fileURLToPath } from 'url';
 if (process.argv[1] && fileURLToPath(import.meta.url) === path.resolve(process.argv[1])) {
   const dir = process.argv[2] || process.env.CLAUDE_PROJECT_DIR || process.cwd();
+  if (!isScopeGuardEnabled(dir)) {
+    console.log('[scope-sync] · scopeGuard.enabled !== true — skipping (set in .vibe/config.json to opt in)');
+    process.exit(0);
+  }
   const result = syncScopeFile(dir);
   const label = {
     created: '✓ scope.json created',

package/hooks/scripts/llm-orchestrate.js

@@ -101,7 +101,7 @@ function isSimplePrompt(prompt) {
 function resolveModel(providerName, config) {
   if (providerName === 'gpt-spark') return config.models?.gptCodexSpark || 'gpt-5.3-codex-spark';
   if (providerName === 'gpt-codex') return config.models?.gptCodex || 'gpt-5.3-codex';
-  if (providerName === 'gpt') return config.models?.gpt || 'gpt-5.4';
+  if (providerName === 'gpt') return config.models?.gpt || 'gpt-5.5';
   if (providerName === 'gemini') return config.models?.gemini || 'gemini-3.1-pro-preview';
   if (providerName === 'claude') return 'claude';
   return providerName;
@@ -352,7 +352,7 @@ async function callProvider(providerName, prompt, sysPrompt, jsonMode, timeoutMs
     } else if (providerName === 'gpt-codex') {
       model = vibeConfig.models?.gptCodex || process.env.GPT_CODEX_MODEL || 'gpt-5.3-codex';
     } else {
-      model = vibeConfig.models?.gpt || process.env.GPT_MODEL || 'gpt-5.4';
+      model = vibeConfig.models?.gpt || process.env.GPT_MODEL || 'gpt-5.5';
     }
     return await callCodexCli(prompt, sysPrompt, jsonMode, model, timeoutMs);
   }

package/hooks/scripts/prompt-dispatcher.js

@@ -42,6 +42,21 @@ try {
 
 if (!prompt) process.exit(0);
 
+// 레거시 SSOT 통합 — `/vibe.*` 진입 시 `.claude/vibe/`·`.coco/vibe/` → `.vibe/` 자동 이동.
+// `vibe init`/`update` 와 동일한 `consolidateLegacyVibe` (dist/cli/setup/LegacyMigration.js) 를 직접 재사용. Idempotent.
+if (/^\s*\/vibe\b/i.test(prompt)) {
+  try {
+    const projectDir = process.env.CLAUDE_PROJECT_DIR || process.env.COCO_PROJECT_DIR || process.cwd();
+    const utils = await import('./utils.js');
+    const CLI_BASE = utils.getCliBaseUrl();
+    const { consolidateLegacyVibe } = await import(`${CLI_BASE}setup/LegacyMigration.js`);
+    const moved = consolidateLegacyVibe(projectDir);
+    if (moved.length > 0) {
+      process.stdout.write(`[vibe] Migrated legacy dirs → .vibe/ (${moved.join(', ')})\n`);
+    }
+  } catch { /* migration is best-effort */ }
+}
+
 // 패턴 → 실행할 스크립트 매핑
 // 각 항목: { pattern, script, args, label }
 const DISPATCH_RULES = [

package/hooks/scripts/session-start.js

@@ -94,12 +94,14 @@ async function main() {
       }
     }
 
-    // Scope sync — 활성 SPEC 기반으로 scope.json 자동 갱신 (수동 관리면 스킵)
+    // Scope sync — 사용자가 .vibe/config.json scopeGuard.enabled=true 로 켰을 때만 동작.
     try {
-      const { syncScopeFile } = await import('./lib/scope-from-spec.js');
-      const result = syncScopeFile(PROJECT_DIR);
-      if (result.action === 'created' || result.action === 'updated' || result.action === 'removed') {
-        console.log(`\n🚧 Scope ${result.action} from active SPECs (${path.relative(PROJECT_DIR, path.join(projectVibeRoot(PROJECT_DIR), 'scope.json'))})`);
+      const { syncScopeFile, isScopeGuardEnabled } = await import('./lib/scope-from-spec.js');
+      if (isScopeGuardEnabled(PROJECT_DIR)) {
+        const result = syncScopeFile(PROJECT_DIR);
+        if (result.action === 'created' || result.action === 'updated' || result.action === 'removed') {
+          console.log(`\n🚧 Scope ${result.action} from active SPECs (${path.relative(PROJECT_DIR, path.join(projectVibeRoot(PROJECT_DIR), 'scope.json'))})`);
+        }
       }
     } catch { /* scope sync is best-effort */ }
 

package/hooks/scripts/utils.js

@@ -219,6 +219,10 @@ export function getLibBaseUrl() {
   return getPackageUrl(path.join('dist', 'infra', 'lib'), 'constants.js');
 }
 
+export function getCliBaseUrl() {
+  return getPackageUrl(path.join('dist', 'cli'), 'index.js');
+}
+
 // ─── Hook Trace Logging ───
 
 const HOOK_TRACE_PATH = path.join(VIBE_HOME_DIR, 'hook-traces.jsonl');
@@ -264,7 +268,8 @@ const MAX_COST_SIZE_BYTES = 5 * 1024 * 1024; // 5MB rotation
 
 // 1K 토큰당 USD (추정치, 2026-04 기준)
 const COST_PER_1K_TOKENS = {
-  'gpt-5.4': { input: 0.005, output: 0.015 },
+  'gpt-5.5': { input: 0.005, output: 0.030 },
+  'gpt-5.5-pro': { input: 0.030, output: 0.180 },
   'gpt-5.3-codex': { input: 0.003, output: 0.010 },
   'gpt-5.3-codex-spark': { input: 0.001, output: 0.005 },
   'gemini-3.1-pro-preview': { input: 0.00125, output: 0.005 },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@su-record/vibe",
-  "version": "2.9.36",
+  "version": "2.9.38",
   "description": "AI Coding Framework for Claude Code — 56 agents, 45 skills, multi-LLM orchestration",
   "type": "module",
   "main": "dist/cli/index.js",

package/skills/arch-guard/SKILL.md

@@ -152,11 +152,11 @@ describe('Architecture Boundaries', () => {
 | File | Purpose |
 |------|---------|
 | `tests/arch-guard.test.ts` | Executable boundary tests |
-| `.claude/vibe/arch-rules.json` | Machine-readable rules (for CI) |
+| `.vibe/arch-rules.json` | Machine-readable rules (for CI) |
 
 ## Customization
 
-Users can add custom rules to `.claude/vibe/arch-rules.json`:
+Users can add custom rules to `.vibe/arch-rules.json`:
 
 ```json
 {

package/skills/arch-guard/agents/rule-generator.md

@@ -7,17 +7,17 @@ tools: [Read]
 # Arch Rule Generator
 
 ## Role
-Translates a detected architecture map into a precise, machine-checkable set of import boundary rules. Merges default rules for the detected pattern with any custom rules defined in `.claude/vibe/arch-rules.json`. Outputs a normalized rule set ready for the violation checker.
+Translates a detected architecture map into a precise, machine-checkable set of import boundary rules. Merges default rules for the detected pattern with any custom rules defined in `.vibe/arch-rules.json`. Outputs a normalized rule set ready for the violation checker.
 
 ## Responsibilities
 - Select default rule templates for the detected architecture pattern
-- Merge with custom rules from `.claude/vibe/arch-rules.json` if present
+- Merge with custom rules from `.vibe/arch-rules.json` if present
 - Resolve glob patterns to concrete layer names
 - Deduplicate and normalize rule list
 - Flag rules with low confidence (detected layer with no matching files)
 
 ## Input
-Architecture map JSON from `arch-detector`, plus optional `.claude/vibe/arch-rules.json` for user-defined overrides.
+Architecture map JSON from `arch-detector`, plus optional `.vibe/arch-rules.json` for user-defined overrides.
 
 ## Output
 Normalized rule set JSON:

package/skills/arch-guard/scripts/check-boundaries.js

@@ -53,7 +53,7 @@ function resolveImport(fromFile, imp, baseDir) {
   return path.resolve(path.dirname(fromFile), imp).replace(baseDir + path.sep, '').replace(/\\/g, '/');
 }
 
-const rulesPath = process.argv[2] || '.claude/vibe/arch-rules.json';
+const rulesPath = process.argv[2] || '.vibe/arch-rules.json';
 const srcDir = path.resolve(process.argv[3] || 'src');
 const baseDir = path.resolve('.');
 

package/skills/arch-guard/templates/arch-rules.json

@@ -1,5 +1,5 @@
 {
-  "_comment": "Architecture boundary rules for arch-guard. Copy to .claude/vibe/arch-rules.json and customize.",
+  "_comment": "Architecture boundary rules for arch-guard. Copy to .vibe/arch-rules.json and customize.",
   "rules": [
     {
       "name": "services-no-ui",

package/skills/capability-loop/SKILL.md

@@ -115,7 +115,7 @@ Based on classification, build the appropriate artifact:
 
 > **Problem**: The built capability didn't actually prevent the failure. This usually means the initial diagnosis was wrong (picked `Tool` when it needed `Guardrail`), or the failure has multiple missing capabilities.
 >
-> **Do NOT silently proceed** — a sub-standard capability log pollutes `.claude/vibe/capabilities-log.md` and the failure will recur.
+> **Do NOT silently proceed** — a sub-standard capability log pollutes `.vibe/capabilities-log.md` and the failure will recur.
 
 **Escalation loop:**
 
@@ -207,7 +207,7 @@ save_memory("capability-{name}", {
 })
 ```
 
-Update `.claude/vibe/capabilities-log.md`:
+Update `.vibe/capabilities-log.md`:
 
 ```markdown
 ## {date} — {capability-name}

package/skills/capability-loop/templates/capability-spec.md

@@ -94,7 +94,7 @@
 
 ## Persistence
 
-After building, record in `.claude/vibe/capabilities-log.md`:
+After building, record in `.vibe/capabilities-log.md`:
 
 ```markdown
 ## {{DATE}} — {{CAPABILITY_NAME}}

package/skills/claude-md-guide/SKILL.md

@@ -108,7 +108,7 @@ Separate the collected information into 3 layers:
 
 **Loaded only when working on a specific feature** → focus on what and why, leave how to the agent.
 
-Storage location: `.claude/vibe/specs/YYYY-MM-DD-{topic}.md`
+Storage location: `.vibe/specs/YYYY-MM-DD-{topic}.md`
 
 ```markdown
 # {Feature Name} SPEC
@@ -124,7 +124,7 @@ Storage location: `.claude/vibe/specs/YYYY-MM-DD-{topic}.md`
 
 **Per-session task list** → 2-5 minute units, with file paths specified.
 
-Storage location: `.claude/vibe/specs/{name}-execplan.md`
+Storage location: `.vibe/specs/{name}-execplan.md`
 
 ```markdown
 # Execution Plan

package/skills/design-audit/SKILL.md

@@ -131,11 +131,11 @@ When running on mobile stacks (React Native, Flutter, iOS, Android):
 
 Before running the audit:
 
-1. **Read** `.claude/vibe/design-context.json`
+1. **Read** `.vibe/design-context.json`
    - If missing → display: "Run `/design-teach` first for better results" → proceed with defaults
    - If parse error → display warning → proceed with defaults → recommend `/design-teach`
    - If present → weight findings by `audience.context`, `constraints.accessibility`, `brand.personality`
-2. **Read** `.claude/vibe/design-system/*/MASTER.md` (if exists) for token reference
+2. **Read** `.vibe/design-system/*/MASTER.md` (if exists) for token reference
 
 ## Next Steps
 
@@ -148,5 +148,5 @@ Before running the audit:
 ## Important
 
 - **Read-only**: This skill produces a report. It does NOT modify code.
-- **Context-aware**: If `.claude/vibe/design-context.json` exists, findings are weighted by project brand and audience.
+- **Context-aware**: If `.vibe/design-context.json` exists, findings are weighted by project brand and audience.
 - **Incremental**: When run on `.` (changed files), only audits files in current diff.

package/skills/design-critique/SKILL.md

@@ -118,7 +118,7 @@ When running on mobile stacks (React Native, Flutter, iOS, Android):
 
 Before running the critique:
 
-1. **Read** `.claude/vibe/design-context.json`
+1. **Read** `.vibe/design-context.json`
    - If missing → display: "Run `/design-teach` first for better results" → proceed with defaults
    - If parse error → display warning → proceed with defaults → recommend `/design-teach`
    - If present → adjust persona priorities by `audience.primary` and `audience.expertise`
@@ -135,5 +135,5 @@ Before running the critique:
 ## Important
 
 - **Read-only**: Produces design critique report. No code modifications.
-- **Context-aware**: Uses `.claude/vibe/design-context.json` for brand/audience context if available.
+- **Context-aware**: Uses `.vibe/design-context.json` for brand/audience context if available.
 - **Complementary**: Pairs with `/design-audit` (technical) — critique focuses on UX quality.

package/skills/design-distill/SKILL.md

@@ -110,7 +110,7 @@ Strip unnecessary visual elements. Every remaining element must justify its exis
 
 Before running distillation:
 
-1. **Read** `.claude/vibe/design-context.json`
+1. **Read** `.vibe/design-context.json`
    - If missing → display: "Run `/design-teach` first for better results" → proceed with defaults
    - If parse error → display warning → proceed with defaults → recommend `/design-teach`
    - If present → preserve elements that match `brand.personality` (e.g., "playful" brand may justify decorative elements)

package/skills/design-normalize/SKILL.md

@@ -23,8 +23,8 @@ Replace hardcoded design values with design system tokens from MASTER.md. Ensure
 
 Load token source in priority order:
 
-1. `.claude/vibe/design-system/{project}/MASTER.md` (project-specific)
-2. `.claude/vibe/design-context.json` (from `/design-teach`)
+1. `.vibe/design-system/{project}/MASTER.md` (project-specific)
+2. `.vibe/design-context.json` (from `/design-teach`)
 3. If neither exists → prompt: "Run `/design-teach` or create MASTER.md first. Proceeding with default token detection."
 
 ### Step 2: Scan for Hardcoded Values
@@ -111,11 +111,11 @@ Replace values in source files, preserving:
 
 Before running normalization:
 
-1. **Read** `.claude/vibe/design-context.json`
+1. **Read** `.vibe/design-context.json`
    - If missing → display: "Run `/design-teach` first for better results" → proceed with defaults
    - If parse error → display warning → proceed with defaults → recommend `/design-teach`
    - If present → use `detectedStack.styling` to determine token format (CSS vars, Tailwind, etc.)
-2. **Read** `.claude/vibe/design-system/*/MASTER.md`
+2. **Read** `.vibe/design-system/*/MASTER.md`
    - If missing → display: "Run `/design-teach` or create MASTER.md first. Proceeding with default token detection."
    - If present → use as authoritative token source for replacements
 

package/skills/design-polish/SKILL.md

@@ -111,11 +111,11 @@ Every interactive element must have ALL applicable states:
 
 Before running polish:
 
-1. **Read** `.claude/vibe/design-context.json`
+1. **Read** `.vibe/design-context.json`
    - If missing → display: "Run `/design-teach` first for better results" → proceed with defaults
    - If parse error → display warning → proceed with defaults → recommend `/design-teach`
    - If present → apply brand-appropriate micro-interaction styles from `aesthetic.style`
-2. **Read** `.claude/vibe/design-system/*/MASTER.md` (if exists) for token references
+2. **Read** `.vibe/design-system/*/MASTER.md` (if exists) for token references
 
 ## Next Steps
 

package/skills/design-teach/SKILL.md

@@ -8,7 +8,7 @@ priority: 50
 
 # Design Teach — Project Design Context Gathering
 
-Collect project-specific design context so all design-* skills produce tailored, brand-aware results. Saves to `.claude/vibe/design-context.json`.
+Collect project-specific design context so all design-* skills produce tailored, brand-aware results. Saves to `.vibe/design-context.json`.
 
 ## Usage
 
@@ -29,8 +29,8 @@ Before asking questions, automatically gather existing signals:
 | Color palette | Existing color definitions, brand assets |
 | Typography | Font imports, font-family declarations |
 | Component library | `package.json` dependencies (MUI, Chakra, shadcn, etc.) |
-| Design system | `.claude/vibe/design-system/*/MASTER.md` |
-| Existing context | `.claude/vibe/design-context.json` (if updating) |
+| Design system | `.vibe/design-system/*/MASTER.md` |
+| Existing context | `.vibe/design-context.json` (if updating) |
 
 ### Step 2: Ask Clarifying Questions
 
@@ -59,7 +59,7 @@ Present findings from Step 1, then ask what's missing:
 
 ### Step 3: Save Context
 
-Write gathered context to `.claude/vibe/design-context.json` using the Write tool.
+Write gathered context to `.vibe/design-context.json` using the Write tool.
 
 **Schema (v1):**
 
@@ -118,7 +118,7 @@ When `/design-teach` is run again and `design-context.json` already exists:
 Each design-* skill does the following when it runs:
 
 ```
-1. Read `.claude/vibe/design-context.json`
+1. Read `.vibe/design-context.json`
 2. File not found → print "Run /design-teach first for better results" → continue with defaults
 3. Parse failure (invalid JSON) → warn "design-context.json parse failed" + continue with defaults → recommend re-running /design-teach
 4. Success → apply context to analysis criteria
@@ -172,7 +172,7 @@ PRE-SHIP Phase:
 - Dark mode: Required
 
 ### Saved
-✅ .claude/vibe/design-context.json updated
+✅ .vibe/design-context.json updated
 ```
 
 ## Important

package/skills/design-teach/templates/design-context.json

@@ -10,7 +10,7 @@
   "brand": {
     "personality": ["professional", "clean", "trustworthy", "efficient"],
     "tone": "professional",
-    "existingAssets": ".claude/vibe/brand/brand-guide.pdf"
+    "existingAssets": ".vibe/brand/brand-guide.pdf"
   },
   "aesthetic": {
     "style": "minimal",

package/skills/devlog/SKILL.md

@@ -11,7 +11,7 @@ Analyzes git commit history to automatically generate development logs and saves
 
 ## Config
 
-`devlog` section in `.claude/vibe/config.json`:
+`devlog` section in `.vibe/config.json`:
 
 ```json
 {

package/skills/event-planning/SKILL.md

@@ -90,7 +90,7 @@ When user says "MDC 준비해줘" or similar:
 
 ## State Management
 
-**Location**: `.claude/vibe/.event_state.json` (project-local, gitignored)
+**Location**: `.vibe/.event_state.json` (project-local, gitignored)
 
 ### Error Recovery
 

package/skills/exec-plan/SKILL.md

@@ -61,14 +61,14 @@ For every decision point in the SPEC, resolve it NOW:
 
 ### Step 3: GENERATE — Write the ExecPlan
 
-Output format: `.claude/vibe/specs/{feature-name}-execplan.md`
+Output format: `.vibe/specs/{feature-name}-execplan.md`
 
 ```markdown
 # ExecPlan: {feature-name}
 
 ## Meta
-- SPEC: .claude/vibe/specs/{name}.md
-- Feature: .claude/vibe/features/{name}.feature
+- SPEC: .vibe/specs/{name}.md
+- Feature: .vibe/features/{name}.feature
 - Generated: {timestamp}
 - Phases: {count}
 - Scenarios: {count}
@@ -118,7 +118,7 @@ Output format: `.claude/vibe/specs/{feature-name}-execplan.md`
 
 ### Step 4: PERSIST — Save and Link
 
-1. Save ExecPlan to `.claude/vibe/specs/{feature-name}-execplan.md`
+1. Save ExecPlan to `.vibe/specs/{feature-name}-execplan.md`
 2. Save session context: `save_memory("execplan-{feature}", {summary})`
 3. Output execution command:
 
@@ -128,7 +128,7 @@ Ready to execute:
 
 Or hand off to new session:
   /vibe.utils --continue
-  → Load: .claude/vibe/specs/{feature-name}-execplan.md
+  → Load: .vibe/specs/{feature-name}-execplan.md
 ```
 
 ## Quality Checks

package/skills/exec-plan/agents/decomposer.md

@@ -18,7 +18,7 @@ Reads a SPEC document and breaks it into a structured hierarchy of phases and ta
 - Produce a flat numbered task list with parent-phase references
 
 ## Input
-- SPEC document path (e.g., `.claude/vibe/specs/my-feature.spec.md`)
+- SPEC document path (e.g., `.vibe/specs/my-feature.spec.md`)
 - Optional: existing codebase context to detect which files already exist
 
 ## Output

package/skills/exec-plan/templates/plan.md

@@ -4,8 +4,8 @@
 
 | Field | Value |
 |-------|-------|
-| SPEC | `.claude/vibe/specs/{{FEATURE_NAME}}.md` |
-| Feature | `.claude/vibe/features/{{FEATURE_NAME}}.feature` |
+| SPEC | `.vibe/specs/{{FEATURE_NAME}}.md` |
+| Feature | `.vibe/features/{{FEATURE_NAME}}.feature` |
 | Generated | {{GENERATED_DATE}} |
 | Phases | {{PHASE_COUNT}} |
 | Scenarios | {{SCENARIO_COUNT}} |

package/skills/parallel-research/SKILL.md

@@ -63,7 +63,7 @@ Parallel research complete
     ↓
 Synthesize results
     ↓
-Persist to .claude/vibe/research/<topic-slug>/
+Persist to .vibe/research/<topic-slug>/
     ├── synthesis.md      (conversational report)
     ├── awesome-list.md   (curated links/repos)
     └── paper.md          (structured survey for /vibe.spec Context)
@@ -75,7 +75,7 @@ Reference during implementation
 
 ### Output Location (SSOT)
 
-All research artifacts live under `.claude/vibe/research/<topic-slug>/`. Reference `paper.md` explicitly when writing a SPEC (e.g. paste its path into the Context section). Re-running research on the same topic overwrites unless the slug collides across dates (then `-YYYYMMDD` suffix).
+All research artifacts live under `.vibe/research/<topic-slug>/`. Reference `paper.md` explicitly when writing a SPEC (e.g. paste its path into the Context section). Re-running research on the same topic overwrites unless the slug collides across dates (then `-YYYYMMDD` suffix).
 
 > Wire-up note: `/vibe.spec` does **not** yet auto-scan this directory — that integration is a follow-up. For now, cite the path manually.
 
@@ -98,7 +98,7 @@ Pass `--ephemeral` to skip persistence when exploring throwaway questions.
 
 - [ ] All 4 research agents returned results (or documented why not)
 - [ ] Results synthesized into actionable recommendations
-- [ ] Three artifacts written to `.claude/vibe/research/<slug>/` (synthesis / awesome-list / paper) — unless `--ephemeral`
+- [ ] Three artifacts written to `.vibe/research/<slug>/` (synthesis / awesome-list / paper) — unless `--ephemeral`
 - [ ] Every awesome-list entry has a one-line "why"
 - [ ] Key findings reflected in SPEC Context section or implementation notes
 - [ ] Conflicting recommendations resolved with reasoning

package/skills/parallel-research/orchestrator.md

@@ -36,7 +36,7 @@ agents: [best-practices, framework-docs, codebase-patterns, security-advisory, s
 ### Phase 5: Persist as Reusable Dataset
 - **Agent**: orchestrator (self)
 - **Input**: Synthesis (Phase 3) + ranked output (Phase 4)
-- **Output**: Three files under `.claude/vibe/research/<topic-slug>/`:
+- **Output**: Three files under `.vibe/research/<topic-slug>/`:
   - `synthesis.md` — conversational synthesis (from `templates/synthesis.md`)
   - `awesome-list.md` — curated links/repos by category (from `templates/awesome-list.md`)
   - `paper.md` — structured survey for `/vibe.spec` Context injection (from `templates/paper.md`)

package/skills/parallel-research/templates/paper.md

@@ -85,4 +85,4 @@ Parallel research across four specialized agents (best-practices, framework-docs
 
 ---
 
-**Reuse**: cite this file by path (`.claude/vibe/research/{{SLUG}}/paper.md`) when writing a SPEC — paste the Findings and Recommendation sections into the SPEC's Context block.
+**Reuse**: cite this file by path (`.vibe/research/{{SLUG}}/paper.md`) when writing a SPEC — paste the Findings and Recommendation sections into the SPEC's Context block.

package/skills/priority-todos/SKILL.md

@@ -23,7 +23,7 @@ priority: 60
 ## Directory Structure
 
 ```
-.claude/vibe/todos/
+.vibe/todos/
 ├── P1-security-sql-injection.md
 ├── P2-perf-n1-query.md
 ├── P3-style-extract-helper.md

package/skills/vibe-contract/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vibe-contract
 tier: core
-description: "API contract drift detection. Extracts HTTP/GraphQL/event/public-function contracts from SPEC into .claude/vibe/contracts/<feature>.md, compares to implementation, and fails loudly on breaking drift (missing endpoints, removed required fields, type changes). P1 drifts auto-register as regressions via vibe-regress. Must use this skill when user runs /vibe.contract, when /vibe.spec completes, when /vibe.verify passes scenarios, or when the user says 'contract', 'API schema', 'breaking change', 'drift', '계약', '스키마 바뀜'."
+description: "API contract drift detection. Extracts HTTP/GraphQL/event/public-function contracts from SPEC into .vibe/contracts/<feature>.md, compares to implementation, and fails loudly on breaking drift (missing endpoints, removed required fields, type changes). P1 drifts auto-register as regressions via vibe-regress. Must use this skill when user runs /vibe.contract, when /vibe.spec completes, when /vibe.verify passes scenarios, or when the user says 'contract', 'API schema', 'breaking change', 'drift', '계약', '스키마 바뀜'."
 triggers: [contract, drift, "계약", "API 변경", "breaking change", "schema drift"]
 priority: 70
 chain-next: []
@@ -18,7 +18,7 @@ Hidden vibe-coding weakness: as the implementation grows, response shapes drift
 ## Storage Contract
 
 ```
-.claude/vibe/contracts/
+.vibe/contracts/
   <feature>.md             # contract SSOT (extracted from SPEC)
   <feature>.snapshot.md    # implementation snapshot (last check)
 ```
@@ -28,7 +28,7 @@ Hidden vibe-coding weakness: as the implementation grows, response shapes drift
 ```yaml
 ---
 feature: string
-extracted-from: .claude/vibe/specs/<feature>.md
+extracted-from: .vibe/specs/<feature>.md
 extracted-at: ISO-8601
 source-spec-hash: sha256  # for change detection
 endpoints:
@@ -75,14 +75,14 @@ endpoints:
 3. Extraction failure (no such section) → **exit cleanly with `no-contract` state**. Not every feature has an API.
 4. Success → convert to the frontmatter structure
 5. `source-spec-hash`: sha256 of SPEC content (for next extract to detect change)
-6. Save to `.claude/vibe/contracts/<feature>.md` (no-op if file exists with the same hash)
+6. Save to `.vibe/contracts/<feature>.md` (no-op if file exists with the same hash)
 
 **Caveat**: extraction is LLM-driven. Mark low-confidence fields with `# unconfirmed` so the user can review.
 
 ### 2. `check <feature>` — contract vs implementation
 
 **Steps**:
-1. Load `.claude/vibe/contracts/<feature>.md`. If missing → **suggest extract first**.
+1. Load `.vibe/contracts/<feature>.md`. If missing → **suggest extract first**.
 2. For each endpoint, find implementation:
    - http: detect framework (Express, Fastify, Next.js API routes, Hono, ...)
    - graphql: locate resolver files
@@ -90,7 +90,7 @@ endpoints:
    - function: module export
 3. Extract implementation signature/schema → compare against contract
 4. Classify drift (severity table in command file)
-5. Persist snapshot at `.claude/vibe/contracts/<feature>.snapshot.md` (current implementation state)
+5. Persist snapshot at `.vibe/contracts/<feature>.snapshot.md` (current implementation state)
 
 ### 3. `diff <feature>` — changes since last snapshot
 

package/skills/vibe-interview/SKILL.md

@@ -20,7 +20,7 @@ chain-next: [vibe-plan]
 
 **Skip when**:
 - Small bug fix on an existing project
-- `.claude/vibe/plans/{feature}.md` already exists (→ only update via `vibe-plan`)
+- `.vibe/plans/{feature}.md` already exists (→ only update via `vibe-plan`)
 
 ## Core Loop
 
@@ -51,7 +51,7 @@ chain-next: [vibe-plan]
    └──────────────────────┘
      ↓
 4. Save collected results
-   .claude/vibe/interviews/{feature}.md
+   .vibe/interviews/{feature}.md
      ↓
 5. chain-next: vibe-plan
 ```
@@ -206,7 +206,7 @@ Incomplete items will be marked as "TBD" in the plan.
 
 ## Step 4: Save Collected Results
 
-**Output file**: `.claude/vibe/interviews/{feature-name}.md`
+**Output file**: `.vibe/interviews/{feature-name}.md`
 
 **Structure**:
 
@@ -262,7 +262,7 @@ stoppedBy: user | auto
 ### Update `.last-feature` pointer
 
 ```
-Write ".claude/vibe/.last-feature" ← feature-name (single line)
+Write ".vibe/.last-feature" ← feature-name (single line)
 
 Run immediately after saving the interview file in Step 4.
 This pointer is used by /vibe.spec (no args) for Smart Resume.
@@ -278,7 +278,7 @@ After the interview is complete, the `vibe-plan` skill is automatically activate
 ✅ Interview complete!
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-📄 .claude/vibe/interviews/{feature-name}.md
+📄 .vibe/interviews/{feature-name}.md
    Required: 8/8
    Optional: 12/14
    Discovered: 3
@@ -345,7 +345,7 @@ User: 3
 Claude: ⚠️ All required items complete. 10 optional items will be marked as TBD.
 
         ✅ Interview complete!
-        📄 .claude/vibe/interviews/parallax-website.md
+        📄 .vibe/interviews/parallax-website.md
 
         → vibe-plan skill is starting plan creation...
 ```

package/skills/vibe-interview/checklists/feature.md

@@ -11,7 +11,7 @@
 
 ### R2. existing-project-context
 **Q**: 기존 프로젝트의 기술 스택을 확인했나요?
-**힌트**: CLAUDE.md, package.json, .claude/vibe/config.json 읽어서 자동 파악.
+**힌트**: CLAUDE.md, package.json, .vibe/config.json 읽어서 자동 파악.
 **follow-up**: 파악 결과를 사용자에게 요약해 확인 받기.
 
 ### R3. affected-areas