@su-record/vibe 2.7.6 → 2.7.9

package/skills/frontend-design/SKILL.md

@@ -4,14 +4,19 @@ description: "Production-grade frontend with bold aesthetic direction for UI-foc
 triggers: [frontend, ui design, aesthetic, beautiful ui, design system, ui quality, visual design]
 priority: 70
 ---
+
 # Frontend Design Skill
 
 Create production-grade frontend with bold aesthetic direction.
 
+## Pre-check (K1)
+
+> Does this project need a custom design direction? If using an existing design system (shadcn/ui, Material UI, Ant Design) without customization, standard component docs suffice.
+
 ## When to Use
 
 - UI-focused projects requiring high visual quality
-- Design system implementation
+- Design system implementation from scratch
 - User-facing features where aesthetics matter
 
 ## Core Principles
@@ -49,24 +54,6 @@ Create production-grade frontend with bold aesthetic direction.
 - Stock photography without curation
 - Safe, corporate color palettes
 
-## Implementation Guidelines
-
-```typescript
-// Design token structure
-const tokens = {
-  colors: {
-    primary: { /* custom palette */ },
-    semantic: { /* success, error, warning */ },
-  },
-  typography: {
-    fontFamily: { /* display, body, mono */ },
-    scale: { /* modular scale */ },
-  },
-  spacing: { /* consistent rhythm */ },
-  motion: { /* duration, easing */ },
-};
-```
-
 ## Quality Checklist
 
 - [ ] Typography creates clear hierarchy
@@ -77,16 +64,10 @@ const tokens = {
 - [ ] Dark mode (if applicable) is intentional
 - [ ] Micro-interactions provide feedback
 
-## Integration with Vibe
-
-Use with `/vibe.utils --ui` for preview:
-
-```bash
-/vibe.utils --ui "login form with bold typography and custom color scheme"
-```
-
-## Resources
+## Done Criteria (K4)
 
-- [Refactoring UI](https://www.refactoringui.com/) - Design principles
-- [Motion Design](https://motion.dev/) - Animation library
-- [Radix Primitives](https://www.radix-ui.com/) - Accessible components
+- [ ] Design tokens defined (colors, typography, spacing, motion)
+- [ ] Visual hierarchy clear at all breakpoints
+- [ ] No default/uncustomized framework styles remain
+- [ ] All interactive states designed (hover, focus, active, disabled)
+- [ ] Accessibility verified (contrast, focus rings, motion preferences)

package/skills/git-worktree/SKILL.md

@@ -4,181 +4,69 @@ description: "Git Worktree for parallel branch work. Auto-activates for PR revie
 triggers: [worktree, PR review, hotfix, parallel branch, multiple branches]
 priority: 50
 ---
-# Git Worktree Skill
 
-Parallel branch work using Git Worktree
+# Git Worktree
 
-## Overview
+## Pre-check (K1)
 
-Perform reviews/tests on other branches without interrupting main work
+> Do you need to work on another branch without losing current work? If you can just `git stash` and switch, worktree may be overkill.
 
-## Usage
+## Core Commands
 
 ```bash
-# Create worktree
-git worktree add ../review-pr123 pr/123
-
-# Work in that directory
-cd ../review-pr123
-npm test
-
-# Clean up after work is done
-git worktree remove ../review-pr123
-```
-
-## Commands
-
-### Create Worktree
-
-```bash
-# Worktree for PR review
+# Create worktree for PR review
 git worktree add ../review-{pr_number} origin/pr/{pr_number}
 
-# Worktree for specific branch
-git worktree add ../feature-work feature/new-feature
-
-# Worktree with new branch
+# Create worktree with new branch (hotfix)
 git worktree add -b hotfix/urgent ../hotfix main
-```
 
-### List Worktrees
-
-```bash
+# List all worktrees
 git worktree list
-# /path/to/main       abc1234 [main]
-# /path/to/review-123 def5678 [pr/123]
-```
-
-### Remove Worktree
-
-```bash
-# Normal removal
-git worktree remove ../review-123
 
-# Force removal (ignore uncommitted changes)
-git worktree remove --force ../review-123
+# Remove when done
+git worktree remove ../review-{pr_number}
 
-# Prune stale worktrees
+# Clean up stale entries
 git worktree prune
 ```
 
-## Workflow Integration
-
-### PR Review Workflow
+## PR Review Workflow
 
 ```
-┌─────────────────────────────────────────────────────────────────┐
-│  /vibe.review PR#123                                             │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  1. git worktree add ../review-123 origin/pr/123               │
-│  2. cd ../review-123                                            │
-│  3. npm install && npm test                                     │
-│  4. Run parallel review agents                                  │
-│  5. Generate review report                                      │
-│  6. cd - && git worktree remove ../review-123                  │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
+1. git worktree add ../review-123 origin/pr/123
+2. cd ../review-123
+3. npm install && npm test
+4. Run review agents
+5. cd - && git worktree remove ../review-123
 ```
 
-### Hotfix Workflow
+## Hotfix Workflow
 
 ```
-┌─────────────────────────────────────────────────────────────────┐
-│  Urgent hotfix while working on feature                         │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  # Keep feature work intact                                     │
-│  git worktree add -b hotfix/critical ../hotfix main            │
-│  cd ../hotfix                                                   │
-│                                                                 │
-│  # Fix and deploy                                               │
-│  vim src/bug.py                                                 │
-│  git commit -am "fix: critical bug"                             │
-│  git push origin hotfix/critical                                │
-│                                                                 │
-│  # Return to feature                                            │
-│  cd - && git worktree remove ../hotfix                         │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Benefits
-
-1. **No Stash Needed**: Keep current work intact
-2. **Full Codebase**: Each worktree is a complete codebase
-3. **Parallel Work**: Work on multiple branches simultaneously
-4. **Clean Testing**: Test in isolated environment
-
-## Best Practices
-
-### Naming Convention
-
-```bash
-# PR review
-../review-{pr_number}
-
-# Hotfix
-../hotfix-{issue_number}
-
-# Experiment
-../experiment-{feature_name}
+1. git worktree add -b hotfix/critical ../hotfix main
+2. cd ../hotfix
+3. Fix bug → commit → push
+4. cd - && git worktree remove ../hotfix
 ```
 
-### Cleanup
+## Naming Convention
 
 ```bash
-# Regular cleanup
-git worktree prune
-
-# Check all worktrees
-git worktree list
-
-# Auto cleanup with script
-for wt in $(git worktree list --porcelain | grep worktree | cut -d' ' -f2); do
-  if [[ $wt == *"review-"* ]] || [[ $wt == *"hotfix-"* ]]; then
-    git worktree remove "$wt" 2>/dev/null || true
-  fi
-done
-```
-
-### Integration with CI/CD
-
-```yaml
-# GitHub Actions example
-- name: Setup Review Worktree
-  run: |
-    git fetch origin pull/${{ github.event.pull_request.number }}/head:pr-${{ github.event.pull_request.number }}
-    git worktree add ../review pr-${{ github.event.pull_request.number }}
-
-- name: Run Tests in Worktree
-  working-directory: ../review
-  run: npm test
-
-- name: Cleanup
-  run: git worktree remove ../review
+../review-{pr_number}         # PR review
+../hotfix-{issue_number}      # Hotfix
+../experiment-{feature_name}  # Experiment
 ```
 
 ## Troubleshooting
 
-### "already checked out" Error
-
-```bash
-# Solution: Branch is already in another worktree
-git worktree list  # Check
-git worktree remove <path>  # Remove
-```
+| Error | Fix |
+|-------|-----|
+| "already checked out" | Branch is in another worktree — `git worktree list`, then remove |
+| Locked worktree | `git worktree unlock <path>` |
+| Stale worktree | `git worktree prune` |
 
-### Locked Worktree
+## Done Criteria (K4)
 
-```bash
-# Solution: Unlock the locked worktree
-git worktree unlock <path>
-```
-
-### Stale Worktree
-
-```bash
-# Solution: Clean up deleted directories
-git worktree prune
-```
+- [ ] Worktree created and work completed in isolation
+- [ ] Worktree removed after work is done
+- [ ] No stale worktrees left (`git worktree list` clean)

package/skills/handoff/SKILL.md

@@ -99,3 +99,11 @@ Or use alongside VIBE auto-restore:
 ```
 
 In this case, saved decisions are also restored via `core_recall_memory`.
+
+## Done Criteria (K4)
+
+- [ ] HANDOFF.md created with all sections filled
+- [ ] Completed/in-progress/next tasks accurately listed
+- [ ] Related files section includes all modified files
+- [ ] Session context saved via `core_auto_save_context`
+- [ ] Key decisions saved via `core_save_memory`

package/skills/parallel-research/SKILL.md

@@ -78,3 +78,10 @@ Reference during implementation
 - Research runs **after requirements confirmed**
 - Split overly broad topics
 - Research results are references, not absolute truth
+
+## Done Criteria (K4)
+
+- [ ] All 4 research agents returned results (or documented why not)
+- [ ] Results synthesized into actionable recommendations
+- [ ] Key findings reflected in SPEC Context section or implementation notes
+- [ ] Conflicting recommendations resolved with reasoning

package/skills/priority-todos/SKILL.md

@@ -4,239 +4,60 @@ description: "Priority-based TODO management (P1/P2/P3). Auto-activates when man
 triggers: [todo, priority, P1, P2, P3, task management, issue, organize]
 priority: 60
 ---
-# Priority-Based Todo Management Skill
 
-Priority-based TODO management system
+# Priority-Based Todo Management
 
-## Overview
+## Pre-check (K1)
 
-Classify tasks by P1/P2/P3 priority to handle important items first
+> Do you need structured priority tracking? For 1-2 item task lists, use inline TODOs. This system is for multi-issue tracking across reviews and sessions.
 
-## Priority Levels
+## Priority Definitions
 
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  Priority Levels                                                 │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  🔴 P1 (Critical)                                               │
-│  ├── Security vulnerabilities                                   │
-│  ├── Data loss risk                                             │
-│  ├── Production incidents                                       │
-│  └── Merge-blocking issues                                      │
-│                                                                 │
-│  🟡 P2 (Important)                                              │
-│  ├── Performance issues                                         │
-│  ├── Missing tests                                              │
-│  ├── Architecture violations                                    │
-│  └── Technical debt                                             │
-│                                                                 │
-│  🔵 P3 (Nice-to-have)                                           │
-│  ├── Code style                                                 │
-│  ├── Refactoring suggestions                                    │
-│  ├── Documentation                                              │
-│  └── Optimization opportunities                                 │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## File-Based Todo System
+| Priority | Meaning | Action | Examples |
+|----------|---------|--------|----------|
+| P1 | **Blocks merge** | Fix immediately | Security vulnerability, data loss risk, production incident |
+| P2 | **Should fix** | Fix before PR | Performance issue, missing tests, architecture violation |
+| P3 | **Backlog** | Fix when time permits | Code style, refactoring suggestion, documentation |
 
-### Directory Structure
+## Directory Structure
 
 ```
 .claude/vibe/todos/
 ├── P1-security-sql-injection.md
-├── P1-data-transaction-missing.md
 ├── P2-perf-n1-query.md
-├── P2-test-missing-edge-case.md
-├── P2-arch-circular-dependency.md
 ├── P3-style-extract-helper.md
-├── P3-docs-add-readme.md
-└── index.md
+├── index.md                      # Summary table with counts/status
+└── done/                         # Archived completed items
 ```
 
-### Todo File Format
-
-```markdown
-# [P1] SQL Injection Vulnerability
-
-## Summary
-User input directly concatenated in SQL query without sanitization.
-
-## Priority Justification
-- 🔴 P1 (Critical)
-- Category: Security
-- Impact: High (data breach risk)
-- Effort: Low (simple fix)
+## Workflow
 
-## Location
-- **File**: src/api/users.py
-- **Line**: 42-45
-- **Function**: `get_user_by_email()`
-
-## Current Code
-```python
-def get_user_by_email(email: str):
-    query = f"SELECT * FROM users WHERE email = '{email}'"
-    return db.execute(query)
-```
-
-## Suggested Fix
-```python
-def get_user_by_email(email: str):
-    query = "SELECT * FROM users WHERE email = %s"
-    return db.execute(query, (email,))
 ```
-
-## Checklist
-- [ ] Fix implemented
-- [ ] Unit test added
-- [ ] Security test added
-- [ ] Code reviewed
-- [ ] Merged
-
-## References
-- OWASP SQL Injection: https://owasp.org/www-community/attacks/SQL_Injection
-- Project Security Guide: docs/security.md
-
-## Metadata
-- Created: 2026-01-11
-- Author: Claude
-- Review: /vibe.review PR#123
+/vibe.review → Creates P1/P2/P3 todo files + updates index.md
+     ↓
+Fix P1 first (blocks merge)
+     ↓
+Fix P2 before PR (warning only)
+     ↓
+P3 → backlog (weekly review)
+     ↓
+Mark done → moves to done/ with date prefix
 ```
 
-### Index File
-
-```markdown
-# Todo Index
-
-## Summary
-| Priority | Count | Status |
-|----------|-------|--------|
-| 🔴 P1 | 2 | 🚨 Blocks merge |
-| 🟡 P2 | 5 | ⚠️ Should fix |
-| 🔵 P3 | 3 | 💡 Backlog |
-
-## 🔴 P1 Critical (Blocks Merge)
-
-| # | Title | Location | Status |
-|---|-------|----------|--------|
-| 1 | SQL Injection | users.py:42 | ❌ Open |
-| 2 | Missing Rollback | payment.py:128 | ❌ Open |
-
-## 🟡 P2 Important
-
-| # | Title | Location | Status |
-|---|-------|----------|--------|
-| 3 | N+1 Query | orders.py:78 | ❌ Open |
-| 4 | Missing Tests | auth.py | ❌ Open |
-| 5 | Circular Dep | services/ | ❌ Open |
-
-## 🔵 P3 Nice-to-have
-
-| # | Title | Location | Status |
-|---|-------|----------|--------|
-| 6 | Extract Helper | utils.py:45 | 💤 Backlog |
-| 7 | Add README | /payment | 💤 Backlog |
-
----
-
-Last updated: 2026-01-11 10:30
-```
+## Todo File Format
 
-## Workflow Commands
+Each file follows: `# [P1] Title` → Summary → Priority Justification → Location (file:line) → Suggested Fix → Checklist (fix, test, review, merge).
 
-### Create Todo
+## Rules
 
-```bash
-# Auto-generated from /vibe.review results
-/vibe.review PR#123
-# -> Creates files in .claude/vibe/todos/
-
-# Manual creation
-core todo add "SQL Injection in users.py" --priority P1 --category security
-```
-
-### List Todos
-
-```bash
-# Full list
-core todo list
-
-# By priority
-core todo list --priority P1
-core todo list --priority P2
-
-# By category
-core todo list --category security
-core todo list --category performance
-```
-
-### Complete Todo
-
-```bash
-# Mark as complete
-core todo done P1-security-sql-injection
-
-# Updates checklist in file + updates index
-```
-
-### Clean Up
-
-```bash
-# Archive completed items
-core todo archive
-
-# Result:
-# .claude/vibe/todos/P1-security-sql-injection.md
-# -> .claude/vibe/todos/done/2026-01-11-P1-security-sql-injection.md
-```
-
-## Integration with TodoWrite
-
-Integration with existing TodoWrite tool:
-
-```javascript
-TodoWrite({
-  todos: [
-    {
-      content: "[P1] Fix SQL injection in users.py:42",
-      status: "in_progress",
-      activeForm: "Fixing SQL injection vulnerability",
-      priority: "P1",  // extended field
-      category: "security"  // extended field
-    },
-    {
-      content: "[P2] Add missing tests for auth",
-      status: "pending",
-      activeForm: "Adding auth tests",
-      priority: "P2",
-      category: "testing"
-    }
-  ]
-})
-```
-
-## Auto-Blocking Rules
-
-```yaml
-# .claude/vibe/config.yaml
-merge_blocking:
-  P1: true   # Block merge if P1 exists
-  P2: false  # Warning only
-  P3: false  # Ignore
-
-notifications:
-  P1: immediate  # Immediate notification
-  P2: daily      # Daily summary
-  P3: weekly     # Weekly summary
-```
+- P1 exists → merge is **blocked**
+- P2 → warning only, recommended to resolve
+- P3 → no blocking, backlog
+- Weekly cleanup: review and archive completed items
 
-## Best Practices
+## Done Criteria (K4)
 
-1. **Handle P1 immediately**: Stop other work and fix
-2. **Handle P2 before PR**: Recommended to resolve before merge
-3. **P3 is backlog**: Handle when time permits
-4. **Regular cleanup**: Review todos weekly
-5. **Document completions**: Document how issues were resolved
+- [ ] All P1 items resolved before merge
+- [ ] P2 items reviewed and either resolved or documented
+- [ ] index.md reflects current state
+- [ ] Completed items archived to `done/` directory