Luma event invite

Files (1)

• SKILL.md

SKILL.md (first lines)

# Luma event invite

## When to use
After the event concept is roughly set (name, date/time, capacity). Prefer **one platform per event** — if the club already chose Partiful, do not also create Luma unless asked.

## Creative inputs (required BEFORE opening Luma)
Do **not** open Luma, start Create Event, or write copy until these are collected (or explicitly waived by the user):

### Vibes
- Mood / energy (e.g. cozy build night, hype demo day, chill cafe hang)
- Visual references if any (colors, textures, campus inside jokes)
- What guests should *feel* when they land on the page

### Brand assets
- Club logo (file or link) if available
- Club colors / fonts / wordmark rules
- Existing event graphics or past Luma covers to match
- If none exist, note "no assets" and describe a cover direction instead

### Language
- Register: casual campus / professional / bilingual / etc.
- Words to use or avoid (club name spelling, inside jokes, accessibility language)
- Tone guardrails (fun, not corporate; beginners welcome, etc.)

Confirm dry-run mode up front: if yes → fill the form and **stop before Publish / Create Event going live**.

## Also confirm
- Event title (working title OK — refine with vibes)
- Date + start/end time (timezone = user's local / campus)
- Location (or "TBD — campus room")
- Capacity / guest limit
- Visibility: public / unlisted / approval-required (default: unlisted or approval for club demos)

## How to use vibes + assets + language
- **Title** — short, energetic; reflect vibes; use club naming rules from Language.
- **Description** — lead with what people will *do* and *feel* (from Vibes); skimmable (short paragraphs or 3–5 bullets); mention food/theme hooks in one line when relevant; beginners-welcome line for build/workshop nights; honor Language register and avoid-list.
- **Cover** — use Brand assets (logo, colors) when provided; otherwise select or generate imagery that matches Vibes. **Replace any random Luma placeholder cover** before review — never show the user a draft with a generic stock placeholder if a real direction exists.
- **Consistency** — title, description, and cover should feel like one package; if assets are missing, say so in the draft note to the user.

## Browser process (one tight pass)
Goal: **one focused browser session** — open Luma, fill the draft, screenshot, stop. Do not loop through multiple create flows.

1. **Prep complete** — vibes, brand assets, and language are collected; title/blurb/cover direction are drafted in chat first.
2. Open https://lu.ma (or https://luma.com — use whatever the live product redirects to).
3. If login/SSO/2FA is required, hand the user the box; never ask for their password.
4. Start **Create event** (or open an existing draft if continuing) — **only once**.
5. Fill in one pass: title, date/time, location, capacity, description/blurb, cover — all aligned to the creative inputs above.
6. **Replace placeholder cover** if Luma dropped in a random default.
7. Screenshot the draft preview / form and show the user.
8. **Stop before Publish / going live.** Ask for explicit publish approval.
9. Only on "publish yes": click Publish / Go live, then report the public Luma URL.
10. Optional follow-up: copy link into calendar, Slack, or email **only if asked**.

### If form automation loops
If clicks repeat, fields reset, or the UI fights back:
- **Stop** the automation immediately.
- **Screenshot** the current state.
- Tell the user which fields are done vs missing.
- Finish **only the missing fields** manually (or hand the user the box) — do not restart the whole flow.

## Guardrails
- Never open Luma until vibes, brand assets, and language are collected (or waived).
- Never publish without an explicit yes in chat.
- Never buy paid Luma boosts / paid features without approval.
- Demo/dry-run mode: leave as draft or clearly labeled test; do not spam the club list.
- If Luma UI changed, adapt to current labels; don't invent clicks you can't see.
- Prefer the signed-in browser over nonexistent Luma connectors.

## Report back
- Vibes, brand assets, and language used (or waived)
- Draft fields filled
- Screenshot of the draft
- Publish status (draft vs live)
- Event URL if live

From idildogaturkmen/COOK, MIT.

More from idildogaturkmen/COOK