@su-record/vibe 3.2.64 → 4.0.1

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

@@ -1,173 +0,0 @@
----
-name: event-comms-reference
-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
----
-# 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) |

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": {}
-}
-```