@su-record/vibe 2.2.2 → 2.2.4

package/commands/vibe.compound.md

@@ -0,0 +1,261 @@
+---
+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
+
+```
+.claude/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 `.claude/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):                                  │
+│  📄 .claude/vibe/solutions/performance/redis-cache-invalidation.md     │
+│                                                                 │
+│  Key insight: Add version suffix to cache key                   │
+│                                                                 │
+│  Apply this solution? [Y/n]                                     │
+│                                                                 │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+## Output
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  📚 SOLUTION DOCUMENTED                                          │
+├─────────────────────────────────────────────────────────────────┤
+│                                                                 │
+│  ✅ Created: .claude/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 `vibe_save_memory`:
+
+```json
+{
+  "type": "solution",
+  "category": "performance",
+  "title": "Redis cache invalidation",
+  "keywords": ["redis", "cache", "invalidation"],
+  "file": ".claude/vibe/solutions/performance/redis-cache-invalidation.md"
+}
+```
+
+## Workflow Integration
+
+```
+/vibe.spec → /vibe.run → /vibe.verify → /vibe.compound
+                                              │
+                                              ▼
+                                    .claude/vibe/solutions/
+                                              │
+                                              ▼
+                                    Future problem?
+                                    Auto-suggest!
+```
+
+---
+
+ARGUMENTS: $ARGUMENTS

package/commands/vibe.continue.md

@@ -0,0 +1,88 @@
+---
+description: Restore previous session context
+argument-hint: [projectPath]
+---
+
+# /vibe.continue
+
+Restore previous session context and continue development.
+
+## Usage
+
+```
+/vibe.continue                    # Restore context for current directory
+/vibe.continue "/path/to/project" # Restore context for specific project
+```
+
+## What It Does
+
+1. **Load Project Memories** - Retrieves saved project decisions, patterns, architecture notes
+2. **Restore Context** - Loads previous session's work state (tasks, blockers, next steps)
+3. **Load Coding Guides** - Applies project-specific coding standards
+
+## Process
+
+```
+/vibe.continue
+      |
+      v
++---------------------------+
+| vibe_start_session  |
+| projectPath: $(pwd)       |
++---------------------------+
+      |
+      v
++---------------------------+
+| Load:                     |
+| - Project memories        |
+| - Previous context        |
+| - Coding guides           |
++---------------------------+
+      |
+      v
+Ready to continue!
+```
+
+## Example
+
+```
+User: /vibe.continue
+
+Claude:
+Session started.
+
+Recent Project Info:
+  - project-stack: Next.js 14, TypeScript, Tailwind...
+  - auth-decision: Using JWT with refresh tokens...
+  - current-feature: Working on login page...
+
+Previous Context:
+  - HIGH priority from 2024-01-15 14:32
+    Task: Implement password validation
+    Blockers: Need to decide on complexity rules
+
+Active Coding Guides:
+  - TypeScript Standards (core): Strict mode, no any...
+
+Ready to continue development! What would you like to work on?
+```
+
+## When to Use
+
+- Starting a new Claude Code session
+- After `/new` command
+- Resuming work after a break
+- Switching between projects
+
+## Related Commands
+
+- `/vibe.run` - Execute implementation
+- `/vibe.spec` - Create SPEC document
+
+---
+
+**Action**: Call `vibe_start_session` with projectPath
+
+```
+vibe_start_session(projectPath: "$ARGUMENTS" || process.cwd())
+```

package/commands/vibe.diagram.md

@@ -0,0 +1,178 @@
+---
+description: Generate diagrams (architecture, ERD, flowchart)
+argument-hint: --er or --flow (optional)
+---
+
+# /vibe.diagram
+
+Generate diagrams (architecture, ERD, flowchart).
+
+## Usage
+
+```
+/vibe.diagram
+/vibe.diagram --er
+/vibe.diagram --flow
+```
+
+## Process
+
+### 1. Determine Diagram Type
+
+- **Default** (`/vibe.diagram`): Architecture diagram
+- **--er**: ERD (Entity-Relationship Diagram)
+- **--flow**: Flowchart (main processes)
+
+### 2. Project Analysis
+
+#### Architecture Diagram
+- Understand project structure (folder structure)
+- Identify major modules and layers
+- Analyze dependency relationships
+
+#### ERD
+- Find database schema files
+  - `backend/models/`
+  - `migrations/`
+  - `schema.sql`
+- Identify table relationships
+
+#### Flowchart
+- Main business logic flows
+- User action → System response
+
+### 3. Generate Mermaid Code
+
+Generate diagram as ASCII art or Mermaid code:
+
+#### Architecture Diagram (Mermaid)
+
+```mermaid
+graph TB
+    Client[React Frontend]
+    API[FastAPI Backend]
+    DB[(PostgreSQL)]
+    Cache[(Redis)]
+
+    Client -->|HTTP| API
+    API -->|Query| DB
+    API -->|Cache| Cache
+```
+
+#### ERD (Mermaid)
+
+```mermaid
+erDiagram
+    USER ||--o{ FEED : creates
+    USER ||--o{ FOLLOW : follows
+    FEED }o--|| RESTAURANT : references
+
+    USER {
+        uuid id PK
+        string email
+        int tier
+    }
+    FEED {
+        uuid id PK
+        uuid user_id FK
+        uuid restaurant_id FK
+        text content
+    }
+```
+
+#### Flowchart (Mermaid)
+
+```mermaid
+flowchart TD
+    Start([User writes feed])
+    GPS{GPS Auth}
+    Vision{Vision API Verify}
+    OCR{OCR Auth}
+    Save[Save Feed]
+
+    Start --> GPS
+    GPS -->|Within 50m| Vision
+    GPS -->|Out of range| Fail
+    Vision -->|Food detected| OCR
+    Vision -->|Failed| Fail
+    OCR -->|Optional| Save
+    Save --> End([Complete])
+```
+
+### 4. Rendering Guide
+
+Guide on how to render generated Mermaid code:
+
+- **GitHub**: Paste in `.md` file (auto-renders)
+- **VSCode**: Install Mermaid extension
+- **Online**: https://mermaid.live/
+
+## Example
+
+```
+User: /vibe.diagram --er
+
+Claude: Generating ERD...
+
+Analyzing project...
+- Database schema found: backend/models/
+- Tables: 15
+- Key relationships: USER, FEED, RESTAURANT
+
+✅ ERD generation complete!
+
+```mermaid
+erDiagram
+    USER ||--o{ FEED : creates
+    USER ||--o{ FOLLOW : "follows/followed_by"
+    USER ||--o{ BOOKMARK : bookmarks
+    FEED }o--|| RESTAURANT : references
+    FEED ||--o{ COMMENT : has
+    FEED ||--o{ LIKE : has
+
+    USER {
+        uuid id PK
+        string email UK
+        string username UK
+        int tier
+        int points
+        timestamp created_at
+    }
+
+    FEED {
+        uuid id PK
+        uuid user_id FK
+        uuid restaurant_id FK
+        text content
+        geography location
+        boolean ocr_verified
+        timestamp created_at
+    }
+
+    RESTAURANT {
+        uuid id PK
+        string name
+        geography location
+        string category
+        timestamp created_at
+    }
+```
+
+**Diagram save location:**
+  .claude/vibe/diagrams/erd-2025-11-17.md
+
+**Rendering options:**
+  1. Push to GitHub (auto-renders)
+  2. Use Mermaid extension in VSCode
+  3. View at https://mermaid.live/
+```
+
+## Notes
+
+- Mermaid is supported in GitHub, GitLab, VSCode, etc.
+- Complex diagrams may need manual adjustments
+- Generated diagrams are saved in `.claude/vibe/diagrams/` folder
+
+---
+
+ARGUMENTS: $ARGUMENTS