@su-record/vibe 2.9.22 → 2.9.23

package/skills/event-ops/rubrics/contingency.md

@@ -1,85 +1,85 @@
-# Contingency Plan for Common Event Issues
-
-## Speaker No-Show
-
-| Severity | Trigger | Response |
-|----------|---------|----------|
-| High | Speaker unreachable 30 min before event | Call + SMS every 5 min. At T-15 min, announce brief delay. At T-0, proceed without or re-order sessions. |
-
-**Mitigation (do in advance):**
-- [ ] Backup speaker or moderator-led discussion identified at D-3
-- [ ] Speaker has organizer's phone number, not just email
-- [ ] Session slides received by D-1 (presenter can proceed without speaker for key points)
-
----
-
-## A/V Failure (Projector / Screen)
-
-| Issue | Immediate Action |
-|-------|----------------|
-| No HDMI signal | Swap adapter → try different port → use backup laptop |
-| Projector lamp failure | Use TV monitor if available; announce "slides on Slido" as fallback |
-| No audio from mic | Switch to backup mic → use presenter's natural voice for small rooms |
-
-**Prevention:**
-- [ ] HDMI cable + adapters (USB-C, Mini DisplayPort) in equipment bag
-- [ ] Backup laptop with slides loaded and tested
-- [ ] Portable Bluetooth speaker for audio fallback (small venues)
-
----
-
-## Zoom / Streaming Failure (Online/Hybrid)
-
-| Issue | Immediate Action |
-|-------|----------------|
-| Zoom disconnected | Restart app → new meeting link sent via pre-drafted SMS/email |
-| Screen share freeze | Stop/restart screen share → switch to phone hotspot if network issue |
-| No audio online | Confirm mic selected in Zoom settings → use phone as audio backup |
-
-**Prevention:**
-- [ ] Backup meeting link created and ready to send
-- [ ] Phone hotspot available as network backup
-- [ ] Co-host assigned to monitor chat/Q&A independently
-
----
-
-## Low Attendance
-
-| Threshold | Action |
-|-----------|--------|
-| < 50% of registered | Proceed normally — lower numbers often mean more intimate discussion |
-| < 10 people (offline) | Reconfigure seating to feel intimate, not sparse |
-
-**Notes:** Never cancel due to low attendance once speakers are confirmed. Record event for future distribution.
-
----
-
-## Over-Capacity
-
-| Threshold | Action |
-|-----------|--------|
-| >10% over room capacity | Direct overflow to live stream or waiting area |
-| Fire safety limit reached | Stop admission at door, offer recording link |
-
-**Prevention:**
-- [ ] Registration cap set at 80–90% of room capacity
-- [ ] Waitlist managed actively from D-14
-
----
-
-## Payment / Settlement Issue
-
-| Issue | Action |
-|-------|--------|
-| PG settlement delayed | Note expected settlement date, record in settlement report |
-| Attendee requests refund day-of | Log name + contact, process after event via standard refund flow |
-| Expense receipt missing | Request digital receipt same day — harder to get after 24 hours |
-
----
-
-## General Escalation Protocol
-
-1. Assess severity: **Can the event continue?** → Yes: mitigate silently. No: brief attendees.
-2. Communicate calmly — attendees follow the organizer's energy.
-3. Log the issue in `.event_state.json` under `"incidents"` for post-event review.
-4. Debrief within 24 hours — add to standard checklist if issue was preventable.
+# Contingency Plan for Common Event Issues
+
+## Speaker No-Show
+
+| Severity | Trigger | Response |
+|----------|---------|----------|
+| High | Speaker unreachable 30 min before event | Call + SMS every 5 min. At T-15 min, announce brief delay. At T-0, proceed without or re-order sessions. |
+
+**Mitigation (do in advance):**
+- [ ] Backup speaker or moderator-led discussion identified at D-3
+- [ ] Speaker has organizer's phone number, not just email
+- [ ] Session slides received by D-1 (presenter can proceed without speaker for key points)
+
+---
+
+## A/V Failure (Projector / Screen)
+
+| Issue | Immediate Action |
+|-------|----------------|
+| No HDMI signal | Swap adapter → try different port → use backup laptop |
+| Projector lamp failure | Use TV monitor if available; announce "slides on Slido" as fallback |
+| No audio from mic | Switch to backup mic → use presenter's natural voice for small rooms |
+
+**Prevention:**
+- [ ] HDMI cable + adapters (USB-C, Mini DisplayPort) in equipment bag
+- [ ] Backup laptop with slides loaded and tested
+- [ ] Portable Bluetooth speaker for audio fallback (small venues)
+
+---
+
+## Zoom / Streaming Failure (Online/Hybrid)
+
+| Issue | Immediate Action |
+|-------|----------------|
+| Zoom disconnected | Restart app → new meeting link sent via pre-drafted SMS/email |
+| Screen share freeze | Stop/restart screen share → switch to phone hotspot if network issue |
+| No audio online | Confirm mic selected in Zoom settings → use phone as audio backup |
+
+**Prevention:**
+- [ ] Backup meeting link created and ready to send
+- [ ] Phone hotspot available as network backup
+- [ ] Co-host assigned to monitor chat/Q&A independently
+
+---
+
+## Low Attendance
+
+| Threshold | Action |
+|-----------|--------|
+| < 50% of registered | Proceed normally — lower numbers often mean more intimate discussion |
+| < 10 people (offline) | Reconfigure seating to feel intimate, not sparse |
+
+**Notes:** Never cancel due to low attendance once speakers are confirmed. Record event for future distribution.
+
+---
+
+## Over-Capacity
+
+| Threshold | Action |
+|-----------|--------|
+| >10% over room capacity | Direct overflow to live stream or waiting area |
+| Fire safety limit reached | Stop admission at door, offer recording link |
+
+**Prevention:**
+- [ ] Registration cap set at 80–90% of room capacity
+- [ ] Waitlist managed actively from D-14
+
+---
+
+## Payment / Settlement Issue
+
+| Issue | Action |
+|-------|--------|
+| PG settlement delayed | Note expected settlement date, record in settlement report |
+| Attendee requests refund day-of | Log name + contact, process after event via standard refund flow |
+| Expense receipt missing | Request digital receipt same day — harder to get after 24 hours |
+
+---
+
+## General Escalation Protocol
+
+1. Assess severity: **Can the event continue?** → Yes: mitigate silently. No: brief attendees.
+2. Communicate calmly — attendees follow the organizer's energy.
+3. Log the issue in `.event_state.json` under `"incidents"` for post-event review.
+4. Debrief within 24 hours — add to standard checklist if issue was preventable.

package/skills/event-ops/templates/d-day-checklist.md

@@ -1,65 +1,65 @@
-# D-Day Operations Checklist
-
-> Event: {{EVENT_NAME}} {{EDITION}}회
-> Date: {{DATE}} {{TIME}}
-> Venue: {{VENUE}}
-> Organizer on duty: {{ORGANIZER_NAME}}
-
----
-
-## Morning (3+ Hours Before)
-
-- [ ] Day-of reminder SMS sent to all attendees ({{SEND_TIME}})
-- [ ] Final headcount confirmed from registration system
-- [ ] Nametag printouts packed and counted
-- [ ] Equipment bag packed: extension cord, HDMI cable, adapters, markers
-- [ ] Emergency contact list saved to phone: venue manager, co-organizer, speakers
-
-## Setup (60 Minutes Before)
-
-- [ ] Arrived at venue — venue manager contacted
-- [ ] Room layout confirmed: seating, stage/podium position
-- [ ] Projector / screen tested with presenter laptop
-- [ ] Microphone(s) tested (wireless + backup)
-- [ ] Zoom / streaming setup (if hybrid or webinar): audio, camera, screen share
-- [ ] Nametag table set up at entrance with pens
-- [ ] Slido QR code displayed (on screen + printed if offline)
-- [ ] Refreshments/snacks arranged
-
-## 30 Minutes Before
-
-- [ ] Operational slides opened on presenter laptop, correct slide showing
-- [ ] Speaker briefing completed: order, timing signals, Q&A format
-- [ ] Camera / recording device positioned and recording started
-- [ ] Greeting staff stationed at entrance
-
-## During Event
-
-- [ ] Doors open on time
-- [ ] Late attendees directed without disrupting session
-- [ ] Time signals given to speakers at 5 min and 1 min remaining
-- [ ] Q&A moderated via Slido — top voted questions surfaced first
-- [ ] Attendance count recorded at peak (for settlement)
-
-## Wrap-Up
-
-- [ ] Thank speakers on stage
-- [ ] Announce next event (date or "stay tuned")
-- [ ] Networking time opened
-- [ ] Recording stopped — file saved to correct directory
-- [ ] Photo assets organized: `output/images/{{EVENT_ID}}_dday/`
-
-## Post-Event (Within 30 Minutes)
-
-- [ ] Venue cleaned and returned to original state
-- [ ] Lost items checked — contact info taken if needed
-- [ ] Equipment collected and accounted for
-- [ ] Venue manager check-out completed
-- [ ] Quick debrief with co-organizers: what went well / what to fix
-
-## Settlement Inputs to Collect Today
-
-- [ ] Actual attendance count recorded
-- [ ] All receipts collected: venue, snacks, gifts
-- [ ] Cash / transfer payment records (if applicable)
-- [ ] Notes on any unexpected expenses
+# D-Day Operations Checklist
+
+> Event: {{EVENT_NAME}} {{EDITION}}회
+> Date: {{DATE}} {{TIME}}
+> Venue: {{VENUE}}
+> Organizer on duty: {{ORGANIZER_NAME}}
+
+---
+
+## Morning (3+ Hours Before)
+
+- [ ] Day-of reminder SMS sent to all attendees ({{SEND_TIME}})
+- [ ] Final headcount confirmed from registration system
+- [ ] Nametag printouts packed and counted
+- [ ] Equipment bag packed: extension cord, HDMI cable, adapters, markers
+- [ ] Emergency contact list saved to phone: venue manager, co-organizer, speakers
+
+## Setup (60 Minutes Before)
+
+- [ ] Arrived at venue — venue manager contacted
+- [ ] Room layout confirmed: seating, stage/podium position
+- [ ] Projector / screen tested with presenter laptop
+- [ ] Microphone(s) tested (wireless + backup)
+- [ ] Zoom / streaming setup (if hybrid or webinar): audio, camera, screen share
+- [ ] Nametag table set up at entrance with pens
+- [ ] Slido QR code displayed (on screen + printed if offline)
+- [ ] Refreshments/snacks arranged
+
+## 30 Minutes Before
+
+- [ ] Operational slides opened on presenter laptop, correct slide showing
+- [ ] Speaker briefing completed: order, timing signals, Q&A format
+- [ ] Camera / recording device positioned and recording started
+- [ ] Greeting staff stationed at entrance
+
+## During Event
+
+- [ ] Doors open on time
+- [ ] Late attendees directed without disrupting session
+- [ ] Time signals given to speakers at 5 min and 1 min remaining
+- [ ] Q&A moderated via Slido — top voted questions surfaced first
+- [ ] Attendance count recorded at peak (for settlement)
+
+## Wrap-Up
+
+- [ ] Thank speakers on stage
+- [ ] Announce next event (date or "stay tuned")
+- [ ] Networking time opened
+- [ ] Recording stopped — file saved to correct directory
+- [ ] Photo assets organized: `output/images/{{EVENT_ID}}_dday/`
+
+## Post-Event (Within 30 Minutes)
+
+- [ ] Venue cleaned and returned to original state
+- [ ] Lost items checked — contact info taken if needed
+- [ ] Equipment collected and accounted for
+- [ ] Venue manager check-out completed
+- [ ] Quick debrief with co-organizers: what went well / what to fix
+
+## Settlement Inputs to Collect Today
+
+- [ ] Actual attendance count recorded
+- [ ] All receipts collected: venue, snacks, gifts
+- [ ] Cash / transfer payment records (if applicable)
+- [ ] Notes on any unexpected expenses

package/skills/event-planning/SKILL.md

@@ -1,144 +1,144 @@
----
-name: event-planning
-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: 70
----
-# 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**: `.claude/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
-```
+---
+name: event-planning
+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: 70
+---
+# 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**: `.claude/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
+```