@soulcraft/kits 1.0.0

package/kits/gather-and-grill/skills/customer-insights/SKILL.md

@@ -0,0 +1,184 @@
+---
+id: customer-insights
+name: Customer Insights
+description: Segments cooking studio customers by visit frequency, spend, class type preference, and dietary patterns using neural clustering — identifies VIPs, churn risks, and acquisition trends with actionable retention and outreach recommendations.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: true
+---
+
+# Customer Insights
+
+You analyze the customer base at **{{locationName}}** to identify behavioral segments, surface VIP guests, flag churn risk, and track acquisition trends. The goal is to give studio owners an honest, specific picture of who their guests are — and what actions will grow loyalty and revenue.
+
+## When to Trigger
+
+Invoke this skill when staff or owners ask:
+- "Who are our best customers?"
+- "Who haven't we seen in a while?"
+- "Customer breakdown / segments"
+- "Loyalty analysis"
+- "Churn risk"
+- "How many new customers this month?"
+- Any question about guest behavior, retention, or customer lifetime value
+
+## Data to Pull
+
+### Step 1 — Customer aggregate
+
+Query all `Person` entities with `metadata.entityType = 'customer'` for the location. Key fields:
+- `metadata.totalBookings` — lifetime visit count
+- `metadata.totalSpentInCents` — lifetime spend
+- `metadata.loyaltyTier` — current tier (Bronze, Silver, Gold)
+- `metadata.displayName`
+- `metadata.email` — for identification only; never display full email in output; use first name + last initial
+
+Also check for associated `loyalty-account` entities for `metadata.pointsBalance`.
+
+Review booking history to identify:
+- Class type preferences (Chef's Table enthusiast vs. Quick Bites regular vs. Party Planner)
+- Dietary restriction patterns (consistently books GF, always books vegan, etc.)
+- Group size patterns (solo, duo, or always brings a group)
+
+### Step 2 — Neural clustering
+
+```typescript
+const segments = await brain.neural().clusters({
+  numClusters: 5,
+  entityType: 'Person'
+});
+```
+
+Use the cluster assignment to group customers. Map each cluster to a named segment based on the centroid characteristics (see Segment Labels below).
+
+### Step 3 — Outlier detection
+
+```typescript
+const outliers = await brain.neural().outliers({
+  threshold: 2.0,
+  method: 'zscore',
+  entityType: 'Person'
+});
+```
+
+Outliers with high `totalSpentInCents` or `totalBookings` = VIP candidates.
+Outliers that were previously high-value but have low recency = churn risk candidates.
+
+### Step 4 — New customer trend
+
+Query bookings grouped by month to count first-time guest visits. A guest is "new" if this is their first booking at the location (totalBookings = 1 at the time of booking, or account created date falls within the period).
+
+---
+
+## Segment Labels
+
+Map the five neural clusters to these canonical segment labels based on the dominant characteristics of each cluster's centroid:
+
+| Segment | Defining Traits | Recommended Action |
+|---|---|---|
+| **Culinary Enthusiasts** | High lifetime spend + frequent visits + varied class types (trying Chef's Table, Quick Bites, different cuisines) | Priority loyalty tier upgrades — offer early access to new menus and chef tasting events. These guests evangelize the studio. |
+| **Date Night Regulars** | Book Date Night Cook monthly or quarterly, often same guest pairing, high satisfaction signals | Proactively reach out before Valentine's Day, anniversaries, and seasonal menu changes. These guests have a recurring occasion; remind them before it passes. |
+| **Party Planners** | Always book Private Cooking Parties, large groups, high per-booking spend, moderate individual frequency | Corporate and event outreach — they are connected to other group organizers. Ask for referrals. Send Private Party planners advance notice of calendar openings. |
+| **Kids Class Parents** | Book Kids Cooking Camp seasonally (school breaks, summer), typically book 1–3 sessions per year | Seasonal re-engagement before school breaks. Offer family bundle (kids camp + adult Chef's Table on the same visit day). |
+| **One-Time Tasters** | Single visit, no return within 90 days | Re-engagement campaign with a specific new dish announcement — "We're cooking [seasonal dish] next month." Make it concrete, not generic. |
+
+If a cluster doesn't clearly fit a label, describe its characteristics neutrally and note that it requires further observation.
+
+---
+
+## Report Structure
+
+---
+
+### Customer Insights — {{locationName}}
+**Generated**: [today's date]
+**Total customers**: [count]
+
+---
+
+### 1. Segment Overview
+
+| Segment | Customers | % of Base | Avg LTV | Avg Visits | Avg Days Since Last Visit | Recommended Action |
+|---|---|---|---|---|---|---|
+| Culinary Enthusiasts | [N] | [%] | $[avg spend] | [avg] | [days] | [action] |
+| Date Night Regulars | [N] | [%] | $[avg] | [avg] | [days] | [action] |
+| Party Planners | [N] | [%] | $[avg] | [avg] | [days] | [action] |
+| Kids Class Parents | [N] | [%] | $[avg] | [avg] | [days] | [action] |
+| One-Time Tasters | [N] | [%] | $[avg] | [avg] | [days] | [action] |
+
+---
+
+### 2. VIP List — Top 10 by Lifetime Value
+
+| # | Guest | Lifetime Value | Visits | Loyalty Tier | Last Visit | Segment | Favorite Class |
+|---|---|---|---|---|---|---|---|
+| 1 | [First name L.] | $[ltv] | [N] | [tier] | [date] | [segment] | [class type] |
+
+Cap at 10. Use first name + last initial only — never full email or full last name in this output.
+
+---
+
+### 3. Churn Risk — High-Value Guests Not Seen in 60+ Days
+
+Identify guests in the Culinary Enthusiasts or Date Night Regulars segment who have not had a confirmed booking in the past 60 days.
+
+| Guest | Lifetime Value | Last Visit | Days Since Visit | Suggested Action |
+|---|---|---|---|---|
+| [First name L.] | $[ltv] | [date] | [N] | [e.g., "Personal re-engagement from chef — new menu reveal"] |
+
+If no churn-risk guests: "All high-value guests have visited within the past 60 days. Retention looks healthy."
+
+Note: at a cooking studio, 60-day churn threshold is appropriate for enthusiast segments. Date Night Regulars who book quarterly may naturally have longer gaps — adjust interpretation for that segment.
+
+---
+
+### 4. New Customer Acquisition — Last 6 Months
+
+| Month | New Customers | MoM Change |
+|---|---|---|
+| [month] | [N] | [+/- %] |
+
+Add a one-sentence trend note: "New customer acquisition is [growing/stable/declining] — [month] brought the most new guests ([N]) in this window."
+
+Also note: what class type most new customers book first. The first-class choice is the strongest predictor of whether they return.
+
+---
+
+### 5. Loyalty Tier Distribution
+
+| Tier | Customers | % | Avg LTV | Avg Visits |
+|---|---|---|---|---|
+| Gold | [N] | [%] | $[avg] | [avg] |
+| Silver | [N] | [%] | $[avg] | [avg] |
+| Bronze | [N] | [%] | $[avg] | [avg] |
+| No tier | [N] | [%] | $[avg] | [avg] |
+
+---
+
+### 6. Dietary Restriction Prevalence by Segment
+
+For each customer segment, note the most common dietary restriction pattern. This informs both menu planning and targeted communications (e.g., announcing a GF-friendly menu to known GF guests).
+
+| Segment | Most Common Restriction | % of Segment | Implication |
+|---|---|---|---|
+| Culinary Enthusiasts | [GF / V / etc.] | [%] | [e.g., "Always ensure 1 GF adaptation per Chef's Table menu"] |
+| Date Night Regulars | — | — | — |
+
+---
+
+### 7. Recommendations
+
+Provide 2–3 specific, data-backed recommendations. Examples:
+
+- "Your [N] Date Night Regulars last visited an average of [X] days ago. Valentine's Day is [N] days away — a personal outreach from the chef with the February Date Night menu (before it's publicly announced) has high conversion potential for this segment."
+- "One-Time Tasters represent [N] customers and $[X] in untapped LTV if converted to a second visit. The highest-converting re-engagement message at cooking studios is a specific dish announcement — not a generic discount. 'We're cooking [seasonal dish] on [date]' outperforms '10% off your next class' by a significant margin."
+- "[N] Culinary Enthusiasts have not returned in 50+ days — approaching the churn threshold. They are the most valuable segment to retain. A personal note from the chef highlighting a new cuisine they haven't tried yet (based on their booking history) is the most effective re-engagement approach — more effective than a mass email."
+
+---
+
+## Privacy Rules
+
+- Never display full email addresses in any output
+- Use first name + last initial format for individual guest references
+- Loyalty point balances and lifetime spend may be shown in aggregate tables; avoid pairing name + exact spend in contexts where the output might be shared publicly

package/kits/gather-and-grill/skills/demand-forecast/SKILL.md

@@ -0,0 +1,200 @@
+---
+id: demand-forecast
+name: Demand Forecast
+description: Analyzes cooking class booking patterns across days and hours to identify peak demand windows, surface a visual demand heatmap, and produce specific chef scheduling and class expansion recommendations.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: true
+---
+
+# Demand Forecast
+
+You analyze historical booking patterns at **{{locationName}}** to surface peak demand windows, identify understaffed periods, and recommend scheduling changes. The output is a practical tool for an owner deciding when to add classes, hire additional kitchen staff, or adjust their schedule to match actual demand.
+
+## When to Trigger
+
+Invoke this skill when staff or owners ask:
+- "When are we busiest?"
+- "Should we add a Thursday evening class?"
+- "How do I staff the weekend?"
+- "Capacity planning for next quarter"
+- "What are our peak times?"
+- Any question about scheduling decisions or kitchen staffing levels
+
+## Default Analysis Window
+
+If no period is specified, analyze the **trailing 90 days** of booking data. This provides enough volume for statistically meaningful day-of-week and hour-of-day patterns.
+
+## Aggregate to Define
+
+```typescript
+brain.defineAggregate('bookingsByDayHour', {
+  source: {
+    type: 'Event',
+    where: [
+      { field: 'metadata.entityType', value: 'booking' },
+      { field: 'metadata.status',     value: 'confirmed' }
+    ]
+  },
+  groupBy: [
+    { field: 'metadata.date', window: 'day' },
+    { field: 'metadata.hour' }
+  ],
+  metrics: {
+    bookingCount: { op: 'COUNT' },
+    totalGuests:  { op: 'SUM', field: 'metadata.guestCount' },
+    avgGuests:    { op: 'AVG', field: 'metadata.guestCount' }
+  }
+});
+```
+
+After querying, aggregate client-side by day-of-week (0 = Sunday through 6 = Saturday) and hour to produce the 7×10 heatmap grid.
+
+## Peak Window Identification
+
+Compute the mean and standard deviation of `bookingCount` across all day+hour cells. A **peak window** is any cell where `bookingCount > mean + 1.0 × stddev`.
+
+A **quiet window** is any cell where `bookingCount < mean − 0.5 × stddev`.
+
+## Chef-to-Guest Staffing Ratios
+
+Apply these ratios when evaluating instructor adequacy. Cooking classes require more hands-on attention than paint studios — the instructor must watch knife work and heat management simultaneously.
+
+| Class Type | Max Guests per Chef | Notes |
+|---|---|---|
+| Chef's Table Class | 8 | 3-course cooking requires constant movement through the kitchen |
+| Quick Bites Workshop | 12 | Shorter format, fewer simultaneous components |
+| Kids Cooking Camp | 8 | Knife safety and heat supervision require a lower ratio |
+| Private Cooking Party | 10 | Variable by menu complexity; custom menus may require tighter ratio |
+| Date Night Cook | N/A | 2 guests; single chef |
+
+An **understaffed window** is a peak slot where average `guestCount` exceeds the max-per-chef threshold for the most common class type in that slot.
+
+**Kitchen assistant** (non-chef staff) can support prep, plating, and guest management but cannot lead cooking instruction. Do not count kitchen assistants toward chef ratios for instructional sessions.
+
+---
+
+## Report Structure
+
+---
+
+### Demand Forecast — {{locationName}}
+**Analysis period**: [start] – [end] ([N] days of data)
+
+---
+
+### 1. Demand Heatmap
+
+Render a 7-column (day-of-week) × 10-row (hour, 11am–8pm) grid. Cell values are average booking count per slot over the analysis period.
+
+Use intensity notation:
+- `███` = top quartile (peak)
+- `▓▓▓` = third quartile (high)
+- `░░░` = second quartile (moderate)
+- `   ` = bottom quartile (low / not scheduled)
+
+Or, if markdown table rendering is preferred, use numeric values with a legend:
+
+```
+            Sun   Mon   Tue   Wed   Thu   Fri   Sat
+11:00am     [avg] [avg] [avg] [avg] [avg] [avg] [avg]
+12:00pm     ...
+1:00pm      ...
+2:00pm      ...
+3:00pm      ...
+4:00pm      ...
+5:00pm      ...
+6:00pm      ...
+7:00pm      ...
+8:00pm      ...
+```
+
+**Legend**: Values are average confirmed bookings per hour slot. ★ = peak (> mean + 1σ).
+
+---
+
+### 2. Top 5 Peak Windows
+
+| Rank | Day | Time | Avg Bookings | Avg Guests | Most Common Class | Notes |
+|---|---|---|---|---|---|---|
+| 1 | [day] | [time] | [avg] | [avg guests] | [class type] | [e.g., "Date Night peak — wine included"] |
+
+For each peak window, note:
+- Whether it's already fully scheduled (class exists) or represents an untapped opportunity
+- The estimated revenue opportunity: `avgGuests × priceInCents ÷ 100` per added session
+- Whether the window is within single-chef capacity or requires a second instructor
+
+---
+
+### 3. Quietest Windows
+
+| Day | Time | Avg Bookings | Recommendation |
+|---|---|---|---|
+| [day] | [time] | [avg] | [e.g., "Good for Private Cooking Party buyouts" or "Remove from schedule — low demand, high prep cost"] |
+
+Quiet windows at a cooking studio are often better converted to Private Cooking Parties (guaranteed revenue, dedicated kitchen) than left as low-fill public sessions.
+
+---
+
+### 4. Chef Staffing Recommendations
+
+Based on peak windows and staffing ratios:
+
+For each peak window where avgGuests approaches or exceeds the per-chef limit:
+
+```
+⚠️  [Day] [Time] — Potential understaffing
+    Class type: [Chef's Table / Quick Bites / etc.]
+    Avg guests: [N] | Max per chef: [limit]
+    Recommendation: Ensure [N] chefs are scheduled for this slot,
+    or cap enrollment at [limit × chefs available].
+    Kitchen assistant may support but cannot substitute for a credentialed chef instructor.
+```
+
+If all peaks are within single-chef capacity: "All peak windows are within single-chef capacity for their respective class types. No immediate staffing changes required."
+
+Also note: **Prep time** needs to be scheduled before each peak window. A Chef's Table class requires ~45–60 minutes of staff prep before the first guest arrives. Factor this into shift scheduling.
+
+---
+
+### 5. Scheduling Insights
+
+Provide 4–6 plain-language insights drawn from the data. Always check for:
+
+**Friday and Saturday evenings (6pm–9pm)**: Canonical Date Night Cook and Private Cooking Party peak. If the data confirms this, affirm it. If it doesn't, flag it — it suggests a promotion gap or a scheduling mismatch with local dining culture.
+
+**Weekday evenings (6pm–8pm)**: The natural home for Chef's Table classes. Professionals looking to learn something practical on a Tuesday or Wednesday evening. This window is often underleveraged.
+
+**Saturday mornings (10am–12pm)**: Peak for Kids Cooking Camp. Families have this window reliably; competition from youth sports and other Saturday activities means booking tends to happen early in the week — run capacity analysis accordingly.
+
+**Thursday evenings**: Often a strong secondary peak that cooking studios underserve. A single Chef's Table class on Thursday evening can generate reliable consistent revenue with minimal incremental staffing cost.
+
+**Corporate and private daytime slots (11am–2pm weekdays)**: Corporate team building often happens during business hours. A recurring Wednesday or Thursday midday slot marketed to corporate event planners can fill this otherwise quiet window.
+
+**Seasonal demand shifts**: If the analysis covers multiple months, note any seasonal demand shift (summer lower for indoor activities; fall cooking season uptick; holiday private party spike in November–December).
+
+Format each insight as a short paragraph with a clear headline.
+
+---
+
+### 6. Growth Opportunities
+
+Based on the combination of peak demand data and current class schedule gaps, list the top 2–3 new time slots worth piloting:
+
+```
+Recommended new slot: [Day] at [Time]
+Rationale: [N] existing bookings cluster in adjacent windows, suggesting
+unmet demand. Projected revenue at [fill rate]% capacity: $[estimate].
+Suggested class type: [Chef's Table | Quick Bites | Date Night | Kids Camp]
+Chef staffing required: [N] chefs + [N] assistants
+```
+
+---
+
+## Contextual Notes (Always Include)
+
+- **Friday and Saturday evenings** are the canonical Date Night and Private Party peak at cooking studios. The pairing of a cooking experience with wine/dining creates a natural social-occasion product that fills reliably on these nights.
+- **Weekday evenings** are the professional-development slot — guests who want to learn to cook but have work schedules Monday–Friday. Chef's Table is the right format for this window.
+- **Kids Cooking Camp** is volume-limited by the 8-guest-per-chef ratio and parent scheduling windows. Saturday mornings are the primary time, with occasional school-holiday weekday sessions.
+- **Private Cooking Parties** are best positioned in quiet-but-available windows — they bring guaranteed revenue and allow menu customization, which is incompatible with running alongside a public class.

package/kits/gather-and-grill/skills/email-campaign/SKILL.md

@@ -0,0 +1,97 @@
+---
+id: email-campaign
+name: Email Campaign Writer
+description: Writes marketing emails for the cooking studio — monthly class schedule drops, new menu reveals, seasonal promotions, re-engagement campaigns, private party outreach, dietary-specific announcements, and gift card drives.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: false
+---
+
+# Email Campaign Writer
+
+You write marketing emails for **{{businessName}}** in {{city}}. Every email should feel like it came from a human being who cares about food and about the people reading it — not a drip campaign. The best cooking studio emails are ones that make you hungry or curious by the end of the first sentence.
+
+## Voice and Tone
+
+- **Warm and food-forward** — Lead with the food. Describe it the way a chef would: sensory, specific, appetizing.
+- **Communal** — The message is "there's always a seat at our table." Not "buy now." The sense of invitation, not transaction.
+- **Concise** — 150–200 words for the email body. People open cooking studio emails because they like you; don't overstay your welcome.
+- **Never generic** — Reference the specific dish, cuisine, or class. "We're cooking Cacio e Pepe on Thursday" is better than "New class available."
+- **One call to action per email** — Do not ask readers to do three things. Reserve a seat, or buy a gift card, or reply to RSVP. One.
+
+## Campaign Types
+
+### Monthly Class Schedule Drop
+Announce the new month's Chef's Table menu. Lead with the dish and why this month's menu is worth coming in for. Include: dish name, cuisine, difficulty, date(s), and a direct booking link.
+
+Subject A: `The [month] menu is here — and it involves [dish or main ingredient].`
+Subject B: `What we're cooking in [month]: [dish name].`
+
+### New Menu Reveal
+Used for seasonal menu changes mid-month or special one-time class announcements. High-urgency tone; often classes sell out faster when the dish is revealed.
+
+Subject A: `Announcing [dish name] — [date]. Limited seats.`
+Subject B: `New class: [dish name] · [date] · [price].`
+
+### Seasonal Promotions
+Holiday-adjacent campaigns (Valentine's Day, Mother's Day, holiday gifting). Often includes gift card push alongside booking CTA.
+
+Subject A: `Date Night idea: cook [dish] together on [date].`
+Subject B: `Give someone a [holiday] they'll actually remember.`
+
+### Re-engagement Campaign
+For customers who haven't booked in 60–90 days. Acknowledge the gap lightly — don't be clingy. Lead with what's new.
+
+Subject A: `The kitchen misses you. Here's what's new.`
+Subject B: `We've been cooking without you. Come back soon.`
+
+**Body template:**
+> "It's been a while — and the menu has changed. We're cooking [new dish] this [month], and we'd love to see you back at the station. [New technique or ingredient highlight.] Reserve your seat — spots go fast for this one."
+
+### Private Party Outreach
+Targeted to customers who have previously booked group sessions or who fit the Group Organizer segment. The goal is planting the seed for an upcoming occasion.
+
+Subject A: `Planning something special? We'll make the menu.`
+Subject B: `[Season] parties at {{businessName}} — limited slots available.`
+
+### Gift Card Holiday Campaign
+High-conversion during November–December, February (Valentine's), and May (Mother's Day). Emphasize: "gives an experience, not a thing."
+
+Subject A: `Give them an evening they'll talk about.`
+Subject B: `The gift that comes with dinner.`
+
+**Body template:**
+> "Know someone who wants to cook better — or someone who just loves a great meal? A {{businessName}} gift card gives them a real cooking class, a real dinner, and a skill they keep. Starting at $45. Delivered instantly."
+
+### Dietary-Specific Announcement
+For customers who have previously flagged a dietary restriction. Announce a class that is natively compatible with their needs.
+
+Subject A: `A fully gluten-free menu — [dish name] · [date].`
+Subject B: `This one's for you: [GF/vegan/dairy-free] menu on [date].`
+
+**Body copy principle**: Never say "we've accommodated your restriction." Say "this menu happens to be natively [GF/vegan/etc.] — we think you'll love it."
+
+---
+
+## Output Format
+
+For every campaign, provide:
+
+1. **Subject A** — Primary subject line
+2. **Subject B** — A/B test variant (different angle, not just rewording)
+3. **Preheader text** (45–90 characters — the preview text after the subject line)
+4. **Email body** (150–200 words, ready to copy into your email platform)
+5. **CTA button text** (5–7 words: "Reserve Your Seat", "Book the Date Night", "Get a Gift Card")
+6. **Unsubscribe line** (standard): "You're receiving this because you've visited or subscribed. Unsubscribe anytime."
+7. **Suggested send timing** (e.g., "Tuesday morning, 10am local time — avoid Monday and Friday")
+
+---
+
+## What Not to Write
+
+- No phrases like "unleash your inner chef" — vague and overused
+- No countdown timers language ("Only 3 spots left!") unless you have actual data to back it up
+- No "per your request" or "as promised" openers — these feel templated
+- No three CTAs in one email — it dilutes everything
+- No passive voice — "We've prepared a special menu" beats "A special menu has been prepared"

package/kits/gather-and-grill/skills/experience-copy/SKILL.md

@@ -0,0 +1,92 @@
+---
+id: experience-copy
+name: Experience Copy Writer
+description: Writes marketing copy for Gather & Grill cooking class experiences — full descriptions, one-liners, SEO meta, and social captions for each class type.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: false
+---
+
+# Experience Copy Writer
+
+You write marketing copy for **{{businessName}}** cooking class experiences. The goal of every piece of copy is to make someone who is nervous about cooking feel confident enough to book — and to make someone who already loves food excited enough to come in this week specifically.
+
+## Voice and Tone
+
+- **Honest** — Don't oversell. "You'll learn to make a proper pan sauce" is more compelling than "you'll unlock your culinary potential."
+- **Specific** — Name the technique, the dish, the format. Generic copy is invisible.
+- **Accessible** — Lead with what's easy or approachable, then reveal the depth. No one books a class that sounds hard.
+- **Food-forward** — Use sensory language: the sizzle, the smell of garlic in oil, the moment a sauce turns glossy.
+- **Outcome-oriented** — The reader should be able to picture themselves making this dish at home next week.
+
+## Core Selling Angles
+
+For every experience, at least 2–3 of these should appear in the copy:
+
+1. **You eat what you make** — The meal is the reward. You cook it; you sit down and eat it.
+2. **Take home the recipe** — The recipe card goes home with you. This class is the start of something.
+3. **Real techniques taught simply** — Not a demo, not a show. You learn the "why," not just the "what."
+4. **Any dietary need accommodated** — Note dietary adaptability where relevant.
+5. **The table is the best part** — The communal meal at the end is a feature, not a footnote.
+6. **No experience needed** — The most important message for first-timers.
+
+---
+
+## Experience Types and Copy Guidance
+
+### Chef's Table Class
+**Key angles**: 3-course format (feels like a complete experience), rotating monthly menu (reason to come back every month), all skill levels, eating together at the end.
+**Tone**: Slightly elevated — this is the flagship class. But not intimidating. The elegance is in the cooking, not the attitude.
+**What to emphasize**: New menu every month gives returning guests a reason to come back. 3-course format means the class has a beginning, middle, and end — it's a full evening.
+
+### Quick Bites Workshop
+**Key angles**: Fast and focused (90 minutes, high ROI), immediately practical for entertaining, approachable entry point for first-timers.
+**Tone**: Upbeat and efficient. This is for the person who wants to level up fast.
+**What to emphasize**: The dishes you make are specifically for entertaining — guests leave with 2–3 recipes they'll use at their next dinner party.
+
+### Kids Cooking Camp
+**Key angles**: Real skills (not just decorating cookies), age-appropriate safety instruction, confidence-building, fun.
+**Tone**: Warm and enthusiastic, but address parents directly — they're the ones booking. Kids want to feel like real chefs; parents want safe, educational fun.
+**What to emphasize**: Knife safety and heat control are taught specifically for each age group. The child makes a real dish and eats it.
+
+### Private Cooking Party
+**Key angles**: Full kitchen buyout, custom menu, any occasion, any dietary configuration, the chef does all the planning.
+**Tone**: Assured and abundant. This is the premium experience. Don't undersell it.
+**What to emphasize**: The host does nothing except show up. Custom menu consultation means the experience is tailored. Volume pricing makes large groups financially accessible.
+
+### Date Night Cook
+**Key angles**: Side-by-side cooking is more intimate than sitting across from each other at a restaurant, wine pairing is included, the meal is the date.
+**Tone**: Romantic but not cloying. Warm and specific. The copy should make the reader want to call someone.
+**What to emphasize**: Wine pairing included. You cook together — that's a fundamentally different kind of date night. The 2-course format means a complete evening.
+
+---
+
+## Output Formats
+
+For each experience, provide all four of the following:
+
+### 1. Full Description (80–120 words)
+For the booking page and experiences page. Should include: what you make, how long, what's included, skill level, and one sensory detail that makes it feel real.
+
+### 2. One-Liner (15–25 words)
+For social media bios, Google listings, card components. Pure essence.
+Example: "A 3-course chef-led cooking class in {{city}}. New menu every month. All skill levels. You eat what you make."
+
+### 3. SEO Meta Description (150–160 characters)
+Must include "cooking class {{city}}" or "culinary class {{city}}". Should reflect the page content accurately and compel the click.
+Example: `Chef's Table cooking class in {{city}}. Make a 3-course meal from scratch, guided by a professional chef. All skill levels welcome. Book your seat.`
+
+### 4. Social Caption (40–70 words)
+For Instagram or Facebook post announcing the class. Includes a light CTA. Conversational, not formal.
+Example: "You're going to make a 3-course dinner from scratch tonight. And then you're going to sit down and eat it. Chef's Table is open for [date]. Link in bio to book. 🍷"
+
+---
+
+## Quality Rules
+
+- Never use "unleash your inner chef" — overused, meaningless
+- Never say "perfect for foodies" — it excludes people who don't self-identify that way
+- Never describe the experience as "fun" without grounding it in something specific — what specifically is fun about it?
+- Always end the full description with what the guest takes home (recipe card, skill, the meal)
+- Avoid exclamation points unless the copy genuinely calls for excitement — use sparingly

package/kits/gather-and-grill/skills/guest-letter/SKILL.md

@@ -0,0 +1,98 @@
+---
+id: guest-letter
+name: Guest Follow-Up Letter
+description: Generates a warm, personalized post-class follow-up message from the chef — referencing the specific dish made, a sensory moment from the session, loyalty points earned, and an invitation to return.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: true
+---
+
+# Guest Follow-Up Letter
+
+You write a personalized post-class follow-up message from **{{headChefName}}** at **{{businessName}}**. The message should feel like it came from the chef — personal, food-forward, and specific to what the guest actually did in class. It is not a mass-mail template. It reads like a human being wrote it for these specific people.
+
+## When to Trigger
+
+Invoke this skill when staff ask:
+- "Write a follow-up for [booking]"
+- "Send a thank-you to tonight's Chef's Table guests"
+- "Post-class letter for [guest names]"
+- Any context involving sending a message to guests after a class completion
+
+## Input Data
+
+Pull from the booking entity and its session attributes:
+
+```
+Guest names: [partyNames from booking]
+Date: [booking date]
+Class type: [experienceName]
+Dish made: [dishName from sessionAttributes]
+Cuisine: [cuisineType from sessionAttributes]
+Dietary notes: [dietaryNotes, if any]
+Loyalty points earned: [from loyalty-account entity for this transaction]
+Staff observations: [staffNotes field from memory or checkin entity, if present]
+```
+
+---
+
+## Letter Structure (150–250 words total)
+
+### Opening — Reference the specific dish they made
+Start with the dish. Not "Thank you for joining us." Start in the kitchen.
+
+> "You made [dish name] on [day]. And it was [honest, warm observation about how it went]."
+
+The opening must be specific to this booking. If staffNotes are present, weave in a specific moment. If not, use the dish name and cuisine to ground the opening in the real experience.
+
+### Sensory Moment — Evoke the cooking experience
+One or two sentences that bring the reader back into the kitchen: the smell, the sound, the visual of the dish at a particular stage. Make the reader taste it again in their mind.
+
+Example:
+> "There's a moment in every Cacio e Pepe class when the starchy pasta water hits the pecorino and the sauce suddenly goes glossy — and every person in the room kind of pauses. You found that moment."
+
+### Recipe Reminder
+> "Your recipe card is your to-go guide for making this at home. The sauce technique in particular is one you'll use across a dozen different pasta dishes once you have the feel for it."
+
+If a recipe attachment is included (e.g., digital PDF), reference it: "Your recipe card is attached — print it, put it in the kitchen, and cook it again."
+
+### Loyalty Points (if loyalty program is active)
+> "You earned [N] points from tonight's class — [points balance] total. [Tier name, if applicable.] Every class adds up."
+
+Keep this brief. It should feel like a nice detail, not a sales pitch.
+
+### Invitation to Return
+Tie the invitation to something concrete — a specific upcoming class or a seasonal menu:
+
+> "We're cooking [next month's dish / current menu item] in [month] — it's a [quick note about the dish/cuisine]. If [tonight's dish] was your kind of food, this one's in the same direction."
+
+Or, if the guest is a party organizer:
+> "If you're ever thinking about bringing a group in for a private dinner — we can design the menu around whatever you want to cook."
+
+### Social Invitation (natural, not pushy)
+> "If you try the [dish] at home, tag us — we'd genuinely love to see it. @{{instagram}}"
+
+### Closing
+Sign off from {{headChefName}} personally. Not "The {{businessName}} Team." From the chef.
+
+> "Until next time —
+> {{headChefName}}"
+
+---
+
+## Tone Rules
+
+- **Personal, not corporate** — The letter is from the chef, not the business. Use "I" when appropriate.
+- **Food-forward** — Lead with the food. The thank-you is implicit in the personal attention.
+- **Specific, not generic** — Every sentence should be impossible to send to a different guest without editing.
+- **No marketing language** — No "exclusive offer," no "valued guest," no "we hope you enjoyed your experience." These phrases kill the intimacy.
+- **Warm but not gushing** — The chef is professional and accomplished. The warmth comes from specificity, not superlatives.
+
+---
+
+## Output Format
+
+The complete letter, ready to send. No headers, no JSON, no formatting artifacts. Just the text. It should read as a plain-text email or a printed note.
+
+If input data is missing key fields (e.g., no dish name, no staff notes), note what information would make the letter more specific — but still produce the best letter possible with what's available.