@su-record/vibe 2.0.11 → 2.2.1

package/.claude/commands/vibe.spec.md

@@ -1,383 +0,0 @@
----
-description: Create SPEC document with Specification Agent
-argument-hint: "feature name"
----
-
-# /vibe.spec
-
-Create a SPEC document (Specification Agent).
-
-## Usage
-
-```
-/vibe.spec "feature-name"
-```
-
-## Rules Reference
-
-**Must follow `.vibe/rules/`:**
-- `core/development-philosophy.md` - Surgical precision, simplicity
-- `core/quick-start.md` - Korean first, DRY, SRP
-- `core/communication-guide.md` - Communication principles
-
-## Description
-
-Collect requirements through conversation with the user and create an **AI-executable PTCF structured SPEC document**.
-
-> **PTCF**: Persona, Task, Context, Format - Google Gemini prompt optimization framework
-
-## External LLM Integration (Optional)
-
-When external LLMs are enabled in `.vibe/config.json`, automatically utilize during SPEC creation:
-
-```
-/vibe.spec "complex feature"
-      ↓
-[Claude Opus] Create SPEC draft
-      ↓
-[GPT enabled?] → Cross-review design via MCP(vibe-gpt)
-      ↓
-[Gemini enabled?] → UI/UX consultation via MCP(vibe-gemini)
-      ↓
-[Claude] Finalize SPEC
-```
-
-| External LLM | Role | When Used |
-|--------------|------|-----------|
-| GPT 5.2 | Architecture/design review | After SPEC draft completion |
-| Gemini 3 | UI/UX consultation | During design reference discussion |
-
-**Activation:**
-```bash
-vibe gpt <api-key>      # Enable GPT
-vibe gemini <api-key>   # Enable Gemini
-vibe status             # Check current settings
-```
-
-## Process
-
-### 1. Project Analysis
-
-**Existing project** (`vibe init`):
-- Source code analysis: `package.json`, `pyproject.toml`, `pubspec.yaml`, `go.mod`, etc.
-- Reference `CLAUDE.md` file (tech stack)
-- Infer framework from file structure
-
-**New project** (`vibe init <project-name>`):
-- Suggest tech stack (2-3 options)
-
-### 2. Collect Requirements via Conversation
-
-**Principles:**
-- Ask **one question at a time**
-- Present options **with numbers** + "Feel free to describe in your own words"
-- **Natural conversation** without fixed order
-
-**Required confirmations:**
-- Purpose (Why): Why is it needed?
-- User (Who): Who will use it?
-- Feature scope (What): What features are needed?
-- Tech stack: Confirm existing stack or suggest new
-- Design reference: UI/UX to reference
-
-### 3. Parallel Research (v2.1.0) - Run AFTER requirements confirmed
-
-**⚠️ IMPORTANT: Research starts ONLY after requirements are confirmed via Q&A**
-
-Requirements confirmed when:
-- Feature type decided (e.g., "passkey authentication")
-- Tech stack confirmed (e.g., "React + Supabase")
-- Core requirements collected
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  🔍 PARALLEL RESEARCH AGENTS (After requirements confirmed)     │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  Task 1: best-practices-agent                                   │
-│  └── Best practices for [confirmed feature] + [confirmed stack] │
-│                                                                 │
-│  Task 2: framework-docs-agent                                   │
-│  └── Latest docs for [confirmed stack] (via context7)           │
-│                                                                 │
-│  Task 3: codebase-patterns-agent                                │
-│  └── Analyze similar patterns in existing codebase              │
-│                                                                 │
-│  Task 4: security-advisory-agent                                │
-│  └── Security advisories for [confirmed feature]                │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-**Execution (ALL in parallel):**
-```
-# Generate specific prompts based on confirmed requirements
-Task(model: "haiku", subagent_type: "Explore",
-     prompt: "Research best practices for [passkey auth] with [React + Supabase]")
-Task(model: "haiku", subagent_type: "Explore",
-     prompt: "Get Supabase Auth + WebAuthn docs from context7")
-Task(model: "haiku", subagent_type: "Explore",
-     prompt: "Find existing auth patterns in this codebase")
-Task(model: "haiku", subagent_type: "Explore",
-     prompt: "Check OWASP WebAuthn security guidelines")
-```
-
-**Research results are reflected in SPEC's Context section.**
-
-### 4. Write SPEC Document (PTCF Structure)
-
-Create `.vibe/specs/{feature-name}.md`:
-
-```markdown
-# SPEC: {feature-name}
-
-## Persona
-<role>
-Define AI role and expertise for implementation
-- Senior developer on the project
-- Follow existing code patterns
-- Write testable code
-</role>
-
-## Context
-<context>
-### Background
-- Why this feature is needed
-- Who will use it
-
-### Tech Stack
-- Backend: {technology}
-- Frontend: {technology}
-- Database: {technology}
-
-### Related Code
-- `src/xxx/`: Existing implementation to reference
-- `src/yyy/`: Files to modify
-
-### Design Reference
-- {Reference app/service}
-</context>
-
-## Task
-<task>
-### Phase 1: {phase-name}
-1. [ ] {specific task}
-   - File: `path/to/file`
-   - Verify: `command`
-2. [ ] {specific task}
-
-### Phase 2: {phase-name}
-1. [ ] {specific task}
-2. [ ] {specific task}
-
-### Phase 3: Testing and Verification
-1. [ ] Unit Tests
-2. [ ] Integration Tests
-</task>
-
-## Constraints
-<constraints>
-- Follow existing code patterns
-- Localize error messages
-- Separate configuration via environment variables
-- {other constraints}
-</constraints>
-
-## Output Format
-<output_format>
-### Files to Create
-- `path/to/new/file.ts`
-- `path/to/new/file.test.ts`
-
-### Files to Modify
-- `path/to/existing/file.ts`
-
-### Verification Commands
-- `npm test`
-- `npm run build`
-</output_format>
-
-## Acceptance Criteria
-<acceptance>
-- [ ] {verifiable criterion 1}
-- [ ] {verifiable criterion 2}
-- [ ] All tests pass
-- [ ] Build succeeds
-</acceptance>
-```
-
-### 5. Create Feature File (BDD) - Required
-
-**Must** create `.vibe/features/{feature-name}.feature` file.
-
-**Creation rules:**
-1. Convert each SPEC Acceptance Criteria → one Scenario
-2. Include Happy Path (normal case) + Edge Case (exception case)
-3. Follow Given-When-Then format
-
-**Feature structure:**
-```markdown
-# Feature: {feature-name}
-
-**SPEC**: `.vibe/specs/{feature-name}.md`
-
-## User Story
-**As a** {user}
-**I want** {feature}
-**So that** {value}
-
-## Scenarios
-
-### Scenario 1: {Happy Path}
-\`\`\`gherkin
-Scenario: {title}
-  Given {precondition}
-  When {action}
-  Then {result}
-\`\`\`
-**Verification**: SPEC AC #1
-
-### Scenario 2: {Edge Case}
-...
-
-## Coverage
-| Scenario | SPEC AC | Status |
-|----------|---------|--------|
-| 1 | AC-1 | ⬜ |
-```
-
-### 6. Ambiguity Scan - Required
-
-After creating SPEC draft, **must perform systematic ambiguity check**.
-
-**Check categories:**
-
-| Category | Check Items |
-|----------|-------------|
-| **Functional Scope** | Missing features, unclear behavior definitions |
-| **Data Model** | Undefined entities, unclear relationships |
-| **Non-Functional** | Missing performance requirements, security considerations |
-| **Edge Cases** | Boundary conditions, error handling scenarios |
-| **Integration Points** | External system integration, API contracts |
-
-**Check process:**
-
-```
-1. Create SPEC draft
-      ↓
-2. Scan by category for ambiguity
-      ↓
-3. Present list of found ambiguities
-      ↓
-4. Request user clarification
-      ↓
-5. Refine SPEC
-      ↓
-6. Re-check (until 0 ambiguities)
-```
-
-**Ambiguity output format:**
-
-```markdown
-## 🔍 Ambiguity Scan Results
-
-### Functional Scope
-- ⚠️ "Login failure behavior" not defined
-- ⚠️ "Session expiration handling" unclear
-
-### Edge Cases
-- ⚠️ Concurrent login permission undefined
-- ⚠️ No password retry limit specified
-
-Please clarify the above items.
-```
-
-### 7. Quality Validation
-
-Self-evaluate against `.vibe/rules/quality/checklist.md` (0-100 score)
-
-## Output
-
-- `.vibe/specs/{feature-name}.md` - PTCF structured SPEC
-- `.vibe/features/{feature-name}.feature` - BDD Feature file
-- Ambiguity scan results (0 ambiguities confirmed)
-- Quality score and improvement suggestions
-
-## Example
-
-```
-User: /vibe.spec "brick-game"
-
-Claude:
-You're making a brick game! What style are you thinking of?
-
-1. Classic Breakout style
-2. Arkanoid (with power-up items)
-3. Custom style with special gameplay
-
-Feel free to describe in your own words.
-
-User: 1
-
-Claude: What platform will it run on?
-
-1. Web (browser)
-2. Mobile (iOS/Android)
-3. Desktop
-
-User: 1
-
-Claude:
-Here are tech stack suggestions for web game development:
-
-1. **Phaser.js** (Recommended) - Game framework with built-in physics engine
-2. **Canvas + JavaScript** - Lightweight with fine control
-3. **PixiJS + Matter.js** - High-performance rendering
-
-User: 1
-
-Claude: What design style?
-
-1. Retro pixel (Atari Breakout)
-2. Neon graphics (Arkanoid)
-3. Modern 3D effects
-
-User: 2
-
-[Conversation continues...]
-
-Claude: SPEC draft created. Running ambiguity scan.
-
-## 🔍 Ambiguity Scan Results
-
-### Functional Scope
-- ⚠️ Game over condition not defined (ball drop vs lives system)
-- ⚠️ Stage clear condition unclear
-
-### Edge Cases
-- ⚠️ Ball reflection angle when hitting paddle edge
-- ⚠️ Multiple brick collision handling
-
-Please clarify the above items.
-
-User: 3 lives, clear when all bricks destroyed, edge reflects at 45 degrees
-
-Claude: Thank you. SPEC has been refined.
-
-🔍 Re-check result: 0 ambiguities
-
-✅ SPEC document complete!
-📄 .vibe/specs/brick-game.md (PTCF structure)
-📄 .vibe/features/brick-game.feature
-📊 Quality score: 92/100 (A)
-```
-
-## Next Step
-
-```
-/vibe.run "brick-game"
-```
-
----
-
-ARGUMENTS: $ARGUMENTS

package/.claude/commands/vibe.tool.md

@@ -1,153 +0,0 @@
----
-description: Natural language tool invocation
-argument-hint: "자연어로 원하는 기능 설명"
----
-
-# /vibe.tool
-
-자연어로 vibe 도구를 호출합니다. 35개 이상의 도구를 하나의 명령어로 사용할 수 있습니다.
-
-## Usage
-
-```
-/vibe.tool "원하는 기능을 자연어로 설명"
-```
-
-## Examples
-
-```
-/vibe.tool "이 프로젝트 스택을 기억해줘: Next.js 14, TypeScript, Tailwind"
-/vibe.tool "저장된 메모리 목록 보여줘"
-/vibe.tool "auth 관련 메모리 검색해줘"
-/vibe.tool "이 코드 복잡도 분석해줘"
-/vibe.tool "UserService 클래스가 어디서 사용되는지 찾아줘"
-/vibe.tool "로그인 기능 PRD 작성해줘"
-```
-
----
-
-## Tool Mapping Table
-
-아래 표를 참고하여 사용자 요청에 가장 적합한 도구를 선택하고 실행하세요.
-
-### Memory (메모리 관리)
-
-| 키워드 | 함수 | 설명 |
-|--------|------|------|
-| 기억해, save, remember, 저장 | `saveMemory({ key, value, category, projectPath })` | 메모리 저장 |
-| 떠올려, recall, 뭐였지 | `recallMemory({ key, projectPath })` | 메모리 조회 |
-| 목록, list, 뭐 있어 | `listMemories({ category, limit, projectPath })` | 메모리 목록 |
-| 삭제, delete, 지워 | `deleteMemory({ key, projectPath })` | 메모리 삭제 |
-| 수정, update, 바꿔 | `updateMemory({ key, value, append, projectPath })` | 메모리 수정 |
-| 찾아, search, 검색 | `searchMemories({ query, category, projectPath })` | 메모리 검색 |
-| 연결, link, 관계 | `linkMemories({ sourceKey, targetKey, relationType, strength, projectPath })` | 메모리 연결 |
-| 그래프, graph, 관계도 | `getMemoryGraph({ key, depth, format, projectPath })` | 지식 그래프 |
-| 타임라인, timeline, 히스토리 | `createMemoryTimeline({ startDate, endDate, groupBy, projectPath })` | 시간순 메모리 |
-| 고급검색, advanced | `searchMemoriesAdvanced({ query, strategy, limit, projectPath })` | 고급 검색 |
-| 세션, session, 컨텍스트 | `startSession({ greeting, loadMemory, loadGuides, projectPath })` | 세션 시작 |
-| 저장해둬, auto-save | `autoSaveContext({ urgency, contextType, summary, projectPath })` | 컨텍스트 자동 저장 |
-| 복원, restore | `restoreSessionContext({ sessionId, restoreLevel, projectPath })` | 세션 복원 |
-| 우선순위, priority | `prioritizeMemory({ currentTask, criticalDecisions, projectPath })` | 우선순위 정리 |
-
-### Semantic (코드 분석)
-
-| 키워드 | 함수 | 설명 |
-|--------|------|------|
-| 심볼, symbol, 정의 찾기 | `findSymbol({ symbolName, projectPath, symbolType })` | 심볼 정의 찾기 |
-| 참조, references, 어디서 쓰여 | `findReferences({ symbolName, projectPath, filePath })` | 참조 찾기 |
-| 의존성, dependencies, 그래프 | `analyzeDependencyGraph({ projectPath, entryPoint, depth })` | 의존성 분석 |
-
-### Convention (코드 품질)
-
-| 키워드 | 함수 | 설명 |
-|--------|------|------|
-| 복잡도, complexity | `analyzeComplexity({ code, metrics })` | 복잡도 분석 |
-| 품질, quality, 검증 | `validateCodeQuality({ code, type, metrics, strict })` | 코드 품질 검증 |
-| 결합도, coupling, 응집도 | `checkCouplingCohesion({ code, type, checkDependencies })` | 결합도/응집도 |
-| 개선, improve, 리팩토링 | `suggestImprovements({ code, focus, priority })` | 개선 제안 |
-| 규칙, rules, 표준 | `applyQualityRules({ scope, language })` | 품질 규칙 적용 |
-| 가이드, guide, 컨벤션 | `getCodingGuide({ name, category })` | 코딩 가이드 |
-
-### Thinking (사고 도구)
-
-| 키워드 | 함수 | 설명 |
-|--------|------|------|
-| 생각, thinking, 연쇄 | `createThinkingChain({ topic, steps })` | 사고 체인 |
-| 문제분석, analyze problem | `analyzeProblem({ problem, domain })` | 문제 분석 |
-| 단계별, step by step | `stepByStepAnalysis({ task, detailLevel, context })` | 단계별 분석 |
-| 계획, plan, 정리 | `formatAsPlan({ content, includeCheckboxes, priority })` | 계획 포맷팅 |
-| 분해, break down | `breakDownProblem({ problem, approach, maxDepth })` | 문제 분해 |
-| 추론, reason, 생각해봐 | `thinkAloudProcess({ scenario, perspective, verbosity })` | 추론 프로세스 |
-
-### Planning (프로젝트 계획)
-
-| 키워드 | 함수 | 설명 |
-|--------|------|------|
-| PRD, 요구사항 문서 | `generatePrd({ productName, productVision, targetAudience })` | PRD 생성 |
-| 사용자 스토리, user story | `createUserStories({ features, userTypes, includeAcceptanceCriteria })` | 사용자 스토리 |
-| 요구사항 분석 | `analyzeRequirements({ requirements, analysisMethod, stakeholders })` | 요구사항 분석 |
-| 로드맵, roadmap | `featureRoadmap({ projectName, features, timeframe, teamSize })` | 로드맵 생성 |
-
-### Prompt (프롬프트 엔지니어링)
-
-| 키워드 | 함수 | 설명 |
-|--------|------|------|
-| 프롬프트 개선 | `enhancePrompt({ prompt, context, enhancement_type })` | 프롬프트 개선 |
-| 프롬프트 분석 | `analyzePrompt({ prompt, criteria })` | 프롬프트 분석 |
-
-### UI (UI 도구)
-
-| 키워드 | 함수 | 설명 |
-|--------|------|------|
-| UI 미리보기, ASCII | `previewUiAscii({ page_name, components, layout_type })` | UI 프리뷰 |
-
-### Time (시간)
-
-| 키워드 | 함수 | 설명 |
-|--------|------|------|
-| 시간, time, 몇시 | `getCurrentTime({ format, timezone })` | 현재 시간 |
-
----
-
-## Process
-
-1. 사용자 입력을 분석하여 위 매핑 테이블에서 적합한 도구 선택
-2. 필요한 파라미터 추출 (자연어에서)
-3. projectPath는 현재 작업 디렉토리(pwd) 사용
-4. 도구 실행 및 결과 반환
-
-## Example Execution
-
-**입력**: `/vibe.tool "프로젝트 스택 기억해: Next.js, TypeScript"`
-
-**실행**:
-```typescript
-saveMemory({
-  key: "project-stack",
-  value: "Next.js, TypeScript",
-  category: "project",
-  projectPath: process.cwd()
-})
-```
-
-**입력**: `/vibe.tool "UserService가 어디서 참조되는지 찾아줘"`
-
-**실행**:
-```typescript
-findReferences({
-  symbolName: "UserService",
-  projectPath: process.cwd()
-})
-```
-
----
-
-## Important Notes
-
-- 모든 메모리 관련 도구는 `projectPath`를 현재 디렉토리로 설정하여 프로젝트별 메모리 격리
-- 키워드 매칭이 애매한 경우, 가장 연관성 높은 도구 선택
-- 여러 도구가 필요한 경우 순차 실행
-
----
-
-ARGUMENTS: $ARGUMENTS

package/.claude/commands/vibe.ui.md

@@ -1,137 +0,0 @@
----
-description: Preview UI with ASCII art
-argument-hint: "UI description"
----
-
-# /vibe.ui
-
-Preview UI with ASCII art.
-
-## Usage
-
-```
-/vibe.ui "login page"
-/vibe.ui "dashboard" --layout grid
-```
-
-## Process
-
-### 1. Analyze UI Description
-
-Analyze user's requested UI description:
-- Page/component name
-- Required UI elements (buttons, inputs, cards, etc.)
-- Layout structure (header-footer, sidebar, grid, etc.)
-
-### 2. Use MCP Tool
-
-Use `mcp__su-record-hi-ai__preview_ui_ascii` tool to generate ASCII art:
-
-```javascript
-{
-  page_name: "Login Page",
-  layout_type: "centered",
-  components: [
-    { type: "header", label: "Welcome", position: "top" },
-    { type: "input", label: "Email", position: "center" },
-    { type: "input", label: "Password", position: "center" },
-    { type: "button", label: "Login", position: "center" }
-  ]
-}
-```
-
-### 3. Output ASCII Art
-
-Output generated ASCII art:
-
-```
-┌─────────────────────────────────────────┐
-│               Welcome                    │
-├─────────────────────────────────────────┤
-│                                          │
-│         ┌─────────────────────┐          │
-│  Email: │                     │          │
-│         └─────────────────────┘          │
-│                                          │
-│         ┌─────────────────────┐          │
-│  Pass:  │                     │          │
-│         └─────────────────────┘          │
-│                                          │
-│         ┌─────────────────────┐          │
-│         │       Login         │          │
-│         └─────────────────────┘          │
-│                                          │
-└─────────────────────────────────────────┘
-```
-
-### 4. Generate Component List
-
-Suggest list of components needed for UI:
-
-**Required Components:**
-- `Header.tsx` - Header ("Welcome")
-- `LoginForm.tsx` - Form container
-- `Input.tsx` - Reusable input field
-- `Button.tsx` - Login button
-
-**Expected File Structure:**
-```
-src/
-├── components/
-│   ├── common/
-│   │   ├── Input.tsx
-│   │   └── Button.tsx
-│   └── auth/
-│       ├── Header.tsx
-│       └── LoginForm.tsx
-└── pages/
-    └── LoginPage.tsx
-```
-
-## Example
-
-```
-User: /vibe.ui "Dashboard page - header, sidebar, main content (3 cards), footer"
-
-Claude: Generating dashboard UI preview...
-
-┌────────────────────────────────────────────────────────┐
-│  [Logo]  Dashboard                    [User] [Logout]  │
-├────────┬───────────────────────────────────────────────┤
-│        │                                               │
-│ Home   │  ┌──────────┐ ┌──────────┐ ┌──────────┐      │
-│ Stats  │  │  Card 1  │ │  Card 2  │ │  Card 3  │      │
-│ Users  │  │          │ │          │ │          │      │
-│ Settings│  │  100     │ │  200     │ │  50      │      │
-│        │  └──────────┘ └──────────┘ └──────────┘      │
-│        │                                               │
-│        │                                               │
-├────────┴───────────────────────────────────────────────┤
-│  © 2025 Company                    Privacy | Terms    │
-└────────────────────────────────────────────────────────┘
-
-**Required Components:**
-1. Header (logo, user menu)
-2. Sidebar (navigation)
-3. StatsCard (reusable card)
-4. Footer (copyright, links)
-5. DashboardLayout (overall layout)
-
-**Layout Structure:**
-- Layout: sidebar (fixed left)
-- Main: grid (3 columns)
-- Responsive: Changes to 1 column on mobile
-
-Next step:
-  vibe spec "dashboard page"
-```
-
-## Notes
-
-- For complex UI, request in multiple parts
-- Layout options: `sidebar`, `header-footer`, `grid`, `centered`, `split`
-- ASCII art is for quick visualization before actual implementation
-
----
-
-ARGUMENTS: $ARGUMENTS