What this prompt does
This prompt has Claude or ChatGPT design a wishlist and gift registry system for a store. You set [store_name] and [store_type], then describe the [product_types], the [social_features] you want, the [registry_occasions], and the [framework]. The model designs the quick-save button, a wishlist dashboard, sharing and collaboration, the gift registry, notifications and re-engagement, merchant-side analytics, and the framework implementation.
It works because every wishlisted item is an intent signal — a future purchase — so the prompt designs saving to be effortless and buying to feel inevitable. By naming [product_types] and [registry_occasions], the model tailors the registry wizard and list organization to your catalog (a $20-to-$3,000 home goods range behaves differently than fashion). The [social_features] variable drives the sharing, collaborative-list, and hint mechanics, and the framework section specifies optimistic UI and cross-device sync.
When to use it
- You're adding wishlists and want multi-list saving with price tracking and back-in-stock alerts.
- You need a gift registry for occasions like weddings, baby showers, or housewarmings.
- You want shareable and collaborative lists with privacy controls and a "hint" feature.
- You're designing purchase coordination so gift-givers can buy without spoiling the list for the owner.
- You need price-drop and back-in-stock notifications that pull buyers back.
- You want merchant analytics on most-wishlisted items and wishlist-to-purchase conversion.
Example output
The model returns a feature-by-feature design document. The quick-save section covers the heart toggle animation, guest-to-account merge, and multi-list selection. The dashboard specifies named lists, price tracking, out-of-stock handling, and drag-to-reorder. The registry section details the creation wizard, a public registry landing page, cash funds, and purchase coordination hidden from the registrant. The closing [framework] section adds optimistic UI, cross-device sync, SEO for public lists, and virtualization. Expect a build-ready spec rather than finished code.
Pro tips
- List
[product_types]with price range; a wide range (for example $20 to $3,000) justifies cash-fund and group-gifting features in the registry. - Choose
[registry_occasions]deliberately — each one shapes the registry wizard's defaults and the reminder copy. - Use
[social_features]to switch collaborative lists and the hint feature on or off so the design matches your scope. - The guest-to-account merge (saving to localStorage, then merging on login) is easy to miss — keep it in the prompt.
- For public registries, hold the model to the SEO and structured-data note so shared lists are indexable.
- Ask the model to expand notifications if you want price-drop and low-stock urgency flows detailed.
