FamilyWise HQ

View saved version →

---
name: familywise-capture-adjust-meals-groceries
description: Capture or adjust one FamilyWise meal or recipe with canonical category, structured ingredients, meal slots, pairings, add-ons, and reviewable grocery or schedule follow-through. Use when the user asks to save, correct, plan, or shop from a meal. Do not fetch arbitrary URLs or silently apply multiple writes.
---

# Capture or Adjust Meals and Groceries

1. Read saved content and run the duplicate check before a save or category correction.
2. Keep `foodCategory` separate from `mealSlots`. Ingredients are separate bounded items, never one semicolon-delimited blob. Preserve pairings and add-ons appropriate to the selected category.
3. FamilyWise does not fetch a recipe page or image URL. Use only text the user supplied or approved in this chat; direct meal-image transfer is unavailable in this connector version.
4. Preview one save or update with its exact Home and fields, then wait for explicit confirmation.
5. Re-read the saved record. Derive grocery candidates only from returned structured ingredients, preview each list change, and confirm each granular write.
6. Stop on duplicate, stale version, wrong Home, unknown result, or a protected-data request.

Referenced files: 1

View saved version →

---
name: familywise-family-briefing
description: Summarize a requested date range from source-backed FamilyWise meals, events, lists, routines, reminders, and allowed busy-time context. Use when the user asks for a family briefing, weekly overview, or what is on the FamilyWise plan. Do not use for medical, custody, private-note, or background-monitoring requests.
---

# Family Briefing

Read only the requested Home and date range. Use meal plan, planning context, saved content, and household operations only when each source is relevant.

Return a concise briefing with:

- the date range and source freshness;
- scheduled meals and missing meal rows;
- FamilyWise events and allowed busy windows;
- open routines, reminders, tasks, and relevant lists;
- information that is absent, stale, or unavailable.

Separate returned facts from suggestions. Never claim complete knowledge, infer medical or custody needs, expose private profile fields, or make a change from this skill.

Referenced files: 1

View saved version →

---
name: familywise-get-started
description: Guide a FamilyWise Plus or Premium customer from current source-backed setup status to a useful first week. Use when the user asks to set up FamilyWise, continue onboarding, connect a Home, or learn the next setup step. Do not use for a one-off read or for protected member, invitation, health, custody, or account setup.
---

# Get Started

Build a useful first FamilyWise week without creating parallel onboarding state.

1. Call `familywise_get_setup_status`. If the result says a shared Home is required, route the customer to FamilyWise Account & Sharing and stop. Never collect member or invitation data in chat.
2. Explain only the returned `nextSafeStep` and incomplete sections. Do not infer completeness from conversation history.
3. For an ordinary planning step, call the matching read tool, show one exact proposed change, and wait for explicit confirmation before calling the granular write tool.
4. Re-read the affected record and setup status after each confirmed change.
5. Stop on wrong Home, insufficient role, stale version, missing confirmation, unknown result, or a request for protected profile data.

There is no batch setup write. Home creation, invitations, birthdates, exact ages, allergies, health information, medications, custody details, and private notes stay in FamilyWise HQ.

Referenced files: 1

View saved version →

---
name: familywise-plan-the-week
description: Review and plan a requested FamilyWise week using current meals, events, routines, reminders, lists, and allowed busy-time context. Use when the user asks to plan, fill, adjust, or review a week. Do not use for medical planning, unapproved calendars, or autonomous batch changes.
---

# Plan the Week

1. Call `familywise_get_meal_plan` for the requested dates and `familywise_get_planning_context` when ordinary schedules, events, or opted-in busy times matter.
2. State the exact Home, date range, freshness, missing rows, and unavailable context.
3. Propose one granular meal, component, event, list, routine, or reminder change at a time. Use only returned IDs, versions, and memberRef values.
4. Show the exact effect and ask for confirmation in a separate turn. Use a fresh idempotency key only after confirmation.
5. Re-read the changed record. Stop on conflict, wrong Home, denied role, unknown result, or any protected-data request.

Do not claim the plan found everything the family forgot and do not run in the background.

Referenced files: 1

View saved version →

---
name: familywise-review-what-needs-attention
description: Identify what may need attention based only on current FamilyWise setup, meals, lists, events, routines, reminders, and allowed schedule context. Use when the user asks what needs attention, what is missing, or what to review. Do not claim complete knowledge or monitor proactively.
---

# Review What Needs Attention

Use the exact heading **What may need attention based on FamilyWise data**.

1. Read setup status and only the FamilyWise sources relevant to the requested dates.
2. Report missing meal rows, incomplete setup sections, open routines or reminders, and list or schedule gaps only when the returned records support them.
3. State unavailable or stale data explicitly.
4. Label any suggested next step as advice.

Do not claim that everything forgotten was found. Do not create an opaque score, background job, notification, or write. Do not infer health, medical, custody, or private household concerns.

Referenced files: 1