@su-record/vibe 3.1.0 → 3.2.1

package/skills/clone/references/scaffold-phases.md

@@ -0,0 +1,59 @@
+# Clone — Phase 3A/3B/3C Builder Contract
+
+> Loaded by vibe.clone SKILL.md Phase 3 (Scaffold) — full prep/dispatch/merge steps for MO/PC scaffold, the 150-line split rule, framework mapping, Phase 3C's import-switch/selector-review steps, and Claude's role checklist. Phase headers, Input lines, and script invocation commands stay in SKILL.md; this file covers the supporting detail only.
+
+```
+  Prep (sequential, once):
+    a. Step 0: clone-spec.js → emit _specs/mo/{Section}.spec.md for every section
+    b. Step A: clone-to-scss.js → SCSS draft in styles/{feature}/mo/ (computed values)
+    c. Orchestrator resolves every spec TODO BEFORE dispatch:
+       ├─ Confirm the interaction model (spec.interaction is a heuristic guess;
+       │  the spec's active-capture "Dynamic behaviors" block overrides it on conflict)
+       ├─ List the states to implement (spec.states + Dynamic behaviors)
+       ├─ Mark copyrighted text for placeholder replacement (skip with --real-content)
+       └─ Map component candidates against component-index.json (reuse vs create)
+    d. 150-line split rule (mechanical — wc -l, don't override with "but it's related"):
+       a completed spec over 150 lines means the section is too big for one builder →
+       split into sub-component specs (one per card variant / repeated pattern) + one
+       wrapper spec that imports them.
+  Dispatch (parallel):
+    ⛔ Every builder prompt embeds the FULL spec text INLINE — never "go read the file".
+       The spec file stays on disk as the audit trail; the prompt must be self-sufficient.
+    ⛔ Builders that write files in parallel run in worktree isolation; sub-component
+       builders complete before their wrapper builder starts.
+    Builder contract (each agent):
+      1. Build HTML structure + semantic tags + framework-specific component file
+         ⛔ No CSS in <style> blocks — only @import/@use of styles/{feature}/mo/
+         ⛔ Build for the CONFIRMED interaction model in the spec; wire every state
+         Framework mapping:
+           - React/Next → .tsx with CSS Modules or styled-components per stack
+           - Vue/Nuxt   → .vue with scoped <style lang="scss"> @import only
+           - Svelte     → .svelte with <style> @import only
+           - Vanilla    → .html + linked .scss
+      2. Asset references → public/images/{feature}/ (already populated in Phase 1)
+      3. SCSS edits per Immutable Rule 1 (evidence-cited only)
+      4. Verify compile (tsc --noEmit or stack equivalent) before finishing
+  Merge (orchestrator, as builders complete):
+    5. Merge worktrees; resolve conflicts (you have full context on every spec)
+    6. clone-validate.js per section — Step B
+       ├─ PASS → section done
+       └─ FAIL → fix discrepancies → re-run step 6 (loop until P1=0, no round cap)
+
+  2. Switch component style imports from styles/{feature}/{bp}/index.scss to the merged
+     styles/{feature}/index.scss
+  3. Review pc-only/mo-only selectors in the merge report — hide/show them with the
+     media query if the original does (evidence: the two sections.json trees)
+
+Claude's role:
+  ✅ Component candidates: decide which patterns become reusable components
+  ✅ HTML semantics: section/h1/p/button/nav tag selection
+  ✅ Text replacement: substitute copyrighted copy with placeholders or user-supplied text
+  ✅ Interaction model: confirm the spec's heuristic guess, then build for the real model
+  ✅ Interactions: implement every state in the spec (hover/focus/active/open), click handlers
+  ✅ SCSS value edits WITH cited evidence (computed.json/states.json/behaviors.json) —
+     clone-validate.js PASS is the judge
+  ❌ Do NOT invent CSS values without extraction evidence
+  ❌ Do NOT write CSS directly in <style> blocks
+  ❌ Do NOT hand-write vw/clamp/@media in Phase 3A/3B (responsive comes from Phase 3C merge)
+  ❌ Do NOT hotlink remote URLs — all assets must use local public/images/ paths
+```

package/skills/clone/references/setup-and-layout.md

@@ -0,0 +1,30 @@
+# Clone — Setup Steps & Output Layout
+
+> Loaded by vibe.clone SKILL.md Full Flow / Phase 0 (Setup) — working-directory + code-output layout and the full Phase 0 setup steps.
+
+```
+Working directory:
+  /tmp/{feature}/
+  ├── mo/ (375×812)  — rendered.html, computed.json, screenshot.png, assets/, sections.json
+  ├── pc/ (1440×900) — rendered.html, computed.json, screenshot.png, assets/, sections.json
+  └── tokens.json    — extracted design tokens (colors/fonts/spacing)
+
+Code output: placed directly in the project directory per detected stack
+  components/{feature}/, components/{feature}/_specs/{mo,pc}/,
+  styles/{feature}/{mo,pc}/ (per-BP drafts) → styles/{feature}/ (Phase 3C merged),
+  public/images/{feature}/, public/ (favicons/OG from assets/seo/)
+```
+
+```
+1. Stack detection:
+   - .vibe/config.json → stack (react/vue/next/svelte/vanilla, scss/tailwind/css-modules)
+   - Fallback: package.json deps
+2. Feature name: URL hostname → kebab-case (e.g. stripe.com → stripe-clone)
+   - User may override with --name=<custom>
+3. Directories:
+   - components/{feature}/, styles/{feature}/, public/images/{feature}/
+4. Component indexing → /tmp/{feature}/component-index.json
+   (scan up to 50 existing components, extract props/slots/classes, within 2 minutes)
+5. Design token scan → /tmp/{feature}/project-tokens.json
+   (SCSS > CSS Variables > Tailwind > CSS-in-JS)
+```

package/skills/docs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: docs
-description: 프로젝트 문서 생성 본체 — README / 아키텍처 / 사용자 가이드 / 릴리즈 노트.
+description: 프로젝트 문서 생성 본체 — README / 아키텍처 / 사용자 가이드 / 릴리즈 노트 / Mermaid 다이어그램 / codemaps.
 when_to_use: /vibe.docs 진입점에서 체인 호출. 직접 호출 금지.
 user-invocable: false
 tier: standard
@@ -179,6 +179,41 @@ Output: `RELEASE_NOTES.md` or append to `CHANGELOG.md`
 - refactor/docs/chore items
 ```
 
+### `/vibe.docs diagram` — Diagram Generation
+
+Generate Mermaid diagrams for architecture, ERD, flowchart, or sequence
+visualization directly (native capability — no dedicated agent). Ground the
+diagram in sources first: folder structure and imports for architecture;
+`models/`, `migrations/`, `schema.*`, ORM definitions for ERDs; the real
+branch/return structure of the code for flowcharts.
+
+**Options:**
+- `/vibe.docs diagram` (default): Architecture overview
+- `/vibe.docs diagram --er`: Entity-Relationship Diagram
+- `/vibe.docs diagram --flow`: Flowchart
+- `/vibe.docs diagram --seq`: Sequence Diagram
+
+> Read `references/diagram-spec.md` for the full output conventions (Mermaid syntax per diagram type, save location, accuracy constraints).
+
+**Example:**
+```
+/vibe.docs diagram --er
+```
+
+### `/vibe.docs codemaps` — Codemaps Generation
+
+Generate auto-documentation from codebase structure directly (native
+capability — no dedicated agent).
+
+**Output Location:** `docs/CODEMAPS/`
+
+> Read `references/codemaps-output.md` for the full generated-files tree, per-file contents, and tools used.
+
+**Example:**
+```
+/vibe.docs codemaps
+```
+
 ## Pipeline Integration
 
 `/vibe.docs` completes the development pipeline:
@@ -202,9 +237,9 @@ When `/vibe.trace` completes with all scenarios passing, suggest:
 - Preserve existing documentation that's still accurate
 - Include concrete code examples from the actual project
 - Keep language consistent with project (Korean/English based on CLAUDE.md)
-- Use documenter agent (changelog mode) for `/vibe.docs release`
-- Use documenter agent (api-docs mode) for API-heavy projects
-- Use diagrammer agent for `/vibe.docs arch` Mermaid generation
+- For `/vibe.docs release` (changelog mode), follow `references/api-docs-changelog.md` natively — no dedicated agent
+- For API-heavy projects (api-docs mode), follow `references/api-docs-changelog.md` natively
+- For `/vibe.docs arch` and `/vibe.docs diagram` Mermaid generation, follow `references/diagram-spec.md` natively
 - Use the `agents-md` skill for `/vibe.docs agent` — applies equally to CLAUDE.md and AGENTS.md
 
 ### DON'T

package/skills/docs/references/api-docs-changelog.md

@@ -0,0 +1,34 @@
+# docs — API Docs & Changelog Spec
+
+> Loaded by docs SKILL.md for `/vibe.docs release` (changelog mode) and API-heavy projects (api-docs mode) — documentation rules for the two artifacts that go stale fastest: API docs and changelogs.
+
+## API Mode
+
+Walk the route handlers/controllers in the given scope and document each
+endpoint: method + path, auth requirement, parameters (path/query/body with
+types, required vs optional, enum values), success and error responses (all
+status codes actually returned), and a runnable example (curl or fetch). List
+endpoints that exist in code but lack documentation — the gap list is as
+valuable as the docs.
+
+## Changelog Mode
+
+From `git diff` and `git log`, classify changes as breaking / added /
+changed / fixed / performance / internal / dependencies. Recommend the
+semantic version bump with a one-line reason. Every breaking change gets
+migration steps; every fix states old vs new behavior.
+
+## Constraints
+
+Return documentation as text output only — never create or write files; the
+calling command decides where content lands. Descriptions are user-facing:
+what changed for the consumer, not which internal function was refactored
+(pure refactors go under Internal, briefly). Document what the code actually
+does, not what comments claim — when they disagree, flag the discrepancy
+rather than picking one silently.
+
+## Done
+
+- API mode: every endpoint in scope documented or explicitly listed as an undocumented gap
+- Changelog mode: all changes classified, version bump recommended with reason, breaking changes have migration steps
+- Output is paste-ready text; zero files created

package/skills/docs/references/codemaps-output.md

@@ -0,0 +1,23 @@
+# docs — Codemaps: Generated Files & Contents
+
+> Loaded by docs SKILL.md `codemaps` mode — full generated-files tree, per-file contents, and tools used.
+
+**Generated Files:**
+```
+docs/CODEMAPS/
+├── INDEX.md          # Overview of all areas
+├── frontend.md       # Frontend structure
+├── backend.md        # API/backend structure
+├── database.md       # Schema documentation
+└── integrations.md   # External services
+```
+
+**Each file contains:**
+- Module table (name, path, description)
+- Data flow diagram (Mermaid)
+- Dependencies list
+- Related areas
+
+**Tools Used:**
+- ts-morph (TypeScript AST)
+- madge (dependency graph)

package/{agents/diagrammer.md → skills/docs/references/diagram-spec.md}

@@ -1,19 +1,6 @@
-# Diagrammer Agent
+# docs — Diagram Generation Spec
 
-Diagram generation specialist — renders architecture, data models, and flows
-as Mermaid.
-
-## Role
-
-- Architecture diagrams from project structure and dependencies
-- ERD from database schemas and model definitions
-- Flowcharts of business logic and user flows
-
-## Model
-
-**Haiku** — fast, structured output
-
-## Goal
+> Loaded by docs SKILL.md `diagram` mode — Mermaid diagram generation rules (architecture, ERD, flowcharts, sequence).
 
 Produce a Mermaid diagram that reflects the actual code, not a generic
 picture. Ground it in sources first: folder structure and imports for

package/skills/exec-plan/SKILL.md

@@ -129,7 +129,7 @@ Ready to execute:
   /vibe.run "{feature-name}" ultrawork
 
 Or hand off to new session:
-  /vibe.utils --continue
+  /vibe.continue
   → Load: .vibe/specs/{feature-name}-execplan.md
 ```
 

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

@@ -144,4 +144,4 @@ save_memory("execplan-{{FEATURE_NAME}}", {
 })
 ```
 
-Resume: `/vibe.utils --continue` → load this file.
+Resume: `/vibe.continue` → load this file.

package/skills/handoff/SKILL.md

@@ -16,9 +16,9 @@ Record work status before session end so the next session can pick up immediatel
 
 A file that records the current work status before context reset. Reading this file in a new session allows immediate continuation.
 
-### Difference from `/vibe.utils --continue`
+### Difference from `/vibe.continue`
 
-| Item | `/vibe.utils --continue` | Handoff |
+| Item | `/vibe.continue` | Handoff |
 |------|--------------------------|---------|
 | Method | Automatic session context restore | Manual handover document |
 | Includes | Memory + session state | Work progress + notes + file list |
@@ -98,7 +98,7 @@ Read HANDOFF.md and continue working
 Or use alongside VIBE auto-restore:
 
 ```
-/vibe.utils --continue
+/vibe.continue
 ```
 
 In this case, saved decisions are also restored via `core_recall_memory`.

package/skills/handoff/templates/handoff.md

@@ -86,7 +86,7 @@ Last commit: `{{LAST_COMMIT_HASH}}` — {{LAST_COMMIT_MESSAGE}}
 
 ```bash
 # 1. Load context
-/vibe.utils --continue
+/vibe.continue
 
 # 2. Read this file if context is missing
 # cat HANDOFF.md

package/skills/spec/SKILL.md

@@ -54,10 +54,15 @@ Task(subagent_type="Explore",
 `vibe/templates/spec-template.md` 구조로 `.vibe/specs/{feature-name}.md` 를 작성한다. 핵심 요건:
 
 - **Overview / Goal** — 무엇을, 왜. 1-3 문장.
+- **Context Sources** — 입력으로 사용한 파일·문서·URL·관측 상태. 출처 없는 추정은 Assumptions 로 분리.
+- **Requirements** — `REQ-{feature}-NNN` ID와 연결된 Done Criteria를 표로 명시.
 - **Done Criteria** — 결정론적 게이트만. 각 항목은 "명령/관찰로 pass·fail 판정 가능"해야 한다 (테스트 exit code, 빌드 성공, 특정 동작 관찰). "잘 동작한다" 류 서술 금지 — 이것이 루프의 JUDGE 입력이 된다.
+- **Evidence Required** — Done 을 증명할 명령 결과·테스트 리포트·로그·스크린샷·코드 위치.
+- **Human Taste (Non-Blocking)** — UX·브랜드·제품 감각처럼 release 시 사람이 판단할 기준. 완료 게이트로 쓰지 않는다.
 - **Scenarios** — Given-When-Then. Happy path + 주요 edge case. 각 시나리오는 Done Criteria 중 하나에 매핑.
 - **Out of Scope** — 이번에 하지 않는 것을 명시 (비어 있으면 스코프 팽창 신호).
 - **Assumptions** — 3단계에서 채택한 기본값 전부.
+- **Constraints** — 구현·보안·호환성 경계. execution packet으로 압축돼도 반드시 보존한다.
 - **API Contract** (해당 시에만) — 엔드포인트/요청/응답 형태. 이 섹션이 있으면 이후 `/vibe.contract` 가 drift 를 검사한다.
 
 이어서 `.vibe/features/{feature-name}.feature` 를 생성한다: 시나리오 섹션을 gherkin 으로 변환 (Done Criteria ↔ Scenario 매핑 유지). `/vibe.run` 이 이 파일을 구현·검증 단위로 사용한다.
@@ -71,6 +76,8 @@ Task(subagent_type="Explore",
 작성 직후, 아래 체크리스트로 자기 SPEC 을 **1회** 점검하고 걸리는 항목을 즉시 고친다. 외부 LLM 리뷰 없음, 수렴 루프 없음 — 한 번 고치면 끝.
 
 - [ ] 모든 Done Criteria 가 명령/관찰로 판정 가능한가 (모델 자기 보고가 아닌)
+- [ ] Context Sources 와 Assumptions 가 분리됐고, 각 Done Criteria 의 Evidence Required 가 있는가
+- [ ] Human Taste 가 결정론적 완료 게이트에 섞이지 않았는가
 - [ ] 모든 시나리오가 Done Criteria 에 매핑되는가 (고아 시나리오 없음)
 - [ ] 수치가 필요한 곳에 수치가 있는가 (제한·타임아웃·크기 — 없으면 기본값 + Assumptions)
 - [ ] Out of Scope 가 비어 있지 않은가

package/skills/vibe/SKILL.md

@@ -64,13 +64,14 @@ user-invocable: true
 | **regression fix** | "회귀", "테스트 깨졌", "다시 통과" | regress → run → verify |
 | **contract drift** | "API 변경", "계약 깨졌", "스펙 불일치" | contract → regress (P1만) |
 | **scaffold** | "프로젝트 만들기", "셋업", "초기 구조" | scaffold |
-| **docs sync** | "문서 갱신", "README", "AGENTS.md" | docs |
+| **docs sync** | "문서 갱신", "README", "AGENTS.md", "다이어그램", "코드맵" | docs (diagram/codemaps 의도 포함) |
 | **analyze** | "분석", "조사", "이건 뭐야" + 파일/URL | analyze |
 | **reason** | "추론", "깊게 생각", "트레이드오프", "어떻게 접근" 등 복잡한 사고 요청 | reason |
 | **event** | "이벤트", "커뮤니티", "D-Day", "행사 자동화" | event |
 | **harness check** | "하네스", "환경 점검" | harness |
 | **test self** | "vibe 테스트", "CC ↔ Codex 비교" | test |
-| **utils** | "이어서", "메모리", "체크포인트" | utils |
+| **session continue** | "이어서", "메모리", "체크포인트" | continue |
+| **image generation** | "이미지 생성", "아이콘", "배너", "목업 이미지" | image |
 
 복수 의도면 우선순위: resume > figma-driven > new feature > 기타.
 

package/skills/vibe.analyze/SKILL.md

@@ -75,15 +75,9 @@ Extract keywords from the user request:
 
 #### 2. Understand Project Structure
 
-Read `CLAUDE.md`, `package.json`, `pyproject.toml`, etc. to identify tech stack:
+Read `CLAUDE.md`, `package.json`, `pyproject.toml`, etc. to identify tech stack.
 
-**Backend:**
-- FastAPI/Django: `app/api/`, `app/services/`, `app/models/`
-- Express/NestJS: `src/controllers/`, `src/services/`, `src/models/`
-
-**Frontend:**
-- React/Next.js: `src/components/`, `src/pages/`, `src/hooks/`
-- Flutter: `lib/screens/`, `lib/services/`, `lib/providers/`
+> Read `references/output-templates.md` for the full backend/frontend stack → directory mapping.
 
 #### 3. Explore Related Code (Parallel Sub-Agents)
 
@@ -105,15 +99,7 @@ Agent(subagent_type="Explore", model="haiku",
   prompt="Find all [FEATURE] related data models, schemas, and database queries. Document relationships and key fields.")
 ```
 
-**Scale for large projects (6+ related files):**
-
-```text
-Agent(subagent_type="Explore", model="haiku",
-  prompt="Find all test files related to [FEATURE]. Identify tested vs untested paths.")
-
-Agent(subagent_type="Explore", model="haiku",
-  prompt="Analyze [FEATURE] configuration, environment variables, and external integrations.")
-```
+> Read `references/output-templates.md` for the additional "Scale for large projects (6+ related files)" agent prompts.
 
 **After all agents return:**
 - Synthesize results → proceed to Flow Analysis
@@ -138,62 +124,13 @@ Agent(subagent_type="Explore", model="haiku",
 
 #### 5. Output
 
-```markdown
-## [feature-name] Analysis Results
-
-### Overview
-- **Feature**: [one-line summary]
-- **Status**: [Complete / In progress / Not implemented]
-- **Files**: N related files
-
-### Structure
-
-#### API Endpoints
-| Method | Path | Description | Auth |
-|--------|------|-------------|------|
-| POST | /api/v1/auth/login | User login | None |
-
-#### Core Services
-- `auth_service.py`: Authentication logic
-  - `login()`: Processes login
-  - `verify_token()`: Validates JWT
-
-#### Data Models
-- `User`: User table
-  - Key fields: id, email, password_hash
-  - Relationships: Session (1:N)
-
-### Reference Files
-- src/api/auth/router.py:L10-50
-- src/services/auth_service.py:L1-100
-```
+> Read `references/output-templates.md` for the full Mode 1 output format.
 
 #### 6. Next Steps
 
-After analysis, suggest mode-specific follow-up actions:
-
-**After code/feature analysis:**
-
-| Task Scope | Approach |
-|------------|----------|
-| Simple fix (1-2 files) | Plan Mode |
-| Complex feature (3+ files) | `/vibe.spec` |
-
-**After document analysis:**
-
-| Goal | Approach |
-|------|----------|
-| Apply findings to project | `/vibe.spec "feature-name"` |
-| Derive improvement direction | Plan Mode |
-| Compare with another source | `/vibe.analyze [other target]` |
+After analysis, suggest mode-specific follow-up actions.
 
-**After website analysis:**
-
-| Goal | Approach |
-|------|----------|
-| Build similar product | `/vibe.spec` |
-| Improve existing UI | `/vibe.figma` |
-| Compare with another site | `/vibe.analyze [other URL]` |
+> Read `references/output-templates.md` for the full Next Steps decision tables (code/feature, document, website).
 
 Wait for user's choice before proceeding.
 
@@ -218,13 +155,7 @@ Analyze document **structure, key content, quality, and applicability** to:
 
 #### 2. Classify Document Type
 
-| Type | Analysis Focus |
-|------|---------------|
-| Technical spec | API definitions, data models, sequence diagrams |
-| Presentation/slides | Key claims, frameworks, case studies |
-| PRD/requirements | User stories, acceptance criteria, scope |
-| Business document | Strategy, decision points, action items |
-| Research/academic | Methodology, conclusions, applicability |
+> Read `references/output-templates.md` for the full document-type → analysis-focus table.
 
 #### 3. Analyze Content (Parallel Sub-Agents)
 
@@ -244,33 +175,7 @@ Agent(subagent_type="general-purpose", model="haiku",
 
 #### 5. Output
 
-```markdown
-## [Document Name] Analysis
-
-### Overview
-- **Type**: [Presentation / Technical spec / PRD / ...]
-- **Topic**: [one-line summary]
-- **Pages/Sections**: N
-- **Audience**: [Developers / PMs / Executives / ...]
-
-### Key Content
-1. **[Concept 1]**: Description
-2. **[Concept 2]**: Description
-
-### Frameworks/Models (if any)
-- [Systematic structure presented in the document]
-
-### Project Relevance
-| Recommendation | Current State | Gap |
-|----------------|---------------|-----|
-| ... | ... | ... |
-
-### Key Insights
-- [Most important takeaway]
-
-### Suggested Actions
-1. ...
-```
+> Read `references/output-templates.md` for the full Mode 2 output format.
 
 #### Fallback
 
@@ -319,40 +224,7 @@ If a Figma URL is detected, switch to **Figma-specific analysis**:
 
 #### 4. Output
 
-```markdown
-## [URL] Analysis
-
-### Overview
-- **Site type**: [SaaS / E-commerce / Portfolio / ...]
-- **Tech stack**: [Next.js, Tailwind, ...]
-- **Overall score**: N/100
-
-### Technical Analysis
-| Area | Detection | Details |
-|------|-----------|---------|
-| Framework | React/Next.js | SSR enabled |
-| CSS | Tailwind CSS | v3.4 |
-
-### UX/UI Analysis
-- **Navigation**: [assessment]
-- **CTA placement**: [assessment]
-- **Responsive design**: [assessment]
-
-### SEO Analysis (N/100)
-| Element | Status | Recommendation |
-|---------|--------|----------------|
-| Title | Present | Appropriate length |
-| Meta Description | Missing | Add description |
-
-### Accessibility (WCAG 2.1 AA)
-- **Semantic HTML**: [assessment]
-- **Keyboard navigation**: [assessment]
-- **Screen reader support**: [assessment]
-
-### Improvement Suggestions
-1. [highest priority]
-2. ...
-```
+> Read `references/output-templates.md` for the full Mode 3 output format.
 
 #### Fallback
 
@@ -393,30 +265,7 @@ If `WebFetch` fails:
 
 Save to `.vibe/reports/analysis-{date}.md`:
 
-```markdown
-# Project Analysis Report
-
-## Overview
-- Analysis date: YYYY-MM-DD HH:MM
-- Scope: Full / Code / Deps / Arch
-
-## Code Quality (N/100)
-- Average complexity: N (good/warning/critical)
-- High complexity files: N
-
-## Dependencies (N/100)
-- Total packages: N
-- Updates needed: N
-- Security issues: N
-
-## Architecture (N/100)
-- Circular dependencies: N found
-- Layer violations: N
-
-## Improvement Suggestions
-1. ...
-2. ...
-```
+> Read `references/output-templates.md` for the full Mode 4 report format.
 
 ## Core Tools (Semantic Analysis)
 
@@ -438,95 +287,9 @@ node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/index
 
 ## Quality Gate (Mandatory)
 
-### Mode-Specific Checklists
-
-**Code/Feature Analysis:**
-
-| Category | Check Item | Weight |
-|----------|------------|--------|
-| Completeness | All related files identified | 20% |
-| Completeness | All API endpoints documented | 15% |
-| Completeness | All data models mapped | 15% |
-| Accuracy | File paths verified to exist | 10% |
-| Accuracy | Line numbers accurate | 10% |
-| Depth | Business logic explained | 10% |
-| Depth | Dependencies mapped | 10% |
-| Actionability | Next steps clearly defined | 10% |
-
-**Document Analysis:**
-
-| Category | Check Item | Weight |
-|----------|------------|--------|
-| Completeness | Full document read | 20% |
-| Completeness | All key concepts extracted | 20% |
-| Structure | Section structure identified | 15% |
-| Depth | Project relevance analyzed | 15% |
-| Depth | Gap analysis performed | 15% |
-| Actionability | Specific follow-up actions suggested | 15% |
-
-**Website Analysis:**
-
-| Category | Check Item | Weight |
-|----------|------------|--------|
-| Completeness | HTML fetched and parsed | 15% |
-| Tech | Tech stack identified | 15% |
-| UX | UX/UI patterns analyzed | 15% |
-| SEO | SEO elements inspected | 15% |
-| A11y | Accessibility checked | 15% |
-| Performance | Performance hints analyzed | 10% |
-| Actionability | Improvements suggested | 15% |
-
-### Score Calculation
-
-```
-Score = sum(checked items * weight) / 100
-
-Grades:
-- 95-100: EXCELLENT — comprehensive analysis
-- 90-94:  GOOD — minor gaps, additional exploration recommended
-- 80-89:  FAIR — needs deeper exploration
-- 0-79:   POOR — incomplete, re-analyze
-```
-
-### Depth Levels
-
-| Level | Scope | Output |
-|-------|-------|--------|
-| L1: Surface | File names, basic structure | File list |
-| L2: Structure | Functions, classes, imports | Structure map |
-| L3: Logic | Business logic, data flow | Flow analysis |
-| L4: Deep | Edge cases, dependencies, risks | Full analysis |
-
-**Minimum**: L3 for feature analysis, L2 for project overview.
-
-### Forbidden Patterns
-
-| Pattern | Problem | Fix |
-|---------|---------|-----|
-| "and more..." | Incomplete | List all items |
-| "etc." | Vague | Be specific |
-| "related files" without paths | Missing detail | Provide file paths |
-| Missing line numbers | Hard to navigate | Use `:L10-50` format |
-| No auth info on endpoints | Security gap | Always specify auth |
-
-### Quality Thresholds
-
-**Code (`--code`):**
-
-| Metric | Good | Warning | Critical |
-|--------|------|---------|----------|
-| Avg Complexity | ≤10 | 11-15 | >15 |
-| Max Function Length | ≤30 | 31-50 | >50 |
-| High Complexity Files | 0 | 1-3 | >3 |
-| Circular Dependencies | 0 | 1 | >1 |
-
-**Dependencies (`--deps`):**
+Each mode has a weighted completeness checklist. Score = sum(checked items × weight) / 100. **Minimum depth: L3 for feature analysis, L2 for project overview.**
 
-| Metric | Good | Warning | Critical |
-|--------|------|---------|----------|
-| Outdated Packages | 0-3 | 4-10 | >10 |
-| Security Vulnerabilities | 0 | 1-2 (low) | Any high/critical |
-| Major Version Behind | 0 | 1-2 | >2 |
+> Read `references/quality-gate.md` for the full mode-specific weighted checklists, score grades, depth-level table, forbidden-patterns table, and quality thresholds (code/deps).
 
 ---