@su-record/vibe 2.9.36 → 2.9.38

package/skills/vibe-plan/SKILL.md

@@ -13,7 +13,7 @@ chain-next: [vibe-spec, vibe-figma]
 
 ## When to Use
 
-- `vibe-interview` has just completed and `.claude/vibe/interviews/{feature}.md` exists
+- `vibe-interview` has just completed and `.vibe/interviews/{feature}.md` exists
 - The user requests "write me a plan document" or "clean up the interview"
 - Need to convert an external PRD/wireframe into the vibe plan document format
 
@@ -24,7 +24,7 @@ chain-next: [vibe-spec, vibe-figma]
 
 ```
 1. Read interview file
-   .claude/vibe/interviews/{feature}.md
+   .vibe/interviews/{feature}.md
      ↓
 2. Load template
    ~/.claude/vibe/templates/plan-template.md
@@ -40,7 +40,7 @@ chain-next: [vibe-spec, vibe-figma]
    type ∈ {api, library, feature-data} → omit
      ↓
 5. Save plan document
-   .claude/vibe/plans/{feature}.md
+   .vibe/plans/{feature}.md
      ↓
 6. Handoff guidance
    Next steps: /vibe.spec, /vibe.figma, parallel
@@ -49,7 +49,7 @@ chain-next: [vibe-spec, vibe-figma]
 ## Step 1: Read Interview File
 
 ```
-Read .claude/vibe/interviews/{feature-name}.md
+Read .vibe/interviews/{feature-name}.md
 ```
 
 Extract `type`, `status`, `requiredCollected`, `optionalCollected`, etc. from the frontmatter.
@@ -104,7 +104,7 @@ Edit anything that doesn't match your intent.
 ### `.last-feature` Pointer Update
 
 ```
-Write ".claude/vibe/.last-feature" ← feature-name (one line)
+Write ".vibe/.last-feature" ← feature-name (one line)
 Run immediately after extracting the feature name from the interview file.
 No-op if the value is already the same.
 ```
@@ -180,7 +180,7 @@ else:  # api, library, feature-data
 
 ## Step 5: Save Plan Document
 
-**Output path**: `.claude/vibe/plans/{feature-name}.md`
+**Output path**: `.vibe/plans/{feature-name}.md`
 
 **Frontmatter**:
 
@@ -191,7 +191,7 @@ type: {website | webapp | mobile | api | library | feature}
 status: draft
 createdAt: {ISO-timestamp}
 lastUpdated: {ISO-timestamp}
-source: .claude/vibe/interviews/{feature-name}.md
+source: .vibe/interviews/{feature-name}.md
 downstream: [spec, figma]  # or [spec] for non-UI
 ---
 ```
@@ -213,7 +213,7 @@ After saving the plan document, guide the user on next steps:
 ✅ Plan document complete!
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-📄 .claude/vibe/plans/{feature-name}.md
+📄 .vibe/plans/{feature-name}.md
    Sections: {N} written
    TBD: {M} (to be decided later)
 
@@ -222,7 +222,7 @@ Type: {type}
 Next steps:
 
   [UI project: website/webapp/mobile]
-  1. /vibe.spec ".claude/vibe/plans/{feature-name}.md"
+  1. /vibe.spec ".vibe/plans/{feature-name}.md"
      → Write code spec → /vibe.run implementation
   2. /vibe.figma
      → Figma design → FE UI code
@@ -230,7 +230,7 @@ Next steps:
      → Feature + Design → website prototype
 
   [Non-UI: api/library]
-  1. /vibe.spec ".claude/vibe/plans/{feature-name}.md"
+  1. /vibe.spec ".vibe/plans/{feature-name}.md"
      → Code spec → /vibe.run implementation
 
 Where would you like to start?

package/skills/vibe-regress/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vibe-regress
 tier: core
-description: "Regression test auto-evolution. Registers bugs (auto from /vibe.verify failures or manual), generates preventive vitest/jest files from bug records, clusters repeated patterns (3+ same root-cause-tag) into shared tests, and imports historical `fix:` commits from git log. Storage: .claude/vibe/regressions/<slug>.md. Must use this skill when user runs /vibe.regress, when /vibe.verify produces a failure, or when the user says 'don't let this happen again' / 'regression test' / '회귀 테스트'."
+description: "Regression test auto-evolution. Registers bugs (auto from /vibe.verify failures or manual), generates preventive vitest/jest files from bug records, clusters repeated patterns (3+ same root-cause-tag) into shared tests, and imports historical `fix:` commits from git log. Storage: .vibe/regressions/<slug>.md. Must use this skill when user runs /vibe.regress, when /vibe.verify produces a failure, or when the user says 'don't let this happen again' / 'regression test' / '회귀 테스트'."
 triggers: [regress, regression, "회귀", "다시는", "반복 버그", "fix commit"]
 priority: 70
 chain-next: []
@@ -18,7 +18,7 @@ A classic vibe-coding weakness: LLMs reintroduce bugs of the same class. Regress
 ## Storage Contract
 
 ```
-.claude/vibe/regressions/
+.vibe/regressions/
   <bug-slug>.md       # one file per bug
   _cluster-<tag>.md   # shared-test design produced by `cluster`
 ```
@@ -69,7 +69,7 @@ Most calls are automatic; manual use is rare (bugs found outside `/vibe.verify`,
    - Fix description
 4. `root-cause-tag` is **inferred from the allowed set, then confirmed with the user**. If unclear → `other`.
 5. Generate slug: kebab-case keywords from the symptom; on collision append `-2`
-6. Write `.claude/vibe/regressions/<slug>.md` (status: `open`)
+6. Write `.vibe/regressions/<slug>.md` (status: `open`)
 
 ### 2. `generate <slug>` — generate preventive test
 
@@ -106,7 +106,7 @@ cart-stock-race-double-deduct     cart      concurrency open             1d
 
 **Steps**:
 1. `git log --grep='^fix:' --format='%H|%s|%ci' --since=<last-import-date>`
-   - `last-import-date` lives in `.claude/vibe/regressions/.import-cursor` (defaults to 90 days ago)
+   - `last-import-date` lives in `.vibe/regressions/.import-cursor` (defaults to 90 days ago)
 2. For each commit:
    - If a bug file with the same `fix-commit` already exists → **skip**
    - Otherwise infer symptom + root-cause-tag from message/diff (LLM call)
@@ -152,7 +152,7 @@ Load skill `vibe-regress` with: register --from-verify
 
 At the start of `/vibe.run "<feature>"`:
 
-1. Filter `.claude/vibe/regressions/*.md` for `feature: <feature-name>` + `status != resolved`
+1. Filter `.vibe/regressions/*.md` for `feature: <feature-name>` + `status != resolved`
 2. If any open items:
    ```
    ⚠️  Open regressions for this feature:

package/skills/vibe-regress/templates/bug.md

@@ -35,7 +35,7 @@ feature: {{FEATURE}}
 
 ## Related
 
-- Feature: [.claude/vibe/features/{{FEATURE}}.feature](../../features/{{FEATURE}}.feature)
+- Feature: [.vibe/features/{{FEATURE}}.feature](../../features/{{FEATURE}}.feature)
 - Fix commit: `{{FIX_COMMIT}}`
 - Regression test: `{{TEST_PATH}}`
 

package/skills/vibe-regress/templates/test-jest.md

@@ -4,7 +4,7 @@
  * Symptom: {{SYMPTOM}}
  * Root cause tag: {{ROOT_CAUSE_TAG}}
  * Fix commit: {{FIX_COMMIT}}
- * Source record: .claude/vibe/regressions/{{SLUG}}.md
+ * Source record: .vibe/regressions/{{SLUG}}.md
  *
  * DO NOT delete this test when the bug is fixed — it exists to prevent the
  * same bug from being reintroduced. Update only if the reproduction steps

package/skills/vibe-regress/templates/test-vitest.md

@@ -4,7 +4,7 @@
  * Symptom: {{SYMPTOM}}
  * Root cause tag: {{ROOT_CAUSE_TAG}}
  * Fix commit: {{FIX_COMMIT}}
- * Source record: .claude/vibe/regressions/{{SLUG}}.md
+ * Source record: .vibe/regressions/{{SLUG}}.md
  *
  * DO NOT delete this test when the bug is fixed — it exists to prevent the
  * same bug from being reintroduced. Update only if the reproduction steps

package/skills/vibe-spec/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vibe-spec
 tier: core
-description: "Create an AI-executable PTCF-structured SPEC document through conversational requirements gathering, parallel research (GPT/Gemini/Claude agents), PTCF writing, ambiguity scan, and 100-point quality gate (loops until perfect or stuck). Produces .claude/vibe/specs/{feature}.md + matching .claude/vibe/features/{feature}.feature (BDD). Must use this skill when the user says 'write spec', 'create spec', '/vibe.spec', or when a plan document exists and is ready for code specification."
+description: "Create an AI-executable PTCF-structured SPEC document through conversational requirements gathering, parallel research (GPT/Gemini/Claude agents), PTCF writing, ambiguity scan, and 100-point quality gate (loops until perfect or stuck). Produces .vibe/specs/{feature}.md + matching .vibe/features/{feature}.feature (BDD). Must use this skill when the user says 'write spec', 'create spec', '/vibe.spec', or when a plan document exists and is ready for code specification."
 triggers: [spec, SPEC, 명세, "코드 명세", "구현 명세", "write spec", "create spec", PTCF]
 priority: 85
 chain-next: [vibe-spec-review]
@@ -225,7 +225,7 @@ $ git checkout -b feature/login-page
 **`.last-feature` pointer update** (immediately after Git branch setup):
 
 ```
-Write ".claude/vibe/.last-feature" ← feature-name (single line)
+Write ".vibe/.last-feature" ← feature-name (single line)
 Execute at the point when the feature name is finalized.
 No-op if the value is already the same.
 ```
@@ -350,7 +350,7 @@ const response = parseUserResponse(question, "1, 2, 4");
 Reference documents are automatically generated in `config.json` based on the stack detected during `vibe init`:
 
 ```json
-// .claude/vibe/config.json
+// .vibe/config.json
 {
   "language": "ko",
   "stacks": [
@@ -376,14 +376,14 @@ Reference documents are automatically generated in `config.json` based on the st
 
 **Workflow:**
 
-1. Read `.claude/vibe/config.json`
+1. Read `.vibe/config.json`
 2. Extract `references.languages[]` paths
 3. Read each language document for stack-specific guidelines
 
 **Example:**
 ```bash
 # 1. Check references in config.json
-Read .claude/vibe/config.json
+Read .vibe/config.json
 
 # 2. Reference documents specified in references.languages
 Read ~/.claude/vibe/languages/typescript-react.md
@@ -401,13 +401,13 @@ Before spawning any research agents, check for a prior persisted dataset:
 
 ```bash
 # Slug = kebab-case of the feature/topic, max 50 chars
-ls .claude/vibe/research/<slug>/paper.md 2>/dev/null
+ls .vibe/research/<slug>/paper.md 2>/dev/null
 ```
 
 **If `paper.md` exists:**
-1. Read `.claude/vibe/research/<slug>/paper.md`
-2. Read `.claude/vibe/research/<slug>/awesome-list.md` (if present)
-3. Inject the **Findings**, **Recommendation**, and **Security considerations** sections verbatim into SPEC Context, prefixed with `> Source: .claude/vibe/research/<slug>/paper.md (cached {{FILE_MTIME}})`
+1. Read `.vibe/research/<slug>/paper.md`
+2. Read `.vibe/research/<slug>/awesome-list.md` (if present)
+3. Inject the **Findings**, **Recommendation**, and **Security considerations** sections verbatim into SPEC Context, prefixed with `> Source: .vibe/research/<slug>/paper.md (cached {{FILE_MTIME}})`
 4. **Skip step 3** (parallel research) entirely — do not re-run GPT/Gemini/Claude agents
 5. Print: `✅ Research cache hit: <slug> (saved ~30s of LLM calls)`
 
@@ -436,7 +436,7 @@ Proceed to step 3. After step 3 completes, the synthesizer **must** write the 3
 6. **DO NOT** create SECURITY_*.md, RESEARCH_*.md, SUMMARY_*.md files
 7. **DO NOT** use Write tool during research phase
 8. **ALL research results** must be returned as text output only
-9. **Files are ONLY created** in Step 4 (SPEC) and Step 5 (Feature) in `.claude/vibe/` directory
+9. **Files are ONLY created** in Step 4 (SPEC) and Step 5 (Feature) in `.vibe/` directory
 
 **When to trigger:**
 1. ✅ Feature type decided (e.g., "passkey authentication")
@@ -520,7 +520,7 @@ node "[LLM_SCRIPT]" gemini orchestrate-json "Security advisories for passkey aut
 ### 3.2 UI/UX Design Intelligence (Auto-triggered)
 
 > **Condition**: Auto-executes when UI/UX keywords are present in the SPEC context (website, landing, dashboard, app, e-commerce, portfolio, SaaS, mobile app, web app, UI, UX, frontend, design)
-> **Disable**: Set `"uiUxAnalysis": false` in `.claude/vibe/config.json`
+> **Disable**: Set `"uiUxAnalysis": false` in `.vibe/config.json`
 
 **When UI/UX keywords are detected, run 3 agents sequentially in parallel with research:**
 
@@ -540,7 +540,7 @@ node "[LLM_SCRIPT]" gemini orchestrate-json "Security advisories for passkey aut
 1. **① ui-industry-analyzer** — Run as Task(haiku) agent:
 ```text
 Task(subagent_type="ui-industry-analyzer",
-  prompt="Analyze product: [USER_DESCRIPTION]. Use core_ui_search to detect category, style priority, color mood, typography mood. Save result to .claude/vibe/design-system/{project}/analysis-result.json")
+  prompt="Analyze product: [USER_DESCRIPTION]. Use core_ui_search to detect category, style priority, color mood, typography mood. Save result to .vibe/design-system/{project}/analysis-result.json")
 ```
 
 2. **②③ parallel execution** — Using ①'s result as input:
@@ -559,7 +559,7 @@ Task(subagent_type="ui-layout-architect",
 ### Design System (Auto-generated)
 - Category: {① category}
 - Style: {① style_priority}
-- MASTER.md: .claude/vibe/design-system/{project}/MASTER.md
+- MASTER.md: .vibe/design-system/{project}/MASTER.md
 - Layout: {③ pattern + sections}
 ```
 
@@ -567,13 +567,13 @@ Task(subagent_type="ui-layout-architect",
 
 > The "no Write during research" rule from step 3 does **not** apply here — research is done; artifacts are safe to persist.
 
-After parallel research + UI/UX intelligence complete, before writing the SPEC, save the merged research to `.claude/vibe/research/<slug>/`:
+After parallel research + UI/UX intelligence complete, before writing the SPEC, save the merged research to `.vibe/research/<slug>/`:
 
 1. Compute slug: kebab-case of feature name, max 50 chars
 2. Write **three files** using templates from `parallel-research/templates/`:
-   - `.claude/vibe/research/<slug>/synthesis.md` — raw merged findings (all agent outputs)
-   - `.claude/vibe/research/<slug>/awesome-list.md` — curated links/repos/patterns (every entry needs a one-line "why"; drop entries without one)
-   - `.claude/vibe/research/<slug>/paper.md` — structured survey (Abstract → Background → Method → Findings → Recommendation → Security → References)
+   - `.vibe/research/<slug>/synthesis.md` — raw merged findings (all agent outputs)
+   - `.vibe/research/<slug>/awesome-list.md` — curated links/repos/patterns (every entry needs a one-line "why"; drop entries without one)
+   - `.vibe/research/<slug>/paper.md` — structured survey (Abstract → Background → Method → Findings → Recommendation → Security → References)
 3. Include a frontmatter header in `paper.md` with a `stack:` field so step 2.9 can detect stack drift
 4. If the directory already exists (user passed `--refresh-research`), overwrite
 
@@ -599,13 +599,13 @@ This makes the next `/vibe.spec` (or future `/vibe.research`) invocation on the
 **Auto-split output (SPEC + Feature files must match):**
 
 ```
-.claude/vibe/specs/{feature-name}/
+.vibe/specs/{feature-name}/
 ├── _index.md           # Master SPEC
 ├── phase-1-setup.md
 ├── phase-2-core.md
 └── ...
 
-.claude/vibe/features/{feature-name}/
+.vibe/features/{feature-name}/
 ├── _index.feature      # Master Feature
 ├── phase-1-setup.feature
 ├── phase-2-core.feature
@@ -640,7 +640,7 @@ This makes the next `/vibe.spec` (or future `/vibe.research`) invocation on the
 ```markdown
 # Feature: {feature-name} (Master)
 
-**Master SPEC**: `.claude/vibe/specs/{feature-name}/_index.md`
+**Master SPEC**: `.vibe/specs/{feature-name}/_index.md`
 
 ## Sub-Features
 
@@ -657,7 +657,7 @@ This makes the next `/vibe.spec` (or future `/vibe.research`) invocation on the
 
 **Small scope (default):**
 
-Create `.claude/vibe/specs/{feature-name}.md`:
+Create `.vibe/specs/{feature-name}.md`:
 
 ```markdown
 ---
@@ -756,7 +756,7 @@ Define AI role and expertise for implementation
 
 #### 5.1 Single File (Small Scope)
 
-Create `.claude/vibe/features/{feature-name}.feature`:
+Create `.vibe/features/{feature-name}.feature`:
 
 **Creation rules:**
 1. Convert each SPEC Acceptance Criteria → one Scenario
@@ -766,7 +766,7 @@ Create `.claude/vibe/features/{feature-name}.feature`:
 ```markdown
 # Feature: {feature-name}
 
-**SPEC**: `.claude/vibe/specs/{feature-name}.md`
+**SPEC**: `.vibe/specs/{feature-name}.md`
 
 ## User Story
 **As a** {user}
@@ -798,7 +798,7 @@ Scenario: {title}
 When SPEC is split into phases, Feature files MUST also be split:
 
 ```
-.claude/vibe/features/{feature-name}/
+.vibe/features/{feature-name}/
 ├── _index.feature        # Master: links to all phase features
 ├── phase-1-setup.feature # Scenarios for phase-1-setup.md
 ├── phase-2-core.feature  # Scenarios for phase-2-core.md
@@ -810,8 +810,8 @@ When SPEC is split into phases, Feature files MUST also be split:
 ```markdown
 # Feature: {feature-name} - Phase {N}: {phase-name}
 
-**SPEC**: `.claude/vibe/specs/{feature-name}/phase-{N}-{name}.md`
-**Master Feature**: `.claude/vibe/features/{feature-name}/_index.feature`
+**SPEC**: `.vibe/specs/{feature-name}/phase-{N}-{name}.md`
+**Master Feature**: `.vibe/features/{feature-name}/_index.feature`
 
 ## User Story (Phase Scope)
 **As a** {user}
@@ -988,8 +988,8 @@ Output the handoff message:
 ✅ SPEC DRAFT COMPLETE: {feature-name}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-📋 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
 📊 Quality Score: {score}/100
 ⏱️ Started: {start_time}
 ⏱️ Completed: {getCurrentTime result}
@@ -1017,22 +1017,22 @@ Option 2 (recommended for large context):
 
 | File | Path | When |
 |------|------|------|
-| SPEC | `.claude/vibe/specs/{feature-name}.md` | After quality validation (Step 7) |
-| Feature | `.claude/vibe/features/{feature-name}.feature` | Immediately after SPEC |
+| SPEC | `.vibe/specs/{feature-name}.md` | After quality validation (Step 7) |
+| Feature | `.vibe/features/{feature-name}.feature` | Immediately after SPEC |
 
 ### Large Scope (Split Files)
 
 | File | Path | When |
 |------|------|------|
-| Master SPEC | `.claude/vibe/specs/{feature-name}/_index.md` | After quality validation |
-| Phase SPEC | `.claude/vibe/specs/{feature-name}/phase-{N}-{name}.md` | Per phase |
-| Master Feature | `.claude/vibe/features/{feature-name}/_index.feature` | After Master SPEC |
-| Phase Feature | `.claude/vibe/features/{feature-name}/phase-{N}-{name}.feature` | Per phase SPEC |
+| Master SPEC | `.vibe/specs/{feature-name}/_index.md` | After quality validation |
+| Phase SPEC | `.vibe/specs/{feature-name}/phase-{N}-{name}.md` | Per phase |
+| Master Feature | `.vibe/features/{feature-name}/_index.feature` | After Master SPEC |
+| Phase Feature | `.vibe/features/{feature-name}/phase-{N}-{name}.feature` | Per phase SPEC |
 
 **❌ FORBIDDEN:**
 
 - Creating files in project root (e.g., `feature-name.md`)
-- Creating files outside `.claude/vibe/` directory
+- Creating files outside `.vibe/` directory
 - Skipping file creation
 - Using different file names than feature-name
 - Creating split SPEC without matching split Feature files
@@ -1048,19 +1048,19 @@ Option 2 (recommended for large context):
 
 **Single file:**
 ```
-1. Write .claude/vibe/specs/{feature-name}.md
-2. Write .claude/vibe/features/{feature-name}.feature
+1. Write .vibe/specs/{feature-name}.md
+2. Write .vibe/features/{feature-name}.feature
 3. Confirm: "✅ Created: specs/{feature-name}.md + features/{feature-name}.feature"
 ```
 
 **Split files:**
 ```
-1. Write .claude/vibe/specs/{feature-name}/_index.md
-2. Write .claude/vibe/specs/{feature-name}/phase-1-setup.md
-3. Write .claude/vibe/specs/{feature-name}/phase-2-core.md
-4. Write .claude/vibe/features/{feature-name}/_index.feature
-5. Write .claude/vibe/features/{feature-name}/phase-1-setup.feature
-6. Write .claude/vibe/features/{feature-name}/phase-2-core.feature
+1. Write .vibe/specs/{feature-name}/_index.md
+2. Write .vibe/specs/{feature-name}/phase-1-setup.md
+3. Write .vibe/specs/{feature-name}/phase-2-core.md
+4. Write .vibe/features/{feature-name}/_index.feature
+5. Write .vibe/features/{feature-name}/phase-1-setup.feature
+6. Write .vibe/features/{feature-name}/phase-2-core.feature
 7. Confirm: "✅ Created: {N} SPEC files + {N} Feature files"
 ```
 
@@ -1144,8 +1144,8 @@ Claude: Thank you. SPEC has been refined.
 ✅ SPEC Complete!
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-📄 .claude/vibe/specs/brick-game.md (PTCF structure)
-📄 .claude/vibe/features/brick-game.feature
+📄 .vibe/specs/brick-game.md (PTCF structure)
+📄 .vibe/features/brick-game.feature
 📊 Quality score: 100/100 ← Loop converged (no remaining gaps)
 ```
 

package/skills/vibe-spec-review/SKILL.md

@@ -26,8 +26,8 @@ Load skill `vibe-spec-review` with feature: "feature-name"
 Or via natural language trigger: "스펙 리뷰", "review spec", "명세 리뷰".
 
 **Prerequisites:**
-- SPEC file exists: `.claude/vibe/specs/{feature-name}.md` (single) or `.claude/vibe/specs/{feature-name}/_index.md` (split)
-- Feature file exists: `.claude/vibe/features/{feature-name}.feature` (single) or `.claude/vibe/features/{feature-name}/_index.feature` (split)
+- SPEC file exists: `.vibe/specs/{feature-name}.md` (single) or `.vibe/specs/{feature-name}/_index.md` (split)
+- Feature file exists: `.vibe/features/{feature-name}.feature` (single) or `.vibe/features/{feature-name}/_index.feature` (split)
 
 ---
 
@@ -48,7 +48,7 @@ Or via natural language trigger: "스펙 리뷰", "review spec", "명세 리뷰"
 **`.last-feature` pointer update** (immediately after Timer):
 
 ```
-Write ".claude/vibe/.last-feature" ← feature-name (one line)
+Write ".vibe/.last-feature" ← feature-name (one line)
 If the value is already the same, no-op.
 ```
 
@@ -80,21 +80,21 @@ Detect SPEC structure (single file or split folder) and read files:
 
 **Single file structure:**
 ```
-.claude/vibe/specs/{feature-name}.md
-.claude/vibe/features/{feature-name}.feature
+.vibe/specs/{feature-name}.md
+.vibe/features/{feature-name}.feature
 ```
 
 **Split folder structure:**
 ```
-.claude/vibe/specs/{feature-name}/_index.md      (+ phase files)
-.claude/vibe/specs/{feature-name}/phase-*.md     (phase-1-xxx.md, phase-2-xxx.md, ...)
-.claude/vibe/features/{feature-name}/_index.feature (+ phase files)
-.claude/vibe/features/{feature-name}/phase-*.feature
+.vibe/specs/{feature-name}/_index.md      (+ phase files)
+.vibe/specs/{feature-name}/phase-*.md     (phase-1-xxx.md, phase-2-xxx.md, ...)
+.vibe/features/{feature-name}/_index.feature (+ phase files)
+.vibe/features/{feature-name}/phase-*.feature
 ```
 
 **Detection logic:**
-1. Check if `.claude/vibe/specs/{feature-name}/` directory exists → Split mode
-2. Otherwise check `.claude/vibe/specs/{feature-name}.md` → Single mode
+1. Check if `.vibe/specs/{feature-name}/` directory exists → Split mode
+2. Otherwise check `.vibe/specs/{feature-name}.md` → Single mode
 3. If neither exists → Error
 
 **Split mode file loading:**
@@ -110,8 +110,8 @@ Detect SPEC structure (single file or split folder) and read files:
 
 Loading files...
   Mode: {single|split}
-  ✅ SPEC: .claude/vibe/specs/{feature-name}.md (or _index.md + N phase files)
-  ✅ Feature: .claude/vibe/features/{feature-name}.feature (or _index.feature + N phase files)
+  ✅ SPEC: .vibe/specs/{feature-name}.md (or _index.md + N phase files)
+  ✅ Feature: .vibe/features/{feature-name}.feature (or _index.feature + N phase files)
 
 Extracted info:
   - Feature: {feature description}
@@ -579,8 +579,8 @@ Total Improvements: {M}
 ⏱️ Completed: {getCurrentTime result}
 
 Updated files:
-  📋 .claude/vibe/specs/{feature-name}.md (or split folder)
-  📋 .claude/vibe/features/{feature-name}.feature (or split folder)
+  📋 .vibe/specs/{feature-name}.md (or split folder)
+  📋 .vibe/features/{feature-name}.feature (or split folder)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -678,8 +678,8 @@ Please answer the following questions:
 ```
 ❌ ERROR: SPEC file not found
 
-Expected (single): .claude/vibe/specs/{feature-name}.md
-Expected (split):  .claude/vibe/specs/{feature-name}/_index.md
+Expected (single): .vibe/specs/{feature-name}.md
+Expected (split):  .vibe/specs/{feature-name}/_index.md
 
 Please run /vibe.spec "{feature-name}" first to create the SPEC.
 ```
@@ -688,8 +688,8 @@ Please run /vibe.spec "{feature-name}" first to create the SPEC.
 ```
 ❌ ERROR: Feature file not found
 
-Expected (single): .claude/vibe/features/{feature-name}.feature
-Expected (split):  .claude/vibe/features/{feature-name}/_index.feature
+Expected (single): .vibe/features/{feature-name}.feature
+Expected (split):  .vibe/features/{feature-name}/_index.feature
 
 Please run /vibe.spec "{feature-name}" first to create the Feature file.
 ```
@@ -718,9 +718,9 @@ ARGUMENTS: $ARGUMENTS
 ```
 Feature name: $ARGUMENTS
 
-1. Check split folder: .claude/vibe/specs/$ARGUMENTS/_index.md
+1. Check split folder: .vibe/specs/$ARGUMENTS/_index.md
    - If exists → Split mode (read all files in folder)
-2. Check single file: .claude/vibe/specs/$ARGUMENTS.md
+2. Check single file: .vibe/specs/$ARGUMENTS.md
    - If exists → Single mode
 3. Neither exists → Show error with both expected paths
 ```

package/skills/vibe-test/SKILL.md

@@ -136,5 +136,5 @@ If `failed` is empty, replace the Failures section with `_All probes passed._`.
 - [ ] Target install dir missing → clean exit with guidance (not an error)
 - [ ] JSON report matches the template above exactly (fields, types, naming)
 - [ ] Markdown summary printed to console after the run
-- [ ] Reports land in `~/.vibe/test-reports/`, never in project-local `.claude/vibe/`
+- [ ] Reports land in `~/.vibe/test-reports/`, never in project-local `.vibe/`
 - [ ] `failed.length > 0` → auto-invokes `/vibe.regress register --from-test`

package/vibe/constitution.md

@@ -11,7 +11,7 @@ This document defines the core principles and coding standards for the project.
 This setting controls **conversation language with user only**.
 All generated documents (SPEC, Feature, etc.) are **always in English**.
 
-To change, modify in `.claude/vibe/config.json`:
+To change, modify in `.vibe/config.json`:
 
 ```json
 {
@@ -23,7 +23,7 @@ To change, modify in `.claude/vibe/config.json`:
 
 ## Document References
 
-All reference documents are stored globally and specified in `.claude/vibe/config.json`:
+All reference documents are stored globally and specified in `.vibe/config.json`:
 
 ```json
 {

package/vibe/templates/claudemd-template.md

@@ -36,9 +36,9 @@
 
 ## References
 
-- **Rules**: See `.claude/vibe/config.json` → `references.rules[]`
-- **Language standards**: See `.claude/vibe/languages/`
-- **Constitution**: See `.claude/vibe/constitution.md`
+- **Rules**: See `.vibe/config.json` → `references.rules[]`
+- **Language standards**: See `.vibe/languages/`
+- **Constitution**: See `.vibe/constitution.md`
 
 ## Workflow
 
@@ -68,7 +68,7 @@ At 70%+ context: `save_memory` → `/new` → `/vibe.utils --continue`
 
 ## Git Commit Rules
 
-**Include:** `.claude/vibe/plans/`, `.claude/vibe/specs/`, `.claude/vibe/features/`, `.claude/vibe/config.json`, `CLAUDE.md`
+**Include:** `.vibe/plans/`, `.vibe/specs/`, `.vibe/features/`, `.vibe/config.json`, `CLAUDE.md`
 **Exclude:** `~/.claude/vibe/rules/`, `~/.claude/commands/`, `~/.claude/agents/`, `~/.claude/skills/`, `.claude/settings.local.json`
 
 <!-- VIBE:END -->

package/vibe/templates/constitution-template.md

@@ -11,7 +11,7 @@ This document defines the core principles and coding standards for the project.
 This setting controls **conversation language with user only**.
 All generated documents (SPEC, Feature, etc.) are **always in English**.
 
-To change, modify in `.claude/vibe/config.json`:
+To change, modify in `.vibe/config.json`:
 
 ```json
 {
@@ -23,7 +23,7 @@ To change, modify in `.claude/vibe/config.json`:
 
 ## Document References
 
-All reference documents are stored globally and specified in `.claude/vibe/config.json`:
+All reference documents are stored globally and specified in `.vibe/config.json`:
 
 ```json
 {

package/vibe/templates/feature-template.md

@@ -2,7 +2,7 @@
 
 > This file is **the core of quality assurance**. All scenarios passing = feature complete.
 
-**SPEC**: `.claude/vibe/specs/{feature-name}.md`
+**SPEC**: `.vibe/specs/{feature-name}.md`
 **Last verified**: -
 **Quality score**: -