@su-record/vibe 3.2.6 → 3.2.7

package/skills/vibe.event-comms/SKILL.md

@@ -1,173 +1,11 @@
 ---
 name: vibe.event-comms
+description: Use when event SMS, email, SNS, invitations, or review communications are requested; compatibility alias for vibe.event communications mode.
 invocation: [auto]
 tier: standard
-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: 60
+user-invocable: true
 ---
-# 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}] Attendance Confirmation
-
-Hello {attendee_name},
-
-Your attendance for {event_name} edition {edition} has been confirmed.
-
-■ Date & Time: {date} {time}
-■ Venue: {venue_detail}
-■ Program:
-{timetable}
-
-■ Live Q&A: {slido_link}
-
-We look forward to seeing you on the day.
-Thank you.
-
-{community_name}
-```
-
-## SNS Posts
-
-### Platform Tone
-
-| Platform | Tone | Length | Style |
-|----------|------|--------|-------|
-| LinkedIn | Professional, formal | 300+ chars | Expert participation encouragement |
-| Threads | Casual, hooking | 150-200 chars | "Haven't seen this yet?" 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}
-
-Introducing {event_name} edition {edition}.
-
-📅 {date} {time}
-📍 {venue}
-
-This session's topic: {topic}
-
-{speaker_intro}
-
-{cta}
-```
-
-### Threads Promo Template
-```
-{hook_casual}
-
-{event_name} edition {edition} is happening!
-
-{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
-
-## Error Recovery
-
-| Failure | Recovery |
-|---------|----------|
-| Aligo API timeout/error | Retry once after 5s. If still failing, output the SMS text as plain text for manual sending |
-| Aligo auth error | Prompt user to verify API key in `~/.vibe/config.json` |
-| Gmail auth expired | Prompt user to refresh the Gmail OAuth token |
-| Gmail quota exceeded | Save email as `.eml` file for manual sending later |
-| SNS post generation fails | Output post text as markdown for manual copy-paste |
-
-## 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) |
+Load `vibe.event` in communications mode and preserve all arguments.

package/skills/vibe.event-ops/SKILL.md

@@ -1,208 +1,11 @@
 ---
 name: vibe.event-ops
+description: Use when event nametags, checklists, slides, images, Slido, or settlement operations are requested; compatibility alias for vibe.event operations mode.
 invocation: [auto]
 tier: standard
-description: "Event operations — nametags, checklists, operational slides, Slido plans, image generation specs, settlement reports."
 triggers: [nametag, event checklist, event slide, slido, 이름표, 행사 체크리스트, 운영 슬라이드, 정산]
 priority: 60
+user-invocable: true
 ---
-# Event Operations
 
-Nametags, checklists, operational slides, Slido configuration, image generation, and settlement.
-
-## Nametags
-
-### Specs
-- Size: 85mm × 60mm
-- A4 layout: 8 per page (2 columns × 4 rows)
-- Layout: Company(9pt gray) / Role(9pt gray) / Name(18pt bold) / Brand(7pt bottom-right)
-- Output: HTML → browser A4 print
-- Data: webhook participant CSV, or blank template if unavailable
-
-### Community Brand
-
-| MDC | webinar | DWK |
-|-----|---------|-----|
-| 마케팅데이터커넥트 | (none) | DATA + WOMEN KOREA TUG |
-
-### HTML Template Structure
-```html
-<!DOCTYPE html>
-<html>
-<head>
-  <style>
-    @page { size: A4; margin: 10mm; }
-    .nametag-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 5mm; }
-    .nametag {
-      width: 85mm; height: 60mm;
-      border: 1px dashed #ccc;
-      padding: 8mm;
-      display: flex; flex-direction: column;
-      justify-content: center; position: relative;
-    }
-    .company { font-size: 9pt; color: #888; }
-    .role { font-size: 9pt; color: #888; }
-    .name { font-size: 18pt; font-weight: bold; margin: 4mm 0; }
-    .brand { font-size: 7pt; position: absolute; bottom: 3mm; right: 5mm; color: #aaa; }
-  </style>
-</head>
-<body>
-  <div class="nametag-grid">
-    <!-- Repeat for each participant -->
-    <div class="nametag">
-      <span class="company">{company}</span>
-      <span class="role">{role}</span>
-      <span class="name">{name}</span>
-      <span class="brand">{brand}</span>
-    </div>
-  </div>
-</body>
-</html>
-```
-
-## Checklist (D-1)
-
-Fixed 4 items for all offline events:
-
-```markdown
-## D-1 Checklist
-
-- [ ] Order water/snacks/meals
-- [ ] Print nametags
-- [ ] Prepare event operational slides
-- [ ] Set up screen/camera/tripod
-```
-
-## Operational Slides
-
-### Format
-- PPTX (16:9)
-- Generated with python-pptx
-- Community colors + timetable patterns
-
-### Slide Structure (5-7 slides)
-1. Cover (event name, topic, datetime, venue)
-2. Timetable (community-specific pattern)
-3~N. Speaker intro (1 slide per speaker)
-N+1. Q&A + Networking (Slido QR placeholder)
-N+2. Thank you + community links
-
-### Community Colors
-
-| MDC | webinar | DWK |
-|-----|---------|-----|
-| #ff6b35 (orange) | #a78bfa (purple) | #34d399 (mint) |
-
-### Timetable Patterns
-
-**MDC (3 speakers)**
-```
-19:00-19:10  Opening + Networking
-19:10-19:35  Session 1: {speaker1_name} — {topic1}
-19:35-20:00  Session 2: {speaker2_name} — {topic2}
-20:00-20:25  Session 3: {speaker3_name} — {topic3}
-20:25-20:40  Q&A + Slido
-20:40-21:00  Networking
-```
-
-**Webinar (1-2 speakers)**
-```
-19:30-19:35  Opening
-19:35-20:30  Session: {speaker_name} — {topic}
-20:30-20:50  Q&A
-20:50-21:00  Closing
-```
-
-**DWK (1-3 speakers + discussion)**
-```
-14:00-14:10  Opening + Icebreaker
-14:10-14:40  Session 1: {speaker1_name} — {topic1}
-14:40-15:10  Session 2: {speaker2_name} — {topic2}
-15:10-15:30  Break
-15:30-16:00  Discussion session
-16:00-16:30  Networking
-```
-
-## Slido Configuration
-
-API is read-only → Claude outputs plan → user manually configures.
-
-### Community Presets
-
-| Community | Items | Structure |
-|-----------|-------|-----------|
-| MDC | 5 | Icebreaker + Pre-Q&A + Balance game 2-3 + Satisfaction |
-| Webinar | 5 | Icebreaker + Skill check + Live Q&A + Word cloud + Feedback |
-| DWK | 10 | Icebreaker + Session feedback + Word cloud + Balance game 3 + Opinion poll 2 + Experience share + Feedback |
-
-## Image Generation
-
-### Model
-Antigravity image backend
-
-### Specs by Community
-
-| Community | Size | Purpose |
-|-----------|------|---------|
-| MDC | 500×500 | Listing thumbnail |
-| MDC | 595×842 | A4 poster |
-| Webinar | 1080×1080 | Instagram/Threads 1:1 |
-| Webinar | 1920×1080 | YouTube 16:9 |
-| Webinar | 1440×1080 | Zoom background 4:3 |
-| DWK | 2000×500 | Banner 4:1 |
-| DWK | 1080×1080 | SNS 1:1 |
-
-### Prompt Dual Structure
-- **API prompt**: No length limit, detailed (colors, layout, text position, logo placement)
-- **User prompt**: ≤400 chars summary → `output/images/{type}_prompt.txt`
-
-### Logo Auto-include
-- Source: `data/assets/common/images/{community} logo.png`
-- Auto-append: "Place logo naturally at bottom-left"
-
-### Smart Resizing
-- Same ratio → Pillow scale only (no API call)
-- Different ratio → Antigravity re-generate (pass original as reference, no white margins)
-
-## Settlement
-
-### MDC
-Revenue(attendance fees) - Expenses(venue, snacks, speaker gifts) = Markdown settlement report
-
-### DWK
-Stripe receipts + speaker gifts → Slack Workflow settlement message (future)
-
-### Webinar
-Free — no settlement needed
-
-## Intro Page Structure (Common)
-
-1. Hook sentence (2-3 lines)
-2. Event info (datetime/venue/fee)
-3. "Recommended for" (5 items)
-4. "What you'll learn" (5 items)
-5. Speaker intro (1 paragraph per speaker)
-6. Program timetable
-7. Attendance benefits
-8. CTA + quote
-
-## Speaker Research
-
-- Check past topic overlap → suggest 3 trend-based topics
-- Collect related post URLs from LinkedIn/Threads/X/Blog/Brunch/Publy
-- Use WebSearch tool (free)
-
-## Speaker Outreach
-
-- DM draft (short, 5-line version) + email draft (formal)
-- Auto-reference existing contact history (for re-outreach)
-- Business card image + LinkedIn URL → `data/speakers/{name}.json` accumulation
-
-## Error Recovery
-
-| Failure | Recovery |
-|---------|----------|
-| Antigravity image API unavailable | Skip image generation, use text-only placeholder slide with community colors |
-| Antigravity image quality too low | Retry with simplified prompt (remove detail, keep core subject) |
-| PPTX generation error | Output slide content as markdown with speaker notes for manual assembly |
-| Nametag HTML render issue | Simplify to basic table layout, remove custom fonts |
+Load `vibe.event` in operations mode and preserve all arguments.

package/skills/vibe.event-planning/SKILL.md

@@ -1,145 +1,11 @@
 ---
 name: vibe.event-planning
+description: Use when event timelines, speaker planning, outreach, or state management are requested; compatibility alias for vibe.event planning mode.
 invocation: [auto]
 tier: standard
-description: "Community event automation — D-Day timeline, community patterns, proactive task execution. Auto-activates for event planning, meetup/webinar/conference management."
 triggers: [event planning, meetup, webinar, conference, 행사, 밋업, 웨비나, D-Day, 이벤트 준비]
 priority: 60
+user-invocable: true
 ---
-# Event Planning
 
-Community event automation with D-Day based proactive execution.
-
-## Supported Communities
-
-| Code | Name | Format | Schedule |
-|------|------|--------|----------|
-| `MDC` | 마케팅데이터커넥트 | Offline meetup, 3 speakers × 20-25min | Odd months, last week weekday 19:00 |
-| `webinar` | 퇴근후AI | Online Zoom, 1-2 speakers × 50-60min | Irregular |
-| `DWK` | Data+Women Korea | Offline/Online, 1-3 speakers + discussion | Irregular |
-
-## D-Day Timeline
-
-### MDC (D-60 → D+2, 11 steps)
-
-| D-Day | Task | Outputs | Confirm |
-|-------|------|---------|---------|
-| D-60 | Topic selection + speaker research | 3 topics + speaker research | — |
-| D-45 | Speaker outreach | DM + email drafts | — |
-| D-40 | Speaker topic confirmation request | Confirmation email | — |
-| D-28 | **Registration page open** | Intro + 2 images + 3 SMS + 1 email + prompts | — |
-| D-30 | SNS promo + notification SMS | LinkedIn/Threads + SMS send | ✅ send |
-| D-14 | Remind | LinkedIn/Threads remind | — |
-| D-3 | Confirmation email + SMS | BCC email + SMS send | ✅ send |
-| D-1 | Nametags + checklist + slides + remind SMS | HTML + MD + PPTX + SMS draft | ✅ print/send |
-| D-Day | Day-of remind | SMS send | ✅ send |
-| D+1 | Review + settlement | Review draft + settlement template | — |
-| D+2 | Site update | (manual) | — |
-
-### Webinar (Planning → D+1, 5 steps)
-
-| D-Day | Task | Outputs | Confirm |
-|-------|------|---------|---------|
-| Planning | Event page | Intro + 3 images + SMS + email + prompts | — |
-| Planning | SNS promo | LinkedIn/Threads | — |
-| D-4 | Zoom + notification | Zoom link(manual) + email(BCC) + SMS | ✅ send |
-| D-Day | Day-of ops | SMS + slides | ✅ send |
-| D+1 | Review post | LinkedIn/Threads | — |
-
-### DWK (D-30 → D+3, 9 steps)
-
-| D-Day | Task | Outputs | Confirm |
-|-------|------|---------|---------|
-| D-30 | Topic + speaker research | 3 topics + speaker research | — |
-| D-25 | Speaker outreach | DM + email drafts | — |
-| D-20 | Speaker topic confirmation | Confirmation email | — |
-| D-16 | Event page | Intro + 2 images + SMS + email + prompts | — |
-| D-15 | SNS promo | LinkedIn/Threads | — |
-| D-3 | Confirmation email + SMS | BCC email + SMS | ✅ send |
-| D-1 | Slido + ops + remind | Slido plan + PPTX + SNS remind | ✅ |
-| D-Day | Day-of ops | SMS + nametags(offline) | ✅ send |
-| D+3 | Review + settlement | Review draft + Stripe/Slack settlement | — |
-
-## Proactive Execution Protocol
-
-When user says "MDC 준비해줘" or similar:
-
-```
-1. Parse: event type + edition + date
-2. Calculate D-Day from today
-3. Identify current step(s) in timeline
-4. Auto-execute ALL pending outputs for current step
-5. Request confirmation ONLY for send/publish actions
-6. Save state to .event_state.json
-```
-
-## State File (.event_state.json)
-
-```json
-{
-  "event_id": "MDC-12",
-  "type": "MDC",
-  "date": "2026-03-30",
-  "title": "마케팅데이터커넥트 12회",
-  "topic": "",
-  "speakers": [],
-  "current_step": "D-28",
-  "completed_steps": ["D-60", "D-45", "D-40"],
-  "outputs": {}
-}
-```
-
-## State Management
-
-**Location**: `.vibe/.event_state.json` (project-local, gitignored)
-
-### Error Recovery
-
-| Failure | Recovery |
-|---------|----------|
-| State file missing | Regenerate from scratch by re-reading event config and completed artifacts |
-| State file corrupted (invalid JSON) | Delete corrupted file, regenerate from current directory state |
-| State phase mismatch | Trust directory artifacts over state file — scan for completed outputs and infer current phase |
-
-## Community Tone Guide
-
-| | MDC | Webinar | DWK |
-|---|---|---|---|
-| Tone | Professional, practical, formal | Friendly, casual, emoji-ok | Warm, inclusive, "together" |
-| Example | "Apply directly in your work" | "Relax after work" | "Women who love data" |
-| Brand color | #ff6b35 (orange) | #a78bfa (purple) | #34d399 (mint) |
-
-## Community Brand Names
-
-| MDC | webinar | DWK |
-|-----|---------|-----|
-| 마케팅데이터커넥트 | (none) | DATA + WOMEN KOREA TUG |
-
-## Confirmation Rules
-
-| Auto-execute (no confirm) | Requires confirmation |
-|---------------------------|----------------------|
-| Intro/SMS/email/SNS **draft** generation | SMS/email **actual send** |
-| Image prompt + API generation | Notion **real registration** (dry_run first) |
-| Checklist/nametag HTML generation | — |
-
-## Absolute Prohibitions
-
-- No SMS/email send without user confirmation
-- **Email recipients MUST use BCC** (never expose attendee emails to each other)
-- No file deletion (move only)
-- No emoji in SMS (EUC-KR incompatible)
-- No Notion registration without dry_run first
-- No .env file commits
-
-## Output Directory Structure
-
-```
-output/
-├── images/           ← Generated images
-│   ├── {type}_prompt.txt    ← User-facing prompt summary (≤400 chars)
-│   └── {type}_{size}.png    ← Generated images
-├── reports/          ← Text outputs (intro, SNS, SMS, email drafts)
-├── log.html          ← Dashboard frontend
-└── serve.py          ← Dashboard server
-```
+Load `vibe.event` in planning mode and preserve all arguments.