@su-record/vibe 3.2.62 → 4.0.0

package/skills/vibe.event/references/contingency.md

@@ -1,85 +0,0 @@
-# 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/vibe.event/references/d-day-checklist-template.md

@@ -1,65 +0,0 @@
-# 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/vibe.event/references/email-invite-template.md

@@ -1,99 +0,0 @@
-# Event Email Invitation Template
-
-> Delivery method: Gmail OAuth 2.0 — MUST use BCC (never expose attendee emails)
-> Timing: Use per D-Day schedule from event-planning skill
-
----
-
-## Registration Open Announcement
-
-```
-Subject: [{{EVENT_NAME}}] {{EDITION}}회 참가 신청 안내
-
-{{ATTENDEE_NAME}}님 안녕하세요.
-
-{{COMMUNITY_NAME}}에서 {{EDITION}}회 행사를 안내드립니다.
-
-■ 주제: {{THEME}}
-■ 일시: {{DATE}} {{TIME}}
-■ 장소: {{VENUE}}
-■ 참가비: {{FEE}}
-
-이번 행사에서 다루는 내용:
-{{WHAT_YOU_WILL_LEARN_1}}
-{{WHAT_YOU_WILL_LEARN_2}}
-{{WHAT_YOU_WILL_LEARN_3}}
-
-참가 신청: {{REGISTRATION_URL}}
-
-신청 마감: {{DEADLINE}}
-
-감사합니다.
-{{COMMUNITY_NAME}} 드림
-```
-
----
-
-## Attendance Confirmation Email (D-3)
-
-```
-Subject: [{{EVENT_NAME}}] {{EDITION}}회 참가 확정 안내
-
-{{ATTENDEE_NAME}}님 안녕하세요.
-
-{{EVENT_NAME}} {{EDITION}}회 참가가 확정되었습니다.
-소중한 시간 내주셔서 감사합니다.
-
-■ 일시: {{DATE}} {{TIME}}
-■ 장소: {{VENUE_DETAIL}}
-   {{VENUE_ADDRESS}}
-   {{VENUE_TRANSPORT}}
-
-■ 프로그램:
-{{TIMETABLE_LINE_1}}
-{{TIMETABLE_LINE_2}}
-{{TIMETABLE_LINE_3}}
-
-■ 실시간 질문: {{SLIDO_LINK}}
-
-당일 현장에서 뵙겠습니다.
-감사합니다.
-
-{{COMMUNITY_NAME}} 드림
-```
-
----
-
-## Post-Event Thank You + Recording Link
-
-```
-Subject: [{{EVENT_NAME}}] {{EDITION}}회 참석 감사드립니다
-
-{{ATTENDEE_NAME}}님 안녕하세요.
-
-{{EVENT_NAME}} {{EDITION}}회에 참석해 주셔서 진심으로 감사드립니다.
-
-■ 행사 후기:
-{{REVIEW_SUMMARY}}
-
-■ 발표 자료:
-{{SLIDE_URL_1}} — {{SPEAKER_1_NAME}}
-{{SLIDE_URL_2}} — {{SPEAKER_2_NAME}}
-
-■ 녹화 영상 (있는 경우):
-{{VIDEO_URL}}
-
-다음 행사 소식도 기대해 주세요.
-
-감사합니다.
-{{COMMUNITY_NAME}} 드림
-```
-
----
-
-## Usage Notes
-
-- Replace all `{{PLACEHOLDER}}` values before sending
-- BCC field only — the `To:` field should be your own sender address or a placeholder
-- Test with `testmode_yn=Y` equivalent before real send
-- Confirm send with event organizer before dispatch

package/skills/vibe.event/references/event-plan-template.md

@@ -1,91 +0,0 @@
-# Event Plan: {{EVENT_NAME}} {{EDITION}}회
-
-| Field | Value |
-|-------|-------|
-| Event type | {{TYPE}} (MDC / Webinar / DWK / Other) |
-| Date & time | {{DATE}} {{TIME}} |
-| Venue | {{VENUE}} |
-| Format | {{OFFLINE / ONLINE / HYBRID}} |
-| Expected attendees | {{EXPECTED_COUNT}} |
-| Registration URL | {{REG_URL}} |
-| Participation fee | {{FEE}} |
-
-## Topic & Theme
-
-**Main theme**: {{THEME}}
-
-**Session topics:**
-
-| # | Topic | Speaker | Duration |
-|---|-------|---------|----------|
-| 1 | {{TOPIC_1}} | {{SPEAKER_1}} | {{DURATION}} |
-| 2 | {{TOPIC_2}} | {{SPEAKER_2}} | {{DURATION}} |
-| 3 | {{TOPIC_3}} | {{SPEAKER_3}} | {{DURATION}} |
-
-## Timetable
-
-| Time | Item |
-|------|------|
-| {{TIME_1}} | {{ITEM_1}} |
-| {{TIME_2}} | {{ITEM_2}} |
-| {{TIME_3}} | {{ITEM_3}} |
-| {{TIME_4}} | Q&A + Networking |
-
-## Speakers
-
-### Speaker 1: {{SPEAKER_1_NAME}}
-
-- Role: {{ROLE}}
-- Company: {{COMPANY}}
-- Topic: {{TOPIC}}
-- Contact: {{EMAIL_OR_DM}}
-- Confirmation status: {{PENDING / CONFIRMED}}
-
-### Speaker 2: {{SPEAKER_2_NAME}}
-
-- Role: {{ROLE}}
-- Company: {{COMPANY}}
-- Topic: {{TOPIC}}
-- Contact: {{EMAIL_OR_DM}}
-- Confirmation status: {{PENDING / CONFIRMED}}
-
-## D-Day Timeline
-
-| D-Day | Task | Owner | Status |
-|-------|------|-------|--------|
-| D-{{N}} | {{TASK_1}} | {{OWNER}} | Not started |
-| D-{{N}} | {{TASK_2}} | {{OWNER}} | Not started |
-| D-3 | Confirmation email + SMS | {{OWNER}} | Not started |
-| D-1 | Nametags + checklist + slides | {{OWNER}} | Not started |
-| D-Day | Day-of operations | {{OWNER}} | Not started |
-| D+1 | Review post + settlement | {{OWNER}} | Not started |
-
-## Budget
-
-| Item | Estimated Cost | Actual Cost |
-|------|---------------|-------------|
-| Venue | {{AMOUNT}} | — |
-| Snacks / Refreshments | {{AMOUNT}} | — |
-| Speaker gifts | {{AMOUNT}} | — |
-| Printing (nametags, etc.) | {{AMOUNT}} | — |
-| **Total** | {{TOTAL}} | — |
-
-Revenue: {{EXPECTED_ATTENDEES}} × {{FEE}} = {{EXPECTED_REVENUE}}
-
-## State File Reference
-
-Save progress to `.event_state.json` after each step completion.
-
-```json
-{
-  "event_id": "{{TYPE}}-{{EDITION}}",
-  "type": "{{TYPE}}",
-  "date": "{{DATE}}",
-  "title": "{{EVENT_NAME}} {{EDITION}}회",
-  "topic": "{{THEME}}",
-  "speakers": [],
-  "current_step": "{{CURRENT_STEP}}",
-  "completed_steps": [],
-  "outputs": {}
-}
-```

package/skills/vibe.event/references/operations.md

@@ -1,208 +0,0 @@
----
-name: event-operations-reference
-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
----
-# 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 → the active harness outputs a 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 the harness's web research capability
-
-## 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 |

package/skills/vibe.event/references/orchestration-legacy.md

@@ -1,97 +0,0 @@
-# Event Orchestration Reference
-
-This preserves the complete pre-merge umbrella routing contract.
-
-## Execution Flow
-
-1. Parse type (`MDC`, `webinar`, `DWK`), edition, required date, optional topic, and DWK format (default offline).
-2. Calculate D-Day from the event date.
-3. Load or create `.event_state.json`.
-4. Determine the current phase: MDC 11 steps (D-60→D+2), webinar 5 steps (planning→D+1), DWK 9 steps (D-30→D+3).
-5. Produce pending content, speaker research, images, communications drafts, and operations materials.
-6. Request confirmation for real SMS/email sends and Notion registration.
-7. Save `.event_state.json`.
-
-## Input Parsing
-
-| Input | Parsed result |
-|---|---|
-| `MDC 12차 3/30` | type=MDC, edition=12, date=2026-03-30 |
-| `webinar AI에이전트` | type=webinar, topic=AI에이전트, date=TBD (ask) |
-| `DWK 5차 5/20 오프라인` | type=DWK, edition=5, date=2026-05-20, format=offline |
-| `status` | Show `.event_state.json` summary |
-| `dashboard` | Run `python output/serve.py` |
-
-## MDC Phases
-
-| Phase | Mode | Outputs |
-|---|---|---|
-| D-60 | planning | 3 topic suggestions + speaker research |
-| D-45 | planning | DM + email outreach drafts |
-| D-40 | operations | Topic confirmation request email |
-| D-28 | planning + operations | Intro + 2 images + 3 SMS + 1 email |
-| D-30 | planning + operations | LinkedIn/Threads promo + SMS send |
-| D-14 | planning | LinkedIn/Threads reminder |
-| D-3 | operations | BCC email + SMS send |
-| D-1 | operations | Nametags + checklist + PPTX + SMS |
-| D-Day | operations | Day-of SMS |
-| D+1 | planning + operations | Review posts + settlement |
-| D+2 | manual | Site update |
-
-## Webinar Phases
-
-| Phase | Mode | Outputs |
-|---|---|---|
-| Planning | planning + operations | Intro + 3 images + SMS + email |
-| Planning | planning | LinkedIn/Threads promo |
-| D-4 | operations | Zoom manual setup + BCC email + SMS |
-| D-Day | operations | SMS + slides |
-| D+1 | planning | Review posts |
-
-## DWK Phases
-
-| Phase | Mode | Outputs |
-|---|---|---|
-| D-30 | planning | 3 topics + speaker research |
-| D-25 | planning | DM + email outreach |
-| D-20 | operations | Topic confirmation email |
-| D-16 | planning + operations | Intro + 2 images + SMS + email |
-| D-15 | planning | LinkedIn/Threads promo |
-| D-3 | operations | BCC email + SMS |
-| D-1 | operations | Slido plan + PPTX + SNS reminder |
-| D-Day | operations | SMS + nametags (offline) |
-| D+3 | planning + operations | Review + settlement |
-
-## State Schema
-
-```json
-{
-  "event_id": "MDC-12",
-  "type": "MDC",
-  "edition": 12,
-  "date": "2026-03-30",
-  "title": "마케팅데이터커넥트 12회",
-  "topic": "마케팅 자동화",
-  "format": "offline",
-  "speakers": [{ "name": "김영수", "company": "Company X", "topic": "마케팅 데이터 파이프라인" }],
-  "current_step": "D-28",
-  "completed_steps": ["D-60", "D-45", "D-40"],
-  "outputs": { "D-28": ["intro.md", "thumbnail_500x500.png", "sms_notification.txt"] },
-  "confirmations_pending": []
-}
-```
-
-## Dashboard
-
-Run `python output/serve.py` and open `http://localhost:8080`. The dashboard provides timeline progress, per-step generation, file previews, provider status, and community color coding.
-
-## Absolute Safety Rules
-
-1. Never send SMS/email without explicit user confirmation.
-2. Always use BCC for email.
-3. Never use emoji in SMS (EUC-KR incompatibility).
-4. Never delete event files; move them when cleanup is needed.
-5. Test SMS with `testmode_yn=Y` before real send.
-6. Never register to Notion without `dry_run` first.
-7. Never commit `.env` files.
-