@su-record/vibe 2.7.18 → 2.7.20

package/skills/commit-push-pr/SKILL.md

@@ -1,75 +1,75 @@
----
-name: commit-push-pr
-description: "Commit, push, and create PR in one go. Auto-activates on commit, PR, push keywords."
-triggers: [commit, push, PR, pull request, merge]
-priority: 70
----
-
-# Commit-Push-PR
-
-## Pre-checks
-
-```bash
-git status            # What's changed
-git diff --stat       # Review changes
-git log --oneline -5  # Recent commits for style
-```
-
-## Workflow
-
-1. Review and stage changed files
-2. Write commit message (Conventional Commits)
-3. Push to remote branch
-4. Create PR with `gh pr create`
-
-## Commit Message Format
-
-```
-[type] title (under 50 chars)
-
-body (optional, 72 char wrap)
-
-Co-Authored-By: Claude <noreply@anthropic.com>
-```
-
-Types: `feat` | `fix` | `docs` | `style` | `refactor` | `test` | `chore` | `perf`
-
-## Security Checks (CRITICAL)
-
-```bash
-# Before committing — detect sensitive files
-git diff --cached --name-only | grep -E '\.(env|pem|key)$|credentials|secret'
-```
-
-**Never commit:** `.env`, `.env.local`, `*.pem`, `*.key`, `credentials.json`, `service-account.json`
-
-> If sensitive files are staged, **immediately warn and abort**.
-
-## Branch Protection
-
-- **No direct commits/pushes to main/master**
-- If on main: create a new branch first
-- **Never** `--force` push to main/master
-
-## PR Format
-
-```bash
-gh pr create \
-  --title "[type] title" \
-  --body "## Changes
-- Key changes
-
-## Related Issues
-- Closes #issue-number
-
-## Testing
-- Test methods and results"
-```
-
-## Done Criteria (K4)
-
-- [ ] No sensitive files in commit
-- [ ] Commit message follows Conventional Commits
-- [ ] Co-Authored-By line included
-- [ ] Not pushing directly to main/master
-- [ ] PR created with clear description
+---
+name: commit-push-pr
+description: "Commit, push, and create PR in one go. Auto-activates on commit, PR, push keywords."
+triggers: [commit, push, PR, pull request, merge]
+priority: 70
+---
+
+# Commit-Push-PR
+
+## Pre-checks
+
+```bash
+git status            # What's changed
+git diff --stat       # Review changes
+git log --oneline -5  # Recent commits for style
+```
+
+## Workflow
+
+1. Review and stage changed files
+2. Write commit message (Conventional Commits)
+3. Push to remote branch
+4. Create PR with `gh pr create`
+
+## Commit Message Format
+
+```
+[type] title (under 50 chars)
+
+body (optional, 72 char wrap)
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+```
+
+Types: `feat` | `fix` | `docs` | `style` | `refactor` | `test` | `chore` | `perf`
+
+## Security Checks (CRITICAL)
+
+```bash
+# Before committing — detect sensitive files
+git diff --cached --name-only | grep -E '\.(env|pem|key)$|credentials|secret'
+```
+
+**Never commit:** `.env`, `.env.local`, `*.pem`, `*.key`, `credentials.json`, `service-account.json`
+
+> If sensitive files are staged, **immediately warn and abort**.
+
+## Branch Protection
+
+- **No direct commits/pushes to main/master**
+- If on main: create a new branch first
+- **Never** `--force` push to main/master
+
+## PR Format
+
+```bash
+gh pr create \
+  --title "[type] title" \
+  --body "## Changes
+- Key changes
+
+## Related Issues
+- Closes #issue-number
+
+## Testing
+- Test methods and results"
+```
+
+## Done Criteria (K4)
+
+- [ ] No sensitive files in commit
+- [ ] Commit message follows Conventional Commits
+- [ ] Co-Authored-By line included
+- [ ] Not pushing directly to main/master
+- [ ] PR created with clear description

package/skills/context7-usage/SKILL.md

@@ -1,105 +1,105 @@
----
-name: context7-usage
-description: "Context7 plugin for latest library documentation. Auto-activates when docs, documentation, latest version, official docs, API reference, or library help is needed."
-triggers: [docs, documentation, latest version, official docs, API reference, library help, context7]
-priority: 60
----
-
-# Context7 Usage
-
-Guide for searching latest library/framework documentation using Context7 plugin with subagent isolation.
-
-## Why Subagent Approach?
-
-| Approach | Problem |
-|----------|---------|
-| Direct plugin call | Docs content fills main context, causing bloat |
-| Subagent isolation | Docs queried in separate context, only results returned |
-
-**Benefits:**
-
-- Prevents context bloat during long coding sessions
-- Solves knowledge cutoff problem with latest docs
-- Main context stays focused on implementation
-
-## When to Use
-
-| Situation | Example |
-|-----------|---------|
-| Latest API check | "React 19 use() hook usage" |
-| Version differences | "Next.js 15 changes" |
-| Official docs needed | "Prisma schema syntax" |
-| Migration guide | "Vue 2 → Vue 3 migration" |
-
-## How It Works
-
-```
-User asks library question
-    ↓
-Skill detects docs need
-    ↓
-Spawn docs-researcher subagent (haiku)
-    ↓
-Subagent calls context7 in isolated context
-    ↓
-Returns only relevant info to main context
-```
-
-## Usage
-
-### Automatic (Recommended)
-
-Just ask library/API questions naturally:
-
-```
-"How do I use React 19 use() hook?"
-"What's new in Next.js 15?"
-"Prisma many-to-many relation syntax"
-```
-
-The skill auto-detects and spawns a docs-researcher subagent.
-
-### Manual Command
-
-```
-/context7:docs <library> [query]
-```
-
-Examples:
-
-```
-/context7:docs react hooks
-/context7:docs next.js app router
-/context7:docs prisma relations
-```
-
-## Implementation Pattern
-
-When you detect a library/API documentation need, spawn a subagent:
-
-```
-Task tool call:
-- subagent_type: Explore
-- model: haiku
-- prompt: "Use context7 to find [library] documentation about [topic]. Return only the relevant API usage examples and key points."
-```
-
-The subagent handles the context7 calls and returns a summary, keeping main context clean.
-
-## Fallback Chain
-
-```
-context7 plugin not installed
-    ↓
-Prompt user: /plugin install context7
-    ↓
-If still unavailable: Web Search for official docs
-```
-
-## Installation
-
-If context7 is not installed, guide user:
-
-```bash
-/plugin install context7
-```
+---
+name: context7-usage
+description: "Context7 plugin for latest library documentation. Auto-activates when docs, documentation, latest version, official docs, API reference, or library help is needed."
+triggers: [docs, documentation, latest version, official docs, API reference, library help, context7]
+priority: 60
+---
+
+# Context7 Usage
+
+Guide for searching latest library/framework documentation using Context7 plugin with subagent isolation.
+
+## Why Subagent Approach?
+
+| Approach | Problem |
+|----------|---------|
+| Direct plugin call | Docs content fills main context, causing bloat |
+| Subagent isolation | Docs queried in separate context, only results returned |
+
+**Benefits:**
+
+- Prevents context bloat during long coding sessions
+- Solves knowledge cutoff problem with latest docs
+- Main context stays focused on implementation
+
+## When to Use
+
+| Situation | Example |
+|-----------|---------|
+| Latest API check | "React 19 use() hook usage" |
+| Version differences | "Next.js 15 changes" |
+| Official docs needed | "Prisma schema syntax" |
+| Migration guide | "Vue 2 → Vue 3 migration" |
+
+## How It Works
+
+```
+User asks library question
+    ↓
+Skill detects docs need
+    ↓
+Spawn docs-researcher subagent (haiku)
+    ↓
+Subagent calls context7 in isolated context
+    ↓
+Returns only relevant info to main context
+```
+
+## Usage
+
+### Automatic (Recommended)
+
+Just ask library/API questions naturally:
+
+```
+"How do I use React 19 use() hook?"
+"What's new in Next.js 15?"
+"Prisma many-to-many relation syntax"
+```
+
+The skill auto-detects and spawns a docs-researcher subagent.
+
+### Manual Command
+
+```
+/context7:docs <library> [query]
+```
+
+Examples:
+
+```
+/context7:docs react hooks
+/context7:docs next.js app router
+/context7:docs prisma relations
+```
+
+## Implementation Pattern
+
+When you detect a library/API documentation need, spawn a subagent:
+
+```
+Task tool call:
+- subagent_type: Explore
+- model: haiku
+- prompt: "Use context7 to find [library] documentation about [topic]. Return only the relevant API usage examples and key points."
+```
+
+The subagent handles the context7 calls and returns a summary, keeping main context clean.
+
+## Fallback Chain
+
+```
+context7 plugin not installed
+    ↓
+Prompt user: /plugin install context7
+    ↓
+If still unavailable: Web Search for official docs
+```
+
+## Installation
+
+If context7 is not installed, guide user:
+
+```bash
+/plugin install context7
+```

package/skills/core-capabilities/SKILL.md

@@ -1,13 +1,13 @@
----
-name: core-capabilities
-description: "DEPRECATED — content covered by CLAUDE.md. Context thresholds and workflow guidance are in CLAUDE.md."
----
-
-# Core Capabilities (Deprecated)
-
-This skill's content is covered by CLAUDE.md:
-- Workflow: `/vibe.spec` → `/vibe.run` → `/vibe.trace` → review → Done
-- Context thresholds: 70% checkpoint, 80% warning, 90% critical
-- Magic keywords: `ultrawork`, `ralph`, `ralplan`, `verify`, `quick`
-
-Refer to CLAUDE.md directly for all framework capabilities.
+---
+name: core-capabilities
+description: "DEPRECATED — content covered by CLAUDE.md. Context thresholds and workflow guidance are in CLAUDE.md."
+---
+
+# Core Capabilities (Deprecated)
+
+This skill's content is covered by CLAUDE.md:
+- Workflow: `/vibe.spec` → `/vibe.run` → `/vibe.trace` → review → Done
+- Context thresholds: 70% checkpoint, 80% warning, 90% critical
+- Magic keywords: `ultrawork`, `ralph`, `ralplan`, `verify`, `quick`
+
+Refer to CLAUDE.md directly for all framework capabilities.

package/skills/e2e-commerce/SKILL.md

@@ -1,61 +1,61 @@
----
-name: e2e-commerce
-description: "E2E test scenarios for commerce checkout and payment flows"
-triggers: [e2e commerce, checkout test, payment test, order flow test]
-priority: 65
----
-
-# E2E Commerce Test Scenarios
-
-## Pre-check (K1)
-
-> Are you testing a checkout/payment/order flow? If testing simple CRUD or non-transactional features, standard E2E patterns suffice — this skill is not needed.
-
-## Must-Test Scenarios
-
-### P0 — Blocks Deployment
-
-| Scenario | What to Verify | Gotcha |
-|----------|---------------|--------|
-| **Happy path checkout** | Cart → Shipping → Payment → Order confirmation | Verify order status text, not just URL change |
-| **Payment failure** | Error message shown, stock released | Check stock is RELEASED after failure, not just error displayed |
-| **Duplicate payment** | Only 1 order created on double-click | `Promise.all([click(), click()])` then verify order count via API |
-| **Out of stock** | Blocks checkout with clear message | Simulate stock depletion mid-checkout via test API |
-
-### P1 — Should Pass
-
-| Scenario | What to Verify | Gotcha |
-|----------|---------------|--------|
-| **Coupon calculation** | Discount amount and total correct | Test percentage AND fixed amount coupons separately |
-| **Webhook resilience** | Order completes even with delayed webhook | Configure 5s delay, verify processing→complete transition |
-| **Cart merge on login** | Guest cart merged into user cart | User cart takes priority for duplicate items |
-| **Partial refund** | Refunded amount correct, order updated | Verify remaining amount, not just refund event |
-
-### P2 — Nice to Have
-
-| Scenario | What to Verify |
-|----------|---------------|
-| Multiple payment methods | Each method completes checkout |
-| Guest checkout | Full flow without login |
-| Order cancellation | Refund triggered, stock restored |
-
-## Test Environment Gotchas
-
-| Gotcha | Fix |
-|--------|-----|
-| Using real PG sandbox in CI | Use MSW (`setupServer`) for mock PG responses |
-| Flaky tests from timing | Use `waitForSelector`/`waitForURL`, never `sleep` |
-| Test data leaks between tests | Seed in `beforeAll`, clean in `afterAll` |
-| Hardcoded test card numbers | Document: `4000000000000002` = decline |
-
-## Related
-
-See `commerce-patterns` skill for implementation gotchas (idempotency, atomic stock, payment state machine) that these tests verify.
-
-## Done Criteria (K4)
-
-- [ ] All P0 scenarios pass in CI
-- [ ] P1 scenarios written and tracked
-- [ ] Test data seeded/cleaned per suite
-- [ ] No flaky tests (no arbitrary waits)
-- [ ] Mock PG server configured for CI
+---
+name: e2e-commerce
+description: "E2E test scenarios for commerce checkout and payment flows"
+triggers: [e2e commerce, checkout test, payment test, order flow test]
+priority: 65
+---
+
+# E2E Commerce Test Scenarios
+
+## Pre-check (K1)
+
+> Are you testing a checkout/payment/order flow? If testing simple CRUD or non-transactional features, standard E2E patterns suffice — this skill is not needed.
+
+## Must-Test Scenarios
+
+### P0 — Blocks Deployment
+
+| Scenario | What to Verify | Gotcha |
+|----------|---------------|--------|
+| **Happy path checkout** | Cart → Shipping → Payment → Order confirmation | Verify order status text, not just URL change |
+| **Payment failure** | Error message shown, stock released | Check stock is RELEASED after failure, not just error displayed |
+| **Duplicate payment** | Only 1 order created on double-click | `Promise.all([click(), click()])` then verify order count via API |
+| **Out of stock** | Blocks checkout with clear message | Simulate stock depletion mid-checkout via test API |
+
+### P1 — Should Pass
+
+| Scenario | What to Verify | Gotcha |
+|----------|---------------|--------|
+| **Coupon calculation** | Discount amount and total correct | Test percentage AND fixed amount coupons separately |
+| **Webhook resilience** | Order completes even with delayed webhook | Configure 5s delay, verify processing→complete transition |
+| **Cart merge on login** | Guest cart merged into user cart | User cart takes priority for duplicate items |
+| **Partial refund** | Refunded amount correct, order updated | Verify remaining amount, not just refund event |
+
+### P2 — Nice to Have
+
+| Scenario | What to Verify |
+|----------|---------------|
+| Multiple payment methods | Each method completes checkout |
+| Guest checkout | Full flow without login |
+| Order cancellation | Refund triggered, stock restored |
+
+## Test Environment Gotchas
+
+| Gotcha | Fix |
+|--------|-----|
+| Using real PG sandbox in CI | Use MSW (`setupServer`) for mock PG responses |
+| Flaky tests from timing | Use `waitForSelector`/`waitForURL`, never `sleep` |
+| Test data leaks between tests | Seed in `beforeAll`, clean in `afterAll` |
+| Hardcoded test card numbers | Document: `4000000000000002` = decline |
+
+## Related
+
+See `commerce-patterns` skill for implementation gotchas (idempotency, atomic stock, payment state machine) that these tests verify.
+
+## Done Criteria (K4)
+
+- [ ] All P0 scenarios pass in CI
+- [ ] P1 scenarios written and tracked
+- [ ] Test data seeded/cleaned per suite
+- [ ] No flaky tests (no arbitrary waits)
+- [ ] Mock PG server configured for CI

package/skills/event-comms/SKILL.md

@@ -0,0 +1,161 @@
+---
+name: event-comms
+description: "Event communication automation — SMS via Aligo, email via Gmail OAuth, SNS posts for LinkedIn/Threads. Handles templates, BCC rules, and confirmation protocol."
+triggers: [sms, aligo, gmail, event email, event sms, 문자 발송, 메일 발송, SNS 홍보]
+priority: 65
+---
+# Event Communications
+
+SMS, email, and SNS content generation for community events.
+
+## SMS (Aligo API)
+
+### Rules
+- Auto-switch to LMS when >90 bytes
+- Use `%고객명%` substitution
+- Always test with `testmode_yn=Y` first
+- **Emoji strictly forbidden** (EUC-KR encoding)
+
+### SMS Types
+
+| Timing | Type | Content |
+|--------|------|---------|
+| D-7~D-3 | Notification LMS | Event name, datetime, venue, fee, registration URL |
+| D-3 | Confirmation SMS | Attendance confirmed + detailed venue |
+| D-1 | Reminder SMS | Tomorrow schedule reminder + venue |
+| D-Day | Day-of SMS | Today schedule reminder |
+
+### Templates
+
+**Notification LMS (D-7~D-3)**
+```
+%고객명%님 안녕하세요.
+
+{event_name} {edition}회 안내드립니다.
+
+일시: {date} {time}
+장소: {venue}
+참가비: {fee}
+
+신청: {url}
+
+{community_name}
+```
+
+**Confirmation SMS (D-3)**
+```
+%고객명%님, {event_name} 참가가 확정되었습니다.
+
+일시: {date} {time}
+장소: {venue_detail}
+
+당일 뵙겠습니다.
+```
+
+**Reminder SMS (D-1)**
+```
+%고객명%님, 내일 {event_name}이 있습니다.
+
+일시: {date} {time}
+장소: {venue}
+
+내일 뵙겠습니다!
+```
+
+**Day-of SMS (D-Day)**
+```
+%고객명%님, 오늘 {time} {event_name}입니다.
+
+장소: {venue}
+
+오늘 뵙겠습니다!
+```
+
+## Email (Gmail OAuth 2.0)
+
+### Rules
+- **MUST use BCC** — never expose attendee emails to each other
+- D-3 confirmation email includes: venue details, timetable, Slido link
+
+### Confirmation Email Template (D-3)
+```
+Subject: [{event_name}] 참가 확정 안내
+
+{attendee_name}님 안녕하세요.
+
+{event_name} {edition}회 참가가 확정되었습니다.
+
+■ 일시: {date} {time}
+■ 장소: {venue_detail}
+■ 프로그램:
+{timetable}
+
+■ 실시간 질문: {slido_link}
+
+당일 뵙겠습니다.
+감사합니다.
+
+{community_name}
+```
+
+## SNS Posts
+
+### Platform Tone
+
+| Platform | Tone | Length | Style |
+|----------|------|--------|-------|
+| LinkedIn | Professional, formal | 300+ chars | Expert participation encouragement |
+| Threads | Casual, hooking | 150-200 chars | "아직 안 봤어?" style |
+
+### Post Types
+
+| Timing | Type | Content |
+|--------|------|---------|
+| Open | Promo post | Event intro + CTA |
+| D-14 | Deadline remind | Urgency + remaining spots |
+| D+1 | Review post | Story → 3 insights → next event preview |
+
+### LinkedIn Promo Template
+```
+{hook_sentence}
+
+{event_name} {edition}회를 소개합니다.
+
+📅 {date} {time}
+📍 {venue}
+
+이번 주제: {topic}
+
+{speaker_intro}
+
+{cta}
+```
+
+### Threads Promo Template
+```
+{hook_casual}
+
+{event_name} {edition}회 열린다!
+
+{date} {time}
+{venue_short}
+
+{topic_casual}
+
+{cta_casual}
+```
+
+### Review Post Structure
+1. Story (emotional hook)
+2. Key insights (3 items)
+3. Next event preview
+4. Thank you + community link
+
+## API Keys Required
+
+| Key | Service | Required |
+|-----|---------|----------|
+| `ALIGO_API_KEY` | Aligo SMS | ✅ (for send) |
+| `ALIGO_USER_ID` | Aligo SMS | ✅ (for send) |
+| `ALIGO_SENDER` | Aligo SMS | ✅ (for send) |
+| `GMAIL_CREDENTIALS_PATH` | Gmail OAuth | ✅ (for email) |