@su-record/vibe 2.7.12 → 2.7.13

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`

package/skills/parallel-research/SKILL.md

@@ -1,87 +1,87 @@
----
-name: parallel-research
-description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
-triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
-priority: 60
----
-# Parallel Research
-
-Parallel research patterns for solving complex problems.
-
-## When Parallel Research is Needed
-
-| Situation | Reason |
-|-----------|--------|
-| New technology adoption | Need best practices |
-| Security-related features | Multi-angle review needed |
-| Architecture design | Multiple perspectives needed |
-| Technology selection | Comparison analysis needed |
-| Complex bugs | Explore multiple causes |
-
-## Research Agents (4 Parallel)
-
-| Agent | Role | Tools |
-|-------|------|-------|
-| best-practices | Search best practices | Web Search, context7 |
-| framework-docs | Search official docs | context7 |
-| codebase-patterns | Analyze existing code patterns | Grep, Glob |
-| security-advisory | Search security advisories | Web Search |
-
-## Usage Methods
-
-### Method 1: Direct Orchestrator Call
-
-```bash
-node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').then(o =>
-  o.research('passkey authentication', ['React', 'Supabase'])
-  .then(r => console.log(r.content[0].text))
-)"
-```
-
-### Method 2: Use /vibe.spec
-
-```
-/vibe.spec "feature-name"
-→ Parallel research runs automatically after requirements confirmed
-```
-
-### Method 3: Parallel Task Tool Execution
-
-```
-Task 1: "Search React auth best practices"
-Task 2: "Search Supabase Auth official docs" (concurrent)
-Task 3: "Analyze existing auth code patterns" (concurrent)
-Task 4: "Search auth security vulnerabilities" (concurrent)
-```
-
-## Using Research Results
-
-```
-Parallel research complete
-    ↓
-Synthesize results
-    ↓
-Reflect in SPEC Context section
-OR
-Reference during implementation
-```
-
-## When Research is NOT Needed
-
-- Simple CRUD operations
-- Already familiar patterns
-- Similar code exists in project
-- Time-critical (supplement with review later)
-
-## Notes
-
-- 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
+---
+name: parallel-research
+description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
+triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
+priority: 60
+---
+# Parallel Research
+
+Parallel research patterns for solving complex problems.
+
+## When Parallel Research is Needed
+
+| Situation | Reason |
+|-----------|--------|
+| New technology adoption | Need best practices |
+| Security-related features | Multi-angle review needed |
+| Architecture design | Multiple perspectives needed |
+| Technology selection | Comparison analysis needed |
+| Complex bugs | Explore multiple causes |
+
+## Research Agents (4 Parallel)
+
+| Agent | Role | Tools |
+|-------|------|-------|
+| best-practices | Search best practices | Web Search, context7 |
+| framework-docs | Search official docs | context7 |
+| codebase-patterns | Analyze existing code patterns | Grep, Glob |
+| security-advisory | Search security advisories | Web Search |
+
+## Usage Methods
+
+### Method 1: Direct Orchestrator Call
+
+```bash
+node -e "import('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').then(o =>
+  o.research('passkey authentication', ['React', 'Supabase'])
+  .then(r => console.log(r.content[0].text))
+)"
+```
+
+### Method 2: Use /vibe.spec
+
+```
+/vibe.spec "feature-name"
+→ Parallel research runs automatically after requirements confirmed
+```
+
+### Method 3: Parallel Task Tool Execution
+
+```
+Task 1: "Search React auth best practices"
+Task 2: "Search Supabase Auth official docs" (concurrent)
+Task 3: "Analyze existing auth code patterns" (concurrent)
+Task 4: "Search auth security vulnerabilities" (concurrent)
+```
+
+## Using Research Results
+
+```
+Parallel research complete
+    ↓
+Synthesize results
+    ↓
+Reflect in SPEC Context section
+OR
+Reference during implementation
+```
+
+## When Research is NOT Needed
+
+- Simple CRUD operations
+- Already familiar patterns
+- Similar code exists in project
+- Time-critical (supplement with review later)
+
+## Notes
+
+- 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

@@ -1,63 +1,63 @@
----
-name: priority-todos
-description: "Priority-based TODO management (P1/P2/P3). Auto-activates when managing tasks, reviewing issues, or organizing work by priority."
-triggers: [todo, priority, P1, P2, P3, task management, issue, organize]
-priority: 60
----
-
-# Priority-Based Todo Management
-
-## Pre-check (K1)
-
-> 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 Definitions
-
-| 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
-
-```
-.claude/vibe/todos/
-├── P1-security-sql-injection.md
-├── P2-perf-n1-query.md
-├── P3-style-extract-helper.md
-├── index.md                      # Summary table with counts/status
-└── done/                         # Archived completed items
-```
-
-## Workflow
-
-```
-/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
-```
-
-## Todo File Format
-
-Each file follows: `# [P1] Title` → Summary → Priority Justification → Location (file:line) → Suggested Fix → Checklist (fix, test, review, merge).
-
-## Rules
-
-- P1 exists → merge is **blocked**
-- P2 → warning only, recommended to resolve
-- P3 → no blocking, backlog
-- Weekly cleanup: review and archive completed items
-
-## Done Criteria (K4)
-
-- [ ] 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
+---
+name: priority-todos
+description: "Priority-based TODO management (P1/P2/P3). Auto-activates when managing tasks, reviewing issues, or organizing work by priority."
+triggers: [todo, priority, P1, P2, P3, task management, issue, organize]
+priority: 60
+---
+
+# Priority-Based Todo Management
+
+## Pre-check (K1)
+
+> 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 Definitions
+
+| 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
+
+```
+.claude/vibe/todos/
+├── P1-security-sql-injection.md
+├── P2-perf-n1-query.md
+├── P3-style-extract-helper.md
+├── index.md                      # Summary table with counts/status
+└── done/                         # Archived completed items
+```
+
+## Workflow
+
+```
+/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
+```
+
+## Todo File Format
+
+Each file follows: `# [P1] Title` → Summary → Priority Justification → Location (file:line) → Suggested Fix → Checklist (fix, test, review, merge).
+
+## Rules
+
+- P1 exists → merge is **blocked**
+- P2 → warning only, recommended to resolve
+- P3 → no blocking, backlog
+- Weekly cleanup: review and archive completed items
+
+## Done Criteria (K4)
+
+- [ ] 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

package/skills/seo-checklist/SKILL.md

@@ -1,57 +1,57 @@
----
-name: seo-checklist
-description: "SEO gotchas for web development - easy-to-miss items that hurt search ranking"
-triggers: [seo, search, meta, sitemap, schema, structured data, og, opengraph, google, naver]
-priority: 65
----
-
-# SEO Checklist
-
-## Pre-check (K1)
-
-> Is this a public-facing web page that needs search visibility? Internal tools, admin panels, and authenticated-only pages don't need SEO optimization.
-
-## Easy-to-Miss Gotchas
-
-### Meta & Social
-
-| Gotcha | Why It Hurts | Fix |
-|--------|-------------|-----|
-| Missing `<link rel="canonical">` | Duplicate content penalty from URL variants | Set canonical on every page, including paginated |
-| OG image wrong size | Cropped/pixelated on social share | Must be exactly **1200x630px** |
-| Same title/description on all pages | Google treats as duplicate content | Unique title (50-60 chars) + description (150-160 chars) per page |
-| Missing `og:type` | Defaults to "website" for articles | Set `article` for posts, `product` for products |
-
-### Technical
-
-| Gotcha | Why It Hurts | Fix |
-|--------|-------------|-----|
-| `robots.txt` blocks important pages | Pages not indexed | `Allow: /` for public, only block `/api/`, `/admin/` |
-| No sitemap or stale sitemap | Crawler misses new pages | Auto-generate, include `<lastmod>` with real dates |
-| `noindex` left in production | Entire site invisible | Verify `<meta name="robots">` in production build |
-| Images without `width`/`height` | CLS layout shift penalty | Always set dimensions + `loading="lazy"` for below-fold |
-
-### Core Web Vitals
-
-| Metric | Target | Common Miss |
-|--------|--------|-------------|
-| LCP | ≤2.5s | Hero image not preloaded — add `<link rel="preload">` |
-| INP | ≤200ms | Heavy JS on interaction — defer non-critical scripts |
-| CLS | ≤0.1 | Dynamic content without reserved space — set `min-height` |
-
-### Structured Data
-
-| Gotcha | Fix |
-|--------|-----|
-| JSON-LD not validated | Test with Google Rich Results Test before deploy |
-| Wrong `@type` | `Product` for products, `Article` for posts, `FAQPage` for FAQs |
-| Missing `BreadcrumbList` | Add breadcrumb schema for all non-root pages |
-
-## Done Criteria (K4)
-
-- [ ] Every page has unique title, description, canonical URL
-- [ ] OG images are 1200x630px on all shareable pages
-- [ ] `robots.txt` and `sitemap.xml` present and correct
-- [ ] Structured data validates in Rich Results Test
-- [ ] Core Web Vitals green (LCP ≤2.5s, INP ≤200ms, CLS ≤0.1)
-- [ ] No `noindex` tags in production
+---
+name: seo-checklist
+description: "SEO gotchas for web development - easy-to-miss items that hurt search ranking"
+triggers: [seo, search, meta, sitemap, schema, structured data, og, opengraph, google, naver]
+priority: 65
+---
+
+# SEO Checklist
+
+## Pre-check (K1)
+
+> Is this a public-facing web page that needs search visibility? Internal tools, admin panels, and authenticated-only pages don't need SEO optimization.
+
+## Easy-to-Miss Gotchas
+
+### Meta & Social
+
+| Gotcha | Why It Hurts | Fix |
+|--------|-------------|-----|
+| Missing `<link rel="canonical">` | Duplicate content penalty from URL variants | Set canonical on every page, including paginated |
+| OG image wrong size | Cropped/pixelated on social share | Must be exactly **1200x630px** |
+| Same title/description on all pages | Google treats as duplicate content | Unique title (50-60 chars) + description (150-160 chars) per page |
+| Missing `og:type` | Defaults to "website" for articles | Set `article` for posts, `product` for products |
+
+### Technical
+
+| Gotcha | Why It Hurts | Fix |
+|--------|-------------|-----|
+| `robots.txt` blocks important pages | Pages not indexed | `Allow: /` for public, only block `/api/`, `/admin/` |
+| No sitemap or stale sitemap | Crawler misses new pages | Auto-generate, include `<lastmod>` with real dates |
+| `noindex` left in production | Entire site invisible | Verify `<meta name="robots">` in production build |
+| Images without `width`/`height` | CLS layout shift penalty | Always set dimensions + `loading="lazy"` for below-fold |
+
+### Core Web Vitals
+
+| Metric | Target | Common Miss |
+|--------|--------|-------------|
+| LCP | ≤2.5s | Hero image not preloaded — add `<link rel="preload">` |
+| INP | ≤200ms | Heavy JS on interaction — defer non-critical scripts |
+| CLS | ≤0.1 | Dynamic content without reserved space — set `min-height` |
+
+### Structured Data
+
+| Gotcha | Fix |
+|--------|-----|
+| JSON-LD not validated | Test with Google Rich Results Test before deploy |
+| Wrong `@type` | `Product` for products, `Article` for posts, `FAQPage` for FAQs |
+| Missing `BreadcrumbList` | Add breadcrumb schema for all non-root pages |
+
+## Done Criteria (K4)
+
+- [ ] Every page has unique title, description, canonical URL
+- [ ] OG images are 1200x630px on all shareable pages
+- [ ] `robots.txt` and `sitemap.xml` present and correct
+- [ ] Structured data validates in Rich Results Test
+- [ ] Core Web Vitals green (LCP ≤2.5s, INP ≤200ms, CLS ≤0.1)
+- [ ] No `noindex` tags in production