@su-record/vibe 2.7.10 → 2.7.11

package/skills/frontend-design/SKILL.md

@@ -1,73 +1,73 @@
----
-name: frontend-design
-description: "Production-grade frontend with bold aesthetic direction for UI-focused projects"
-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 from scratch
-- User-facing features where aesthetics matter
-
-## Core Principles
-
-### 1. Typography
-- Choose distinctive typefaces that set the tone
-- Establish clear hierarchy through size, weight, and spacing
-- Consider custom fonts that reflect brand personality
-
-### 2. Color & Theme
-- Develop unique color palettes beyond defaults
-- Consider dark/light mode with intentional contrast
-- Use color purposefully for hierarchy and emphasis
-
-### 3. Motion & Animation
-- Add meaningful micro-interactions
-- Use motion to guide user attention
-- Implement smooth transitions between states
-
-### 4. Composition & Layout
-- Create visual rhythm through spacing
-- Use asymmetry and unconventional layouts when appropriate
-- Balance density with breathing room
-
-### 5. Visual Details
-- Custom icons and illustrations
-- Thoughtful shadows and depth
-- Refined borders, corners, and surfaces
-
-## Anti-Patterns to Avoid
-
-- Generic Bootstrap/Tailwind defaults without customization
-- Overused fonts (Inter, Roboto without styling)
-- Predictable card-based layouts everywhere
-- Stock photography without curation
-- Safe, corporate color palettes
-
-## Quality Checklist
-
-- [ ] Typography creates clear hierarchy
-- [ ] Color palette is distinctive and accessible
-- [ ] Animations are smooth (60fps)
-- [ ] Layout works across breakpoints
-- [ ] Empty/loading/error states are designed
-- [ ] Dark mode (if applicable) is intentional
-- [ ] Micro-interactions provide feedback
-
-## Done Criteria (K4)
-
-- [ ] 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)
+---
+name: frontend-design
+description: "Production-grade frontend with bold aesthetic direction for UI-focused projects"
+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 from scratch
+- User-facing features where aesthetics matter
+
+## Core Principles
+
+### 1. Typography
+- Choose distinctive typefaces that set the tone
+- Establish clear hierarchy through size, weight, and spacing
+- Consider custom fonts that reflect brand personality
+
+### 2. Color & Theme
+- Develop unique color palettes beyond defaults
+- Consider dark/light mode with intentional contrast
+- Use color purposefully for hierarchy and emphasis
+
+### 3. Motion & Animation
+- Add meaningful micro-interactions
+- Use motion to guide user attention
+- Implement smooth transitions between states
+
+### 4. Composition & Layout
+- Create visual rhythm through spacing
+- Use asymmetry and unconventional layouts when appropriate
+- Balance density with breathing room
+
+### 5. Visual Details
+- Custom icons and illustrations
+- Thoughtful shadows and depth
+- Refined borders, corners, and surfaces
+
+## Anti-Patterns to Avoid
+
+- Generic Bootstrap/Tailwind defaults without customization
+- Overused fonts (Inter, Roboto without styling)
+- Predictable card-based layouts everywhere
+- Stock photography without curation
+- Safe, corporate color palettes
+
+## Quality Checklist
+
+- [ ] Typography creates clear hierarchy
+- [ ] Color palette is distinctive and accessible
+- [ ] Animations are smooth (60fps)
+- [ ] Layout works across breakpoints
+- [ ] Empty/loading/error states are designed
+- [ ] Dark mode (if applicable) is intentional
+- [ ] Micro-interactions provide feedback
+
+## Done Criteria (K4)
+
+- [ ] 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

@@ -1,72 +1,72 @@
----
-name: git-worktree
-description: "Git Worktree for parallel branch work. Auto-activates for PR review, hotfix, parallel testing, or working on multiple branches simultaneously."
-triggers: [worktree, PR review, hotfix, parallel branch, multiple branches]
-priority: 50
----
-
-# Git Worktree
-
-## Pre-check (K1)
-
-> Do you need to work on another branch without losing current work? If you can just `git stash` and switch, worktree may be overkill.
-
-## Core Commands
-
-```bash
-# Create worktree for PR review
-git worktree add ../review-{pr_number} origin/pr/{pr_number}
-
-# Create worktree with new branch (hotfix)
-git worktree add -b hotfix/urgent ../hotfix main
-
-# List all worktrees
-git worktree list
-
-# Remove when done
-git worktree remove ../review-{pr_number}
-
-# Clean up stale entries
-git worktree prune
-```
-
-## PR Review Workflow
-
-```
-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
-
-```
-1. git worktree add -b hotfix/critical ../hotfix main
-2. cd ../hotfix
-3. Fix bug → commit → push
-4. cd - && git worktree remove ../hotfix
-```
-
-## Naming Convention
-
-```bash
-../review-{pr_number}         # PR review
-../hotfix-{issue_number}      # Hotfix
-../experiment-{feature_name}  # Experiment
-```
-
-## Troubleshooting
-
-| 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` |
-
-## Done Criteria (K4)
-
-- [ ] Worktree created and work completed in isolation
-- [ ] Worktree removed after work is done
-- [ ] No stale worktrees left (`git worktree list` clean)
+---
+name: git-worktree
+description: "Git Worktree for parallel branch work. Auto-activates for PR review, hotfix, parallel testing, or working on multiple branches simultaneously."
+triggers: [worktree, PR review, hotfix, parallel branch, multiple branches]
+priority: 50
+---
+
+# Git Worktree
+
+## Pre-check (K1)
+
+> Do you need to work on another branch without losing current work? If you can just `git stash` and switch, worktree may be overkill.
+
+## Core Commands
+
+```bash
+# Create worktree for PR review
+git worktree add ../review-{pr_number} origin/pr/{pr_number}
+
+# Create worktree with new branch (hotfix)
+git worktree add -b hotfix/urgent ../hotfix main
+
+# List all worktrees
+git worktree list
+
+# Remove when done
+git worktree remove ../review-{pr_number}
+
+# Clean up stale entries
+git worktree prune
+```
+
+## PR Review Workflow
+
+```
+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
+
+```
+1. git worktree add -b hotfix/critical ../hotfix main
+2. cd ../hotfix
+3. Fix bug → commit → push
+4. cd - && git worktree remove ../hotfix
+```
+
+## Naming Convention
+
+```bash
+../review-{pr_number}         # PR review
+../hotfix-{issue_number}      # Hotfix
+../experiment-{feature_name}  # Experiment
+```
+
+## Troubleshooting
+
+| 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` |
+
+## Done Criteria (K4)
+
+- [ ] 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

@@ -1,109 +1,109 @@
----
-name: handoff
-description: "Generate HANDOFF.md work handover document before session end. Auto-activates on handoff, handover, session cleanup keywords."
-triggers: [handoff, handover, session cleanup, session end, context save]
-priority: 70
----
-
-# Handoff — Session Handover Document
-
-Record work status before session end so the next session can pick up immediately.
-
-## What is HANDOFF.md?
-
-A file that records the current work status before context reset. Reading this file in a new session allows immediate continuation.
-
-### Difference from `/vibe.utils --continue`
-
-| Item | `/vibe.utils --continue` | Handoff |
-|------|--------------------------|---------|
-| Method | Automatic session context restore | Manual handover document |
-| Includes | Memory + session state | Work progress + notes + file list |
-| When to use | At new session start | Before session end |
-| Purpose | Quick auto-restore | Detailed handover (team/future self) |
-
-## When to Use
-
-- When context reaches 80-100k tokens
-- After using `/compact` 3 times
-- Before pausing work for an extended period
-- When progress recording is needed during complex work
-
-## VIBE Tool Integration
-
-Use VIBE built-in tools to save current state before generating Handoff:
-
-```bash
-# Save current session context
-core_auto_save_context
-
-# Save important decisions to memory
-core_save_memory --key "handoff-decision" --value "Decided on JWT for auth" --category "project"
-
-# Verify saved memories
-core_list_memories --category "project"
-```
-
-## HANDOFF.md Template
-
-```markdown
-# Work Handover Document
-
-## Completed Tasks
-- [x] Completed task 1
-- [x] Completed task 2
-
-## In Progress
-- [ ] Currently working on
-  - Progress: 70%
-  - Next step: implement ~~
-
-## Next Tasks
-1. High priority task
-2. Next task
-
-## Notes & Cautions
-- Do not touch: ~~
-- Known bugs: ~~
-- Temporary workarounds: ~~
-
-## Related Files
-- src/components/Login.tsx — Login form
-- src/api/auth.ts — Auth API
-
-## Last State
-- Branch: feature/auth
-- Last commit: abc1234
-- Test status: passing
-```
-
-## Generation Steps
-
-1. Check current changed files with `git status`
-2. Check recent commits with `git log --oneline -5`
-3. Organize in-progress and remaining tasks
-4. Save session context with `core_auto_save_context`
-5. Save key decisions with `core_save_memory`
-6. Generate HANDOFF.md file
-
-## Restoring in New Session
-
-```
-Read HANDOFF.md and continue working
-```
-
-Or use alongside VIBE auto-restore:
-
-```
-/vibe.utils --continue
-```
-
-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`
+---
+name: handoff
+description: "Generate HANDOFF.md work handover document before session end. Auto-activates on handoff, handover, session cleanup keywords."
+triggers: [handoff, handover, session cleanup, session end, context save]
+priority: 70
+---
+
+# Handoff — Session Handover Document
+
+Record work status before session end so the next session can pick up immediately.
+
+## What is HANDOFF.md?
+
+A file that records the current work status before context reset. Reading this file in a new session allows immediate continuation.
+
+### Difference from `/vibe.utils --continue`
+
+| Item | `/vibe.utils --continue` | Handoff |
+|------|--------------------------|---------|
+| Method | Automatic session context restore | Manual handover document |
+| Includes | Memory + session state | Work progress + notes + file list |
+| When to use | At new session start | Before session end |
+| Purpose | Quick auto-restore | Detailed handover (team/future self) |
+
+## When to Use
+
+- When context reaches 80-100k tokens
+- After using `/compact` 3 times
+- Before pausing work for an extended period
+- When progress recording is needed during complex work
+
+## VIBE Tool Integration
+
+Use VIBE built-in tools to save current state before generating Handoff:
+
+```bash
+# Save current session context
+core_auto_save_context
+
+# Save important decisions to memory
+core_save_memory --key "handoff-decision" --value "Decided on JWT for auth" --category "project"
+
+# Verify saved memories
+core_list_memories --category "project"
+```
+
+## HANDOFF.md Template
+
+```markdown
+# Work Handover Document
+
+## Completed Tasks
+- [x] Completed task 1
+- [x] Completed task 2
+
+## In Progress
+- [ ] Currently working on
+  - Progress: 70%
+  - Next step: implement ~~
+
+## Next Tasks
+1. High priority task
+2. Next task
+
+## Notes & Cautions
+- Do not touch: ~~
+- Known bugs: ~~
+- Temporary workarounds: ~~
+
+## Related Files
+- src/components/Login.tsx — Login form
+- src/api/auth.ts — Auth API
+
+## Last State
+- Branch: feature/auth
+- Last commit: abc1234
+- Test status: passing
+```
+
+## Generation Steps
+
+1. Check current changed files with `git status`
+2. Check recent commits with `git log --oneline -5`
+3. Organize in-progress and remaining tasks
+4. Save session context with `core_auto_save_context`
+5. Save key decisions with `core_save_memory`
+6. Generate HANDOFF.md file
+
+## Restoring in New Session
+
+```
+Read HANDOFF.md and continue working
+```
+
+Or use alongside VIBE auto-restore:
+
+```
+/vibe.utils --continue
+```
+
+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`