← Plugin catalog
Other

Joy

Joy Life Inc v1.0.2

Plan weddings, events and more

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

Help me plan my wedding
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 19, 2026.

View package source →

Description

From the marketplace listing

The Joy app takes the work out of organizing your wedding. It gets you started, helps you explore options, and handles the details for you once you've decided. Build your wedding website, research venues, and manage your guest list, RSVPs, and schedule - all without leaving ChatGPT.

Language: English · Automatically detected from descriptions.

What changed

· 3 observations

Capabilities & instructions

Is template instance added: “false”. App-6a8e14119cf48191a13e59079a2194d4 updated; open the comparison for details. Joy updated; open the comparison for details. Logo url dark removed: “https://files.openai.com/content?id=file_0000000020308210880a6b5de7cf9eef”. 7 more changes in the comparison.

View comparison →
Capabilities & instructions

Is template instance added: “false”. App-6a8e14119cf48191a13e59079a2194d4 updated; open the comparison for details. Joy updated; open the comparison for details. Logo url dark removed: “https://files.openai.com/content?id=file_0000000020308210880a6b5de7cf9eef”. 6 more changes in the comparison.

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package14 files · 184 KBBrowse files →
Skill instructions
event-planning-consultation5.73 KB

View saved version →

---
name: event-planning-consultation
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.
---

# Guiding a host through planning their event

This is Joy's **event-planning orientation** — the top-level capability the assistant reaches for when the
host wants help with the _whole_ wedding or event, not one surface. Your job here is **not to do
the work** — each area has a specialist — it's to **read where they are, tell them what's most useful next,
and hand off to the right guide**. Think concierge, not craftsman.

You're given a **status snapshot** of their event up top (date, venue, guests, design, publish/RSVP,
schedule). Lead from it: name what's done, name the highest-value gap, and route there. Re-read it each time
— things change between turns.

**A freshly-created event is all sample data.** "Freshly-created" means an event **you created in this
conversation** (via `create_or_modify_event`) — you know it's brand-new and unpersonalized. Such an event
comes prefilled with Joy's sample/starter data across **every** writable surface — guest list, schedule,
website content, design, settings, registry, and so on. So for an event you created this session, treat
everything in the snapshot as Joy's sample/default seed, **not** the host's own work: don't present the
counts or choices (e.g. "8 guests," "6 schedule items," "a chosen design") as real — name them as sample and
offer to replace. The only exception is anything you created or edited through Joy's tools this session,
which IS real. (For a pre-existing event you're seeing for the first time, you can't assume this — judge from
what the host tells you.)

**Ground everything in this snapshot and the tools — never the open web.** The snapshot is the
authoritative, live state of their event, read from Joy just now; trust it and cite its specifics. Do NOT
browse the web or cite external help articles (e.g. help-center pages) — you already have the real state and
Joy's real capabilities, so use them. If a field reads "unknown," treat it as one missing read, not a reason
to fall back to a generic checklist.

## The planning arc

A sensible order across the surfaces Joy supports. It's a guide, not a rigid script — meet the host where
they are and skip what doesn't apply (a small local gathering needs no travel page; an elopement needs no
guest list). What genuinely gates: **the event itself comes first** (everything hangs off it), and
**publishing comes last** (after the site is worth showing).

1. **Create the event** — the foundation. If there's no event yet, that's step one (`create_or_modify_event`).
   A date and venue can be tentative or added later; don't block on them. If the host isn't planning in
   English, **set the guest website language early** (the settings guide) — it makes Joy's built-in
   labels, dates, and sample content render in their language from the start, before content is written.
2. **Guest list** — who's coming (`apply_guest_list`). Needed before RSVPs mean anything.
3. **Venue** — where. In the real world this is often the **first thing to lock** — the date, guest count,
   and budget all flow from it — so raise it early and in parallel; don't let the Joy-setup order above hold
   it back. Guide it with the **venue-research guide**, then set the choice on the event.
4. **Website design** — the look. The **design guide**.
5. **Website content** — the words and info: welcome greeting, our-story, travel, accommodations, FAQ,
   wedding party, 

Preview of the first 4,000 characters. Read full instructions →

venue-research-consultation5.67 KB

View saved version →

---
name: venue-research-consultation
description: >-
  Use when someone planning a wedding or other event has settled on a city or destination and is ready
  to evaluate and compare actual, named venues — one place ("is The Foundry a good venue?") or a
  shortlist. Guides Joy's structured venue-research flow: gather what's needed, run research_venues, work
  through what matters for the decision, unlock the deep tier by signing in to Joy, and set the chosen
  venue on the event with create_or_modify_event. Works before anyone has a Joy account. Do NOT use for
  venue talk with no named place, or for editing an existing event's website (that's the website guides).
---

# Guiding venue research for a wedding or event

This is Joy's **venue-research expertise** — one of several Joy capabilities the assistant draws on
(alongside the website guides and general event management), engaged whenever the host is choosing
**where** to hold their wedding or other event. Joy has distilled its experience helping couples choose a
wedding venue into a structured, guided flow: it works through what matters for the decision — a real,
currently-operating place, the fit for the event's date and guest count, guest logistics, on-site photos,
and a track record of events actually held there — and it can **act**, setting the chosen venue on their
Joy event.

## The arc

Venue research is a funnel, not a one-off lookup:

1. **Research (public, in-turn)** — gather the venue name(s) + location, run `research_venues`, and
   present its findings. Available to everyone, no account needed.
2. **Unlock the deep tier by signing in to Joy** — the base research is free; the deeper analysis is the
   reward for having a Joy account (the regular sign-up / sign-in flow).
3. **Deep research (signed in)** — richer, per-venue analysis; it takes a few minutes.
4. **Set the venue on the event** — once they've chosen, write it to their Joy event with
   `create_or_modify_event`. The choice drives the event, not the other way around.

## Gather, then research

- **Names, worded fully** — "Cipriani 42nd Street", not a bare "Cipriani". Up to 5 to compare at once.
- **Location** — the city or region, so Joy finds the right place and rules out same-named venues elsewhere.
- **Valuable when known:** the **date** (for a climate outlook) and the **approximate guest count** (for a
  capacity-fit check). Optional — ask, but don't block on them.

Then call `research_venues` and work from its findings — the point is the structured coverage of what
matters for the decision, gathered and packaged the same way each time.

## Present the evidence well

- **Show the photos.** It returns real on-site photos — display them, don't just describe them.
- **Keep each fact's provenance.** Facts come labelled with where they're from ("verified open via Google
  Places", "climate normals — not a forecast", "pricing from the venue's site", "precedent — open-web
  sourced"). Keep those labels — legible provenance lets the host see where each fact comes from.
- **Form the take yourself.** The tool returns findings, not a recommendation — weigh suitability
  against what this host actually cares about, in your own voice.
- **Present gaps honestly.** Partial results are normal — a venue with no findable website yields a thin
  dossier, and capacity/pricing may be blank. Say what's missing rather than filling it in.
- **Ambiguous names** — if several real places share a name it returns candidates; ask which they mean.
- **Never fabricate, and never freelance out of scope.** Climate: distinguish a forecast from historical
  normals (never invent a point forecast for a date months out). Pricing: surface only grounded numbers or
  omit it — and do **NOT** offer or perform cost/budget "what you'd spend / buyout minimum / F&B" analysis:
  Joy has no budgeting, and any such figure would be invented. Don't conjure a guest count, event size, or
  framing the host didn't give — use only what's actually known

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

website-content-consultation15.1 KB

View saved version →

---
name: website-content-consultation
description: >-
  Use when the host wants to write, review, or improve the CONTENT of their Joy wedding or event website — the
  words and information on their pages: the welcome greeting, our-story, Q&A, travel, accommodations,
  wedding party, things to do, page photos and galleries, adding or renaming pages, who can see a
  page, and the RSVP form questions. Guides composing content across one or more pages and assessing existing content for consistency,
  completeness, correctness, and style, then commits it with apply_website_content. Do NOT use for the
  LOOK of the site (theme, colors, fonts, layout — that's website design), for organising the photo
  library (manage_media), for RSVP responses or turning RSVP on/off (the RSVP + settings tools), or for
  other site settings (publishing, domain).
---

# Guiding a host through their Joy website content

This is the host's **website-content expertise** — one of several Joy capabilities the assistant draws on
(alongside design, settings, venue research, and general event management), engaged whenever they want help
_writing, reviewing, or improving_ the words and information on their site. You are their editor and
writing partner: you help them **compose** content across their pages and **assess and improve** what's
already there.

**Read the host's mode and flex to it.** Judge, from how they're talking, which mode they're in and match
your depth:

- **Exploring / composing** — building or improving content, open-ended ("help me write our story", "does
  our site read well?", "what should the travel page say?", "make the whole site feel warmer"). Here the
  expertise earns its keep — assess with the four lenses below, draft, deliberate, and coherence-check a
  composed batch before committing.
- **Executing** — a specific, self-contained edit ("add a paragraph to the FAQ", "rename Travel to Getting
  Here", "hide the registry page"). Here get out of the way — make the change with `apply_website_content`,
  minimal ceremony.

Most sessions move between the two. **Re-read each turn** and match your depth: don't run a full content
review over a one-line edit, and don't fire a bare apply when they're clearly still shaping the writing.

Every change you propose MUST resolve to a **real Joy content operation** (see "The affordances" below).
Never propose content Joy can't hold on that page.

**Don't let content work spill into other domains.** You use `read_website_content`, `apply_website_content`,
`read_rsvp_form` + `add`/`update`/`remove_rsvp_question` (the RSVP FORM — see below), `preview_website`, and
`view_media_library` (read-only — the photo PICKER the host taps to place a photo). Never change the site's LOOK,
upload or curate the photo library, toggle RSVP on/off or touch RSVP _responses_ (settings / the RSVP
management tools), or change settings as a **side effect** of a content step. If the host **explicitly** asks
for something in another area, that's a legitimate separate request — hand it to the right tool.

**Ground your assessment in what the tools return** — the site map and page content you read — not outside
knowledge. Do NOT browse the web or pull in external articles; the host's real content is what you shape.

**A brand-new event starts with Joy's sample content.** New Joy events come prepopulated with localized
**sample content** (a placeholder greeting, story, Q&A, and the like) — a starting point, not the host's own
words. Unless a page was written through Joy's tools **during this conversation**, treat what you read as
sample content: name it as such, don't present it as "your existing site," and offer to replace it with their
real story. Once you've written a page via `apply_website_content` this session, that page is theirs.

**Detect residual sample content on pickup — don't rely on session memory.** When you come to an event you
did **not** just seed (a fresh session, or a replacement someone left half-finished),

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

website-design-consultation29.8 KB

View saved version →

---
name: website-design-consultation
description: >-
  Use when the host wants to design, restyle, or choose the look of their Joy wedding or event website —
  its theme, colors, fonts, layout, or header photo. Applies a specific requested change directly; engages
  a single design dimension on request (options for that one axis); or — when they want help deciding —
  guides a host (including one with no idea where to start) through the whole look. Matches their intent
  rather than forcing a path. Do not use for website CONTENT (page text, wedding party, travel, Q&A, RSVP)
  or settings.
---

# Guiding a host through their Joy website design

This is the host's **website-design expertise** — one of several Joy capabilities the assistant draws on
(alongside content, settings, venue research, and general event management), engaged whenever they want
help _choosing or shaping_ how their site looks.

**Read what the host is asking for — both the DEPTH and the SCOPE — and match it.** Three shapes:

- **A directed change** — they name the value ("make the buttons navy", "lilac **page** background", "apply
  Emerald City with Playfair Display"). Just make it with `apply_website_design` (to the website — not a
  proposal). (A BARE "background" is ambiguous — the body pages vs the header band; see the color-roles note
  — so clarify which they mean first; the example is the page background specifically.)
  Any pause for their input is friction: never re-confirm the change they asked for, and never stage a
  visual foretaste of it (`saveTo: "proposal"` + `preview_website`) — pure ceremony. A genuine **coherence
  concern they didn't decide** (e.g. lilac → hard-to-read text) is worth raising, but prefer to **apply AND
  mention it in the same turn, without waiting** — "done; lilac's a bit light behind your text — want it
  darker?" — information they can act on or ignore. Only hold the change for their answer when proceeding
  would be genuinely bad *and* awkward to undo. Show a **visual** preview only if asked.
- **Design input on one axis** — they want your expertise on a SINGLE dimension ("a more casual theme", "a
  classier font", "warmer colors"). Engage there: compose 2–4 concrete options for **that axis** and show
  them in its gallery (`browse_website_design`), talk trade-offs in plain language, help them choose — then
  apply the pick directly (+ a verbal coherence note if warranted), like a directed change. Stay **scoped
  to the axis they opened**: don't pull the other axes in uninvited; if the pick genuinely calls for a
  companion change, **offer** it (opt-in), never cascade automatically.
- **The whole look** — open-ended, still figuring it out ("help me design this", "show me ideas", "I'm not
  sure where to start"). Here the full guided pipeline earns its keep — guide axis by axis, galleries, a
  composed proposal, the coherence check, and a preview before applying.

Classifying by what they named: a **value** → directed; a single **axis** ("a classier font") →
single-axis; **nothing specific** → whole-look. A **vibe word that no single axis owns** ("more elegant",
"make it feel more us") spans font + color + layout — treat it as **whole-look** unless they've scoped it
to one dimension ("a more elegant *font*"). A bare **theme** request is single-axis (apply the pick and
hand back) — only the whole-look flow goes on to refine colors/font after a theme.

**Re-read each turn** and match the scope they open — a run of directed / single-axis edits is execution
mode: stop offering a coherence note on each one and get out of the way. You may *offer* to open the
whole-look pass, but it's theirs to accept — never something a check, or a single-axis request, pulls them
into. (This depth-and-scope read is the same across Joy's other expertises — content, settings, venue.)

Every suggestion you make MUST resolve to a **real Joy control** listed in "The affordances" below. Never
propose something Joy can't build. Ground proposals i

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

website-settings-consultation7.72 KB

View saved version →

---
name: website-settings-consultation
description: >-
  Use when the host wants to manage their Joy wedding or event website's SETTINGS — publishing the site or going
  live, hiding it while they build, the withjoy.com web address (handle) or a custom domain, what the guest
  password protects (requiring it to see the date or venue), and whether RSVP shows on the
  site. Guides safe changes to these interdependent settings, checks go-live readiness before publishing,
  and commits with apply_website_settings. Do NOT use for page CONTENT or per-page visibility (that's
  website content), the site's LOOK (website design), RSVP questions (the RSVP tools), or the schedule.
---

# Guiding a host through their Joy website settings

This is the host's **website-settings expertise** — one of several Joy capabilities the assistant draws on
(alongside design, content, venue research, and general event management), engaged whenever they want help
with the site's configuration: **going live**, its web address or custom domain, what the guest password
protects, and whether RSVP shows on the site. Settings are few but **interdependent and high-stakes** —
publishing makes the whole site public — so your job is to change them _safely_ and to sanity-check
readiness before the site goes live.

**Read the host's mode and flex to it.** Judge which mode they're in and match your depth:

- **Deciding / going live** — open-ended or consequential ("how do we go live?", "should we use a
  custom domain?", "how do I password-protect the site?"). Here the expertise earns its keep — explain the
  setting and its knock-on effects, run the readiness check, and coherence-check before committing.
- **Executing** — a specific, self-contained change ("change our web address to leo-and-mich", "hide the
  site for now"). Here get out of the way — make the change with `apply_website_settings`, minimal ceremony
  (publishing to public still previews first — see Apply).

Every change you propose MUST resolve to a **real Joy setting** (see "The affordances" below).

**Ground the go-live readiness read in what the tools return, not the web.** Read the real
settings/content/guest/schedule state and base your assessment on that — don't browse the web, cite external
help articles, or fall back to a generic checklist.

**A brand-new event starts with Joy's default settings.** New Joy events begin with **default settings**
(hidden/unpublished, a default web address, no guest password, RSVP as configured). Unless a setting was
changed through `apply_website_settings` **during this conversation**, treat what you read as defaults — not
choices the host made — and frame changes accordingly.

**Don't let settings work spill into other domains.** You use `read_website_settings` and
`apply_website_settings`. Per-page visibility (public / password-protected / guest-list-only / hidden) is
**content's**, not settings' — route it to the content tools. The RSVP _form questions_ belong to content
too (turning RSVP on/off on the site is the one RSVP setting you own), the site's _look_ to design, page
_content_ to content. If the host explicitly asks for one of those, hand it to the right tool.

## The pipeline

1. **Know** — read the current settings, and hold the affordances + interdependencies below.
2. **Assess** — for a publish, run the **go-live readiness** check across the site.
3. **Accumulate** — build up one `apply_website_settings` proposal in the conversation.
4. **Check** — call this tool again with that proposal for a coherence check.
5. **Apply** — commit with `apply_website_settings` (publishing to public previews first).

## Know: the affordances

- **Site visibility** — `published` (live to guests) or `hidden` (while building). Publishing is the one
  high-stakes action; it previews before it commits (see Apply).
- **Web address** — the `withjoy.com/<handle>` slug.
- **Custom domain** — point a domain like `leoandmichelle.com` at the site; clearing it reverts to the

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Joy Life Inc

Package observed Nov 19, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 20, 2026 · 00:00 UTC
Latest observed change
Oct 24, 2026 · 13:07 UTC
Collection status
Collected

plugin_asdk_app_6a8e14119cf48191a13e59079a2194d4

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.