@su-record/vibe 3.2.64 → 4.0.1

package/skills/vibe.figma/templates/remapped-tree.md

@@ -1,277 +0,0 @@
-# Remapped Tree Template
-
-tree.json을 코드 생성에 최적화된 구조로 리매핑한다.
-모든 브레이크포인트의 tree.json을 동시에 입력받아, 노드 매칭 + CSS diff까지 포함.
-
----
-
-## 입력
-
-```
-/tmp/{feature}/
-  mo-main/tree.json    ← 모바일 Figma tree
-  pc-main/tree.json    ← 데스크탑 Figma tree (있으면)
-```
-
-## 출력
-
-```
-/tmp/{feature}/remapped.json
-```
-
----
-
-## 구조 정의
-
-```json
-{
-  "feature": "winter-pcbang",
-  "designWidth": {
-    "mo": 720,
-    "pc": 2560
-  },
-  "minWidth": 340,
-  "breakpoint": 1025,
-  "sections": [
-    {
-      "section": "hero",
-      "tag": "section",
-      "storyboard": {
-        "name": "Hero (키비주얼)",
-        "features": ["키비주얼 + 이벤트 정보 + 공유 버튼"],
-        "interactions": ["공유 버튼 클릭 → 공유 다이얼로그"],
-        "states": ["default"]
-      },
-      "bg": {
-        "mo": { "nodeId": "...", "file": "mo-main/bg/hero-bg.webp" },
-        "pc": { "nodeId": "...", "file": "pc-main/bg/hero-bg.webp" }
-      },
-      "size": {
-        "mo": { "w": 720, "h": 1280 },
-        "pc": { "w": 2560, "h": 1080 }
-      },
-      "children": [
-        {
-          "role": "title-group",
-          "type": "flex-column",
-          "css": {
-            "mo": { "alignItems": "center", "gap": "24px", "width": "620px" },
-            "pc": { "alignItems": "center", "gap": "40px", "width": "1200px" }
-          },
-          "children": [
-            {
-              "role": "title-image",
-              "type": "node-render",
-              "render": {
-                "mo": { "nodeId": "...", "file": "mo-main/content/hero-title.webp", "size": { "w": 620, "h": 174 } },
-                "pc": { "nodeId": "...", "file": "pc-main/content/hero-title.webp", "size": { "w": 1200, "h": 340 } }
-              },
-              "alt": "추운 겨울, 따뜻한 보상이 펑펑"
-            },
-            {
-              "role": "subtitle-image",
-              "type": "node-render",
-              "render": {
-                "mo": { "nodeId": "...", "file": "mo-main/content/hero-subtitle.webp", "size": { "w": 586, "h": 32 } },
-                "pc": { "nodeId": "...", "file": "pc-main/content/hero-subtitle.webp", "size": { "w": 1100, "h": 60 } }
-              },
-              "alt": "겨울을 녹일 보상, 지금 PC방에서 획득하세요!"
-            }
-          ]
-        },
-        {
-          "role": "share-button",
-          "type": "interactive",
-          "tag": "button",
-          "css": {
-            "mo": { "width": "72px", "height": "72px", "borderRadius": "500px", "backgroundColor": "rgba(13,40,61,0.5)", "border": "1px solid #fff" },
-            "pc": { "width": "96px", "height": "96px", "borderRadius": "500px", "backgroundColor": "rgba(13,40,61,0.5)", "border": "1px solid #fff" }
-          },
-          "event": "share"
-        },
-        {
-          "role": "period-panel",
-          "type": "content-with-bg",
-          "bg": {
-            "mo": { "nodeId": "...", "file": "mo-main/bg/period-bg.webp" },
-            "pc": { "nodeId": "...", "file": "pc-main/bg/period-bg.webp" }
-          },
-          "size": {
-            "mo": { "w": 720, "h": 500 },
-            "pc": { "w": 2560, "h": 400 }
-          },
-          "children": [
-            {
-              "role": "target-label",
-              "type": "text",
-              "tag": "p",
-              "content": "참여 대상 : PC 유저 (Steam, Kakao)",
-              "css": {
-                "mo": { "fontSize": "24px", "fontWeight": "600", "color": "#ffffff", "textAlign": "center" },
-                "pc": { "fontSize": "32px", "fontWeight": "600", "color": "#ffffff", "textAlign": "center" }
-              }
-            },
-            {
-              "role": "info-group",
-              "type": "flex-column",
-              "css": {
-                "mo": { "gap": "10px", "padding": "22px 14px" },
-                "pc": { "gap": "16px", "padding": "30px 40px" }
-              },
-              "children": [
-                {
-                  "role": "info-row",
-                  "type": "flex-column",
-                  "css": {
-                    "mo": { "gap": "4px" },
-                    "pc": { "gap": "8px" }
-                  },
-                  "children": [
-                    {
-                      "role": "label",
-                      "type": "text",
-                      "tag": "span",
-                      "content": "이벤트 기간 (이벤트 참여 및 미션 수행)",
-                      "css": {
-                        "mo": { "fontSize": "24px", "fontWeight": "700", "color": "#003879" },
-                        "pc": { "fontSize": "28px", "fontWeight": "700", "color": "#003879" }
-                      }
-                    },
-                    {
-                      "role": "value",
-                      "type": "text",
-                      "tag": "span",
-                      "content": "2025.12.22. 11:00 ~ 2026.01.18. 11:00 [KST]",
-                      "css": {
-                        "mo": { "fontSize": "28px", "fontWeight": "500", "color": "#171716", "fontFamily": "'Roboto Condensed', sans-serif" },
-                        "pc": { "fontSize": "36px", "fontWeight": "500", "color": "#171716", "fontFamily": "'Roboto Condensed', sans-serif" }
-                      }
-                    }
-                  ]
-                }
-              ]
-            }
-          ]
-        }
-      ]
-    }
-  ]
-}
-```
-
----
-
-## 노드 타입 분류
-
-tree.json의 각 노드를 다음 타입 중 하나로 분류:
-
-| type | 판별 기준 | 코드 출력 |
-|------|----------|---------|
-| `section` | 1depth 자식 프레임 | `<section>` + background-image |
-| `flex-column` | Auto Layout VERTICAL | `<div>` + flex-direction: column |
-| `flex-row` | Auto Layout HORIZONTAL | `<div>` + flex-direction: row |
-| `text` | TEXT 노드 | `<span>/<p>/<h2>` + typography CSS |
-| `node-render` | 콘텐츠 이미지 (타이틀, 아이콘) | `<img>` + 노드 렌더링 |
-| `vector-group` | VECTOR 3+ 자식 (커스텀 폰트) | `<img>` + GROUP 렌더링 |
-| `interactive` | name에 btn/CTA/link | `<button>/<a>` + event |
-| `content-with-bg` | 콘텐츠 + 배경 프레임 | `<div>` + background-image + children |
-| `repeat` | 같은 구조 INSTANCE 3+ | `v-for` / `.map()` |
-| `skip` | 장식선, 0px, BG 하위 개별 레이어 | 제외 |
-
----
-
-## 브레이크포인트 노드 매칭
-
-```
-MO tree.json 1depth 자식:
-  Hero (720x1280) ──────── PC tree.json에서 "Hero" name 매칭
-  KID (720x487)   ──────── PC: "KID" 매칭
-  Daily (720x3604) ─────── PC: "Daily" 매칭
-
-매칭 기준:
-  1순위: name 완전 일치
-  2순위: name prefix 일치 (Hero_MO → Hero_PC)
-  3순위: 순서 기반 (같은 위치의 자식)
-  매칭 불가: 해당 BP에만 존재하는 섹션으로 표시
-```
-
----
-
-## CSS diff → SCSS 출력 규칙
-
-```
-remapped.json의 mo/pc CSS를 비교:
-
-같은 값:
-  → 기본 스타일로 출력 (vw 기반, mo designWidth 사용)
-
-다른 값:
-  → 기본: mo 값 (vw 기반)
-  → @media (min-width: {breakpoint}px): pc 값 (vw 기반, pc designWidth 사용)
-
-예시:
-  "gap": { "mo": "24px", "pc": "40px" }
-  →
-  gap: 3.33vw;                    // 24 / 720 × 100
-  @media (min-width: 1025px) {
-    gap: 1.56vw;                  // 40 / 2560 × 100
-  }
-
-  "color": { "mo": "#003879", "pc": "#003879" }
-  → (같으므로 @media 없음)
-  color: #003879;
-```
-
----
-
-## 리매핑 프로세스
-
-```
-입력:
-  - Phase 1 스토리보드 스펙 (섹션 목록 + 기능 정의 + 인터랙션)
-  - Phase 2 추출 데이터 (모든 BP의 tree.json + 렌더링 이미지)
-
-1. 스토리보드 × tree.json 섹션 매칭
-   스토리보드에서 정의한 섹션 목록을 tree.json 1depth 자식과 매칭:
-
-   | 스토리보드 섹션 | tree.json name | 매칭 방법 |
-   |---------------|---------------|----------|
-   | Hero (키비주얼) | "Hero" | name 일치 |
-   | KID (로그인) | "KID" | name 일치 |
-   | Daily (출석 미션) | "Daily" | name 일치 |
-   | PlayTime (플레이타임) | "Frame 633371" | name 불일치 → 순서 기반 |
-
-   name이 "Frame 633372" 같은 무의미한 이름이면:
-   → 스토리보드의 섹션 순서로 매칭
-   → 매칭 후 스토리보드의 role/기능을 remapped.json에 기록
-
-2. 스토리보드 기능 정의 → 노드 역할 확정
-   스토리보드에서 정의한 기능/인터랙션으로 tree 노드의 role을 확정:
-
-   스토리보드: "STEP 1. 일일 출석 - 출석하기 버튼"
-   tree.json: Daily > Contents > FRAME > children 중 name="Btn_CheckIn"
-   → role: "interactive", event: "check-in", tag: "button"
-
-   스토리보드: "누적 출석 보상 - DAY2, DAY3, DAY5, DAY10"
-   tree.json: Daily > Contents > FRAME > INSTANCE × 4
-   → role: "repeat", items: 4, template: first INSTANCE
-
-   스토리보드가 없는 노드:
-   → name/type 기반 추정 (기존 방식 유지)
-   → 장식/BG는 스토리보드에 없으므로 자동 분류
-
-3. BP 간 섹션 매칭
-   모든 BP의 tree.json에서 같은 섹션 찾기:
-   → name 일치 또는 스토리보드 매칭 결과로 연결
-   → MO Hero ↔ PC Hero
-
-4. 각 섹션에 대해 재귀적으로:
-   a. 노드 타입 분류 (위 테이블) — 스토리보드로 확정된 role 우선
-   b. BG 프레임 식별 → frame-render로 마킹
-   c. 콘텐츠 이미지/벡터 그룹 → node-render로 마킹
-   d. TEXT 노드 → content + css 추출
-   e. skip 대상 제거
-   f. 각 BP의 CSS 값을 mo/pc로 분리 저장
-
-5. remapped.json 출력
-```

package/skills/vibe.git-worktree/SKILL.md

@@ -1,70 +0,0 @@
----
-name: vibe.git-worktree
-invocation: [auto]
-tier: optional
-description: "Use when PR review, hotfix, parallel testing, or simultaneous branch work needs an isolated Git worktree."
-triggers: [worktree, hotfix, parallel branch, multiple branches]
-priority: 50
----
-
-# Git Worktree
-
-## Pre-check (K1)
-
-> Do you need to work on another branch without losing current work? If you can just `git stash` and switch, worktree may be overkill.
-
-## Core Commands
-
-```bash
-# Create worktree for PR review
-git worktree add ../review-{pr_number} origin/pr/{pr_number}
-
-# Create worktree with new branch (hotfix)
-git worktree add -b hotfix/urgent ../hotfix main
-
-# List all worktrees
-git worktree list
-
-# Remove when done
-git worktree remove ../review-{pr_number}
-
-# Clean up stale entries
-git worktree prune
-```
-
-## PR Review Workflow
-
-```
-1. git worktree add ../review-123 origin/pr/123
-2. cd ../review-123
-3. npm install && npm test
-4. Run review agents
-5. cd - && git worktree remove ../review-123
-```
-
-## Hotfix Workflow
-
-```
-1. git worktree add -b hotfix/critical ../hotfix main
-2. cd ../hotfix
-3. Fix bug → commit → push
-4. cd - && git worktree remove ../hotfix
-```
-
-## Naming Convention
-
-```bash
-../review-{pr_number}         # PR review
-../hotfix-{issue_number}      # Hotfix
-../experiment-{feature_name}  # Experiment
-```
-
-## Troubleshooting
-
-Read `references/troubleshooting.md` only when creation, locking, or cleanup fails. Successful calls do not load it.
-
-## Done Criteria (K4)
-
-- [ ] Worktree created and work completed in isolation
-- [ ] Worktree removed after work is done
-- [ ] No stale worktrees left (`git worktree list` clean)

package/skills/vibe.git-worktree/references/troubleshooting.md

@@ -1,9 +0,0 @@
-# Worktree Troubleshooting
-
-Load only after a worktree command fails.
-
-| Error | Fix |
-|-------|-----|
-| "already checked out" | Branch is in another worktree — `git worktree list`, then remove |
-| Locked worktree | `git worktree unlock <path>` |
-| Stale worktree | `git worktree prune` |

package/skills/vibe.git-worktree/rubrics/when-to-use.md

@@ -1,55 +0,0 @@
-# Git Worktree: When to Use Decision Guide
-
-## Decision Tree
-
-```
-Need to work on a different branch?
-    │
-    ├─ How long? < 5 minutes
-    │       └─ Use git stash + switch
-    │
-    ├─ Will you need to run tests/build?
-    │       └─ No → git stash is fine
-    │           Yes → Consider worktree
-    │
-    └─ Can you commit current work?
-            └─ Yes → commit + switch (simplest)
-                No → worktree or stash
-```
-
-## Use Worktree When
-
-| Scenario | Reason |
-|----------|--------|
-| Reviewing a PR that needs running | Avoids dirty working tree; test in isolation |
-| Critical hotfix while mid-feature | Keep feature branch untouched |
-| A/B testing two implementations | Both runnable simultaneously |
-| Long-running parallel experiment | Work on both without context switching |
-
-## Skip Worktree When
-
-| Scenario | Better Alternative |
-|----------|--------------------|
-| Quick config change on another branch | `git stash && git switch` |
-| Just reading code on another branch | `git show branch:file` |
-| Already committed current work | `git switch` directly |
-| Change touches same files | Merging will conflict regardless |
-| Repo uses large node_modules | Each worktree needs separate install — expensive |
-
-## Cost/Benefit
-
-| Factor | Worktree Cost |
-|--------|--------------|
-| Disk space | Full working copy per worktree |
-| `npm install` / `pnpm install` | Required in each worktree |
-| Mental overhead | Tracking multiple worktree paths |
-| Cleanup discipline | Must `git worktree remove` when done |
-
-**Rule of thumb**: If the task is under 15 minutes, `git stash` is almost always faster than setting up a worktree.
-
-## Gotchas
-
-- A branch can only be checked out in **one** worktree at a time
-- Worktrees share `.git` — commits in any worktree are immediately visible in all
-- Forgetting to remove worktrees leaves stale locks — run `git worktree prune` periodically
-- CI/CD hooks may not run correctly outside the main worktree path

package/skills/vibe.harness/SKILL.md

@@ -1,144 +0,0 @@
----
-name: vibe.harness
-description: 프로젝트의 Claude Code·Codex 하네스 품질과 병목을 진단하거나 6축 성숙도 점수가 필요할 때 사용한다.
-argument-hint: (no arguments)
-user-invocable: true
----
-
-# /vibe.harness
-
-## 완료 기준
-
-- [ ] 6개 평가 축에 각각 점수와 파일 근거가 있다.
-- [ ] 적용할 수 없는 하네스 항목은 감점 대신 N/A로 기록되어 있다.
-- [ ] P1 finding마다 검사 명령 또는 파일 위치가 있다.
-- [ ] harness 보고서가 지정 경로에 존재한다.
-
-Diagnose project Harness Engineering maturity across 6 axes and suggest targeted improvements.
-
-> Harness = the working environment that enables AI to operate effectively on its own.
-> Encompasses context, constraints, workflows, verification, and compounding — not just guardrails.
-
-## Step 0: Detect Project Type
-
-Before scoring, read `CLAUDE.md` and `package.json` to determine project type:
-
-| Type | Signal | Effect |
-|------|--------|--------|
-| **Application** (webapp, api, fullstack, mobile) | `type` in config, app-like structure | Full rubric applies |
-| **Package/Library** | `"main"` or `"exports"` in package.json, "npm package" in CLAUDE.md | Skip docs/, .dev/ items (mark N/A), adjust total denominator |
-| **Monorepo** | `workspaces` in package.json, `apps/` or `packages/` dirs | Score each workspace separately |
-
-When items are N/A, **remove their points from the total** rather than scoring 0. A library scoring 65/80 (N/A items excluded) = 81%, not 65%.
-
----
-
-## Process
-
-### 1. Collect Project State (Parallel Delegation)
-
-Delegate the three independent inspections through the harness's native
-collaboration capability. Claude Code maps each worker to Task/Agent; Codex
-maps each worker to native collaboration. Inherit the session model by default
-and dispatch concurrently when capacity permits:
-
-```text
-- Worker: check scaffolding, docs/.dev presence, source organization, test separation, and top-level structure.
-- Worker: check `CLAUDE.md`/`AGENTS.md`, harness rules, lifecycle configuration, `.vibe/config.json`, and installed skills.
-- Worker: check SPEC/Feature files, tests, CI configuration, and learning records.
-```
-
-### 2. Score Each Axis
-
-#### Axis 1: Scaffolding — /20
-
-| Item | Criteria | Points |
-|------|----------|--------|
-| Role-based folders | src/ subdivided by role (components/, services/, models/, etc.) | /5 |
-| docs/ exists | Business document directory with content (N/A for packages/libraries) | /4 |
-| .dev/ exists | AI work log directory (N/A for packages/libraries) | /3 |
-| tests/ separated | Tests not co-located with source files | /3 |
-| .gitignore complete | Includes out/, .dev/scratch/, settings.local.json | /2 |
-| Layer separation | Domain/service/infra or similar architectural layers | /3 |
-
-#### Axis 2: Context — /20
-
-| Item | Criteria | Points |
-|------|----------|--------|
-| CLAUDE.md exists | Serves as project map | /5 |
-| CLAUDE.md is concise | ~100 lines or fewer, pointer-based | /3 |
-| Rules defined | Coding rules and test conventions in .claude/rules/ or similar | /4 |
-| Progressive disclosure | Skill tier separation or rules loaded via glob patterns | /3 |
-| docs/ referenced | CLAUDE.md references docs/ for business context | /3 |
-| Language rules | Stack-specific coding standards defined | /2 |
-
-#### Axis 3: Planning — /15
-
-| Item | Criteria | Points |
-|------|----------|--------|
-| SPEC workflow | System for generating spec/feature files | /5 |
-| Requirements gathering | Interview or requirements collection process exists | /4 |
-| Approval gates | Confirmation step between planning and implementation | /3 |
-| Templates | SPEC/Feature templates available | /3 |
-
-#### Axis 4: Orchestration — /15
-
-| Item | Criteria | Points |
-|------|----------|--------|
-| Agents or skills | Specialized agents or skills defined | /5 |
-| Parallel composition | Parallel native subagents (architect + implementer + tester, etc.) | /4 |
-| Permission model | Per-agent permission separation (read-only vs write) | /3 |
-| Non-code workflows | Support for documentation, research, and other non-code tasks | /3 |
-
-#### Axis 5: Verification — /15
-
-| Item | Criteria | Points |
-|------|----------|--------|
-| Automated quality checks | Explicit lint/type/test/JUDGE commands; lifecycle hooks may accelerate them | /4 |
-| Tests exist | Test files present and executable | /4 |
-| CI/CD | Automated build/test pipeline configured | /4 |
-| Traceability | SPEC → code → test mapping (RTM) | /3 |
-
-#### Axis 6: Compounding — /15
-
-| Item | Criteria | Points |
-|------|----------|--------|
-| Learnings recorded | Troubleshooting records in .dev/learnings/ (N/A for packages/libraries) | /4 |
-| Pattern accumulation | Repeated tasks codified as skills or rules | /4 |
-| Auto-improvement | Evolution Engine or similar self-improvement mechanism | /4 |
-| Memory | Cross-session learning persistence mechanism | /3 |
-
-### 3. Generate Report
-
-형식: `references/report-template.md` (Step 3 호출 시에만 읽는다).
-
-### 4. Save Report
-
-Save results to `.vibe/reports/harness-{date}.md` for historical tracking.
-
-### 5. Self-Repair Chain
-
-After scoring, if actionable gaps are detected:
-
-| Condition | Auto-Suggestion |
-|-----------|-----------------|
-| Scaffolding < 10/20 | Suggest `/vibe.scaffold` to generate missing directories |
-| Context < 10/20 | Suggest `vibe update` to regenerate CLAUDE.md |
-| Planning < 8/15 | Suggest `/vibe.spec` to establish SPEC workflow |
-| Verification < 8/15 | Suggest `vibe init` to install quality hooks |
-| Compounding < 8/15 | Suggest creating `.dev/learnings/` and enabling evolution engine |
-
-If user approves auto-fix, execute the suggested commands in sequence, then re-run `/vibe.harness` to verify improvement.
-
----
-
-## Principles
-
-1. **Score honestly** — never inflate scores
-2. **Suggest specific actions** — executable commands, not vague advice like "improve structure"
-3. **Focus on top 3** — don't try to fix everything at once
-4. **Track over time** — enable score comparison across runs via saved reports
-
----
-
-ARGUMENTS: $ARGUMENTS

package/skills/vibe.harness/references/report-template.md

@@ -1,46 +0,0 @@
-# Harness Diagnosis — 리포트 형식
-
-> `vibe.harness` Step 3 이 출력하는 진단 리포트의 형식. 채점 루브릭은 SKILL.md 의
-> `### 2. Score Each Axis` 가 SSOT 다 — 점수 기준을 여기에 다시 적지 않는다.
-
-```markdown
-## Harness Diagnosis (N/100)
-
-### Score and Grade
-- **Score**: N/100
-- **Grade**: [S / A / B / C / D]
-
-| Grade | Range | Description |
-|-------|-------|-------------|
-| S | 90-100 | Production-ready Harness |
-| A | 75-89 | Well-structured, minor gaps |
-| B | 60-74 | Functional but missing key elements |
-| C | 40-59 | Basic setup, significant gaps |
-| D | 0-39 | Minimal or no Harness |
-
-### Axis Scores
-
-| Axis | Score | Details |
-|------|-------|---------|
-| Scaffolding | /20 | [findings] |
-| Context | /20 | [findings] |
-| Planning | /15 | [findings] |
-| Orchestration | /15 | [findings] |
-| Verification | /15 | [findings] |
-| Compounding | /15 | [findings] |
-
-### Top 3 Improvements
-
-1. **[lowest axis]**: [specific action with command]
-2. **[second lowest]**: [specific action with command]
-3. **[third lowest]**: [specific action with command]
-
-### Auto-Fixable Items
-
-The following can be improved immediately:
-1. [ ] `/vibe.scaffold` — generate missing project directories
-2. [ ] `vibe init` — initialize AI configuration
-3. [ ] `vibe update` — regenerate CLAUDE.md from project analysis
-
-Proceed with auto-fix? (y/n)
-```

package/skills/vibe.image/SKILL.md

@@ -1,77 +0,0 @@
----
-name: vibe.image
-description: 아이콘·배너·목업 같은 래스터 이미지 산출물이 필요할 때 Antigravity 이미지 backend로 생성한다.
-argument-hint: '"description" [--pro] [--icon "AppName"] [--size WxH]'
-user-invocable: true
----
-
-# /vibe.image
-
-## Done Criteria
-
-- [ ] 요청된 이미지 파일이 지정 경로에 존재한다.
-- [ ] 파일 형식과 픽셀 크기가 요청값과 일치한다.
-- [ ] 투명 배경 요청 시 alpha channel이 존재한다.
-- [ ] 생성 결과 경로가 최종 응답에 포함된다.
-
-Generate images using the Antigravity image backend.
-
-- **Default**: Antigravity fast image - 빠르고 가벼운 이미지 생성
-- **--pro**: Antigravity pro image - 고품질 이미지 생성
-
-## Usage
-
-```
-/vibe.image "description"          # Generate image with Antigravity (icon, banner, etc.)
-/vibe.image --pro "description"    # High-quality generation
-/vibe.image --icon "AppName"       # Generate app icon/favicon
-```
-
-## MANDATORY Tool Invocation
-
-**CRITICAL: You MUST use the following command to generate images. Do NOT search for scripts, do NOT use gcloud, do NOT use any other method.**
-
-**Step 0: Script path:**
-- `[LLM_SCRIPT]` = `{{VIBE_PATH}}/hooks/scripts/llm-orchestrate.js`
-
-**Step 0-b: 비용 게이트 (생성 전 의무)** — 이미지 생성은 되돌릴 수 없는 지출이다. SSOT: `vibe/rules/loop-contract.md` 비용 게이트 절.
-
-```bash
-node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/tools/dispatch/index.js').then(t => { const op={kind:'paid-generation',provider:'antigravity',label:'이미지 {N}장 생성'}; console.log(t.formatCostGate(op, t.evaluateCostGate(op))); })"
-```
-
-`ask` 면 생성 전에 무엇을 몇 장 만들지 제시하고 확인받는다. `autonomous` 면 묻지 않고 인박스에 기록한 뒤 진행한다. `.vibe/config.json` 의 `costGate.paidGenerationRequiresApproval: false` 로 끌 수 있다.
-
-**General image generation (Antigravity fast image):**
-```bash
-node "[LLM_SCRIPT]" antigravity image "IMAGE_DESCRIPTION" --output "OUTPUT_PATH"
-```
-
-**Pro quality (Antigravity pro image):**
-```bash
-node "[LLM_SCRIPT]" antigravity image "IMAGE_DESCRIPTION" --pro --output "OUTPUT_PATH"
-```
-
-**With size option:**
-```bash
-node "[LLM_SCRIPT]" antigravity image "IMAGE_DESCRIPTION" --size "1920x1080" --output "OUTPUT_PATH"
-```
-
-## How to Parse User Request
-
-1. Extract the **image description** from the user's message (what to generate)
-2. Extract the **output path** from the user's message (where to save)
-   - If user specifies a path, use that path
-   - Default: `--output "./generated-image.png"`
-3. Extract **size** if specified, otherwise default 1024x1024
-4. If user requests **high quality / pro / 고품질**, add `--pro` flag
-
-> Read `references/image-generation-examples.md` for full worked examples, the JSON output format, and the --icon prompt template + example commands.
-
-## Prerequisites
-
-- Antigravity API key configured (`vibe antigravity key <key>`)
-
----
-
-ARGUMENTS: $ARGUMENTS