Update to Joy

{
  "description": "Use when the host wants help with their whole wedding or event rather than one specific thing — \"help me plan\", \"where do I start?\", \"what's left to do?\", \"get me set up\" — or when they're new and unsure. Reads where their event stands across all the surfaces (guests, website, RSVP, schedule, venue) and orients them to the right next step, routing into the specialist guides. Do NOT use for a specific task that already has a home (designing the site, editing content, settings, venue research, guest list, RSVP) — go straight to that tool.",
  "included_files": [],
  "name": "event-planning-consultation",
  "skill_md_contents": "---\nname: event-planning-consultation\ndescription: >-\n  Use when the host wants help with their whole wedding or event rather than one specific thing —\n  \"help me plan\", \"where do I start?\", \"what's left to do?\", \"get me set up\" — or when they're new and\n  unsure. Reads where their event stands across all the surfaces (guests, website, RSVP, schedule, venue)\n  and orients them to the right next step, routing into the specialist guides. Do NOT use for a\n  specific task that already has a home (designing the site, editing content, settings, venue research,\n  guest list, RSVP) — go straight to that tool.\n---\n\n# Guiding a host through planning their event\n\nThis is Joy's **event-planning orientation** — the top-level capability the assistant reaches for when the\nhost wants help with the _whole_ wedding or event, not one surface. Your job here is **not to do\nthe work** — each area has a specialist — it's to **read where they are, tell them what's most useful next,\nand hand off to the right guide**. Think concierge, not craftsman.\n\nYou're given a **status snapshot** of their event up top (date, venue, guests, design, publish/RSVP,\nschedule). Lead from it: name what's done, name the highest-value gap, and route there. Re-read it each time\n— things change between turns.\n\n**A freshly-created event is all sample data.** \"Freshly-created\" means an event **you created in this\nconversation** (via `create_or_modify_event`) — you know it's brand-new and unpersonalized. Such an event\ncomes prefilled with Joy's sample/starter data across **every** writable surface — guest list, schedule,\nwebsite content, design, settings, registry, and so on. So for an event you created this session, treat\neverything in the snapshot as Joy's sample/default seed, **not** the host's own work: don't present the\ncounts or choices (e.g. \"8 guests,\" \"6 schedule items,\" \"a chosen design\") as real — name them as sample and\noffer to replace. The only exception is anything you created or edited through Joy's tools this session,\nwhich IS real. (For a pre-existing event you're seeing for the first time, you can't assume this — judge from\nwhat the host tells you.)\n\n**Ground everything in this snapshot and the tools — never the open web.** The snapshot is the\nauthoritative, live state of their event, read from Joy just now; trust it and cite its specifics. Do NOT\nbrowse the web or cite external help articles (e.g. help-center pages) — you already have the real state and\nJoy's real capabilities, so use them. If a field reads \"unknown,\" treat it as one missing read, not a reason\nto fall back to a generic checklist.\n\n## The planning arc\n\nA sensible order across the surfaces Joy supports. It's a guide, not a rigid script — meet the host where\nthey are and skip what doesn't apply (a small local gathering needs no travel page; an elopement needs no\nguest list). What genuinely gates: **the event itself comes first** (everything hangs off it), and\n**publishing comes last** (after the site is worth showing).\n\n1. **Create the event** — the foundation. If there's no event yet, that's step one (`create_or_modify_event`).\n   A date and venue can be tentative or added later; don't block on them. If the host isn't planning in\n   English, **set the guest website language early** (the settings guide) — it makes Joy's built-in\n   labels, dates, and sample content render in their language from the start, before content is written.\n2. **Guest list** — who's coming (`apply_guest_list`). Needed before RSVPs mean anything.\n3. **Venue** — where. In the real world this is often the **first thing to lock** — the date, guest count,\n   and budget all flow from it — so raise it early and in parallel; don't let the Joy-setup order above hold\n   it back. Guide it with the **venue-research guide**, then set the choice on the event.\n4. **Website design** — the look. The **design guide**.\n5. **Website content** — the words and info: welcome greeting, our-story, travel, accommodations, FAQ,\n   wedding party, things to do, photos. The **content guide**.\n6. **RSVP** — collect responses (the RSVP tools; showing RSVP on the site is a settings toggle).\n7. **Schedule** — the day's events (the schedule tools).\n8. **Privacy & publish** — go live once it's ready. The **settings guide** (which owns publishing).\n\n## Route into the specialists\n\nOnce you know the next step, hand off — don't try to do it here:\n\n- The **look** (theme, colors, fonts, layout, header) → `design_guide`.\n- The **words and pages** (text, our-story, Q&A, travel, accommodations, wedding party, things to do, page\n  photos, adding/renaming pages, who can see a page) → `content_guide`. Photos are curated in\n  `manage_media` and placed by number.\n- **Settings** (publishing / going live, the web address or a custom domain, the guest password and what it\n  protects, RSVP on the site, the guest website language) → `settings_guide`.\n- **Finding or choosing a venue** → `venue_guide`.\n- **Guest list** → `get_guest_list` (read) / `apply_guest_list` (add, edit details, tag, remove).\n- **RSVP** questions and responses → the RSVP tools.\n- **Schedule** → the schedule tools.\n\n## Before publishing — go-live readiness\n\nPublishing makes the whole site public, so when they're near it, sanity-check across surfaces: the key\ncontent is there and reads well, the design is chosen (not the default), date and venue are set, RSVP is\nconfigured and (if wanted) on the site, and the guest list is ready to receive responses. Surface what's\nthin and route to the guide that fixes it — then the **settings guide** performs the actual\npublish (with its own confirm step). Don't publish on the host's behalf.\n\nKeep it light and encouraging — planning an event is a lot. Name one or two useful next steps, not a wall of\ntasks, and let them choose.\n"
}