@su-record/vibe 3.2.6 → 3.2.8

package/skills/vibe/references/routing-examples.md

@@ -0,0 +1,85 @@
+# /vibe — Routing Examples & Output Format
+
+> vibe SKILL.md 에서 참조. 라우팅 예시 4종과 최종 출력 포맷.
+
+## Routing Examples
+
+### 예시 1: 신규 + figma
+
+```
+입력: /vibe "https://www.figma.com/design/abc/login 로 로그인 페이지"
+
+→ Intent: figma-driven UI
+→ Resume: 없음
+→ Pipeline:
+   1. /vibe.figma  (figma Extract + Convert Mode)
+   2. /vibe.spec   (생성된 SPEC 자동 보정)
+   3. /vibe.run
+   4. /vibe.verify
+   5. /vibe.trace
+```
+
+### 예시 2: Resume
+
+```
+입력: /vibe "이어서"  (혹은 빈 호출)
+
+→ Resume: .vibe/specs/login/ 발견 (3개 phase 파일)
+→ .vibe/features/login/ 없음
+→ Pipeline:
+   1. /vibe.run (구현부터)
+   2. /vibe.verify
+   3. /vibe.trace
+```
+
+### 예시 3: Review only
+
+```
+입력: /vibe "이 코드 리뷰만" + 📎 src/auth/login.ts
+
+→ Intent: review only
+→ Pipeline:
+   1. /vibe.review (단일 phase)
+```
+
+### 예시 4: automationLevel autonomous (ultrawork 별칭)
+
+```
+입력: /vibe "결제 API 만들어줘" ultrawork
+
+→ automationLevel: autonomous 설정 → SPEC 승인 게이트 skip
+→ 병렬 ACT 활성화
+→ ANCHOR→ACT→JUDGE→RECORD 루프 (게이트 통과까지 자동 반복)
+→ stuck 시 TODO 기록 후 루프 종료 (사용자 질문 없음)
+```
+
+
+## Output
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎯 /vibe Dynamic Dispatcher
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+[Phase 0: Input 분석]
+...
+
+[Phase 1: Intent 분류]
+→ new feature + figma-driven UI
+
+[Phase 2: Resume 감지]
+→ 진행 중인 작업 없음
+
+[Phase 3: 파이프라인 설계]
+...
+
+[Phase 4: 실행]
+... (SPEC 승인은 spec 단계 내부의 1회 게이트)
+
+[Phase 5: 종료 보고]
+...
+```
+
+---
+
+ARGUMENTS: {자연어 요구사항 + 첨부}

package/skills/vibe.agents-md/SKILL.md

@@ -3,13 +3,20 @@ name: vibe.agents-md
 user-invocable: false
 invocation: [auto, chain]
 tier: standard
-description: "Author and optimize AGENTS.md / CLAUDE.md (same doctrine, different filenames): write new context files from scratch, or strip discoverable info and keep only gotchas. Based on Addy Osmani's AGENTS.md principles + Curse of Instructions research. Activates on agents.md, claude.md, context file authoring/optimization."
+description: "Use when authoring or optimizing AGENTS.md or CLAUDE.md — create the context file or remove discoverable detail while preserving project-specific gotchas."
 triggers: [agents.md, claude.md, context file, optimize agents, optimize claude, write claude.md, create claude.md, project instructions]
 priority: 50
 ---
 
 # agents-md — Context File Author & Optimizer
 
+## Done Criteria
+
+- [ ] 요청된 AGENTS.md 또는 CLAUDE.md가 존재한다.
+- [ ] 저장소에서 탐색 가능한 일반 정보가 중복 서술되지 않는다.
+- [ ] 프로젝트 고유 제약과 검증 명령이 남아 있다.
+- [ ] 두 파일을 함께 관리하면 공통 규칙의 의미가 일치한다.
+
 Author and optimize AGENTS.md / CLAUDE.md files. They are the **same doctrine
 under different filenames** — everything below applies to both.
 Reference: https://addyosmani.com/blog/agents-md/
@@ -30,13 +37,8 @@ under-weight the middle. Most important rules → top. Frequently violated rules
 
 Search project root for these files:
 
-```
-Glob: pattern="AGENTS.md"
-Glob: pattern="CLAUDE.md"
-Glob: pattern=".cursorrules"
-Glob: pattern=".github/copilot-instructions.md"
-Glob: pattern=".windsurfrules"
-```
+Use the harness's file-pattern search capability for `AGENTS.md`, `CLAUDE.md`,
+`.cursorrules`, `.github/copilot-instructions.md`, and `.windsurfrules`.
 
 If a target exists → optimize it (Steps 2–3). If none exists and the user wants
 one → author it (Step 1b), then run the same optimization pass on the draft.
@@ -75,7 +77,7 @@ Information the agent can find by exploring the code:
 
 | Type | Example | Discovery Path |
 |------|---------|---------------|
-| Directory structure | "Components are in src/" | `ls`, `Glob` |
+| Directory structure | "Components are in src/" | directory listing or file-pattern search |
 | Tech stack | "Uses React + TypeScript" | `package.json`, file extensions |
 | Phase/progress tables | "Phase 1 ✅, Phase 2 ✅..." | Just history, not actionable guidance |
 | Build/test commands | "Run tests with npm test" | `package.json` scripts |
@@ -134,7 +136,7 @@ Rules:
 - Each gotcha has **bold title + specific do/don't**
 - "Don't use X" is more useful than "We use X"
 - Target under 50 lines total; 60–150 acceptable for complex projects; at 300+ the agent ignores half of it
-- Don't inline everything — Claude Code follows `@docs/FILE.md` references and loads them on demand (progressive disclosure)
+- Don't inline everything — point to `docs/FILE.md` and load it on demand (progressive disclosure)
 
 ## Step 4: CLAUDE.md Separation (if applicable)
 

package/skills/vibe.analyze/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vibe.analyze
-description: Analyze any target — code, document, website, or Figma design
+description: Use when code, documents, websites, Figma, or project quality must be analyzed into an evidence-backed report.
 argument-hint: '"feature-name" or file.pdf or https://... or --code or --deps or --arch'
 user-invocable: true
 ---
@@ -39,9 +39,9 @@ Determine analysis mode from the argument pattern:
 
 ## File Reading Policy (Mandatory)
 
-- **SPEC/Feature files**: Always use `Read` tool for the full file (never Grep for content)
+- **SPEC/Feature files**: Always use the harness's full-file reading capability (never text search for content)
 - **Source files**: Read the entire file before analyzing (no partial reads)
-- **Grep restriction**: Use only for locating files, not for understanding content
+- **Text-search restriction**: Use only for locating files, not for understanding content
 - **Agent prompts**: Always include "Read target files in full before analyzing"
 - **No partial analysis**: Never judge a file by a few lines around a Grep match
 
@@ -55,217 +55,19 @@ Determine analysis mode from the argument pattern:
 
 > **Timer**: Record start time at the beginning. Include elapsed time in the final report.
 
-## Mode 1: Feature/Module Analysis (`/vibe.analyze "feature-name"`)
+## 모드 라우팅 (하나만 로드)
 
-### Goal
+입력 판별 결과에 따라 **아래 reference 중 정확히 하나만** 읽는다. 한 번의 호출은 한 모드만 실행하므로,
+나머지 셋은 읽지 않는다 — 이것이 이 스킬에서 컨텍스트를 가장 크게 줄이는 지점이다.
 
-Explore all source code related to the requested feature/module and analyze flow to:
-1. Understand current implementation status
-2. Map code structure and dependencies
-3. Build context for future development/modification requests
+| 모드 | 선택 조건 | 본문 |
+|---|---|---|
+| **1** Feature/Module | 인자가 기능·모듈 이름 (코드 분석) | `references/mode1-feature.md` |
+| **2** Document | 인자가 PDF·Markdown·슬라이드 파일 | `references/mode2-document.md` |
+| **3** Website | 인자가 http(s) URL | `references/mode3-website.md` |
+| **4** Project Quality | `--code` / `--deps` / `--arch` 플래그 | `references/mode4-quality.md` |
 
-### Process
-
-#### 1. Request Analysis
-
-Extract keywords from the user request:
-- Feature name (e.g., login, feed, payment)
-- Action (e.g., create, read, update, delete)
-- Scope (e.g., backend only, frontend only, full)
-
-#### 2. Understand Project Structure
-
-Read `CLAUDE.md`, `package.json`, `pyproject.toml`, etc. to identify tech stack.
-
-> Read `references/output-templates.md` for the full backend/frontend stack → directory mapping.
-
-#### 3. Explore Related Code (Parallel Sub-Agents)
-
-**MANDATORY: Always use native Explore sub-agents. Never explore in main session.**
-
-> Why: 3 Explore agents return ~600 tokens of summaries to main session.
-> Direct Glob/Grep/Read in main session would add 5-15K tokens of raw content.
-
-**Parallel exploration (ALL in ONE message):**
-
-```text
-Agent(subagent_type="Explore", model="haiku",
-  prompt="Find all [FEATURE] related API endpoints. List file paths, HTTP methods, routes, and auth requirements.")
-
-Agent(subagent_type="Explore", model="haiku",
-  prompt="Find all [FEATURE] related services, business logic, and utility functions. Map dependencies.")
-
-Agent(subagent_type="Explore", model="haiku",
-  prompt="Find all [FEATURE] related data models, schemas, and database queries. Document relationships and key fields.")
-```
-
-> 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
-- Only Read specific files in main session when agent summaries need clarification
-
-#### 4. Flow Analysis
-
-**API Flow:**
-- Endpoint URL and HTTP method
-- Request/response schema
-- Authentication/authorization requirements
-
-**Business Logic:**
-- Core methods and their roles
-- Validation rules
-- External service integrations
-
-**Data Flow:**
-- Related tables/models
-- Relationships (1:N, N:M)
-- Key query patterns
-
-#### 5. Output
-
-> Read `references/output-templates.md` for the full Mode 1 output format.
-
-#### 6. Next Steps
-
-After analysis, suggest mode-specific follow-up actions.
-
-> Read `references/output-templates.md` for the full Next Steps decision tables (code/feature, document, website).
-
-Wait for user's choice before proceeding.
-
----
-
-## Mode 2: Document Analysis (PDF, Markdown, Slides)
-
-### Goal
-
-Analyze document **structure, key content, quality, and applicability** to:
-1. Extract and organize information from the document
-2. Map relevance to the current project
-3. Suggest follow-up actions (development, improvement, application)
-
-### Process
-
-#### 1. Read Document
-
-- **PDF**: Use `Read` tool with `pages` parameter (split large documents into chunks of 20 pages)
-- **Markdown/Text**: Use `Read` tool for the full file
-- **Image-heavy documents**: Analyze visual elements (slides, diagrams) alongside text
-
-#### 2. Classify Document Type
-
-> Read `references/output-templates.md` for the full document-type → analysis-focus table.
-
-#### 3. Analyze Content (Parallel Sub-Agents)
-
-```text
-Agent(subagent_type="general-purpose", model="haiku",
-  prompt="Read the document at [PATH] and extract: 1) Section structure / table of contents 2) Key concepts and definitions 3) Main arguments or claims. Use the Read tool with pages parameter for PDFs.")
-
-Agent(subagent_type="general-purpose", model="haiku",
-  prompt="Read the document at [PATH] and extract: 1) Actionable recommendations 2) Data points, metrics, examples 3) References to external resources. Use the Read tool with pages parameter for PDFs.")
-```
-
-#### 4. Project Relevance Analysis
-
-- Map how document content applies to the current project
-- Check if patterns/tools/techniques mentioned are already implemented
-- Gap analysis: document recommendations vs current project state
-
-#### 5. Output
-
-> Read `references/output-templates.md` for the full Mode 2 output format.
-
-#### Fallback
-
-If `Read` fails for a document format:
-1. Check file extension and try alternative parsing
-2. If binary format is unsupported, inform user and suggest converting to PDF/markdown
-3. Never produce an analysis based on partial or failed reads
-
----
-
-## Mode 3: Website Analysis (URL)
-
-### Goal
-
-Analyze website **tech stack, UX/UI, SEO, accessibility, and performance** to:
-1. Understand technical implementation
-2. Identify improvement opportunities
-3. Collect benchmarking insights
-
-### Process
-
-#### 1. Fetch Website
-
-- Use `WebFetch` tool to retrieve HTML
-- Fetch key pages (home, main feature pages, login, etc.)
-
-#### 2. Analyze (Parallel Sub-Agents)
-
-```text
-Agent(subagent_type="general-purpose", model="haiku",
-  prompt="Analyze the HTML from [URL] (use WebFetch). Extract: 1) Tech stack (framework, meta tags, scripts) 2) Page structure (header, nav, main sections, footer) 3) SEO elements (title, meta description, OG tags, structured data)")
-
-Agent(subagent_type="general-purpose", model="haiku",
-  prompt="Analyze the HTML from [URL] (use WebFetch). Extract: 1) Accessibility (ARIA labels, semantic HTML, alt texts, heading hierarchy) 2) Performance hints (script loading, image optimization) 3) Mobile responsiveness (viewport meta, media queries)")
-
-Agent(subagent_type="general-purpose", model="haiku",
-  prompt="Analyze the HTML from [URL] (use WebFetch). Extract: 1) UX patterns (navigation, CTA placement, form design) 2) Design system hints (CSS variables, component patterns) 3) Content strategy (copywriting tone, information hierarchy)")
-```
-
-#### 3. Figma URL Handling
-
-If a Figma URL is detected, switch to **Figma-specific analysis**:
-- Use `get_design_context` or `get_screenshot` to collect design data
-- Analyze component structure, design tokens, layout patterns
-- Compare design intent with current project code
-
-#### 4. Output
-
-> Read `references/output-templates.md` for the full Mode 3 output format.
-
-#### Fallback
-
-If `WebFetch` fails:
-1. Retry once with a simplified URL (strip query params)
-2. If still failing, inform user of the error (timeout, DNS, etc.)
-3. Suggest user provide HTML file directly: `/vibe.analyze page.html`
-
----
-
-## Mode 4: Project Quality Analysis (--code/--deps/--arch)
-
-### Scope
-
-- **Default** (`/vibe.analyze`): Full analysis (code + dependencies + architecture)
-- `--code`: Code quality only
-- `--deps`: Dependency analysis only
-- `--arch`: Architecture analysis only
-
-### Code Quality (--code)
-
-- Cyclomatic complexity analysis
-- Code quality validation
-- Coupling/cohesion assessment
-
-### Dependencies (--deps)
-
-- Read `package.json` / `pyproject.toml` / `pubspec.yaml`
-- Detect version conflicts, security vulnerabilities, outdated packages
-
-### Architecture (--arch)
-
-- Identify core modules
-- Map module dependencies
-- Detect circular dependencies and layer violations
-
-### Report
-
-Save to `.vibe/reports/analysis-{date}.md`:
-
-> Read `references/output-templates.md` for the full Mode 4 report format.
+두 모드가 동시에 해당하면 사용자에게 어느 쪽인지 묻는다 — 임의로 고르지 않는다.
 
 ## Core Tools (Semantic Analysis)
 
@@ -294,3 +96,12 @@ Each mode has a weighted completeness checklist. Score = sum(checked items × we
 ---
 
 ARGUMENTS: $ARGUMENTS
+
+## Done Criteria
+
+- [ ] The report records the target and selected mode.
+- [ ] Every material finding has a file/line, URL, or source-location citation.
+- [ ] The selected mode's minimum depth and quality score pass.
+- [ ] The specified `.vibe/reports/` output exists.
+
+ARGUMENTS: $ARGUMENTS

package/skills/vibe.analyze/references/mode1-feature.md

@@ -0,0 +1,81 @@
+# Mode 1: Feature/Module Analysis
+
+> vibe.analyze SKILL.md 의 모드 라우팅에서 **이 모드가 선택됐을 때만** 로드한다.
+
+## Mode 1: Feature/Module Analysis (`/vibe.analyze "feature-name"`)
+
+### Goal
+
+Explore all source code related to the requested feature/module and analyze flow to:
+1. Understand current implementation status
+2. Map code structure and dependencies
+3. Build context for future development/modification requests
+
+### Process
+
+#### 1. Request Analysis
+
+Extract keywords from the user request:
+- Feature name (e.g., login, feed, payment)
+- Action (e.g., create, read, update, delete)
+- Scope (e.g., backend only, frontend only, full)
+
+#### 2. Understand Project Structure
+
+Read `CLAUDE.md`, `package.json`, `pyproject.toml`, etc. to identify tech stack.
+
+> Read `references/output-templates.md` for the full backend/frontend stack → directory mapping.
+
+#### 3. Explore Related Code (Parallel Sub-Agents)
+
+**MANDATORY: Delegate independent exploration through the harness's native collaboration capability. Never explore all branches in the coordinator session.**
+
+> Why: 3 Explore agents return ~600 tokens of summaries to main session.
+> Direct file-pattern search, text search, and full-file reading in the coordinator session would add 5-15K tokens of raw content.
+
+**Harness adapter:** Claude Code maps each worker to Task/Agent; Codex maps each
+worker to native collaboration. Inherit the session model by default. Dispatch
+the following independent workers concurrently when capacity permits:
+
+```text
+- Worker: find all [FEATURE] related API endpoints; list paths, methods, routes, and auth requirements.
+- Worker: find all [FEATURE] related services, business logic, utilities, and dependencies.
+- Worker: find all [FEATURE] related data models, schemas, queries, relationships, and key fields.
+```
+
+> 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
+- Only Read specific files in main session when agent summaries need clarification
+
+#### 4. Flow Analysis
+
+**API Flow:**
+- Endpoint URL and HTTP method
+- Request/response schema
+- Authentication/authorization requirements
+
+**Business Logic:**
+- Core methods and their roles
+- Validation rules
+- External service integrations
+
+**Data Flow:**
+- Related tables/models
+- Relationships (1:N, N:M)
+- Key query patterns
+
+#### 5. Output
+
+> Read `references/output-templates.md` for the full Mode 1 output format.
+
+#### 6. Next Steps
+
+After analysis, suggest mode-specific follow-up actions.
+
+> Read `references/output-templates.md` for the full Next Steps decision tables (code/feature, document, website).
+
+Wait for user's choice before proceeding.
+
+---

package/skills/vibe.analyze/references/mode2-document.md

@@ -0,0 +1,50 @@
+# Mode 2: Document Analysis (PDF, Markdown, Slides)
+
+> vibe.analyze SKILL.md 의 모드 라우팅에서 **이 모드가 선택됐을 때만** 로드한다.
+
+## Mode 2: Document Analysis (PDF, Markdown, Slides)
+
+### Goal
+
+Analyze document **structure, key content, quality, and applicability** to:
+1. Extract and organize information from the document
+2. Map relevance to the current project
+3. Suggest follow-up actions (development, improvement, application)
+
+### Process
+
+#### 1. Read Document
+
+- **PDF**: Use `Read` tool with `pages` parameter (split large documents into chunks of 20 pages)
+- **Markdown/Text**: Use `Read` tool for the full file
+- **Image-heavy documents**: Analyze visual elements (slides, diagrams) alongside text
+
+#### 2. Classify Document Type
+
+> Read `references/output-templates.md` for the full document-type → analysis-focus table.
+
+#### 3. Analyze Content (Parallel Sub-Agents)
+
+```text
+- Worker: read [PATH] in full (page ranges for PDFs) and extract section structure, key concepts, definitions, and claims.
+- Worker: read [PATH] in full (page ranges for PDFs) and extract recommendations, data points, examples, and references.
+```
+
+#### 4. Project Relevance Analysis
+
+- Map how document content applies to the current project
+- Check if patterns/tools/techniques mentioned are already implemented
+- Gap analysis: document recommendations vs current project state
+
+#### 5. Output
+
+> Read `references/output-templates.md` for the full Mode 2 output format.
+
+#### Fallback
+
+If `Read` fails for a document format:
+1. Check file extension and try alternative parsing
+2. If binary format is unsupported, inform user and suggest converting to PDF/markdown
+3. Never produce an analysis based on partial or failed reads
+
+---

package/skills/vibe.analyze/references/mode3-website.md

@@ -0,0 +1,47 @@
+# Mode 3: Website Analysis (URL)
+
+> vibe.analyze SKILL.md 의 모드 라우팅에서 **이 모드가 선택됐을 때만** 로드한다.
+
+## Mode 3: Website Analysis (URL)
+
+### Goal
+
+Analyze website **tech stack, UX/UI, SEO, accessibility, and performance** to:
+1. Understand technical implementation
+2. Identify improvement opportunities
+3. Collect benchmarking insights
+
+### Process
+
+#### 1. Fetch Website
+
+- Use the harness's web-page retrieval capability to retrieve HTML
+- Fetch key pages (home, main feature pages, login, etc.)
+
+#### 2. Analyze (Parallel Sub-Agents)
+
+```text
+- Worker: retrieve and analyze [URL] for tech stack, page structure, and SEO elements.
+- Worker: retrieve and analyze [URL] for accessibility, performance hints, and responsiveness.
+- Worker: retrieve and analyze [URL] for UX patterns, design-system signals, and content strategy.
+```
+
+#### 3. Figma URL Handling
+
+If a Figma URL is detected, switch to **Figma-specific analysis**:
+- Use `get_design_context` or `get_screenshot` to collect design data
+- Analyze component structure, design tokens, layout patterns
+- Compare design intent with current project code
+
+#### 4. Output
+
+> Read `references/output-templates.md` for the full Mode 3 output format.
+
+#### Fallback
+
+If web-page retrieval fails:
+1. Retry once with a simplified URL (strip query params)
+2. If still failing, inform user of the error (timeout, DNS, etc.)
+3. Suggest user provide HTML file directly: `/vibe.analyze page.html`
+
+---

package/skills/vibe.analyze/references/mode4-quality.md

@@ -0,0 +1,35 @@
+# Mode 4: Project Quality Analysis (--code/--deps/--arch)
+
+> vibe.analyze SKILL.md 의 모드 라우팅에서 **이 모드가 선택됐을 때만** 로드한다.
+
+## Mode 4: Project Quality Analysis (--code/--deps/--arch)
+
+### Scope
+
+- **Default** (`/vibe.analyze`): Full analysis (code + dependencies + architecture)
+- `--code`: Code quality only
+- `--deps`: Dependency analysis only
+- `--arch`: Architecture analysis only
+
+### Code Quality (--code)
+
+- Cyclomatic complexity analysis
+- Code quality validation
+- Coupling/cohesion assessment
+
+### Dependencies (--deps)
+
+- Read `package.json` / `pyproject.toml` / `pubspec.yaml`
+- Detect version conflicts, security vulnerabilities, outdated packages
+
+### Architecture (--arch)
+
+- Identify core modules
+- Map module dependencies
+- Detect circular dependencies and layer violations
+
+### Report
+
+Save to `.vibe/reports/analysis-{date}.md`:
+
+> Read `references/output-templates.md` for the full Mode 4 report format.

package/skills/vibe.analyze/references/output-templates.md

@@ -15,10 +15,10 @@
 ## Mode 1: Scale for Large Projects (6+ related files) — Additional Agent Prompts
 
 ```text
-Agent(subagent_type="Explore", model="haiku",
+Agent(subagent_type="Explore",
   prompt="Find all test files related to [FEATURE]. Identify tested vs untested paths.")
 
-Agent(subagent_type="Explore", model="haiku",
+Agent(subagent_type="Explore",
   prompt="Analyze [FEATURE] configuration, environment variables, and external integrations.")
 ```
 

package/skills/vibe.brand-assets/SKILL.md

@@ -32,8 +32,8 @@ Auto-generate app icons and favicons based on SPEC brand information.
 - `android-chrome-512x512.png`
 
 ### Mobile (if applicable)
-- iOS: `AppIcon.appiconset/` with all sizes
-- Android: `mipmap-*/` adaptive icons
+
+For native iOS or Android targets only, read `references/mobile-assets.md`. Web-only favicon/OG calls do not load it.
 
 ## SPEC Brand Section
 

package/skills/vibe.brand-assets/references/mobile-assets.md

@@ -0,0 +1,6 @@
+# Native Mobile Brand Assets
+
+Load only when the target includes a native iOS or Android app.
+
+- iOS: `AppIcon.appiconset/` with all sizes
+- Android: `mipmap-*/` adaptive icons