@su-record/vibe 2.9.23 → 2.9.24

package/README.md

@@ -1,13 +1,13 @@
 # VIBE
 
-**Easy vibe coding. Minimum quality guaranteed.**
+**바이브 코딩은 쉽게. 최소 품질은 보장.**
 
 [![npm](https://img.shields.io/npm/v/@su-record/vibe)](https://www.npmjs.com/package/@su-record/vibe)
 [![npm downloads](https://img.shields.io/npm/dt/@su-record/vibe.svg?style=flat-square&color=blue)](https://www.npmjs.com/package/@su-record/vibe)
 [![Node.js](https://img.shields.io/badge/node-%3E%3D18-green)](https://nodejs.org/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-yellow.svg)](LICENSE)
 
-Vibe is a quality harness for AI coding tools. It wraps around Claude Code, Codex, Cursor, or Gemini CLI and automatically enforces type safety, code quality, and security — so you can vibe-code fast without shipping garbage.
+Vibe는 AI 코딩 도구를 위한 품질 하네스입니다. Claude Code, Codex, Cursor, Gemini CLI를 감싸고, 타입 안전성, 코드 품질, 보안을 자동으로 강제합니다. 빠르게 바이브 코딩하되, 엉망인 코드가 나가지 않게.
 
 ```bash
 npm install -g @su-record/vibe
@@ -16,205 +16,156 @@ vibe init
 
 ---
 
-## The Workflow
+## 워크플로우
 
-One entry point. Everything else is automatic.
+진입점 하나. 나머지는 자동.
 
 ```
-/vibe.spec "coffee brand landing page"
+/vibe.spec "커피 브랜드 랜딩 페이지"
      |
      v
-  Interview  ─── "Who's the audience?" "What sections?" "Dark mode?" ───
-     |                     (loops until you say stop)
+  인터뷰    ─── "타깃은 누구?" "어떤 섹션?" "다크 모드?" ───
+     |                   (사용자가 "그만"할 때까지 반복)
      v
-  Plan       ─── Structured planning document (.claude/vibe/plans/)
+  기획서    ─── 구조화된 마크다운 기획서 (.claude/vibe/plans/)
      |
      v
-  SPEC       ─── PTCF spec + BDD features, GPT+Gemini parallel research
+  SPEC     ─── PTCF 명세 + BDD 피처, GPT+Gemini 병렬 리서치
      |
      v
-  Review     ─── Race review (GPT vs Gemini), quality gate (100-point, loop until perfect)
+  리뷰     ─── Race Review (GPT vs Gemini), 품질 게이트 (100점, 수렴까지 루프)
      |
      +──────────────────────────────┐
      v                              v
-  /vibe.run (Logic)            /vibe.figma (UI)
-  Implement from SPEC          Figma design ↔ Code
-  12 agents review             Read or Write
+  /vibe.run (로직)             /vibe.figma (UI)
+  SPEC 기반 구현               Figma 디자인 ↔ 코드
+  12개 에이전트 리뷰            읽기 또는 쓰기
      |                              |
      v                              v
-  /vibe.verify ──── /vibe.trace ──── Done
+  /vibe.verify ──── /vibe.trace ──── 완료
 ```
 
-**Smart Resume** — Stop at any step, close the session, come back later. `/vibe.spec` auto-detects where you left off and picks up from there. No need to remember feature names.
+**Smart Resume** — 아무 단계에서나 멈추고, 세션을 닫고, 나중에 돌아오세요. `/vibe.spec`이 중단된 위치를 자동 감지하고 이어서 진행합니다. feature 이름을 외울 필요 없음.
 
-**ultrawork** — Add `ultrawork` to skip all confirmation gates and run the full pipeline hands-free.
+**ultrawork** — 어느 명령이든 `ultrawork`를 붙이면 모든 확인 게이트를 건너뛰고 전체 파이프라인을 자동 실행합니다.
 
 ---
 
-## Quick Start
+## 빠른 시작
 
 ```bash
-# Install
+# 설치
 npm install -g @su-record/vibe
 
-# Initialize (auto-detects your stack, generates project-aware CLAUDE.md)
+# 프로젝트 초기화 (스택 자동 감지)
 cd your-project
 vibe init
 
-# Start your AI coding tool
+# AI 코딩 도구 시작
 claude
 
-# Run the workflow
-/vibe.spec "add user authentication"
+# 워크플로우 실행
+/vibe.spec "사용자 인증 추가"
 ```
 
 ---
 
-## Harness Engineering
+## Figma ↔ 코드
 
-Vibe is built on the [Harness Engineering](https://anthropic.com/engineering/harness-design) principle — designing the working environment so AI operates effectively on its own.
-
-### The 6 Axes
-
-| Axis | What it covers | Vibe implementation |
-|------|---------------|---------------------|
-| **Scaffolding** | Project structure, tools, boundaries | `/vibe.scaffold` generates optimized folder structure (docs/, .dev/, layered src/) |
-| **Context** | What AI knows | `vibe init` generates project-aware CLAUDE.md from actual structure analysis |
-| **Planning** | What to build | `/vibe.spec` → interview → plan → SPEC → review pipeline |
-| **Orchestration** | How to execute | 40+ agents, 12 teams, skill-based dispatch |
-| **Verification** | How to trust | Hooks, convergence loops, RTM traceability |
-| **Compounding** | How to improve | Evolution engine, session memory, auto-generated skills |
-
-### Diagnose Your Project
-
-```bash
-/vibe.harness    # Score your project across all 6 axes (0-100)
-```
-
-Produces a detailed report with per-axis scores, grade (S/A/B/C/D), and auto-fixable improvement suggestions. Detects project type (app vs package/library) and adjusts scoring accordingly.
-
----
-
-## Analyze Anything
-
-`/vibe.analyze` works on more than just source code:
+양방향. Figma에서 디자인을 읽거나, 기획서에서 Figma에 디자인을 쓰거나.
 
 ```bash
-/vibe.analyze "login"              # Feature/module code exploration
-/vibe.analyze --code               # Code quality analysis
-/vibe.analyze report.pdf           # Document analysis (PDF, slides, markdown)
-/vibe.analyze https://example.com  # Website analysis (UX, tech, SEO, a11y)
-/vibe.analyze https://figma.com/…  # Figma design analysis
-```
-
-Auto-detects input type (file extension → URL pattern → flag → string) and routes to the appropriate analysis mode with mode-specific quality gates.
-
----
-
-## Figma ↔ Code
-
-Bidirectional. Read designs from Figma, or write designs to Figma from a plan.
-
-```bash
-# READ — Add UI to existing project (follows project conventions)
+# READ — 기존 프로젝트에 UI 추가 (프로젝트 컨벤션 준수)
 /vibe.figma <figma-url> <figma-url>
 
-# READ — New standalone page (independent styles)
+# READ — 신규 독립 페이지 (독립 스타일)
 /vibe.figma --new <figma-url>
 
-# WRITE — Create Figma design from plan document
-/vibe.figma plan.md --create                 # Full (wireframe + visual design)
-/vibe.figma plan.md --create-storyboard      # Wireframe only
-/vibe.figma plan.md --create-design          # Visual design only
+# WRITE — 기획서에서 Figma 디자인 생성
+/vibe.figma plan.md --create                 # Full (와이어 + 비주얼 디자인)
+/vibe.figma plan.md --create-storyboard      # 와이어만
+/vibe.figma plan.md --create-design          # 비주얼 디자인만
 ```
 
-**How READ works**: Extracts the Figma node tree + 30 CSS properties via REST API, maps Auto Layout to Flexbox 1:1, generates responsive SCSS. Screenshot is for verification only — the tree is the source of truth.
+**READ 동작**: Figma REST API로 노드 트리 + 30개 CSS 속성 추출. Auto Layout → Flexbox 1:1 기계적 매핑. 스크린샷은 검증용 — 트리가 원천.
 
-**How WRITE works**: Parses plan document sections (Look & Feel, layout, responsive strategy), builds wireframe first for structure review, then applies visual design with design system components. Idempotent — re-run after editing the plan and only changed sections update.
+**WRITE 동작**: 기획서의 Look & Feel, 레이아웃, 반응형 전략 섹션을 파싱하여 와이어프레임을 먼저 그리고 (구조 검토), 그 위에 디자인 시스템 컴포넌트로 비주얼 적용. 멱등성 보장 — 기획서 수정 후 재실행하면 변경된 섹션만 갱신.
 
 ---
 
-## Quality Gates
+## 품질 게이트
 
-Three layers of defense on every tool call:
+모든 도구 호출마다 3계층 방어:
 
-| Layer | What it blocks |
-|-------|----------------|
-| Pre-commit hooks | `any` types, `@ts-ignore`, `console.log`, functions > 50 lines |
-| Review agents | 12 specialized reviewers run in parallel (security, performance, a11y, complexity, ...) |
-| Convergence loop | Review findings loop until P1 = 0. No round cap. Stuck = ask user, never silently proceed. |
+| 계층 | 차단 대상 |
+|------|----------|
+| Pre-commit 훅 | `any` 타입, `@ts-ignore`, `console.log`, 50줄 초과 함수 |
+| 리뷰 에이전트 | 12개 전문 리뷰어 병렬 실행 (보안, 성능, 접근성, 복잡도, ...) |
+| 수렴 루프 | 리뷰 findings P1=0까지 루프. 라운드 캡 없음. Stuck이면 사용자에게 질문, 절대 조용히 넘어가지 않음. |
 
 ---
 
-## Key Features
-
-**40+ agents** — Exploration, implementation, architecture, parallel code review, UI/UX analysis, security audit, Figma analysis/building.
-
-**44 skills** — Not all loaded at once. 3-tier system prevents context overload:
+## 주요 기능
 
-| Tier | When loaded | Purpose | Examples |
-|------|-------------|---------|----------|
-| **Core** | Always active | Bug prevention, workflow entry | quality gates, interview, plan |
-| **Standard** | `vibe init` selects by stack | Stack/capability support | figma, design-audit, techdebt |
-| **Optional** | Explicit `/skill` only | Reference, wrappers | chub-usage, context7 |
+**40+ 에이전트** — 탐색, 구현, 아키텍처, 병렬 코드 리뷰, UI/UX 분석, 보안 감사, Figma 분석/빌드.
 
-**Multi-LLM** — Claude orchestrates, GPT reasons, Gemini researches. Auto-routes by availability. Works Claude-only by default. When running under coco (GPT as primary), Claude CLI becomes the secondary for cross-validation — roles automatically reverse based on `~/.coco/` detection.
+**44개 스킬** — 한 번에 다 로드되지 않음. 3-tier 시스템으로 컨텍스트 과부하 방지:
 
-**Stack detection** — Auto-detects 24 frameworks (Next.js, Django, Rails, Go, Rust, Flutter, and more) and applies framework-specific rules and skills.
+| 티어 | 로드 시점 | 용도 | 예시 |
+|------|----------|------|------|
+| **Core** | 항상 활성 | 버그 방지, 워크플로 진입 | 품질 게이트, 인터뷰, 기획 |
+| **Standard** | `vibe init`이 스택별 선택 | 스택/역할 지원 | figma, design-audit, techdebt |
+| **Optional** | 명시적 `/skill` 호출만 | 레퍼런스, 래퍼 | chub-usage, context7 |
 
-**Project-aware CLAUDE.md** — `vibe init` and `vibe update` analyze your project's actual structure (folders, tech stack, build commands) and generate a tailored CLAUDE.md — not a static template.
+**멀티 LLM** — Claude가 오케스트레이션, GPT가 추론, Gemini가 리서치. 가용 모델에 따라 자동 라우팅. 기본값은 Claude 단독. coco 환경(GPT 주관)에서는 Claude CLI가 보조로 전환되어 cross-validation 수행 — `~/.coco/` 감지로 역할 자동 역전.
 
-**Session memory** — Decisions, constraints, and goals persist across sessions via SQLite + FTS5 hybrid search.
+**스택 감지** — 24개 프레임워크 자동 감지 (Next.js, Django, Rails, Go, Rust, Flutter 등) 후 프레임워크별 규칙과 스킬 적용.
 
-**Smart Resume** — `.last-feature` pointer tracks your latest work. `/vibe.spec` without arguments shows where you left off or lists all in-progress features.
+**세션 메모리** — 결정, 제약, 목표가 SQLite + FTS5 검색으로 세션 간 유지.
 
-**Self-repair** — Skills include error recovery tables. `/vibe.harness` diagnoses gaps and chains to `/vibe.scaffold` → `vibe update` for automated fixes.
+**Smart Resume** — `.last-feature` 포인터가 마지막 작업을 추적. 인자 없이 `/vibe.spec`을 호출하면 중단된 위치를 보여주거나 진행 중 feature 목록을 제시.
 
 ---
 
-## Supported Tools
+## 지원 도구
 
-| CLI | Status |
-|-----|--------|
-| [Claude Code](https://claude.ai/code) | Full support |
-| coco (`~/.coco/`) | Full support (auto-detect) |
-| [Codex](https://github.com/openai/codex) | Plugin |
-| [Cursor](https://cursor.sh) | Agents + Rules |
-| [Gemini CLI](https://github.com/google-gemini/gemini-cli) | Agents + Skills |
+| CLI | 상태 |
+|-----|------|
+| [Claude Code](https://claude.ai/code) | 전체 지원 |
+| coco (`~/.coco/`) | 전체 지원 (자동 감지) |
+| [Codex](https://github.com/openai/codex) | 플러그인 |
+| [Cursor](https://cursor.sh) | 에이전트 + 룰 |
+| [Gemini CLI](https://github.com/google-gemini/gemini-cli) | 에이전트 + 스킬 |
 
 ---
 
-## Commands
+## 명령어
 
-| Command | Purpose |
-|---------|---------|
-| `/vibe.spec` | Single entry point — interview, plan, spec, review, then run |
-| `/vibe.run` | Implement from SPEC |
-| `/vibe.figma` | Figma ↔ Code (read or write, 3 modes) |
-| `/vibe.verify` | Verify implementation against SPEC |
-| `/vibe.trace` | Requirements traceability matrix |
-| `/vibe.analyze` | Analyze any target — code, documents, websites, Figma |
-| `/vibe.scaffold` | Generate or audit project folder structure |
-| `/vibe.harness` | Diagnose Harness Engineering maturity (6-axis scoring) |
-| `/vibe.docs` | Generate project documentation |
+| 명령어 | 용도 |
+|--------|------|
+| `/vibe.spec` | 단일 진입점 — 인터뷰, 기획, SPEC, 리뷰, 그리고 구현까지 |
+| `/vibe.run` | SPEC 기반 구현 |
+| `/vibe.figma` | Figma ↔ 코드 (읽기 또는 쓰기, 3가지 모드) |
+| `/vibe.verify` | 구현이 SPEC에 맞는지 검증 |
+| `/vibe.trace` | 요구사항 추적 매트릭스 |
 
 ---
 
-## Documentation
+## 문서
 
-Full guides, skill reference, and configuration details are in the [Wiki](https://github.com/su-record/vibe/wiki).
+상세 가이드, 스킬 레퍼런스, 설정 방법은 [Wiki](https://github.com/su-record/vibe/wiki)를 참고하세요.
 
-- [README (Korean)](README.ko.md)
-- [Release Notes](RELEASE_NOTES.md)
+- [README (English)](README.md)
+- [릴리스 노트](RELEASE_NOTES.md)
 
 ---
 
-## Requirements
+## 요구사항
 
 - Node.js >= 18.0.0
-- Claude Code (required)
-- GPT, Gemini (optional)
+- Claude Code (필수)
+- GPT, Gemini (선택)
 
-## License
+## 라이선스
 
 MIT — Copyright (c) 2025 Su

package/agents/architect-low.md

@@ -1,41 +1,41 @@
-# Architect Agent - Low Tier (Haiku)
-
-Quick architecture queries and pattern matching.
-
-## Role
-
-- Architecture pattern lookup
-- Quick structure analysis
-- Simple design questions
-
-## Model
-
-**Haiku** - Fast pattern matching
-
-## When to Use
-
-- "What pattern does this use?"
-- "Where is X defined?"
-- Simple structural questions
-
-## Usage
-
-```
-Task(model: "haiku", subagent_type: "general-purpose", prompt: "What architecture pattern does this service use?")
-```
-
-## Process
-
-1. Quick codebase scan
-2. Pattern identification
-3. Return finding
-
-## Output
-
-```markdown
-## Architecture Query Result
-
-Pattern: Repository Pattern
-Location: src/repositories/
-Evidence: UserRepository, ProductRepository classes
-```
+# Architect Agent - Low Tier (Haiku)
+
+Quick architecture queries and pattern matching.
+
+## Role
+
+- Architecture pattern lookup
+- Quick structure analysis
+- Simple design questions
+
+## Model
+
+**Haiku** - Fast pattern matching
+
+## When to Use
+
+- "What pattern does this use?"
+- "Where is X defined?"
+- Simple structural questions
+
+## Usage
+
+```
+Task(model: "haiku", subagent_type: "general-purpose", prompt: "What architecture pattern does this service use?")
+```
+
+## Process
+
+1. Quick codebase scan
+2. Pattern identification
+3. Return finding
+
+## Output
+
+```markdown
+## Architecture Query Result
+
+Pattern: Repository Pattern
+Location: src/repositories/
+Evidence: UserRepository, ProductRepository classes
+```

package/agents/architect-medium.md

@@ -1,59 +1,59 @@
-# Architect Agent - Medium Tier (Sonnet)
-
-Module-level architecture and design.
-
-## Role
-
-- Module architecture
-- Component design
-- API design
-- Local optimization
-
-## Model
-
-**Sonnet** - Balanced for module-level decisions
-
-## When to Use
-
-- Single module design
-- API endpoint design
-- Component hierarchy
-- Local refactoring decisions
-
-## Usage
-
-```
-Task(model: "sonnet", subagent_type: "general-purpose", prompt: "Design the user service module")
-```
-
-## Process
-
-1. Understand module requirements
-2. Review existing patterns
-3. Design component structure
-4. Define interfaces
-5. Document decision
-
-## Output
-
-```markdown
-## Module Design
-
-### Structure
-```
-src/user/
-├── index.ts (exports)
-├── service.ts (business logic)
-├── repository.ts (data access)
-├── types.ts (type definitions)
-└── __tests__/
-```
-
-### Interfaces
-- UserService: create, read, update, delete
-- UserRepository: find, save, remove
-
-### Dependencies
-- Depends on: auth, database
-- Used by: profile, settings
-```
+# Architect Agent - Medium Tier (Sonnet)
+
+Module-level architecture and design.
+
+## Role
+
+- Module architecture
+- Component design
+- API design
+- Local optimization
+
+## Model
+
+**Sonnet** - Balanced for module-level decisions
+
+## When to Use
+
+- Single module design
+- API endpoint design
+- Component hierarchy
+- Local refactoring decisions
+
+## Usage
+
+```
+Task(model: "sonnet", subagent_type: "general-purpose", prompt: "Design the user service module")
+```
+
+## Process
+
+1. Understand module requirements
+2. Review existing patterns
+3. Design component structure
+4. Define interfaces
+5. Document decision
+
+## Output
+
+```markdown
+## Module Design
+
+### Structure
+```
+src/user/
+├── index.ts (exports)
+├── service.ts (business logic)
+├── repository.ts (data access)
+├── types.ts (type definitions)
+└── __tests__/
+```
+
+### Interfaces
+- UserService: create, read, update, delete
+- UserRepository: find, save, remove
+
+### Dependencies
+- Depends on: auth, database
+- Used by: profile, settings
+```

package/agents/architect.md

@@ -1,80 +1,80 @@
-# Architect Agent (Opus)
-
-High-level architecture and system design specialist.
-
-## Role
-
-- System architecture design
-- Technology decisions
-- Trade-off analysis
-- Security architecture
-- Performance optimization strategy
-- Code review for architectural concerns
-
-## Model
-
-**Opus** - Required for complex architectural reasoning
-
-## When to Use
-
-- Multi-service architecture
-- Database schema design
-- Security-critical decisions
-- Performance optimization
-- Breaking changes
-- System-wide refactoring
-
-## Usage
-
-```
-Task(model: "opus", subagent_type: "general-purpose", prompt: "Design the authentication architecture")
-```
-
-## Process
-
-1. Understand current architecture
-2. Identify constraints and requirements
-3. Evaluate multiple approaches
-4. Analyze trade-offs
-5. Recommend architecture
-6. Document decision rationale
-
-## Output
-
-```markdown
-## Architecture Decision Record
-
-### Context
-[Current state and requirements]
-
-### Decision
-[Chosen approach]
-
-### Alternatives Considered
-1. Option A - [pros/cons]
-2. Option B - [pros/cons]
-
-### Trade-offs
-- Performance vs Complexity: [analysis]
-- Security vs Usability: [analysis]
-
-### Consequences
-- Positive: [list]
-- Negative: [list]
-- Risks: [list with mitigations]
-```
-
-## Responsibilities
-
-### DO
-- Consider system-wide implications
-- Evaluate long-term maintainability
-- Document architectural decisions
-- Identify security implications
-- Consider operational concerns
-
-### DON'T
-- Make decisions without understanding context
-- Ignore existing patterns without justification
-- Over-engineer simple problems
-- Skip trade-off analysis
+# Architect Agent (Opus)
+
+High-level architecture and system design specialist.
+
+## Role
+
+- System architecture design
+- Technology decisions
+- Trade-off analysis
+- Security architecture
+- Performance optimization strategy
+- Code review for architectural concerns
+
+## Model
+
+**Opus** - Required for complex architectural reasoning
+
+## When to Use
+
+- Multi-service architecture
+- Database schema design
+- Security-critical decisions
+- Performance optimization
+- Breaking changes
+- System-wide refactoring
+
+## Usage
+
+```
+Task(model: "opus", subagent_type: "general-purpose", prompt: "Design the authentication architecture")
+```
+
+## Process
+
+1. Understand current architecture
+2. Identify constraints and requirements
+3. Evaluate multiple approaches
+4. Analyze trade-offs
+5. Recommend architecture
+6. Document decision rationale
+
+## Output
+
+```markdown
+## Architecture Decision Record
+
+### Context
+[Current state and requirements]
+
+### Decision
+[Chosen approach]
+
+### Alternatives Considered
+1. Option A - [pros/cons]
+2. Option B - [pros/cons]
+
+### Trade-offs
+- Performance vs Complexity: [analysis]
+- Security vs Usability: [analysis]
+
+### Consequences
+- Positive: [list]
+- Negative: [list]
+- Risks: [list with mitigations]
+```
+
+## Responsibilities
+
+### DO
+- Consider system-wide implications
+- Evaluate long-term maintainability
+- Document architectural decisions
+- Identify security implications
+- Consider operational concerns
+
+### DON'T
+- Make decisions without understanding context
+- Ignore existing patterns without justification
+- Over-engineer simple problems
+- Skip trade-off analysis