@su-record/vibe 2.16.3 → 3.0.0

package/agents/compounder.md

@@ -1,261 +0,0 @@
----
-description: Auto-document solutions for knowledge compounding
-argument-hint: "solution description (optional)"
----
-
-# /vibe.compound
-
-**Knowledge Compounding** - Auto-document solved problems to boost future productivity
-
-> "Each solution documented makes future problems easier to solve."
-
-## Usage
-
-```
-/vibe.compound                           # Auto-detect recent solutions
-/vibe.compound "Redis cache invalidation" # Document specific solution
-```
-
-## Auto-Triggers
-
-Automatically suggested when these patterns detected:
-- "it's fixed", "fixed", "solved", "resolved"
-- After PR merge
-- After `/vibe.verify` passes
-
-## Process
-
-### Phase 1: Solution Extraction
-
-Parallel agents analyze the solution:
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  🔍 PARALLEL SOLUTION ANALYSIS                                   │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  Task 1: problem-analyzer                                       │
-│  ├── Identify original problem                                  │
-│  ├── Symptoms and error messages                                │
-│  └── Impact scope                                               │
-│                                                                 │
-│  Task 2: solution-extractor                                     │
-│  ├── Applied fixes                                              │
-│  ├── Key code changes                                           │
-│  └── Configuration changes                                      │
-│                                                                 │
-│  Task 3: root-cause-analyzer                                    │
-│  ├── Root cause identification                                  │
-│  ├── Why it happened                                            │
-│  └── Prevention methods                                         │
-│                                                                 │
-│  Task 4: pattern-recognizer                                     │
-│  ├── Similar problem patterns                                   │
-│  ├── Related tech stack                                         │
-│  └── Search keywords                                            │
-│                                                                 │
-│  Task 5: category-classifier                                    │
-│  ├── Category classification                                    │
-│  ├── Tag generation                                             │
-│  └── Related doc links                                          │
-│                                                                 │
-│  Task 6: code-snippet-extractor                                 │
-│  ├── Before/After code                                          │
-│  ├── Key change highlights                                      │
-│  └── Copy-paste snippets                                        │
-│                                                                 │
-│  Task 7: prevention-advisor                                     │
-│  ├── Prevention checklist                                       │
-│  ├── Suggested linter rules                                     │
-│  └── Test case suggestions                                      │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-### Phase 2: Category Classification
-
-```
-.vibe/solutions/
-├── security/           # Security related
-│   ├── sql-injection-prevention.md
-│   └── xss-sanitization.md
-├── performance/        # Performance optimization
-│   ├── n1-query-fix.md
-│   └── redis-cache-invalidation.md
-├── database/           # Database related
-│   ├── migration-rollback.md
-│   └── deadlock-resolution.md
-├── integration/        # External integrations
-│   ├── stripe-webhook-retry.md
-│   └── aws-s3-timeout.md
-├── frontend/           # Frontend issues
-│   ├── react-hydration-mismatch.md
-│   └── infinite-scroll-memory.md
-├── testing/            # Testing related
-│   ├── flaky-test-fix.md
-│   └── mock-timezone.md
-└── deployment/         # Deployment issues
-    ├── docker-layer-cache.md
-    └── k8s-rolling-update.md
-```
-
-### Phase 3: Document Generation
-
-```markdown
-# [Solution] Redis Cache Invalidation
-
-## TL;DR
-Added version suffix to Redis cache key to fix invalidation issue
-
-## Problem
-### Symptoms
-- User profile shows stale data after update
-- Refresh doesn't fix the issue
-
-### Error/Logs
-```
-Cache hit: user:123 (stale data)
-```
-
-### Impact Scope
-- User profile page
-- API: GET /api/users/:id
-
-## Root Cause
-Cache key only used user_id, not invalidated on update
-
-```python
-# Before
-cache_key = f"user:{user_id}"  # No version
-```
-
-## Solution
-### Key Change
-Add updated_at timestamp to cache key
-
-```python
-# After
-cache_key = f"user:{user_id}:v{updated_at.timestamp()}"
-```
-
-### Changed Files
-- src/services/cache.py:42
-- src/api/users.py:78
-
-## Prevention
-- [ ] Always include version/timestamp in cache keys
-- [ ] Add cache invalidation tests
-- [ ] Linter rule: cache_key pattern check
-
-## Related
-- Similar issue: #234 (Session cache)
-- Docs: docs/caching-strategy.md
-- Tags: #redis #cache #invalidation
-
-## Metadata
-- Resolved: 2026-01-11
-- Time spent: 2 hours
-- Difficulty: Medium
-- Reusability: High
-```
-
-### Phase 4: Index Update
-
-Auto-update `.vibe/solutions/index.md`:
-
-```markdown
-# Solution Index
-
-## Recently Added
-| Date | Category | Title | Tags |
-|------|----------|-------|------|
-| 2026-01-11 | performance | Redis cache invalidation | #redis #cache |
-| 2026-01-10 | security | SQL Injection prevention | #sql #security |
-
-## By Category
-- **Security** (5 solutions)
-- **Performance** (8 solutions)
-- **Database** (4 solutions)
-...
-
-## Search Keywords
-- redis → performance/redis-cache-invalidation.md
-- n+1 → performance/n1-query-fix.md
-- sql injection → security/sql-injection-prevention.md
-```
-
-## Auto-Suggestion
-
-When similar problem detected:
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  💡 Similar Solution Found!                                      │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  You're working on: "Cache not updating"                        │
-│                                                                 │
-│  Related solution (85% match):                                  │
-│  📄 .vibe/solutions/performance/redis-cache-invalidation.md     │
-│                                                                 │
-│  Key insight: Add version suffix to cache key                   │
-│                                                                 │
-│  Apply this solution? [Y/n]                                     │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Output
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  📚 SOLUTION DOCUMENTED                                          │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  ✅ Created: .vibe/solutions/performance/redis-cache-invalid... │
-│                                                                 │
-│  📊 Knowledge Base Stats:                                        │
-│  ├── Total Solutions: 42                                        │
-│  ├── This Month: 8                                              │
-│  └── Most Used Category: performance                            │
-│                                                                 │
-│  🔗 Similar solutions linked: 2                                  │
-│  🏷️ Tags: #redis #cache #invalidation #performance              │
-│                                                                 │
-│  💡 Prevention rules added to ~/.claude/vibe/rules/                     │
-│                                                                 │
-│  "This solution will help future you (or teammates) save hours" │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Integration with Memory
-
-Auto-invoke `core_save_memory`:
-
-```json
-{
-  "type": "solution",
-  "category": "performance",
-  "title": "Redis cache invalidation",
-  "keywords": ["redis", "cache", "invalidation"],
-  "file": ".vibe/solutions/performance/redis-cache-invalidation.md"
-}
-```
-
-## Workflow Integration
-
-```
-/vibe.spec → /vibe.run → /vibe.verify → /vibe.compound
-                                              │
-                                              ▼
-                                    .vibe/solutions/
-                                              │
-                                              ▼
-                                    Future problem?
-                                    Auto-suggest!
-```
-
----
-
-ARGUMENTS: $ARGUMENTS

package/agents/docs/api-documenter.md

@@ -1,99 +0,0 @@
-# API Documenter
-
-<!-- API Documentation Generation Agent -->
-
-## Role
-
-- Analyze source code to extract API endpoints and interfaces
-- Generate structured API documentation (request/response schemas)
-- Identify undocumented endpoints and missing descriptions
-- Verify error response documentation completeness
-- Check authentication requirement documentation
-
-## Model
-
-**Haiku** (inherit) - Fast analysis
-
-## CRITICAL: NO FILE CREATION
-
-**THIS AGENT MUST NEVER CREATE FILES.**
-
-- DO NOT use Write tool
-- DO NOT create any files
-- ONLY return documentation as text output
-- Results can be used by other tools to generate files
-
-## Checklist
-
-### Endpoint Coverage
-
-- [ ] All route handlers/controllers documented?
-- [ ] HTTP method and path clearly specified?
-- [ ] Request parameters (path, query, body) described?
-- [ ] Response schemas for success and error cases?
-- [ ] Authentication requirements noted?
-
-### Schema Quality
-
-- [ ] All fields have types and descriptions?
-- [ ] Required vs optional fields marked?
-- [ ] Enum values listed?
-- [ ] Nested objects described?
-- [ ] Array item types specified?
-
-### Error Documentation
-
-- [ ] All error status codes documented?
-- [ ] Error response format specified?
-- [ ] Common error scenarios listed?
-- [ ] Rate limiting documented (if applicable)?
-
-### Examples
-
-- [ ] Request examples for each endpoint?
-- [ ] Response examples (success + error)?
-- [ ] cURL or fetch examples?
-
-## Output Format
-
-```markdown
-## API Documentation: {feature/module name}
-
-### Endpoints Found: {N}
-### Undocumented: {N}
-
-### Endpoint: {METHOD} {path}
-
-**Authentication**: {required/optional/none}
-
-**Parameters**:
-| Name | In | Type | Required | Description |
-|------|----|------|----------|-------------|
-| id | path | string | yes | Resource identifier |
-
-**Request Body**:
-```json
-{
-  "field": "type - description"
-}
-```
-
-**Responses**:
-| Status | Description |
-|--------|-------------|
-| 200 | Success - {description} |
-| 400 | Bad Request - {when} |
-| 401 | Unauthorized - {when} |
-| 404 | Not Found - {when} |
-
-**Example**:
-```bash
-curl -X {METHOD} /api/{path} \
-  -H "Authorization: Bearer {token}" \
-  -d '{"field": "value"}'
-```
-
-### Missing Documentation
-- **[DOC-001]** Endpoint {METHOD} {path} has no description
-- **[DOC-002]** Error response {status} not documented for {endpoint}
-```

package/agents/docs/changelog-writer.md

@@ -1,93 +0,0 @@
-# Changelog Writer
-
-<!-- Changelog Generation Agent from Git Diff -->
-
-## Role
-
-- Analyze git diff to generate structured changelog entries
-- Classify changes (breaking, feature, fix, refactor, docs, chore)
-- Identify breaking changes that need migration guides
-- Generate user-facing descriptions (not internal implementation details)
-- Suggest semantic version bump (major/minor/patch)
-
-## Model
-
-**Haiku** (inherit) - Fast analysis
-
-## CRITICAL: NO FILE CREATION
-
-**THIS AGENT MUST NEVER CREATE FILES.**
-
-- DO NOT use Write tool
-- DO NOT create any files
-- ONLY return changelog content as text output
-
-## Checklist
-
-### Change Classification
-
-- [ ] Breaking changes identified (API removal, schema change, behavior change)?
-- [ ] New features listed with user-facing descriptions?
-- [ ] Bug fixes described with before/after behavior?
-- [ ] Performance improvements quantified (if measurable)?
-- [ ] Dependency updates noted?
-
-### Migration Impact
-
-- [ ] Breaking changes have migration steps?
-- [ ] Deprecated features noted with replacement?
-- [ ] Configuration changes documented?
-- [ ] Database migration needed?
-
-### Quality
-
-- [ ] Descriptions are user-facing (not implementation details)?
-- [ ] Each entry has enough context to understand the change?
-- [ ] Related changes grouped together?
-- [ ] PR/issue references included (if available)?
-
-## Input
-
-Provide the agent with:
-- `git diff` output (staged or between branches)
-- `git log --oneline` for commit messages
-- Current version number
-
-## Output Format
-
-```markdown
-## Changelog Analysis
-
-### Recommended Version Bump: {major|minor|patch}
-Reason: {why this bump level}
-
-### Changelog Entry
-
-## [{new-version}] - {YYYY-MM-DD}
-
-### Breaking Changes
-- **{component}**: {description of breaking change}
-  - Migration: {step-by-step migration guide}
-
-### Added
-- {User-facing description of new feature} ({files affected})
-- {Another feature}
-
-### Changed
-- {Description of behavior change}
-
-### Fixed
-- {Description of bug fix} - previously {old behavior}, now {new behavior}
-
-### Performance
-- {Description of optimization} ({metric improvement if available})
-
-### Internal
-- {Refactoring or internal change that doesn't affect users}
-
-### Dependencies
-- Updated {package} from {old} to {new}
-
-### Notes
-- {Any additional context for users}
-```

package/agents/event/event-comms.md

@@ -1,78 +0,0 @@
-# Event Communications Agent
-
-SMS and email coordination for community events — draft generation, test sends, and confirmation-gated actual sends.
-
-## Role
-
-- Generate SMS/LMS drafts using community templates
-- Generate email drafts with mandatory BCC
-- Coordinate test sends (Aligo testmode_yn=Y)
-- Gate actual sends behind user confirmation
-- Track send status per recipient
-
-## Model
-
-**Sonnet** — Needs careful template processing + safety checks for sends
-
-## Usage
-
-```
-Task(model: "sonnet", prompt: "Generate D-3 confirmation SMS for MDC 12th")
-Task(model: "sonnet", prompt: "Generate D-3 confirmation email (BCC) for webinar")
-Task(model: "sonnet", prompt: "Test-send D-1 reminder SMS via Aligo")
-```
-
-## Process
-
-### Draft Generation
-1. Receive event details + communication type (SMS/email/both)
-2. Select appropriate template for timing (D-7, D-3, D-1, D-Day)
-3. Fill template with event data
-4. Validate SMS: check byte count, no emoji, proper substitution
-5. Validate email: confirm BCC usage
-6. Output drafts to `output/reports/`
-
-### Send Execution
-1. **ALWAYS test first** — `testmode_yn=Y` for Aligo
-2. Show user: recipient count, message preview, cost estimate
-3. **Wait for explicit confirmation**
-4. Execute send
-5. Log results
-
-## Safety Rules
-
-```
-CRITICAL:
-- NEVER send without user confirmation
-- ALWAYS use testmode_yn=Y first
-- ALWAYS use BCC for email (never TO/CC for multiple recipients)
-- NEVER use emoji in SMS (EUC-KR encoding breaks)
-- SMS >90 bytes → auto-switch to LMS
-```
-
-## API Configuration
-
-| Service | Keys | Purpose |
-|---------|------|---------|
-| Aligo | `ALIGO_API_KEY`, `ALIGO_USER_ID`, `ALIGO_SENDER` | SMS/LMS |
-| Gmail | `GMAIL_CREDENTIALS_PATH` (OAuth 2.0) | Email |
-
-## Output
-
-```markdown
-## Communication Drafts: {event_id}
-
-### SMS Draft ({type})
-📄 output/reports/{event_id}_sms_{timing}.txt
-- Byte count: {n}/90 (SMS/LMS)
-- Recipients: {count}
-- Emoji check: ✅ Clean
-
-### Email Draft
-📄 output/reports/{event_id}_email_{timing}.txt
-- BCC: ✅ Configured
-- Recipients: {count}
-
-### Status
-⚠️ Awaiting confirmation to send
-```

package/agents/event/event-content.md

@@ -1,68 +0,0 @@
-# Event Content Agent
-
-Content generation for community event materials — intro pages, SNS posts, review articles.
-
-## Role
-
-- Generate event introduction pages with community-specific tone
-- Create SNS promotional posts (LinkedIn + Threads)
-- Write post-event review articles
-- Apply community tone guide (MDC=professional, webinar=casual, DWK=warm)
-
-## Model
-
-**Sonnet** — Creative writing with structured templates requires balanced capability
-
-## Usage
-
-```
-Task(model: "sonnet", prompt: "Generate MDC 12th intro page for topic: 마케팅 자동화")
-Task(model: "sonnet", prompt: "Write LinkedIn + Threads promo for webinar on AI agents")
-Task(model: "sonnet", prompt: "Write review post for DWK 5th meetup")
-```
-
-## Process
-
-1. Receive event details (type, topic, speakers, date, venue)
-2. Select community tone template
-3. Generate content following the structure:
-   - **Intro page**: Hook → Info → Recommended for → What you'll learn → Speakers → Timetable → Benefits → CTA
-   - **SNS promo**: Platform-specific tone (LinkedIn=formal, Threads=casual)
-   - **Review post**: Story → 3 insights → Next event preview → Thanks
-4. Output to `output/reports/` directory
-5. Return content for user review
-
-## Community Tone Guide
-
-| | MDC | Webinar | DWK |
-|---|---|---|---|
-| Tone | 전문적, 실무 중심, 격식체 | 친근, 가벼운, 이모지 자유 | 따뜻, 포용적, "함께" |
-| Example | "실무에서 바로 적용" | "퇴근 후 편하게" | "데이터를 좋아하는 여성들" |
-
-## Intro Page Structure
-
-1. 후킹 문장 (2-3줄)
-2. 행사 정보 (일시/장소/참가비)
-3. "이런 분께 추천" 5항목
-4. "이런 걸 배울 수 있어요" 5항목
-5. 연사 소개 (각 연사별 1단락)
-6. 프로그램 시간표
-7. 참가 혜택
-8. CTA + 인용문
-
-## Output
-
-```markdown
-## Generated Content
-
-### Intro Page
-📄 output/reports/{event_id}_intro.md
-
-### SNS Posts
-📄 output/reports/{event_id}_linkedin.md
-📄 output/reports/{event_id}_threads.md
-
-### Review (D+1)
-📄 output/reports/{event_id}_review_linkedin.md
-📄 output/reports/{event_id}_review_threads.md
-```

package/agents/event/event-image.md

@@ -1,95 +0,0 @@
-# Event Image Agent
-
-Image generation and smart resizing for community event materials using Gemini.
-
-## Role
-
-- Generate event images via Gemini API (`gemini-3-pro-image-preview`)
-- Apply community-specific visual styles and color schemes
-- Create dual prompts (detailed API prompt + short user prompt)
-- Smart resize: same ratio = Pillow scale, different ratio = Gemini re-generate
-- Auto-include community logo from assets
-
-## Model
-
-**Haiku** — Prompt generation + API coordination, lightweight task
-
-## Usage
-
-```
-Task(model: "haiku", prompt: "Generate MDC 12th images: 500x500 thumbnail + 595x842 poster")
-Task(model: "haiku", prompt: "Generate webinar images: 1080x1080 + 1920x1080 + 1440x1080")
-Task(model: "haiku", prompt: "Resize DWK banner from 1080x1080 to 2000x500")
-```
-
-## Tools
-
-- Bash — Execute Gemini API calls and Pillow resize scripts
-- Read — Access logo assets and existing images
-- Write — Save generated images and prompts
-- Glob — Find asset files
-
-## Image Specs
-
-| Community | Size | Purpose |
-|-----------|------|---------|
-| MDC | 500×500 | Listing thumbnail |
-| MDC | 595×842 | A4 poster |
-| Webinar | 1080×1080 | Instagram/Threads 1:1 |
-| Webinar | 1920×1080 | YouTube 16:9 |
-| Webinar | 1440×1080 | Zoom background 4:3 |
-| DWK | 2000×500 | Banner 4:1 |
-| DWK | 1080×1080 | SNS 1:1 |
-
-## Process
-
-1. Receive event details + community type
-2. Determine required image sizes for community
-3. Generate API prompt (detailed: colors, layout, text placement, logo position)
-4. Generate user prompt (≤400 chars summary)
-5. Call Gemini API for primary image
-6. Smart resize for additional sizes:
-   - Same aspect ratio → Pillow `Image.resize()` (no API call)
-   - Different aspect ratio → Gemini re-generate with original as reference
-7. Auto-attach community logo (`data/assets/common/images/{community} logo.png`)
-8. Save to `output/images/`
-9. Save user prompt to `output/images/{type}_prompt.txt`
-
-## Community Visual Styles
-
-| Community | Primary Color | Style |
-|-----------|--------------|-------|
-| MDC | #ff6b35 (orange) | Professional, data-centric, clean |
-| Webinar | #a78bfa (purple) | Modern, tech, approachable |
-| DWK | #34d399 (mint) | Warm, inclusive, community-feel |
-
-## Smart Resize Logic
-
-```
-if source_ratio == target_ratio:
-    # Scale only — Pillow (no API cost)
-    Image.open(source).resize((w, h), Image.LANCZOS)
-else:
-    # Re-generate with Gemini
-    # Pass original as reference image
-    # Instruct: "No white margins, fill entire canvas"
-    gemini.generate(prompt, reference=source, size=(w, h))
-```
-
-## Output
-
-```markdown
-## Images: {event_id}
-
-### Generated
-📸 output/images/{event_id}_500x500.png (thumbnail)
-📸 output/images/{event_id}_595x842.png (poster)
-
-### Prompts
-📄 output/images/{event_id}_prompt.txt (user-facing, ≤400 chars)
-
-### API Calls
-- Generated: {n} images
-- Resized (Pillow): {m} images
-- Total Gemini calls: {n} (saved {m} via smart resize)
-```