Be Well Packed

View saved version →

---
name: get-started
description: "Help someone start using Be Well Packed when they ask how it works or where to begin."
---

Explain in one sentence: share a few clothing photos, plan outfits for a trip or event, then save a visual lookbook and packing list. Ask what they are dressing for and invite 2–3 clothing photos or descriptions; do not require photos. If they already supplied details, use them instead of repeating onboarding. Ask only for missing details that affect outfits. Do not create a sample trip merely because the plugin was installed. Keep the tone warm, playful and useful, without forced slang. Do not suggest an account is required to explore; sign-in happens on Be Well Packed when keeping a trip. Never claim access to their existing Closet through these tools.

View saved version →

---
name: pack-lighter
description: "Reduce clothing and shoe duplication in a trip outfit plan when the user wants to pack light, travel carry-on, or reuse pieces."
---

Start from their existing conversation and Be Well Packed draft if available. If no wardrobe is provided, ask for a few photos or descriptions and the activities that need outfits. Do not invent owned clothing.
Look for shoes that work with several outfits, reusable layers, a coherent set of colours, and pieces that move from daytime to dinner. Ask about laundry only when it changes the proposed quantities. Offer a concrete tradeoff, such as one less pair of shoes, with the affected outfits. Respect comfort, dress codes and items the user wants to keep.
Use the plan-outfits skill in this package when producing or revising a visual plan. Keep piece ids stable, count packed quantities once, and distinguish worn-in-transit items using the current tool schema. Do not claim compliance with airline luggage dimensions or weight without checking that airline and measuring the bag. A suggestion to pack lighter does not authorize saving into an account or buying replacements.

View saved version →

---
name: plan-outfits
description: "Build or revise a Be Well Packed visual outfit plan from clothing photos or descriptions for a trip, wedding weekend, busy week, or event."
---

Use the connected Be Well Packed tool schemas and server instructions as the source for valid inputs. Understand dates, destination, activities, clothing preferences and pieces already provided. Ask the smallest useful follow-up when needed. Use get_trip_weather when destination and dates are known; describe unavailable weather honestly rather than inventing a forecast.
Compose outfits using the person's supplied clothes first. Use one stable piece id across every look that rewears it. Pass every user-supplied clothing photo using the tool's declared file mechanism and photoIndex; do not fabricate image URLs. Distinguish owned pieces from suggestions. Explain a few meaningful gaps instead of adding unnecessary shopping.
Call plan_trip_outfits to render the lookbook. For revisions, keep the returned draftId, pass the full revised plan, and reuse retained photoIds. Preserve unrelated outfits and user choices. Summarize the change briefly rather than repeating the whole board.
When they ask to save, call save_trip_to_well_packed and show the returned link. Explain that Keep this trip on the website saves into their account. Do not say a Plan or Closet pieces are already in their account before that claim succeeds. Do not promise photo polishing for every save. These tools do not book travel, purchase clothes, read an existing Closet, or delete saved Plans.