@su-record/vibe 3.2.62 → 4.0.0

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

@@ -1,118 +0,0 @@
-# Capability Spec: {{CAPABILITY_NAME}}
-
-**Date**: {{DATE}}
-**Origin**: {{FAILURE_ANALYSIS_FILE}}
-**Category**: {{TOOL | GUARDRAIL | ABSTRACTION | DOCUMENTATION | FEEDBACK}}
-**Priority**: {{P1 | P2 | P3}}
-
----
-
-## Problem Statement
-
-**Failure this solves**: {{FAILURE_DESCRIPTION}}
-
-**Without this capability:**
-{{WITHOUT_CAPABILITY_DESCRIPTION}}
-
-**With this capability:**
-{{WITH_CAPABILITY_DESCRIPTION}}
-
----
-
-## Specification
-
-### What It Does
-
-{{CAPABILITY_DESCRIPTION_DETAILED}}
-
-### Inputs
-
-| Input | Type | Source | Required |
-|-------|------|--------|----------|
-| {{INPUT_1}} | {{TYPE_1}} | {{SOURCE_1}} | {{YES/NO}} |
-| {{INPUT_2}} | {{TYPE_2}} | {{SOURCE_2}} | {{YES/NO}} |
-
-### Outputs
-
-| Output | Type | Format | Notes |
-|--------|------|--------|-------|
-| {{OUTPUT_1}} | {{TYPE_1}} | {{FORMAT_1}} | {{NOTES_1}} |
-
-### Behavior
-
-1. {{BEHAVIOR_STEP_1}}
-2. {{BEHAVIOR_STEP_2}}
-3. {{BEHAVIOR_STEP_3}}
-
-### Error Cases
-
-| Condition | Behavior |
-|-----------|----------|
-| {{ERROR_CASE_1}} | {{ERROR_BEHAVIOR_1}} |
-| {{ERROR_CASE_2}} | {{ERROR_BEHAVIOR_2}} |
-
----
-
-## Implementation Plan
-
-### Files to Create
-
-- `{{NEW_FILE_1}}` — {{PURPOSE_1}}
-- `{{NEW_FILE_2}}` — {{PURPOSE_2}}
-
-### Files to Modify
-
-- `{{MODIFIED_FILE_1}}` — {{CHANGE_DESCRIPTION_1}}
-
-### Integration Points
-
-- Triggers on: {{TRIGGER_CONDITION}}
-- Called by: {{CALLER}}
-- Calls into: {{DEPENDENCIES}}
-
----
-
-## Acceptance Criteria
-
-- [ ] {{ACCEPTANCE_CRITERION_1}}
-- [ ] {{ACCEPTANCE_CRITERION_2}}
-- [ ] {{ACCEPTANCE_CRITERION_3}}
-- [ ] Original failure scenario no longer occurs
-- [ ] Existing functionality unaffected (regression tests pass)
-
----
-
-## Verification Plan
-
-**Test to add**: `{{TEST_FILE}}` — `{{TEST_DESCRIPTION}}`
-
-**Manual verification steps:**
-1. {{VERIFY_STEP_1}}
-2. {{VERIFY_STEP_2}}
-
----
-
-## Persistence
-
-After building, record in `.vibe/capabilities-log.md`:
-
-```markdown
-## {{DATE}} — {{CAPABILITY_NAME}}
-
-**Failure**: {{FAILURE_SHORT}}
-**Missing**: {{MISSING_CAPABILITY_SHORT}}
-**Built**: {{WHAT_WAS_BUILT}}
-**Files**: {{FILES_LIST}}
-**Prevents**: {{FAILURE_CLASS}}
-```
-
-Save to memory:
-```
-save_memory("capability-{{CAPABILITY_NAME}}", {
-  "failure": "{{FAILURE_SHORT}}",
-  "diagnosis": "{{MISSING_CAPABILITY_SHORT}}",
-  "category": "{{CATEGORY}}",
-  "solution": "{{WHAT_WAS_BUILT}}",
-  "files_changed": [{{FILES_LIST}}]
-})
-```

package/skills/vibe.capability-loop/templates/failure-analysis.md

@@ -1,118 +0,0 @@
-# Failure Analysis: {{FAILURE_TITLE}}
-
-**Date**: {{DATE}}
-**Reporter**: {{REPORTER}}
-**Occurrence count**: {{OCCURRENCE_COUNT}}
-**First seen**: {{FIRST_SEEN_DATE}}
-
----
-
-## Failure Description
-
-**What happened:**
-{{FAILURE_DESCRIPTION}}
-
-**Expected behavior:**
-{{EXPECTED_BEHAVIOR}}
-
-**Actual behavior:**
-{{ACTUAL_BEHAVIOR}}
-
-**Reproduction steps:**
-1. {{STEP_1}}
-2. {{STEP_2}}
-3. {{STEP_3}}
-
----
-
-## Diagnosis
-
-Answer all five questions:
-
-### 1. Missing Tool?
-> Did the agent lack a command, API, or utility to accomplish the task?
-
-{{TOOL_DIAGNOSIS}}
-
-- Missing: {{MISSING_TOOL_OR_NONE}}
-- Where to build: {{TOOL_BUILD_LOCATION_OR_NA}}
-
-### 2. Missing Guardrail?
-> Should the agent have been prevented from doing this?
-
-{{GUARDRAIL_DIAGNOSIS}}
-
-- Missing: {{MISSING_GUARDRAIL_OR_NONE}}
-- Where to build: {{GUARDRAIL_BUILD_LOCATION_OR_NA}}
-
-### 3. Missing Abstraction?
-> Was the agent repeating work that should be shared code?
-
-{{ABSTRACTION_DIAGNOSIS}}
-
-- Missing: {{MISSING_ABSTRACTION_OR_NONE}}
-- Where to build: {{ABSTRACTION_BUILD_LOCATION_OR_NA}}
-
-### 4. Missing Documentation?
-> Did the agent lack knowledge that should be discoverable?
-
-{{DOCUMENTATION_DIAGNOSIS}}
-
-- Missing: {{MISSING_DOC_OR_NONE}}
-- Where to add: {{DOC_LOCATION_OR_NA}}
-
-### 5. Missing Feedback?
-> Did the agent not know it was doing the wrong thing?
-
-{{FEEDBACK_DIAGNOSIS}}
-
-- Missing: {{MISSING_FEEDBACK_OR_NONE}}
-- Where to add: {{FEEDBACK_LOCATION_OR_NA}}
-
----
-
-## Root Cause
-
-**Primary category**: {{TOOL | GUARDRAIL | ABSTRACTION | DOCUMENTATION | FEEDBACK}}
-
-**Root cause statement**: {{ROOT_CAUSE_ONE_SENTENCE}}
-
-**Contributing factors:**
-- {{FACTOR_1}}
-- {{FACTOR_2}}
-
----
-
-## Capability to Build
-
-**Capability name**: `{{CAPABILITY_NAME}}`
-
-**What to build**: {{CAPABILITY_DESCRIPTION}}
-
-**Build plan:**
-1. {{BUILD_STEP_1}}
-2. {{BUILD_STEP_2}}
-3. {{BUILD_STEP_3}}
-
-**Files to create/modify:**
-- `{{FILE_1}}` — {{FILE_1_PURPOSE}}
-- `{{FILE_2}}` — {{FILE_2_PURPOSE}}
-
----
-
-## Verification
-
-- [ ] Original failure reproduced before fix
-- [ ] New capability prevents the failure
-- [ ] Existing tests still pass
-- [ ] New test added that would catch this failure class
-
----
-
-## Prevents
-
-This capability prevents the following class of failures:
-
-> {{FAILURE_CLASS_DESCRIPTION}}
-
-Estimated recurrence if not built: {{HIGH | MEDIUM | LOW}}

package/skills/vibe.chub-usage/SKILL.md

@@ -1,11 +0,0 @@
----
-name: vibe.chub-usage
-description: Compatibility alias for chub-based current API documentation lookup. Use when callers invoke vibe.chub-usage directly.
-invocation: [auto]
-tier: optional
-triggers: [chub, context hub, API docs, latest API, deprecated API, SDK documentation, api reference, 최신 문서]
-priority: 60
-user-invocable: true
----
-
-Load `vibe.documentation-provider` and force the chub provider while preserving all arguments.

package/skills/vibe.clone/SKILL.md

@@ -1,136 +0,0 @@
----
-name: vibe.clone
-description: 참조할 라이브 사이트 URL이 있고 그 마크업을 현재 스택으로 재현할 때 — 헤드리스 브라우저로 렌더된 DOM·computed CSS·에셋을 캡처해 픽셀 검증까지 루프
-argument-hint: "<url> [<url2>...] [--name=<feature>] [--sub] [--mo-only] [--pc-only] [--ignore-robots] [--no-interact] [--real-content]"
-user-invocable: true
----
-
-# /vibe.clone
-
-URL을 받아 **마크업 수준으로 정밀 복제**하고 현재 프로젝트 스택에 맞춰 컴포넌트/스타일을 스캐폴딩한다.
-휴리스틱·추정·생략은 금지 — 아래 Immutable Rules가 판정 기준이다.
-
-## Usage
-
-```
-/vibe.clone <url>                              # 인터랙티브: MO+PC 양쪽 캡처 (기본)
-/vibe.clone <url> --mo-only                    # 모바일(375×812)만 캡처
-/vibe.clone <url> --pc-only                    # 데스크탑(1440×900)만 캡처
-/vibe.clone <url> --name=stripe-clone          # 기능 이름 지정 (기본: 호스트명 kebab-case)
-/vibe.clone <url> --sub                        # 사이트맵/메가메뉴 하위 메뉴 URL까지 함께 클론
-/vibe.clone <url1> <url2> <url3>               # 다중 페이지 클론 (같은 사이트의 여러 경로)
-/vibe.clone <url> --ignore-robots              # robots.txt 무시 (사이트 소유자 허가 있을 때만)
-/vibe.clone <url> --no-interact                # 능동 인터랙션 스윕 끄기 (완전 결정론적 캡처)
-/vibe.clone <url> --real-content               # 텍스트 verbatim 유지 (본인 소유/허가 확인 1회 필수)
-```
-
-## Argument Routing
-
-```
-Step 1) 인자 수집
-  urls         = http(s):// 로 시작하는 모든 인자
-  feature      = --name=<value> | URL host → kebab-case
-  scope        = --mo-only | --pc-only | (기본: both)
-  sub / ignoreRobots / realContent = 각 플래그 유무
-    (realContent 는 소유·허가 확인 질문 1회 후 적용)
-
-Step 2) 인자 검증 — 하나라도 걸리면 중단
-  urls.length === 0          → 사용자에게 URL 입력 요청
-  ! /^https?:\/\//.test(url) → "유효한 URL이 아닙니다"
-  --sub && urls.length > 1   → "--sub는 기준 URL 1개와 함께 사용하세요"
-
-Step 3) 실행 진입 → Execution Plan Phase 0
-  URL 다중 입력 시 각 URL마다 별도 feature 디렉토리 (URL path 기반 suffix)
-```
-
-## Core Principles
-
-```
-The rendered DOM is the source of truth for markup. Screenshots are for pixel verification only.
-
-✅ Puppeteer-rendered DOM (post-JS) → HTML structural mapping
-✅ Computed CSS → SCSS direct conversion (no guessing)
-✅ All remote assets (images, fonts) → downloaded locally and rewritten to project paths
-✅ The active harness handles semantic decisions only: tag selection, component splitting, interactions
-✅ Screenshots are used for verification only, not generation
-```
-
-## Immutable Rules
-
-이 7개가 클론 품질의 판정 기준이다. 각 Phase의 명령어는 references 에 있지만, **이 규칙은 항상 인라인**이다.
-
-```
-1. Do NOT generate CSS values by guessing or eyeballing screenshots.
-   ✅ clone-to-scss.js output is a DRAFT (skeleton), not a frozen artifact. You MAY
-      rewrite SCSS values/selectors — but ONLY with evidence cited from computed.json /
-      states.json / behaviors.json (value correction, dedupe, selector restructuring).
-   ✅ clone-validate.js PASS is the sole judge of value correctness — not self-report.
-   ❌ Do NOT invent values with no extraction evidence ("looks like 18px" is forbidden).
-   ❌ Do NOT write CSS values directly inside scoped <style> blocks — style LOCATION
-      rule: all values live in styles/{feature}/ SCSS (value authority and style
-      location are separate rules; both hold).
-
-2. Do NOT hotlink remote assets. All images/fonts must be downloaded and rewritten.
-
-3. Do NOT skip the pixel verification loop (Phase 5). The clone is incomplete without it.
-
-4. Do NOT copy textual content verbatim from copyrighted sources for production use.
-   This skill is for layout/markup learning ("클론 코딩"). Replace text with placeholders
-   or user-provided copy when shipping a real product.
-   Exception: `--real-content` — the user confirms (once, explicitly) they own the site
-   or have permission. Then keep text verbatim; clone-spec.js is invoked with
-   `--real-content` so specs mark copy as verbatim.
-
-5. Do NOT build a section without confirming its interaction model. The model in
-   sections.json is a static-DOM heuristic — verify scroll-driven vs click-driven vs
-   time-driven vs hover against the live site. Misidentifying it is the #1 clone failure mode.
-
-6. Do NOT ship default-state-only. Implement every harvested state (hover/focus/active/open/
-   tab-switch) from states.json / the section spec.
-
-7. Do NOT ignore behaviors.json. The ACTIVE interaction sweep (scroll-state diffs,
-   click-driven tab content-swap detection, hover diffs, in-view entrance animations,
-   time-driven mutation candidates, smooth-scroll-lib detection) catches JS-set state
-   that static CSS harvesting is blind to. When the spec's "Dynamic behaviors" block
-   conflicts with the static interaction heuristic, the active capture wins.
-```
-
-## Execution Plan
-
-**Phase 단계 건너뛰기 금지.** 각 Phase의 정확한 명령어와 금지 사항은 `references/phase-commands.md` 가 SSOT다.
-
-| Phase | 하는 일 | 상세 |
-|---|---|---|
-| **0** Setup | 스택 감지 · feature 이름 · 디렉토리 · 컴포넌트 인덱싱 · 토큰 스캔. `--sub` 면 URL 목록 확장 | `references/setup-and-layout.md` |
-| **1** Capture | 헤드리스 브라우저로 MO/PC **병렬** 캡처 → rendered.html · computed.json · screenshot.png · states.json · behaviors.json · assets/ | `references/capture-rules.md` · `references/phase-commands.md` |
-| **2** Refine | DOM → sections.json (BP마다 독립). interaction 모델 추정 + 상태 규칙 포함 | `references/refine-rules.md` |
-| **2.5** Foundation | **순차, 섹션 빌드 전.** 폰트 배선 · SEO 에셋 → public/ · SVG dedupe → 아이콘 모듈 · scrollLib 페이지 레벨 배선 | `references/phase-commands.md` |
-| **3** Scaffold | spec 게이트 → SCSS 초안 → 섹션별 빌더 병렬 디스패치 → 섹션마다 validate PASS. **MO 완주 후 PC** | `references/phase-commands.md` · `references/scaffold-phases.md` |
-| **3C** Responsive Merge | MO+PC 모두 Phase 5 통과 후 mobile-first 병합 (MO=기본, PC diff만 `@media`) | `references/phase-commands.md` |
-| **4** Compile Gate | 컴파일 성공까지 루프. baseline 대비 **신규** 에러만 수정 | `references/verification-loops.md` |
-| **5** Pixel Verification | **필수.** P1=0까지 루프. 병합 후엔 MO·PC 양쪽 재실행 | `references/verification-loops.md` |
-
-⛔ Phase 4 통과 후 Phase 5 진입은 자동이다. Phase 5 완료 전에 "완료 요약"을 출력하지 않는다.
-
-## Prerequisites
-
-- **puppeteer**: optional peer dependency. 미설치 시 Phase 1에서 `npm install puppeteer` 안내 후 중단
-- **Chromium**: puppeteer 자동 다운로드 (`npx puppeteer browsers install chrome`)
-- **dev 서버**: Phase 4-5에서 `npm run dev` 호출. 스크립트가 미정의면 사용자에게 명시
-- **robots.txt 준수**: 기본 차단. `--ignore-robots` 는 사이트 소유자/CTF/학습 명시일 때만
-
-## Legal & Error Recovery
-
-용도 제한(학습·본인 소유·허가받은 리디자인), 금지 사항(저작권 콘텐츠 무단 재게시·브랜드 사칭·robots.txt 우회),
-`--real-content` 확인 절차, 오류 복구 표: `references/legal-and-error-recovery.md`
-
-사용자 의도가 사칭이나 기만이면 즉시 거부한다 — 플래그 유무와 무관하다.
-
-## Done Criteria
-
-- [ ] 요청된 모든 BP(scope)에 대해 Phase 1–2 산출물이 존재한다
-- [ ] 모든 섹션이 spec의 TODO를 해소한 뒤 빌드됐다
-- [ ] 모든 섹션이 `clone-validate.js` PASS를 받았다
-- [ ] 원격 에셋이 남아있지 않다 — 모든 `<img>`/background-image가 로컬 경로로 해석된다
-- [ ] Phase 4 컴파일 통과 (baseline 대비 신규 에러 0)
-- [ ] Phase 5 P1=0 — 병합 후라면 MO·PC 양쪽에서

package/skills/vibe.clone/references/capture-rules.md

@@ -1,48 +0,0 @@
-# Clone — Phase 1 Capture Output & Rules
-
-> Loaded by vibe.clone SKILL.md Phase 1 (Capture) — full per-breakpoint output directory listing and the deterministic capture rule set.
-
-### Output per breakpoint
-
-```
-/tmp/{feature}/{bp}/
-  ├── rendered.html       — final DOM after JS execution
-  ├── computed.json       — per-element computed CSS + bounding box
-  ├── screenshot.png      — full-page screenshot
-  ├── states.json         — non-default state rules (hover/focus/active/checked/tab/aria/data-state)
-  ├── behaviors.json      — ACTIVE sweep: scroll / tab / hover / in-view / time-driven + scrollLib
-  ├── assets/
-  │   ├── images/         — all <img>, background-image, <picture> sources
-  │   ├── fonts/          — @font-face srcs
-  │   └── seo/            — favicons, apple-touch-icons, OG images, webmanifest
-  └── asset-map.json      — remote URL → local path mapping
-```
-
-### Capture rules
-
-```
-1. Wait for `networkidle2` (no in-flight requests for 500ms) before snapshot
-2. Scroll to bottom slowly to trigger lazy-loaded content
-3. Resolve all <img src>, srcset, and computed background-image URLs
-4. Resolve @font-face src() URLs from all stylesheets
-5. Download assets in parallel (concurrency=8), preserve original extensions
-6. Rewrite asset URLs in rendered.html and computed.json to local paths
-7. Strip inline analytics/tracking scripts before saving rendered.html
-8. Harvest non-default state rules from all stylesheets → states.json
-   (deterministic: read :hover/:focus/:active/:checked/[aria-*]/[data-state]/.is-*/.active/
-    .scrolled/.sticky/.pinned/… declarations straight from CSS — NO scripted clicking)
-9. ACTIVE interaction sweep → behaviors.json (runs after lazy-load, before freeze).
-   Drives the live page to capture JS-set state that CSS harvesting can't see:
-   - Scroll-state diff: tag sticky/fixed/top-bar headers+nav, snapshot computed CSS at
-     scroll 0, scroll past threshold, re-snapshot, diff → {prop: {from, to}, triggerScrollY}
-   - Tab groups: click tab-like sibling sets, detect whether content swaps on click
-   - Hover diff: hover interactive elements (1 sample per tag+class signature, max 30),
-     diff computed styles → JS-set hover states that :hover harvesting misses
-   - In-view entrance: fresh reload, tag below-fold "waiting to animate" nodes
-     (opacity 0 / transform offset), scroll each into view, diff → fade-up/slide-in
-   - Time-driven: 3s no-input MutationObserver watch → carousel/auto-cycle candidates
-   - Scroll-lib detection: Lenis / Locomotive Scroll (native scrolling feels different —
-     the user spots it immediately; wire the lib page-level, not per-section)
-   Disable with --no-interact (restores the old fully-deterministic, screenshot-stable capture).
-10. SEO asset harvest: favicon / apple-touch-icon / webmanifest / og:image → assets/seo/
-```

package/skills/vibe.clone/references/legal-and-error-recovery.md

@@ -1,40 +0,0 @@
-# Clone — Legal & Ethical Notes + Error Recovery
-
-> Loaded by vibe.clone SKILL.md — full legal/ethical usage notes and the Error Recovery troubleshooting table.
-
-## Legal & Ethical Notes
-
-```
-This skill is intended for:
-  ✅ "Clone coding" learning exercises (markup/layout study)
-  ✅ Rebuilding the user's own previously-deployed sites
-  ✅ Authorized redesigns where the user has rights to the source
-
-NOT intended for:
-  ❌ Republishing copyrighted content (text, images, logos) without permission
-  ❌ Deceptive look-alike sites (phishing, brand impersonation)
-  ❌ Bypassing robots.txt or rate-limiting protections
-
-Claude must:
-  - Replace copyrighted text content with placeholders (e.g. "[Lorem ipsum]") by default
-  - --real-content: ask ONE explicit confirmation (site ownership / permission) before
-    Phase 3; on confirmation keep text verbatim (clone-spec.js --real-content)
-  - Skip and warn when robots.txt disallows fetching the target path
-  - Refuse if the user's stated intent is brand impersonation or deception
-```
-
-## Error Recovery
-
-| Failure | Recovery |
-|---------|----------|
-| clone-extract.js Puppeteer launch failure | Verify Node ≥18 and that Chromium is installed (`npx puppeteer browsers install chrome`). Retry once. |
-| Target site blocks headless (403/Cloudflare) | Retry with `--stealth` flag (uses puppeteer-extra stealth plugin). If still blocked, report to user. |
-| Asset download 404 | Log to asset-map.json with `status: missing`. Use a 1×1 transparent placeholder. Continue. |
-| robots.txt disallows path | Halt Phase 1. Inform user; require explicit `--ignore-robots` flag to proceed. |
-| clone-refine.js produces empty sections | Site likely uses Shadow DOM or canvas rendering. Report and ask whether to fall back to screenshot-only mode. |
-| Pixel diff stuck > 0.05 after 5 rounds | Likely font fallback or anti-aliasing. Report metric, allow user to accept threshold. |
-| Interaction model guess wrong (Phase 5) | section.interaction is a static-DOM heuristic. Re-observe the live site, correct the model in the spec, rebuild the section for the confirmed model. |
-| states.json empty but site has hover/tabs | States may be set via inline JS, not CSS rules. Check behaviors.json (active sweep captures scroll/tab JS state). If still missing, note in the spec and capture manually during Phase 5. |
-| behaviors.json missing or empty | Active sweep was disabled (--no-interact), hit no sticky/tab elements, or errored (logged, non-fatal). Falls back to static states.json. Re-run without --no-interact to retry. |
-| clone-merge-responsive.js reports many mo-only/pc-only selectors | Section detection diverged between BPs (layout differs structurally). Expected for hidden-on-mobile elements; verify each against the two sections.json trees and gate with the media query manually if needed. |
-| Merged build fails Phase 5 at one viewport only | The merge dropped or mis-bucketed a declaration. Diff the failing viewport's computed CSS against its sections.json; fix in the merged SCSS with that evidence. |

package/skills/vibe.clone/references/phase-commands.md

@@ -1,118 +0,0 @@
-# Clone — Phase Commands (BLOCKING)
-
-> Loaded by vibe.clone SKILL.md Phases 1 / 2 / 3 / 3C. These are the **only** sanctioned
-> commands for each phase. `{{VIBE_PATH}}` is substituted at install time.
-
-## Global prohibitions
-
-```
-⛔ Writing custom capture/refine/SCSS/spec scripts (puppeteer-fetch.mjs, ad-hoc parsers) is forbidden.
-⛔ Do NOT use WebFetch or curl for capture — they cannot render JS-driven SPAs.
-⛔ Do NOT parse rendered.html with custom Python/Node scripts.
-✅ Use the bundled scripts. If output is unsatisfactory, modify the script — not the workflow.
-```
-
-## Phase 1: Capture
-
-Coordinator pattern — run MO/PC capture as parallel workers.
-
-```bash
-# Mobile (375×812)
-node {{VIBE_PATH}}/hooks/scripts/clone-extract.js capture <URL> \
-  --out=/tmp/{feature}/mo/ --viewport=375x812 --bp=mo
-
-# Desktop (1440×900)
-node {{VIBE_PATH}}/hooks/scripts/clone-extract.js capture <URL> \
-  --out=/tmp/{feature}/pc/ --viewport=1440x900 --bp=pc
-
-# --sub URL expansion (Phase 0, once)
-node {{VIBE_PATH}}/hooks/scripts/clone-extract.js suburls <url> \
-  --out=/tmp/{feature}/menu-urls.json [--ignore-robots]
-```
-
-`--sub` collection rule: prefer `/sitemap`, else header/nav/mega-menu. Include same-origin URLs
-sharing the locale prefix. Exclude external links, language switchers, search, TOP, and footer
-policy/contact/partner/newsroom links.
-
-## Phase 2: Refine
-
-```bash
-# MO  (--states is optional — auto-resolved as states.json next to computed.json)
-node {{VIBE_PATH}}/hooks/scripts/clone-refine.js \
-  /tmp/{feature}/mo/rendered.html /tmp/{feature}/mo/computed.json \
-  --out=/tmp/{feature}/mo/sections.json --states=/tmp/{feature}/mo/states.json --bp=mo
-
-# PC
-node {{VIBE_PATH}}/hooks/scripts/clone-refine.js \
-  /tmp/{feature}/pc/rendered.html /tmp/{feature}/pc/computed.json \
-  --out=/tmp/{feature}/pc/sections.json --states=/tmp/{feature}/pc/states.json --bp=pc
-```
-
-⛔ Phase 3 is blocked until refine completes for **all** required BPs.
-
-## Phase 3: Scaffold
-
-```bash
-# Step 0: per-section build-contract specs (once per BP)
-node {{VIBE_PATH}}/hooks/scripts/clone-spec.js \
-  /tmp/{feature}/{bp}/sections.json \
-  --out=<project>/components/{feature}/_specs/{bp}/ \
-  --feature={feature} [--real-content]
-
-# Step A: SCSS draft (once per BP — note the per-BP out dir)
-node {{VIBE_PATH}}/hooks/scripts/clone-to-scss.js \
-  /tmp/{feature}/{bp}/sections.json \
-  --out=<project>/styles/{feature}/{bp}/ \
-  --token-file=/tmp/{feature}/project-tokens.json
-
-# Step B: per-section validation (after writing each section's component code)
-node {{VIBE_PATH}}/hooks/scripts/clone-validate.js \
-  <project>/styles/{feature}/{bp}/ /tmp/{feature}/{bp}/sections.json --section={SectionName}
-```
-
-Gate rules:
-
-- ⛔ **No section is built without a completed spec.** Step 0 emits `_specs/{Section}.spec.md`
-  (interaction model + active-capture Dynamic behaviors + states + computed CSS + assets + text +
-  checklist). clone-spec.js auto-loads `behaviors.json` from the sections.json dir and attaches
-  matching behaviors per section. Before dispatching a section's builder, review its spec and
-  resolve every `TODO` (confirm interaction model, list states, choose tags, replace copyrighted
-  text — skipped with `--real-content`). The spec is the contract **and** the audit trail.
-- ⛔ **Step A must run first** — its output is the DRAFT every section starts from. Later SCSS
-  edits are allowed per Immutable Rule 1 (evidence-cited only); clone-validate.js PASS is the judge.
-- ⛔ **Do NOT proceed past a section without a clone-validate.js PASS for it.**
-- Spec over 150 lines → split into sub-component specs (mechanical check: `wc -l`).
-
-Order: Phase 3A (MO scaffold → Phase 4 → Phase 5) → Phase 3B (PC, same process) → Phase 3C.
-
-## Phase 3C: Responsive Merge
-
-Runs only after **both** MO and PC pass Phase 5.
-
-```bash
-node {{VIBE_PATH}}/hooks/scripts/clone-merge-responsive.js \
-  --mo=<project>/styles/{feature}/mo/ \
-  --pc=<project>/styles/{feature}/pc/ \
-  --out=<project>/styles/{feature}/ [--breakpoint=1024]
-```
-
-Mobile-first merge: MO declarations become the base, PC diffs go into a `@media (min-width)` block.
-Then switch component imports to the merged `index.scss` and re-run Phase 4 → Phase 5 at **both**
-viewports. ⛔ The clone is NOT complete until the MERGED build passes Phase 5 at both.
-
-## Phase 2.5: Foundation (no script — do this yourself)
-
-Nothing renders right until the foundation exists. Not delegated — it touches shared files.
-
-```
-1. Fonts: verify _base.scss @font-face srcs point at downloaded assets/fonts/ files.
-   Next.js stack → wire via next/font/local in the layout instead of raw @font-face.
-2. Favicon / OG / manifest: copy assets/seo/* → public/ (project convention path),
-   wire metadata (layout.tsx metadata / <head>) to the local files.
-3. SVG icons: collect inline <svg> from rendered.html, dedupe by path data, emit one
-   stack-appropriate icon module (e.g. components/{feature}/icons.tsx).
-   Name by visual function (SearchIcon, ArrowRightIcon, LogoIcon).
-4. Global behaviors from behaviors.json: scrollLib detected → install/wire page-level
-   (Lenis etc.); global keyframes/scroll-snap → styles/{feature}/_shared.scss.
-5. Verify: compile passes before moving on.
-```

package/skills/vibe.clone/references/refine-rules.md

@@ -1,61 +0,0 @@
-# Clone — Phase 2 Refinement Rules & Output Schema
-
-> Loaded by vibe.clone SKILL.md Phase 2 (Refine) — full refinement rule set and the sections.json output schema.
-
-### Refinement rules
-
-```
-Refinement applied when converting rendered.html + computed.json → sections.json:
-  1. Strip <script>, <noscript>, <style>, tracking pixels
-  2. Strip nodes with display:none, visibility:hidden, opacity:0, size 0
-  3. Detect sections: <header>, <nav>, top-level <section>/<main> children, <footer>
-     Fallback: top-level children of <body> with height > 100px
-  4. Detect repeated patterns (sibling nodes with same tag+class signature, count >= 3)
-     → mark as component candidates
-  5. Extract design tokens:
-     - colors: unique color/background-color values, sorted by frequency
-     - typography: font-family/size/weight combinations
-     - spacing: padding/margin values (px), bucketed to nearest 4px
-  6. Background images (background-image: url) → images.bg
-  7. Inline <img> → images.content
-  8. Keep CSS subset: layout (display/flex/grid/position/inset/margin/padding/width/height/gap),
-     typography (font-*, line-height, letter-spacing, text-*, color),
-     decoration (background, border, border-radius, box-shadow, opacity),
-     transform/transition
-  9. Classify interaction model per section (static-DOM heuristic) → section.interaction
-     = { model, confidence, signals[], note }. model ∈ static | click-driven | scroll-driven
-     | time-driven | hover. This is a best-guess + ranked SIGNALS, NOT a silent decision —
-     the builder confirms it against the live site (Phase 5). Misidentifying the interaction
-     model is the #1 clone failure mode (scroll-driven original built as a click UI, etc.).
- 10. Attach matching state rules from states.json to each section → section.states
-     (rules whose selector references a class/leaf-tag inside that section's subtree)
-```
-
-### Output
-
-```
-/tmp/{feature}/{bp}/sections.json:
-  {
-    meta: { feature, url, viewport, bp },
-    tokens: { colors: [...], typography: [...], spacing: [...] },
-    sections: [
-      {
-        name: "Header" | "Hero" | "Features" | ...,
-        nodeRef, tag, size, css,
-        interaction: {        // static-DOM heuristic — builder confirms in Phase 5
-          model: "static" | "click-driven" | "scroll-driven" | "time-driven" | "hover",
-          confidence: "high" | "medium" | "low",
-          signals: [...],     // ranked evidence (sticky, infinite animation, role=tab, …)
-          note
-        },
-        text,                 // text content (placeholder candidates)
-        components: [...],    // detected repeated patterns
-        states: [             // non-default state rules scoped to this section
-          { selector, media, css }
-        ],
-        children: [...],      // full recursive subtree
-        images: { bg, content: [...] }
-      }
-    ]
-  }
-```