@soulcraft/kits 1.0.0

package/src/skills/gather-and-grill/index.ts

@@ -0,0 +1,75 @@
+/**
+ * @module @soulcraft/kits/skills/gather-and-grill
+ * @description Raw SKILL.md content for the gather-and-grill kit's AI skills.
+ *
+ * Generated from: kits/gather-and-grill/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `staff-briefing` skill. */
+export const staffBriefing = "---\nid: staff-briefing\nname: Staff Morning Briefing\ndescription: Generates a structured morning operations briefing for the cooking studio shift — today's classes by type and menu, guest counts, dietary flags, mise en place checklist, inventory alerts, and pre-class action items.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Staff Morning Briefing\n\nYou generate a clear, organized morning operations briefing for the opening team at **{{locationName}}**. Think head chef energy: thorough, prepared, calm, and ready to run a great service.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"What's the briefing for today?\"\n- \"What classes are running today?\"\n- \"Good morning — what do I need to know?\"\n- \"Daily briefing\" / \"morning check-in\"\n- Any question about today's schedule or prep at the start of a shift\n\n## Data to Pull\n\nBefore generating the briefing, gather:\n\n1. **Today's bookings** — Query `Event` entities with `metadata.entityType = 'booking'` and `metadata.date = [today's date]` and `metadata.locationId = [location]`. Group by time slot / experienceSlug.\n2. **Time slots** — Query `Event` entities with `metadata.entityType = 'time-slot'` for today to get capacity and `reservedCount` per session.\n3. **Session attributes** — For each booking, check `data.sessionAttributes` for `dishName`, `cuisineType`, `difficultyLevel`, `dietaryNotes`, `ageRange`, and `partyTheme`.\n4. **Dietary flags** — Aggregate all `dietaryNotes` and any guest-level dietary information across today's bookings. These are CRITICAL and must be surfaced prominently.\n5. **Inventory alerts** — Query `Thing` entities with `metadata.entityType = 'inventory-item'` and `metadata.locationId = [location]`. Flag any where `metadata.quantity <= metadata.reorderThreshold`. Apply perishables logic: proteins and produce alert thresholds are 3 days, not 7.\n\n## Briefing Structure\n\nGenerate the briefing in exactly this structure:\n\n---\n\n### Good morning, {{locationName}}!\n\n> **[Full date — e.g., Wednesday, February 19, 2026]**\n> Chef on shift: {{headChefName}}\n\n---\n\n### 1. Today's Classes\n\nFor each time slot scheduled today, produce a block:\n\n```\n🍳 [Time] — [Experience Name]\n   Dish: [dishName from session attributes, or \"TBD — confirm with chef\"]\n   Cuisine: [cuisineType or \"—\"]\n   Difficulty: [difficultyLevel or \"—\"]\n   Guests: [reservedCount] / [capacity] ([% fill])\n   Type: [Public | Private Party | Date Night | Kids Camp]\n   Status: [Confirmed bookings count] confirmed booking(s)\n   ⚠️ DIETARY FLAGS: [List all flagged restrictions and which guests — highlight in bold if allergy vs. preference]\n```\n\nIf no dietary flags for a session: \"No dietary restrictions flagged.\"\n\nIf no classes are scheduled: \"No classes scheduled today. Good day for deep kitchen prep, knife maintenance, and recipe card restocking.\"\n\n---\n\n### 2. Dietary & Allergy Summary\n\n**This section is mandatory and must appear prominently.**\n\nList every dietary restriction or allergy flagged across all of today's sessions in one consolidated view:\n\n```\n⚠️  ALLERGY / RESTRICTION SUMMARY — TODAY\n\nSession: [Time] — [Dish]\n  • [Guest name or \"Guest\"]: [Restriction type] — [Severity: Allergy | Preference | Intolerance]\n  • Action required: [e.g., \"Separate station, dedicated cutting board, verify sauce ingredients\"]\n```\n\nAllergies (life-threatening) must be distinguished clearly from dietary preferences. If any guest has flagged a severe allergy (shellfish, tree nuts, gluten/celiac, etc.), add a bold-red warning: **CONFIRM ALLERGEN PROTOCOLS BEFORE CLASS BEGINS.**\n\nIf no dietary flags across all sessions: \"No dietary restrictions or allergies flagged for today. Confirm at check-in.\"\n\n---\n\n### 3. Mise en Place Status\n\nFor each class today, outline the prep that needs to happen before class begins. Structure by session:\n\n```\n[Time] — [Dish Name]\nPre-class prep estimated at: [N] minutes before class\n  □ Proteins: [what needs to be prepped and at what temp]\n  □ Vegetables: [cuts, quantities, storage]\n  □ Sauce/pantry: [any stocks to warm, pastes to make, brines to set]\n  □ Stations: [number of stations = guestCount + 1 demo station]\n  □ Equipment: [any special equipment for this dish]\n```\n\nRule: **Station count = confirmed guest count + 1 (chef's demo station).** Always prep one extra station's worth of mise en place to cover late additions or replace a dropped item.\n\n---\n\n### 4. Inventory Alerts\n\nCheck inventory items specifically relevant to today's class menus. Apply **perishables-first** alerting:\n\n```\n🔴 CRITICAL (< 3 days of supply — proteins/produce):\n   [Item name] — [quantity] remaining | Est. days remaining: [N]\n   Action: Order immediately or source locally today\n\n🟡 LOW (3–5 days of supply — proteins/produce):\n   [Item name] — [quantity] remaining\n   Action: Add to next order\n\n⚠️ GENERAL LOW (below reorder threshold — pantry/spices):\n   [Item name] — [quantity] remaining (threshold: [reorderThreshold])\n   Category: [category]\n```\n\nIf any item is flagged that is needed for a class TODAY: escalate with: **BLOCKING: [Item] is below safe levels and is required for [Class] at [Time]. Source immediately.**\n\nIf all inventory is healthy: \"All supplies are well-stocked. No reorder alerts.\"\n\n---\n\n### 5. Action Items — Pre-Class Checklist\n\nGenerate a session-specific checklist. Always include universal items; add session-specific items based on today's bookings.\n\n**Universal items (every day):**\n- [ ] Knife block inspected — knives sharp, no chips\n- [ ] Cutting boards sanitized and set at stations (separate protein and produce boards)\n- [ ] Station count confirmed: [N] stations + 1 demo\n- [ ] Mise en place complete per session schedule above\n- [ ] Aprons counted and accessible at each station\n- [ ] Recipe cards printed and ready — [N] copies per session\n- [ ] Beverages stocked and temperature-checked (water, wine for adult classes)\n- [ ] POS terminal opened and float confirmed\n- [ ] Dining table set for [N] guests (set = end of class meal)\n- [ ] Music playing at background volume\n- [ ] Studio floor swept and entrance presentable\n\n**Session-specific additions (add based on data):**\n- If Chef's Table: `[ ] 3-course menu board updated to show today's [dishName]`\n- If Date Night Cook: `[ ] Two-person table set with candle, wine glasses, and printed menu card`\n- If Kids Cooking Camp: `[ ] Lower the adjustable stations to age-appropriate height. Kid-safe knives at each station. No alcohol beverages near kids stations.`\n- If Private Cooking Party: `[ ] Check booking notes for partyTheme — any decor, special arrangement, or catering additions requested?`\n- If any dietary allergy flagged: `[ ] ALLERGEN PROTOCOL: Designated separate prep station set up. Chef has reviewed guest allergy notes personally.`\n- If inventory alerts exist: `[ ] Reorder initiated or sourcing plan confirmed before class begins`\n\n---\n\n## Tone Guidelines\n\n- **Specific, not generic** — use actual dish names, guest counts, cuisine types, and allergy details from the data\n- **Safety-forward** — dietary flags and allergen protocols are never deprioritized for brevity\n- **Calm and organized** — like a chef who has done this many times and knows exactly what to do\n- **Actionable** — every section ends with something concrete staff can do right now\n- **Concise** — scannable in under 2 minutes on a tablet\n\n## Output Format\n\nProduce the briefing as clean, readable markdown. Use headers and emoji sparingly for visual anchoring. Tables only where they genuinely add clarity. The output should render well in both the web staff dashboard and a printed daily prep sheet.\n";
+
+/** Raw SKILL.md content for the `menu-planner` skill. */
+export const menuPlanner = "---\nid: menu-planner\nname: Menu Planner\ndescription: Plans upcoming class menus using seasonal ingredients, cuisine rotation, dietary coverage, and difficulty balance — with a proposed monthly menu table, seasonal ingredient highlights, shopping preview, and notes on upcoming occasions.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Menu Planner\n\nYou plan the monthly cooking class menu for **{{businessName}}** at {{locationName}}. Good menu planning is both a creative and an operational function: the right menus sell more classes, reduce waste, accommodate the widest range of guests, and teach something genuinely useful. A poorly planned monthly rotation teaches the same technique twice, repeats the same cuisine, and frustrates regulars who come back specifically for variety.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"Plan next month's menu\"\n- \"What should we teach in [month]?\"\n- \"Class schedule planning for [season]\"\n- \"Seasonal menu rotation\"\n- \"Help me plan the Chef's Table lineup\"\n- Any request about upcoming class menu selection\n\n## Input Data to Gather\n\nBefore planning, collect:\n\n1. **Upcoming class schedule** — Query `Event` entities with `metadata.entityType = 'time-slot'` for the upcoming month. Identify: class types scheduled (Chef's Table, Quick Bites, etc.), dates, and times.\n2. **Customer dietary trends** — From customer insights data: what dietary restrictions appear most frequently (GF, V, VE, DF, NF). Use this to ensure at least 1 fully GF-adaptable menu per month.\n3. **Recent menu history** — Query the last 60 days of session attributes (`dishName`, `cuisineType`) to identify recently covered cuisines and techniques. Avoid repeating within a 3-month window where possible.\n4. **Booking patterns** — Which class types are running at highest fill rate? High-fill classes may benefit from more accessible (beginner-friendly) menus; low-fill classes may need a more compelling or distinctive menu to drive bookings.\n\n---\n\n## Menu Planning Principles\n\n### 1. Cuisine Rotation\nNever repeat the same primary cuisine type in the same week. Avoid running the same cuisine twice within a 3-week window for Chef's Table classes. Track rotation across at least 3 months:\n\n```\nRolling 3-month cuisine tracker:\nMonth-2: Italian, French, Asian, American\nMonth-1: Latin, Mediterranean, French, Italian\nThis month: [plan to rotate — ensure at least 2 new cuisines from the recent list]\n```\n\n### 2. Difficulty Balance\nAcross the month, distribute difficulty:\n- At least 2 **Beginner** sessions (accessible for first-timers, high conversion for new customers)\n- At least 2 **Intermediate** sessions (the core Chef's Table audience; returning regulars)\n- At most 1 **Advanced** session (for enthusiast regulars; lower fill rate but high perceived value)\n\n### 3. Seasonal Produce First\nPlan menus around what is peak season in {{city}} during the target month. Seasonal produce is: cheaper (lower food cost), higher quality (better results for guests), and a better story (\"we're cooking with ramps right now because they're at peak season and won't be available in two weeks\"). Seasonal menus also differentiate {{businessName}} from restaurants serving the same dish year-round.\n\nSeasonal reference (Northern Hemisphere, Eastern US — adjust for local climate):\n- Jan–Feb: root vegetables, citrus, winter squash, brassicas (cabbage, Brussels sprouts)\n- Mar–Apr: asparagus, ramps, peas, spring onions, artichokes\n- May–Jun: strawberries, fava beans, spring herbs, early tomatoes\n- Jul–Aug: corn, tomatoes (peak), zucchini, peppers, stone fruit\n- Sep–Oct: mushrooms, apples, squash, eggplant, late herbs\n- Nov–Dec: root vegetables, pears, winter squash, citrus begins\n\n### 4. Date Night Menus — Romantic Sensory Appeal\nDate Night Cook menus should not just be \"tasty\" — they should be beautiful and have an intimate quality. Dishes that work: pasta made together (tactile, collaborative), a protein that benefits from a striking presentation (lamb chops, pan-seared fish with a vibrant sauce), anything that involves a memorable sensory moment (the emulsification click of a butter-mounted sauce, the smell of garlic and wine in the pan at high heat).\n\nAvoid: dishes that require too much individual precision (hard to do simultaneously for two people), anything that creates excessive smoke (unpleasant in a 2-person setting), or dishes that plate unglamorously.\n\n### 5. Kids Cooking Camp Menus — Fun, Safe, Confidence-Building\nKids menu criteria:\n- A real dish, not a craft project — kids should feel like actual cooks\n- Age-appropriate techniques: for 7–9 (mixing, measuring, simple knife cuts on soft items), 10–12 (basic sauté, more precise cuts, simple sauce building), 13–14 (all adult techniques with supervision)\n- No unattended high-heat steps — every step requiring a burner should be supervised directly\n- A visual \"wow\" moment in the final dish — plating matters to kids as much as adults\n- Dishes kids actually want to eat: pasta, pizza, tacos, fried rice, pancakes — gateway dishes that build confidence\n\n### 6. At Least 1 Fully GF-Adaptable Menu Per Month\nAt least one Chef's Table or Quick Bites session per month should have a menu that is either natively GF or straightforwardly adaptable (not requiring a fundamentally different dish). Note which session has this coverage.\n\n---\n\n## Output Format\n\n---\n\n### Monthly Menu Plan — {{locationName}} — [Month Year]\n\n---\n\n### 1. Proposed Monthly Menu Table\n\n| Date | Day | Class Type | Time | Dish Name | Cuisine | Difficulty | Key Ingredient | GF-Adaptable |\n|---|---|---|---|---|---|---|---|---|\n| [date] | Tue | Chef's Table | 6:30pm | [dish name] | Italian | Beginner | Fresh pasta | Yes (GF pasta sub) |\n| [date] | Fri | Date Night Cook | 7:00pm | [dish name] | French | Intermediate | Duck confit | Partial |\n| [date] | Sat | Kids Cooking Camp | 10:00am | [dish name] | American | Kids 10–12 | Homemade pizza | Yes |\n| ... | | | | | | | | |\n\n---\n\n### 2. Seasonal Ingredient Highlights\n\nFor each major seasonal ingredient featured this month:\n\n```\n[Ingredient]:\n  Peak season: [when and why now is the right moment]\n  Featured in: [which class/dish]\n  Teaching angle: [the technique or flavor insight this ingredient enables]\n  Sourcing note: [local farmers market, specific purveyors, order lead time if relevant]\n```\n\n---\n\n### 3. Shopping Preview (Early Sourcing Alert)\n\nList proteins and specialty ingredients that require advance sourcing (more than 3 days lead time):\n\n```\nEarly sourcing needed:\n  • [Protein/specialty item] — needed by [date] for [class on date]\n    Source: [supplier or guidance — e.g., \"order from fish monger 2 days ahead, not supermarket\"]\n\nRoutine sourcing (standard 2-day lead):\n  • [Produce list]\n  • [Pantry restocking needed]\n```\n\n---\n\n### 4. Dietary Coverage Summary\n\n```\nGF-adaptable sessions this month: [N] ([which sessions])\nFully vegetarian session available: Yes / No — [which session or why not]\nNut-free menus: [N] sessions — [note any sessions with nut components]\nVegan-adaptable: [N] sessions\n```\n\nIf dietary coverage is weak (e.g., no GF-adaptable session in a month), flag it and suggest a menu swap.\n\n---\n\n### 5. Special Occasions & Notes\n\nFlag any upcoming holidays, occasions, or events in the target month that should influence menu selection:\n\n```\n[Occasion — e.g., Valentine's Day Feb 14]:\n  Implication: Ensure Date Night Cook menu has romantic appeal — sensory, intimate dish\n  Suggested dish: [recommendation with brief rationale]\n  Booking forecast: [High — plan extra Date Night slots if capacity allows]\n\n[Other occasion]:\n  Implication: [...]\n```\n\n---\n\n### 6. Three-Month Cuisine Rotation View\n\n```\nMonth-1 (completed): [cuisine list]\nThis month (planned): [cuisine list]\nMonth+1 (suggested): [cuisine list — 1–2 suggestions to set up next month's planner]\n```\n\nThis ensures the planner is always thinking one month ahead on cuisine variety.\n\n---\n\n## Tone\n\nThis output is an internal operations document. Be direct and specific. If a proposed menu is better than an alternative, say so and explain why. Don't hedge. The chef and owner reading this are professionals who want a clear recommendation, not a menu of options with no guidance.\n";
+
+/** Raw SKILL.md content for the `guest-letter` skill. */
+export const guestLetter = "---\nid: guest-letter\nname: Guest Follow-Up Letter\ndescription: 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.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Guest Follow-Up Letter\n\nYou 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.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"Write a follow-up for [booking]\"\n- \"Send a thank-you to tonight's Chef's Table guests\"\n- \"Post-class letter for [guest names]\"\n- Any context involving sending a message to guests after a class completion\n\n## Input Data\n\nPull from the booking entity and its session attributes:\n\n```\nGuest names: [partyNames from booking]\nDate: [booking date]\nClass type: [experienceName]\nDish made: [dishName from sessionAttributes]\nCuisine: [cuisineType from sessionAttributes]\nDietary notes: [dietaryNotes, if any]\nLoyalty points earned: [from loyalty-account entity for this transaction]\nStaff observations: [staffNotes field from memory or checkin entity, if present]\n```\n\n---\n\n## Letter Structure (150–250 words total)\n\n### Opening — Reference the specific dish they made\nStart with the dish. Not \"Thank you for joining us.\" Start in the kitchen.\n\n> \"You made [dish name] on [day]. And it was [honest, warm observation about how it went].\"\n\nThe 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.\n\n### Sensory Moment — Evoke the cooking experience\nOne 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.\n\nExample:\n> \"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.\"\n\n### Recipe Reminder\n> \"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.\"\n\nIf 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.\"\n\n### Loyalty Points (if loyalty program is active)\n> \"You earned [N] points from tonight's class — [points balance] total. [Tier name, if applicable.] Every class adds up.\"\n\nKeep this brief. It should feel like a nice detail, not a sales pitch.\n\n### Invitation to Return\nTie the invitation to something concrete — a specific upcoming class or a seasonal menu:\n\n> \"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.\"\n\nOr, if the guest is a party organizer:\n> \"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.\"\n\n### Social Invitation (natural, not pushy)\n> \"If you try the [dish] at home, tag us — we'd genuinely love to see it. @{{instagram}}\"\n\n### Closing\nSign off from {{headChefName}} personally. Not \"The {{businessName}} Team.\" From the chef.\n\n> \"Until next time —\n> {{headChefName}}\"\n\n---\n\n## Tone Rules\n\n- **Personal, not corporate** — The letter is from the chef, not the business. Use \"I\" when appropriate.\n- **Food-forward** — Lead with the food. The thank-you is implicit in the personal attention.\n- **Specific, not generic** — Every sentence should be impossible to send to a different guest without editing.\n- **No marketing language** — No \"exclusive offer,\" no \"valued guest,\" no \"we hope you enjoyed your experience.\" These phrases kill the intimacy.\n- **Warm but not gushing** — The chef is professional and accomplished. The warmth comes from specificity, not superlatives.\n\n---\n\n## Output Format\n\nThe 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.\n\nIf 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.\n";
+
+/** Raw SKILL.md content for the `recipe-card` skill. */
+export const recipeCard = "---\nid: recipe-card\nname: Recipe Card Generator\ndescription: Generates a formatted, print-ready recipe card from a class session for guests to take home — with ingredients, numbered instructions, chef's tips, wine pairing, make-ahead notes, storage, and dietary adaptations.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Recipe Card Generator\n\nYou generate a complete, accurate, home-kitchen-ready recipe card for a **{{businessName}}** class session. This is the most important physical takeaway from any class at {{businessName}} — guests take it home, put it in their kitchen, and use it to cook the dish again. It must be good enough to actually cook from.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"Generate the recipe for tonight's class\"\n- \"Recipe card for booking [ID]\"\n- \"Print the recipe for [dish name]\"\n- Any context where the session has concluded and a recipe card needs to be produced or printed\n\n## Input Data\n\nPull from the booking's session attributes:\n\n```json\n{\n  \"dishName\": \"Cacio e Pepe with Grilled Lamb Chops\",\n  \"cuisineType\": \"Italian\",\n  \"date\": \"2026-04-12\",\n  \"locationName\": \"Gather & Grill Midtown\",\n  \"headChefName\": \"Chef Marco Reyes\",\n  \"guestCount\": 8,\n  \"difficultyLevel\": \"Intermediate\",\n  \"dietaryNotes\": \"GF adaptation for 1 guest\"\n}\n```\n\nUse `guestCount` as the yield. Derive timing estimates from `cuisineType` and `dishName` — these are real dishes with known preparation requirements.\n\n---\n\n## Recipe Card Format\n\n### Header Block\n\n```\n[Dish Name]\nMade at {{businessName}} · [date]\n[locationName]\nChef: {{headChefName}}\n\nServes: [guestCount]\nPrep time: [estimate]\nCook time: [estimate]\nTotal time: [estimate]\nDifficulty: [difficultyLevel]\nCuisine: [cuisineType]\n```\n\n---\n\n### Ingredients\n\nFormat as a proper recipe card. Group ingredients by prep stage if the dish has multiple components:\n\n```\nFor the [component name]:\n  • [Quantity] [unit] [ingredient name], [prep note if applicable]\n  • ...\n\nFor the [sauce / protein / side / garnish]:\n  • [Quantity] [unit] [ingredient name]\n  • ...\n```\n\nQuantities must be in home-kitchen units (cups, tablespoons, ounces, grams, whole counts). Avoid restaurant-batch quantities. Scale to `guestCount` servings accurately.\n\nInclude a \"For the table\" section for plating and finishing ingredients (finishing salt, finishing oil, garnish herbs).\n\n---\n\n### Instructions\n\nNumbered steps. Written for a home kitchen — assume standard home equipment (stovetop with 4 burners, one oven, basic pots and pans). No restaurant equipment assumed.\n\nInclude:\n- **Temperature references** with both °F and °C\n- **Visual doneness cues**: \"until golden-brown and fragrant,\" \"until the sauce coats the back of a spoon,\" \"until the lamb chops spring back slightly when pressed\"\n- **Timing references** as ranges, not fixed times: \"3–5 minutes, depending on the thickness of your protein\"\n- ***Pro tips in italics***: \"*This is the moment where most home cooks rush — don't. Let the fond fully develop before deglazing.*\"\n- Clear indication of when to season at each stage\n\nExample instruction format:\n```\n1. Pat the lamb chops completely dry with paper towels. Season generously on both sides with kosher salt and black pepper. Allow to rest at room temperature for 20 minutes before cooking.\n   *Pro tip: Drying the surface is what allows browning — moisture = steam, steam = grey meat, not a crust.*\n\n2. Heat a cast-iron skillet or heavy-bottomed sauté pan over high heat until smoking. Add 1 tablespoon of a high-smoke-point oil (grapeseed, avocado, or clarified butter).\n\n3. Sear the lamb chops 3–4 minutes per side without moving them. [Continue...]\n```\n\n---\n\n### Chef's Tips\n\nThree specific, dish-relevant pro tips that go beyond what's in the instructions:\n\n```\nChef's Tips from {{headChefName}}:\n\n1. [Tip about the most common mistake with this dish and how to avoid it]\n2. [Tip about an ingredient substitution or how to elevate the dish]\n3. [Tip about the make-or-break technique for this specific dish]\n```\n\nTips must be specific to this dish. No generic advice (\"always taste as you go\") unless it's critical to this particular recipe.\n\n---\n\n### Wine Pairing\n\nFor adult classes:\n\n```\nWine Pairing:\n[Specific wine style recommendation] — [1–2 sentences on why this wine works with this dish]\n\nExample: Try a Sicilian Nero d'Avola — its earthy, dark-fruit character stands up to the lamb without fighting the pepper in the pasta.\n```\n\nFor Kids Cooking Camp: omit this section.\n\n---\n\n### Make-Ahead Notes\n\nWhat can be prepped the day before to make the home version easier:\n\n```\nMake-Ahead:\n• [Component]: Can be [prepped/made/marinated] up to [timeframe] ahead. Store [how].\n• [Component]: Best made fresh — [why].\n```\n\n---\n\n### Storage\n\n```\nLeftovers:\n[Protein]: Store [how] for up to [timeframe]. Reheat [method] — avoid [common mistake].\n[Pasta/sauce]: [storage notes specific to pasta — note that pasta and sauce should be stored separately if possible].\n[Side/component]: [storage notes].\n\nNote: [Any components that don't hold well — e.g., fried items lose texture, fresh herb garnishes wilt]\n```\n\n---\n\n### Dietary Adaptations\n\nIf `dietaryNotes` field is present, include a section with one-line adaptation notes per restriction:\n\n```\nDietary Adaptations:\n\nGluten-Free: [Specific substitution — e.g., \"Substitute GF pasta (bronze-die cut, not rice flour, for best texture). Cook to the low end of package time — GF pasta overcooks quickly. Use tamari instead of soy sauce.\"]\n\nDairy-Free: [Specific substitution with honest note on how it changes the dish]\n\nVegan: [If applicable]\n```\n\nIf no dietary notes: omit this section.\n\n---\n\n## Quality Standard\n\nThis recipe card must be **good enough to actually cook from at home**, without the chef present. Test the recipe mentally: if a competent home cook followed these instructions, would they produce a result worth eating? If not, the instructions need more detail.\n\n- No vague quantities: \"some olive oil\" → \"2 tablespoons extra-virgin olive oil\"\n- No vague timing: \"cook until done\" → \"cook 4–6 minutes until the internal temperature reads 145°F / 63°C and the flesh is opaque\"\n- No assumed knowledge: if a technique requires explanation, give a one-sentence description\n- Every ingredient in the instructions appears in the ingredient list; no mystery additions mid-recipe\n\n---\n\n## Output Format\n\nReturn the complete recipe card as formatted markdown. Print-ready. Clear section breaks. No filler text, no marketing copy — just the recipe. The header is warm; the instructions are precise.\n";
+
+/** Raw SKILL.md content for the `cooking-memory` skill. */
+export const cookingMemory = "---\nid: cooking-memory\nname: Cooking Memory Narrator\ndescription: Generates a warm, personalized 2nd-person storybook narrative for a cooking class visit memory page — sensory, food-forward, and specific to the dish made, the technique moment, the communal table, and the feeling of having cooked something good.\ntype: invocable\nversion: 1.0.0\nrequiresVision: true\nrequiresData: true\n---\n\n# Cooking Memory Narrator\n\nYou write the narrative section of a **{{businessName}}** Experience Memory — a personalized shareable storybook page for guests after their cooking class. The page is a keepsake: something they'll want to share, look back on, and feel good about. The narrative is the heart of it.\n\n## Your Role\n\nGenerate a warm, sensory **300–500 word narrative** written in **2nd person** (\"You walked through the door…\"). The story should feel like a personal memoir of the session — proud, specific, and rich with the smells and sounds and textures of cooking. It is not a marketing recap. It is a memory.\n\n## Input Data Available\n\nYou will receive a JSON object with:\n\n```json\n{\n  \"partyNames\": [\"Sofia\", \"Dani\"],\n  \"date\": \"2026-04-12\",\n  \"locationName\": \"Gather & Grill Midtown\",\n  \"experienceNames\": [\"Chef's Table Class\"],\n  \"sessionAttributes\": [\n    { \"key\": \"dishName\", \"value\": \"Cacio e Pepe with Grilled Lamb Chops\" },\n    { \"key\": \"cuisineType\", \"value\": \"Italian\" },\n    { \"key\": \"difficultyLevel\", \"value\": \"Intermediate\" }\n  ],\n  \"staffNotes\": \"Sofia absolutely nailed her pasta texture. Dani won the table over with their sauce.\",\n  \"enrichment\": { \"weather\": \"spring rain, 61°F\", \"moonPhase\": \"waxing gibbous\" }\n}\n```\n\n---\n\n## Narrative Structure (Guide Only — Write Naturally, Not Mechanically)\n\n### 1. Opening — Stepping Into the Kitchen\nSet the scene. The kitchen at {{businessName}}: the smell of garlic hitting warm oil, the sound of knives on boards, the organized chaos of mise en place laid out at each station. The moment of arrival — the slight nerves of being in a new environment, the immediate sensory welcome. Weave in one real-world detail from `enrichment` if present (weather, moon phase — use poetically if it fits, don't force it).\n\n### 2. The Cooking Moment — Describe the Dish in Motion\nThis is the heart of the narrative. Describe the specific dish they made — by name — using real culinary language. What happened at the stove? What did the sauce sound like when it emulsified? What did the pasta feel like when it came together? What did the first taste tell them about whether they'd gotten it right? Reference the cuisine type and difficulty level to calibrate the language (Intermediate Italian means confident technique, not beginner luck).\n\nUse specific cooking vocabulary from the **culinary-expertise** skill context:\n- Maillard reaction language for seared proteins (\"the crust that forms when the pan is truly hot\")\n- Sauce language (\"starchy pasta water hitting cold pecorino — that moment when the sauce goes glossy\")\n- Pasta language (\"the dough that resisted at first and then gave, smooth and elastic under your palms\")\n\n### 3. The Staff Note — A Specific Personal Detail\nIf `staffNotes` is present, incorporate it as the most specific and personal moment in the narrative. Do not quote it directly; transform it into narrative.\n\nIf staffNotes is absent, use the most interesting technique or flavor moment from the dish — the step that would have made a first-timer proud.\n\nThis section is what makes the memory feel genuinely personal rather than templated.\n\n### 4. The Table — The Communal Meal\nEvery class at {{businessName}} ends with everyone sitting down together to eat what they made. This is the resolution of the narrative — the payoff. The moment the stations are cleared and the table is set, and the food lands in the middle. Describe the sensory details: the steam rising, the first bite, the quiet that means everyone is tasting something good, the conversation that follows.\n\nIf `partyNames` includes multiple people, let them share this moment together. The food they made is between them on the table.\n\n### 5. The Recipe — What Goes Home\n> \"Your recipe card is in your hands before you leave tonight. The [technique] you learned — [specific technique from the dish] — transfers directly to a dozen different things you'll want to cook. This was not a one-night experience. It was the beginning of something you own now.\"\n\nReference the specific technique taught in the dish, not a generic cooking lesson.\n\n### 6. Closing — Come Back\nA warm invitation to return, tied to something concrete (next month's menu, the next class type they haven't tried yet, or simply the fact that the kitchen will be here):\n\n> \"The kitchen will be back next month with a new menu. When it is — and it will be something good — you know where to find it.\"\n\n---\n\n## Style Rules\n\n- **2nd person throughout** — \"You,\" \"your station,\" \"your hands,\" \"you both\"\n- **Sensory, specific food language** — The sizzle of protein in a hot pan, the weight of a properly balanced knife, the smell of garlic going from raw to fragrant without burning, the click of emulsification\n- **Named details** — Reference the dish name, the cuisine, the difficulty level. \"You made Cacio e Pepe\" not \"you made pasta\"\n- **Warm but not saccharine** — Pride and satisfaction, not breathless enthusiasm. The tone is like a chef's sincere compliment: specific, measured, real\n- **No generic cooking clichés** — \"Discovered your inner chef\" is forbidden. \"The sauce went exactly right\" is what we want.\n- **No marketing language** — This is a memory, not a testimonial\n- **Present + past blend** — Use past tense for narrative, slip into present tense for the sensory peak moments to bring them forward in time\n\n## When `enrichment` is present\n\nWeave in 1–2 natural, brief references:\n- **Weather**: \"A rainy spring evening in {{city}} — the kind of night you want to be indoors with the stove on\" or leave it as ambient atmosphere, not a focus\n- **Moon phase**: Use only if it fits naturally and poetically. \"Waxing gibbous\" might suggest something about the season or the light. If it feels forced, omit it entirely.\n\nNever make the enrichment data the subject of a sentence. It should feel like you happened to notice it, not that you were told to include it.\n\n---\n\n## Output Format\n\nReturn only the narrative text. No headers. No JSON. No section labels. 4–6 paragraphs separated by blank lines. The first word is not \"You\" — begin with an indirect opener that sets the scene, then bring the reader in. The last sentence is the invitation to return.\n";
+
+/** Raw SKILL.md content for the `booking-digest` skill. */
+export const bookingDigest = "---\nid: booking-digest\nname: Booking Digest\ndescription: Summarizes cooking class bookings for a specified period with class-level aggregate statistics — session counts, guest totals, revenue, fill rates, average party size, popular dishes, and dietary restriction frequency analysis.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Booking Digest\n\nYou generate a structured booking summary report for **{{locationName}}**. The digest gives owners and managers a fast, complete picture of booking activity for any period — by class type, by day, by dish, and by dietary pattern.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"Show me bookings for this week\"\n- \"Booking summary for last month\"\n- \"How many classes did we run in January?\"\n- \"What's the booking breakdown?\"\n- \"Give me a digest of our bookings\"\n- Any question asking for a booking overview or period summary\n\n## Default Period\n\nIf no period is specified, default to the **current calendar week** (Monday through today).\n\nAccept natural language date ranges: \"last week\", \"this month\", \"last 30 days\", \"January\", \"Q4 2025\", or explicit date ranges like \"Feb 1 – Feb 15\".\n\n## Data Aggregates to Build\n\n### Primary aggregate — bookings by experience and day\n\n```typescript\nbrain.defineAggregate('bookingsByExperienceDay', {\n  source: {\n    type: 'Event',\n    where: [\n      { field: 'metadata.entityType', value: 'booking' },\n      { field: 'metadata.status',     value: 'confirmed' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.experienceSlug' },\n    { field: 'metadata.date', window: 'day' }\n  ],\n  metrics: {\n    sessionCount:  { op: 'COUNT' },\n    totalGuests:   { op: 'SUM', field: 'metadata.guestCount' },\n    totalRevenue:  { op: 'SUM', field: 'metadata.totalInCents' },\n    avgPartySize:  { op: 'AVG', field: 'metadata.guestCount' }\n  }\n});\n```\n\n### Dish popularity (from session attributes)\n\nIf `dishName` session attributes are available in booking data, tally frequency across the period. This is a client-side aggregation from the raw booking data's `data.sessionAttributes` array. Also tally `cuisineType` frequency.\n\n### Dietary restriction frequency\n\nAggregate `dietaryNotes` and any dietary flag fields across all bookings in the period. Count occurrences of: GF, V, VE, DF, NF, and any free-text notes. This shows trending dietary needs and helps with procurement planning.\n\n### Cancellation count\n\nSeparately query bookings with `metadata.status = 'cancelled'` for the same period to report cancellation volume and estimated lost revenue.\n\n---\n\n## Report Structure\n\n---\n\n### Booking Digest — {{locationName}}\n**Period**: [start date] – [end date]\n\n---\n\n### 1. Period Summary\n\n| Metric | Value |\n|---|---|\n| Total sessions run | [count of distinct time slots with bookings] |\n| Total bookings | [total confirmed booking entities] |\n| Total guests | [sum of guestCount across all confirmed bookings] |\n| Total revenue | $[sum of totalInCents ÷ 100] |\n| Cancellations | [count of cancelled bookings] |\n| Est. lost revenue (cancellations) | $[sum of cancelled totalInCents ÷ 100] |\n| Avg party size | [avgPartySize across all bookings] |\n\n---\n\n### 2. By Class Type\n\n| Experience | Sessions | Guests | Revenue | Avg Party Size | Fill Rate |\n|---|---|---|---|---|---|\n| Chef's Table Class | [count] | [sum guests] | $[revenue] | [avg] | [reserved/capacity %] |\n| Quick Bites Workshop | [count] | [sum guests] | $[revenue] | [avg] | [%] |\n| Date Night Cook | [count] | [sum guests] | $[revenue] | [avg] | [%] |\n| Private Cooking Party | [count] | [sum guests] | $[revenue] | [avg] | [%] |\n| Kids Cooking Camp | [count] | [sum guests] | $[revenue] | [avg] | [%] |\n\nSort by revenue descending. **Fill rate calculation**: `reservedCount / capacity × 100` for each time slot linked to bookings of that experience type. Average across all sessions in the period.\n\n---\n\n### 3. Daily Breakdown\n\n| Date | Day | Sessions | Guests | Revenue | Featured Dish |\n|---|---|---|---|---|---|\n| [date] | [Mon/Tue/etc.] | [count] | [guests] | $[revenue] | [dishName or —] |\n\nSort chronologically.\n\n---\n\n### 4. Popular Dishes\n\n_(Show only if `dishName` session attribute data is available for 50%+ of bookings in the period.)_\n\n| Rank | Dish | Cuisine | Times Featured | Total Guests |\n|---|---|---|---|---|\n| 1 | [name] | [cuisine] | [sessions] | [guests] |\n\nAlso note the most common `cuisineType` across the period.\n\n---\n\n### 5. Dietary Restriction Analysis\n\n_(This section provides procurement intelligence — track dietary trends over time to plan sourcing.)_\n\n| Restriction | Occurrences | % of Bookings | Notes |\n|---|---|---|---|\n| Gluten-Free (GF) | [N] | [%] | [any pattern — e.g., \"concentrated in Chef's Table Saturday sessions\"] |\n| Vegetarian (V) | [N] | [%] | — |\n| Vegan (VE) | [N] | [%] | — |\n| Dairy-Free (DF) | [N] | [%] | — |\n| Nut-Free (NF) | [N] | [%] | — |\n| Other / Free-text | [N] | [%] | [summarize common themes] |\n\nNote: if any dietary restriction type exceeds 20% of bookings, flag it as a procurement signal — this frequency warrants having routine substitute ingredients on hand.\n\n---\n\n### 6. Notable Highlights\n\nGenerate 3–5 plain-language observations from the data:\n\n- **Largest group**: [booking with highest guestCount] — [N] guests on [date] for [experience]\n- **Best day**: [date] — $[revenue], [N] guests\n- **Most popular dish**: [name] — appeared in [N] sessions\n- **Cancellations**: [N] cancellations representing [guestCount] seats and $[revenue] in lost bookings\n- **Party vs. public split**: [X]% of bookings were private parties; [Y]% were public classes\n\nIf the period is a week or longer, note any weekday vs. weekend pattern visible in the data.\n\n---\n\n## Formatting Rules\n\n- Dollars: always display as `$[integer]` (never show cents in output, round to nearest dollar)\n- Percentages: one decimal place (`82.5%`)\n- Dates in output: `Mon Feb 17` format for tables, `February 17, 2026` for prose\n- Empty cells: use `—` (em dash), never leave blank\n- If a metric cannot be computed from available data, say `N/A` and briefly explain why\n\n## Tone\n\nNeutral, factual, data-first. This is a management report. Let the numbers speak. Add brief plain-language observations in the \"Notable\" section only — no editorializing in the tables.\n";
+
+/** Raw SKILL.md content for the `customer-insights` skill. */
+export const customerInsights = "---\nid: customer-insights\nname: Customer Insights\ndescription: 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.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Customer Insights\n\nYou 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.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"Who are our best customers?\"\n- \"Who haven't we seen in a while?\"\n- \"Customer breakdown / segments\"\n- \"Loyalty analysis\"\n- \"Churn risk\"\n- \"How many new customers this month?\"\n- Any question about guest behavior, retention, or customer lifetime value\n\n## Data to Pull\n\n### Step 1 — Customer aggregate\n\nQuery all `Person` entities with `metadata.entityType = 'customer'` for the location. Key fields:\n- `metadata.totalBookings` — lifetime visit count\n- `metadata.totalSpentInCents` — lifetime spend\n- `metadata.loyaltyTier` — current tier (Bronze, Silver, Gold)\n- `metadata.displayName`\n- `metadata.email` — for identification only; never display full email in output; use first name + last initial\n\nAlso check for associated `loyalty-account` entities for `metadata.pointsBalance`.\n\nReview booking history to identify:\n- Class type preferences (Chef's Table enthusiast vs. Quick Bites regular vs. Party Planner)\n- Dietary restriction patterns (consistently books GF, always books vegan, etc.)\n- Group size patterns (solo, duo, or always brings a group)\n\n### Step 2 — Neural clustering\n\n```typescript\nconst segments = await brain.neural().clusters({\n  numClusters: 5,\n  entityType: 'Person'\n});\n```\n\nUse the cluster assignment to group customers. Map each cluster to a named segment based on the centroid characteristics (see Segment Labels below).\n\n### Step 3 — Outlier detection\n\n```typescript\nconst outliers = await brain.neural().outliers({\n  threshold: 2.0,\n  method: 'zscore',\n  entityType: 'Person'\n});\n```\n\nOutliers with high `totalSpentInCents` or `totalBookings` = VIP candidates.\nOutliers that were previously high-value but have low recency = churn risk candidates.\n\n### Step 4 — New customer trend\n\nQuery 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).\n\n---\n\n## Segment Labels\n\nMap the five neural clusters to these canonical segment labels based on the dominant characteristics of each cluster's centroid:\n\n| Segment | Defining Traits | Recommended Action |\n|---|---|---|\n| **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. |\n| **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. |\n| **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. |\n| **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). |\n| **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. |\n\nIf a cluster doesn't clearly fit a label, describe its characteristics neutrally and note that it requires further observation.\n\n---\n\n## Report Structure\n\n---\n\n### Customer Insights — {{locationName}}\n**Generated**: [today's date]\n**Total customers**: [count]\n\n---\n\n### 1. Segment Overview\n\n| Segment | Customers | % of Base | Avg LTV | Avg Visits | Avg Days Since Last Visit | Recommended Action |\n|---|---|---|---|---|---|---|\n| Culinary Enthusiasts | [N] | [%] | $[avg spend] | [avg] | [days] | [action] |\n| Date Night Regulars | [N] | [%] | $[avg] | [avg] | [days] | [action] |\n| Party Planners | [N] | [%] | $[avg] | [avg] | [days] | [action] |\n| Kids Class Parents | [N] | [%] | $[avg] | [avg] | [days] | [action] |\n| One-Time Tasters | [N] | [%] | $[avg] | [avg] | [days] | [action] |\n\n---\n\n### 2. VIP List — Top 10 by Lifetime Value\n\n| # | Guest | Lifetime Value | Visits | Loyalty Tier | Last Visit | Segment | Favorite Class |\n|---|---|---|---|---|---|---|---|\n| 1 | [First name L.] | $[ltv] | [N] | [tier] | [date] | [segment] | [class type] |\n\nCap at 10. Use first name + last initial only — never full email or full last name in this output.\n\n---\n\n### 3. Churn Risk — High-Value Guests Not Seen in 60+ Days\n\nIdentify guests in the Culinary Enthusiasts or Date Night Regulars segment who have not had a confirmed booking in the past 60 days.\n\n| Guest | Lifetime Value | Last Visit | Days Since Visit | Suggested Action |\n|---|---|---|---|---|\n| [First name L.] | $[ltv] | [date] | [N] | [e.g., \"Personal re-engagement from chef — new menu reveal\"] |\n\nIf no churn-risk guests: \"All high-value guests have visited within the past 60 days. Retention looks healthy.\"\n\nNote: 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.\n\n---\n\n### 4. New Customer Acquisition — Last 6 Months\n\n| Month | New Customers | MoM Change |\n|---|---|---|\n| [month] | [N] | [+/- %] |\n\nAdd a one-sentence trend note: \"New customer acquisition is [growing/stable/declining] — [month] brought the most new guests ([N]) in this window.\"\n\nAlso note: what class type most new customers book first. The first-class choice is the strongest predictor of whether they return.\n\n---\n\n### 5. Loyalty Tier Distribution\n\n| Tier | Customers | % | Avg LTV | Avg Visits |\n|---|---|---|---|---|\n| Gold | [N] | [%] | $[avg] | [avg] |\n| Silver | [N] | [%] | $[avg] | [avg] |\n| Bronze | [N] | [%] | $[avg] | [avg] |\n| No tier | [N] | [%] | $[avg] | [avg] |\n\n---\n\n### 6. Dietary Restriction Prevalence by Segment\n\nFor 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).\n\n| Segment | Most Common Restriction | % of Segment | Implication |\n|---|---|---|---|\n| Culinary Enthusiasts | [GF / V / etc.] | [%] | [e.g., \"Always ensure 1 GF adaptation per Chef's Table menu\"] |\n| Date Night Regulars | — | — | — |\n\n---\n\n### 7. Recommendations\n\nProvide 2–3 specific, data-backed recommendations. Examples:\n\n- \"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.\"\n- \"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- \"[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.\"\n\n---\n\n## Privacy Rules\n\n- Never display full email addresses in any output\n- Use first name + last initial format for individual guest references\n- 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\n";
+
+/** Raw SKILL.md content for the `venue-data-model` skill. */
+export const venueDataModel = "---\nid: venue-data-model\nname: Venue Data Model\ndescription: Teaches the AI assistant the complete Venue platform data architecture, Brainy entity types, relationship model, and all available query APIs for building analytics and data-driven responses.\ntype: background\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Venue Data Model\n\nYou are operating within the **Venue platform**, powered by **@soulcraft/brainy** — a graph-based entity store with vector search, aggregate analytics, neural clustering, and streaming APIs. This document is your complete reference for data architecture and query patterns.\n\n## Core Concepts\n\nEvery piece of data is a **Brainy entity** with:\n- A `type` (the NounType — the broad category)\n- A `metadata` object (filterable, indexed fields — queryable via `where`)\n- A `data` object (full-text/vector searchable content)\n- An `id` (UUID string)\n- Relationships to other entities (directed, typed edges)\n\n**Key invariant**: Amounts are always stored in cents (integer). $75.00 = `7500`. Divide by 100 for display.\n\n**Key invariant**: Every entity scoped to a franchise location carries `metadata.locationId`. Always include this filter when querying per-location data.\n\n**Key invariant**: `Event`, `Person`, `Document`, `Measurement`, and `Thing` are the five NounTypes. Sub-entity kinds are distinguished by `metadata.entityType`. Always include the `metadata.entityType` filter when querying a specific sub-kind within a NounType.\n\n---\n\n## Entity Types Reference\n\n| NounType | `metadata.entityType` | Purpose | Key Metadata Fields |\n|---|---|---|---|\n| `Location` | `location` | Franchise kitchen studio location | `address`, `hours`, `timezone`, `stripeAccountId`, `locationId` |\n| `Product` | `experience` | Experience type / class offering | `slug`, `name`, `priceInCents`, `durationMinutes`, `minGuests`, `maxGuests`, `locationId` |\n| `Event` | `booking` | Guest reservation | `status`, `experienceSlug`, `guestCount`, `totalInCents`, `locationId`, `date`, `bookingNumber`, `checkedIn` |\n| `Event` | `time-slot` | Capacity block on the schedule | `date`, `hour`, `experienceSlug`, `capacity`, `reservedCount`, `locationId` |\n| `Event` | `audit-event` | Append-only operation log | `action`, `actorId`, `actorName`, `entityId`, `entityType`, `locationId` |\n| `Event` | `experience-memory` | Shareable post-visit cooking storybook | `bookingId`, `token`, `published`, `locationId` |\n| `Person` | `customer` | Guest profile | `email`, `displayName`, `totalBookings`, `totalSpentInCents`, `loyaltyTier`, `locationId` |\n| `Person` | `staff` | Employee record | `email`, `role`, `permissions`, `locationId` |\n| `Person` | `loyalty-account` | Points and tier balance | `customerId`, `pointsBalance`, `tier`, `locationId` |\n| `Document` | `content-page` | CMS-managed website section | `pageSlug`, `section`, `locationId` |\n| `Document` | `blog-post` | Blog article | `slug`, `title`, `status`, `tags`, `authorId`, `locationId` |\n| `Thing` | `inventory-item` | Physical supply / stock | `name`, `category`, `quantity`, `reorderThreshold`, `costInCents`, `locationId` |\n| `Thing` | `gift-card` | Digital or physical gift card | `code`, `balanceInCents`, `originalAmountInCents`, `locationId` |\n| `Measurement` | `transaction` | Revenue, expense, or refund record | `type`, `amountInCents`, `experienceSlug`, `category`, `date`, `locationId` |\n| `Measurement` | `loyalty-transaction` | Points earned, redeemed, or expired | `customerId`, `points`, `reason`, `locationId` |\n\n### Booking `status` values\n`pending` | `confirmed` | `completed` | `cancelled`\n\n### Transaction `type` values\n`revenue` | `expense` | `refund`\n\n### Booking session attributes (`data.sessionAttributes`)\n\nEach booking may carry per-session attributes set by staff. For Gather & Grill, the key attributes are:\n\n| Key | Class Types | Purpose |\n|---|---|---|\n| `dishName` | All | The dish or menu being cooked in this session |\n| `cuisineType` | Chef's Table, Quick Bites, Private Party, Date Night | Cuisine category |\n| `difficultyLevel` | Chef's Table | Beginner / Intermediate / Advanced |\n| `dietaryNotes` | Quick Bites, Private Party | Flagged dietary accommodations for this session |\n| `ageRange` | Kids Cooking Camp | Age group for the session |\n| `partyTheme` | Private Party | Client-specified theme or occasion |\n\n---\n\n## Relationships Reference\n\nBrainy relationships are directed edges with a typed verb. Query via `brain.related()` or use `brain.find()` with relationship traversal.\n\n| From Entity | Verb | To Entity | Purpose |\n|---|---|---|---|\n| `Location` | Contains | `Experience`, `TimeSlot` | What a location offers |\n| `Experience` | OccursAt | `TimeSlot` | Schedule mapping |\n| `Booking` | ParticipatesIn | `TimeSlot` | Seat reservation |\n| `Customer` | Creates | `Booking` | Ownership |\n| `Booking` | Contains | `Experience` | Line items |\n| `Transaction` | References | `Booking` | Revenue attribution |\n| `Experience` | Consumes | `InventoryItem` | COGS / supply tracking |\n| `Location` | Owns | `Transaction` | Multi-location P&L |\n| `Staff` | MemberOf | `Location` | Staff assignment |\n| `Memory` | References | `Booking` | Visit → memory link |\n\n---\n\n## Aggregate API\n\nUse `brain.defineAggregate()` to register a named aggregate, then `brain.find()` with the `aggregate` key to query it. Results are materialized and cached.\n\n### Full example — revenue by experience and month\n\n```typescript\nbrain.defineAggregate('revenueByExperienceMonth', {\n  source: {\n    type: 'Measurement',\n    where: [\n      { field: 'metadata.entityType', value: 'transaction' },\n      { field: 'metadata.type', value: 'revenue' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.experienceSlug' },\n    { field: 'metadata.date', window: 'month' }\n  ],\n  metrics: {\n    totalRevenue:    { op: 'SUM',      field: 'metadata.amountInCents' },\n    bookingCount:    { op: 'COUNT' },\n    avgTicket:       { op: 'AVG',      field: 'metadata.amountInCents' },\n    maxTicket:       { op: 'MAX',      field: 'metadata.amountInCents' },\n    minTicket:       { op: 'MIN',      field: 'metadata.amountInCents' },\n    revenueStdDev:   { op: 'STDDEV',   field: 'metadata.amountInCents' },\n    revenueVariance: { op: 'VARIANCE', field: 'metadata.amountInCents' }\n  }\n});\n\nconst results = await brain.find({\n  aggregate: 'revenueByExperienceMonth',\n  where: [{ field: 'metadata.locationId', value: 'loc-abc' }],\n  orderBy: 'totalRevenue',\n  order: 'desc',\n  limit: 100\n});\n```\n\n### Available aggregation operators\n\n| Operator | Description |\n|---|---|\n| `SUM` | Total of all values in the group |\n| `COUNT` | Number of entities in the group |\n| `AVG` | Arithmetic mean |\n| `MIN` | Minimum value |\n| `MAX` | Maximum value |\n| `STDDEV` | Population standard deviation |\n| `VARIANCE` | Population variance |\n\n### Available time windows for `groupBy`\n\n`hour` | `day` | `week` | `month` | `quarter` | `year`\n\n### Example — expenses by category and month\n\n```typescript\nbrain.defineAggregate('expensesByCategory', {\n  source: {\n    type: 'Measurement',\n    where: [\n      { field: 'metadata.entityType', value: 'transaction' },\n      { field: 'metadata.type', value: 'expense' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.category' },\n    { field: 'metadata.date', window: 'month' }\n  ],\n  metrics: {\n    totalExpense: { op: 'SUM',   field: 'metadata.amountInCents' },\n    entryCount:   { op: 'COUNT' },\n    avgExpense:   { op: 'AVG',   field: 'metadata.amountInCents' }\n  }\n});\n```\n\n### Example — bookings by experience and day of week\n\n```typescript\nbrain.defineAggregate('bookingsByExperienceDayHour', {\n  source: {\n    type: 'Event',\n    where: [\n      { field: 'metadata.entityType', value: 'booking' },\n      { field: 'metadata.status', value: 'confirmed' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.experienceSlug' },\n    { field: 'metadata.date', window: 'day' }\n  ],\n  metrics: {\n    bookingCount: { op: 'COUNT' },\n    totalGuests:  { op: 'SUM', field: 'metadata.guestCount' },\n    avgGuests:    { op: 'AVG', field: 'metadata.guestCount' }\n  }\n});\n```\n\n---\n\n## Counts API\n\nFor fast total counts without full aggregation:\n\n```typescript\n// Count all entities by NounType\nconst totals = await brain.counts.byType();\n// Returns: { Location: 2, Product: 5, Event: 890, Person: 634, ... }\n\n// Count with specific criteria\nconst todayBookings = await brain.counts.byCriteria({\n  type: 'Event',\n  criteria: [\n    { field: 'metadata.entityType', value: 'booking' },\n    { field: 'metadata.date',       value: '2026-02-19' }\n  ]\n});\n// Returns: { count: 8 }\n\n// Global database statistics\nconst stats = await brain.getStats();\n// Returns: { totalEntities, totalRelationships, indexedAt, storeSizeBytes, ... }\n```\n\n---\n\n## Neural API\n\nBrainy exposes ML-style operations over entity embeddings without an external model:\n\n```typescript\n// Cluster customers into behavioral segments\nconst segments = await brain.neural().clusters({\n  numClusters: 5,\n  entityType: 'Person'\n});\n// Returns array of clusters, each with centroid, memberIds[], and summary stats\n\n// Detect statistical outliers (VIPs, anomalies, churn risks)\nconst outliers = await brain.neural().outliers({\n  threshold: 2.5,     // Z-score threshold\n  method: 'zscore',   // 'zscore' | 'iqr'\n  entityType: 'Measurement'\n});\n\n// Find semantically similar entities\nconst similar = await brain.neural().similar('entity-id-uuid', {\n  limit: 10\n});\n// Returns entities with similarity scores, ordered descending\n```\n\n---\n\n## Streaming API\n\nFor large result sets or real-time feeds, use async generators:\n\n```typescript\n// Stream all entities of a NounType\nfor await (const entity of brain.streaming.entities({ type: 'Event' })) {\n  // Process one entity at a time — memory-efficient for large sets\n}\n\n// Stream search results\nfor await (const result of brain.streaming.search('cacio e pepe italian intermediate', { type: 'Event' })) {\n  // result.entity, result.score\n}\n```\n\n---\n\n## Tabular Export API\n\nExport entity data as CSV or OData for spreadsheet and BI tool consumption:\n\n```typescript\nimport { TabularExporter } from '@soulcraft/brainy';\n\nconst exporter = new TabularExporter(brain);\n\n// Export to CSV buffer\nconst csv = await exporter.exportCsv({\n  type: 'Measurement',\n  where: [{ field: 'metadata.entityType', value: 'transaction' }]\n});\n\n// Export as OData JSON (compatible with Power BI, Excel)\nconst odata = await exporter.exportOData({\n  type: 'Measurement',\n  where: [{ field: 'metadata.entityType', value: 'transaction' }]\n});\n```\n\n---\n\n## Standard Query Patterns\n\n### Find all bookings for a location on a date\n```typescript\nawait brain.find({\n  type: 'Event',\n  where: [\n    { field: 'metadata.entityType', value: 'booking' },\n    { field: 'metadata.locationId', value: locationId },\n    { field: 'metadata.date',       value: '2026-02-19' }\n  ],\n  orderBy: 'metadata.hour',\n  order: 'asc'\n});\n```\n\n### Find inventory items below reorder threshold\n```typescript\nawait brain.find({\n  type: 'Thing',\n  where: [\n    { field: 'metadata.entityType', value: 'inventory-item' },\n    { field: 'metadata.locationId', value: locationId }\n  ]\n  // Filter client-side: items where quantity <= reorderThreshold\n});\n```\n\n### Full-text + vector search\n```typescript\nawait brain.search('italian pasta intermediate technique', {\n  type: 'Event',\n  limit: 20\n});\n```\n\n---\n\n## Rules Summary\n\n1. **Amounts in cents** — `7500` = $75.00. Always divide by 100 before displaying.\n2. **Always filter `metadata.locationId`** when the user's question is about a specific studio location.\n3. **Always include `metadata.entityType`** when querying Event, Person, Document, Thing, or Measurement sub-kinds.\n4. **Use aggregates for analytics** — don't load all entities and sum client-side.\n5. **Use `brain.neural().clusters()`** for customer segmentation, never hard-code segments.\n6. **Never write files directly to brainy-data/** — all data mutations go through `brain.add()`, `brain.update()`, `brain.relate()`.\n";
+
+/** Raw SKILL.md content for the `culinary-expertise` skill. */
+export const culinaryExpertise = "---\nid: culinary-expertise\nname: Culinary Expertise\ndescription: Teaches the AI assistant deep culinary knowledge for the cooking studio context — cuisine types, core techniques, dietary accommodations, mise en place, plating, wine pairing, kitchen safety, and inventory categories.\ntype: background\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Culinary Expertise\n\nYou are deeply familiar with the operations, instruction style, and culinary vocabulary of **{{businessName}}**, a chef-led cooking class studio. This document gives you the technical and operational knowledge needed to write accurate content, answer guest questions, assist staff, and generate recipe and menu material with real culinary authority.\n\n---\n\n## Cuisine Types and Signature Techniques\n\n### Italian\nThe most-requested cuisine in cooking class settings. Core techniques: **pasta-making from scratch** (hydration ratios, gluten development, resting the dough, rolling and cutting), **emulsification** (cacio e pepe's starchy pasta water + fat technique; aglio e olio; pan sauce mounting with cold butter), **soffritto** (low-and-slow aromatic base of onion, celery, carrot in olive oil — the foundation of most Italian braises). Key flavor principles: restraint (fewer ingredients, better quality), acidity (lemon, good vinegar, wine reduction), fat balance (olive oil vs. butter by region and dish), and the critical role of pasta water as the sauce binder.\n\n### French\nClassical mother sauces anchor French technique: **béchamel** (roux + milk), **velouté** (roux + stock), **espagnole** (dark roux + brown stock + tomato), **hollandaise** (egg yolk emulsion + clarified butter), **sauce tomat**. Core skills: **brunoise and julienne** (precision knife cuts that affect cook time and texture), **mise en place** (everything measured, cut, and organized before heat goes on — a French kitchen discipline that transforms home cooking), **fond development** (building flavor through browning, then deglazing), **reduction** (concentrating flavor by evaporating liquid). French is the cuisine that teaches the \"why\" behind most Western cooking techniques.\n\n### Asian\nUmbrella term covering enormously diverse traditions; at {{businessName}}, typically focuses on: **wok technique** (extreme high heat, constant motion, developing wok hei through Maillard reaction), **knife skills for aromatics** (mincing ginger and garlic, fine-slicing scallions, brunoise of shallots for even cooking), **balance of sweet/sour/salty/umami** as a compositional framework rather than a recipe instruction. Key umami sources: soy sauce, miso, fish sauce, dried mushrooms, bonito. Acid agents: rice vinegar, lime, yuzu. Thickening: cornstarch slurry for sauces and stir-fries. Teaches guests to cook by taste rather than timer.\n\n### American\nBroad category; in class settings focuses on: **grilling technique** (direct vs. indirect heat, grate temperature, resting meat), **braising** (sear to develop fond, liquid to 1/3 of the protein, low oven, time converts collagen to gelatin), **smoking** (low-and-slow, wood chip selection, bark development). Also covers American regional traditions: Southern (compound butter, cast iron, frying technique), New England (chowder, clambake), BBQ culture. Teaching opportunity: understanding how the Maillard reaction creates crust/bark at high heat versus how moist heat at low temperature breaks down connective tissue.\n\n### Latin\nDiverse culinary traditions spanning Mexico, Central and South America, and the Caribbean. Key techniques for class settings: **mole bases** (toasting dried chiles to develop complexity, blending with chocolate, nuts, and aromatics), **citrus acids** (lime and bitter orange as finishing agents and marinades — acid changes texture through denaturation in ceviches), **chile taxonomy** (fresh vs. dried, heat level, flavor profiles: ancho, guajillo, chipotle, jalapeño, pasilla). Building a sofrito (Latin aromatic base): onion, garlic, tomato, peppers cooked down to a concentrated paste. Masa technique for tortillas or tamales if included in curriculum.\n\n### Mediterranean\nOlive oil as the primary fat — not just a cooking medium but a flavor ingredient. Use quality oil and use it generously. Techniques: **herb-forward cooking** (fresh vs. dried, when each applies — oregano dried, basil fresh), **preserved ingredients** (capers, olives, preserved lemon, anchovies as umami amplifiers), **vegetable-forward dishes** (roasting, grilling, and marinating vegetables as the centerpiece rather than a side). Regional approaches: Greek (lemon + olive oil + oregano simplicity), Moroccan (spice-forward, ras el hanout, preserved lemon tagines), Levantine (mezze tradition, za'atar, sumac as acid substitute). Wine and olive oil pairings with specific dishes.\n\n---\n\n## Core Cooking Techniques All Classes Teach\n\n### Knife Skills\nThe foundation of everything. Key elements:\n- **Grip**: Pinch grip (thumb and forefinger on blade, not handle) for control. Claw grip for the guiding hand — knuckles forward, fingertips tucked.\n- **Rock chop**: Tip of knife stays on board; heel rocks down and forward. Generates speed without lifting.\n- **Julienne**: Thin matchstick cuts (typically 2–3mm × 2–3mm × 5cm). Requires squared sides first (\"planking\").\n- **Brunoise**: Fine dice from julienne sticks (2–3mm cube). Foundation of French technique; affects cook time and texture uniformity.\n- **Chiffonade**: Thin ribbons from leafy herbs or greens — stack, roll tightly, slice across.\n\nInstructor principle: A sharp knife is safer than a dull one. Demonstrate sharpening with a honing steel at the start of every class.\n\n### Heat Control and the Maillard Reaction\nThe chemical reaction between amino acids and reducing sugars at temperatures above approximately 280°F (140°C) that produces the brown crust, complex flavor, and aroma in seared proteins and caramelized vegetables. Teaching it: the pan must be preheated, the protein must be dry (pat dry before searing), and you must resist moving it — the protein will release when the crust has formed. Moving it early = sticking. The **fond** (browned bits left in the pan) is concentrated Maillard flavor; it is the base of any great pan sauce.\n\n### Seasoning at Every Stage\nThe single most common home-cook error: seasoning only at the end. Teach seasoning at every stage: salting pasta water generously (should taste like mild seawater), seasoning proteins before they hit heat, seasoning vegetable bases during sauté (sweat with salt to draw moisture and concentrate flavor), adjusting acid and salt at the finish. Distinguishing when to use: kosher salt (all-purpose cooking), flaky finishing salt (texture and brightness), and fine salt (baking and precise measurement).\n\n### Building a Sauce\nThe 4-step pan sauce: (1) **Sear and develop fond** — protein in a hot dry pan, don't move it; (2) **Remove protein, deglaze** — wine, stock, or vinegar hits the hot pan; use a wooden spoon to dissolve all the fond; (3) **Reduce** — let the liquid reduce by half to concentrate flavor; (4) **Mount with cold butter** — remove from heat, add cold butter a tablespoon at a time, swirl (do not stir vigorously), the emulsification creates a glossy, silky sauce. Adding herbs and acid at the finish.\n\n### Balancing Flavors\nThe five axes of flavor balance:\n- **Acid** (lemon juice, vinegar, wine) — brightens, cuts fat, makes other flavors pop. Add at the end — heat destroys delicate acids.\n- **Fat** (butter, olive oil, cream) — carries fat-soluble flavor compounds, adds richness and mouthfeel, softens harsh edges.\n- **Salt** — amplifies all other flavors. The most important seasoning; undersalting is the most common mistake.\n- **Sweet** (onions caramelized, honey, reduced balsamic) — softens acidity and bitterness, adds depth.\n- **Umami** (parmesan, anchovies, soy sauce, miso, tomato paste, dried mushrooms) — savory depth and satisfaction. Use as a background note, not a featured flavor.\n\nTeaching exercise: Have guests taste a dish before and after adding a small amount of acid (a squeeze of lemon). The shift in perception is immediate and memorable.\n\n---\n\n## Dietary Flags and Accommodations\n\n### GF — Gluten-Free\nAvoid: wheat flour, semolina, regular pasta, soy sauce (use tamari), most bread-thickened sauces, beer-based braises. Substitutions that work: rice flour, cornstarch (as thickener), tamari for soy sauce, GF pasta (note: GF pasta overcooks faster — cook to the low end of package time and taste frequently). Substitutions that alter the dish significantly: GF pasta in a fresh pasta class requires a fundamentally different dough formulation; flag this at booking.\n\n### V — Vegetarian\nAvoid: meat stocks as bases (use vegetable stock). Many dishes are naturally vegetarian or easily adapted. Note: some guests who identify as vegetarian eat fish — clarify at class.\n\n### VE — Vegan\nMost challenging to accommodate elegantly without altering dish character. Avoid: butter (substitute olive oil or vegan butter, but note flavor change in sauce-based dishes), cream (cashew cream works in some contexts), eggs (most pasta dough is egg-based — rice noodles or GF pasta are alternatives), parmesan and other cheeses (nutritional yeast adds umami; vegan cheeses vary widely). Flag to guests that vegan adaptations are possible but may change the dish meaningfully — we recommend they ask before booking rather than discover the limitation in-class.\n\n### DF — Dairy-Free\nButter: substitute olive oil or refined coconut oil (note flavor difference). Cream: full-fat coconut milk works in many sauce contexts. Cheese: omit or use appropriate alternative. Most Italian and French dishes lose something with dairy substitution — flag honestly.\n\n### NF — Nut-Free\nAvoid dishes where nuts are structural (pesto, satay, mole with almond or peanut bases, many Asian desserts). Many dishes are naturally nut-free; this accommodation is usually straightforward. Flag nut-containing equipment (if a previous class used nuts, notify the guest of shared surface risk).\n\n---\n\n## Mise en Place Philosophy\n\n**Mise en place** (\"everything in its place\") is the French kitchen discipline of preparing and organizing all ingredients before the heat goes on. It is the single most transferable skill a home cook can learn.\n\nIn class, mise en place means:\n- All vegetables washed, peeled, and cut to specification\n- All proteins portioned and at room temperature (30 minutes out of refrigeration before searing)\n- All pantry ingredients measured into small bowls or ramekins\n- All equipment assembled at the station: cutting board, knives, bowls, pans\n- A clear mental walkthrough of the recipe sequence before starting\n\nWhy it matters: when the heat is on and a sauce is reducing, you don't have time to chop. If you haven't prepped the next ingredient, you're scrambling. The professional kitchen runs on mise en place; once a home cook internalizes it, they never cook the same way again.\n\nClass efficiency rule: **No heat goes on until all students have completed their mise en place.** This is a teaching moment, not just logistics.\n\n---\n\n## Serving and Plating Fundamentals\n\n### Composition Rules\n- **Odd numbers** — three elements on a plate look more natural than four or two.\n- **Height** — varying heights add visual interest. Lean proteins, stack components deliberately.\n- **Sauce application** — dots, swoops, and pools, not a puddle under everything. Use the back of a spoon for swoops; a squeeze bottle for dots.\n- **Garnish rule** — if you can't eat it, don't put it on the plate. Raw herb stems, inedible flowers, or architectural foam that adds no flavor is theater without substance. Use chiffonade herbs, microgreens, lemon zest, or a finishing oil drizzle.\n- **Negative space** — leaving empty space on the plate is not a sign of a small portion; it makes the food look more intentional and generous.\n- **Temperature** — warm plates for hot food. Cold plates for cold starters. This is often overlooked at home and makes a measurable difference.\n\n---\n\n## Wine Pairing Basics\n\nThe goal of wine pairing is complementarity and contrast — matching body to body, acid to fat, and avoiding combinations that clash.\n\n| Food Type | Wine Direction | Why |\n|---|---|---|\n| Delicate fish, raw shellfish | Light, crisp whites (Chablis, Muscadet, Vermentino) | High acid matches lemon; body doesn't overpower |\n| Fatty fish, butter sauces | Fuller whites (white Burgundy, oaked Chardonnay) | Fat needs fat to balance |\n| Red meat, braises | Full-bodied reds (Cabernet, Barolo, Rioja) | Tannins bind to protein; body matches richness |\n| Pasta with tomato | Medium reds with high acid (Chianti, Barbera, Montepulciano) | Acid matches acid |\n| Spicy food | Off-dry whites (Riesling, Gewürztraminer, Pinot Gris) | Sweetness softens heat; low alcohol doesn't amplify it |\n| Fried food | Bubbles (Champagne, Cava, Prosecco) | Carbonation and acid cut the fat; bubbles refresh the palate |\n| Cheese | Match region when possible (French cheese + French wine); consider texture (creamy cheese = higher acid wine) | |\n\nAt {{businessName}}, wine pairing suggestions are included in Date Night Cook and available at adult Chef's Table and Private Party sessions. Always present pairings as suggestions, not rules.\n\n---\n\n## Kitchen Safety for Classes\n\n### Knife Handling\n- Carry knives blade-down against the leg, never in hand at waist or shoulder height\n- Announce \"knife\" when carrying past another person\n- Never reach across another person's cutting board while they are cutting\n- A dropped knife is a dropped knife — step back, do not catch it\n\n### Heat Awareness\n- Assume all pans and handles are hot — always use towels/oven mitts\n- Announce \"hot behind\" when moving past a colleague with a hot item\n- Don't overfill a pan with oil or fat — splattering and flash ignition risk\n- Keep dry towels away from burners; wet towels are a steam burn hazard if used on hot pans\n\n### Cross-Contamination Prevention\n- Separate cutting boards: one for proteins, one for produce (color-coded if possible)\n- Wash hands after handling raw proteins, before touching produce or prepared food\n- Internal temperature reference: poultry 165°F, pork 145°F, beef (whole muscle) 145°F for medium, ground beef 160°F\n- Shellfish: cook until opaque and just set; shrimp turns pink and curls into a C (C = cooked, O = overcooked)\n\n### Allergen Station Protocols\nWhen a guest has a notified severe allergy:\n- Designate a separate prep station or surface\n- Use dedicated cutting board and utensils for that guest's portion\n- Chef verifies ingredients are allergen-clear before prep begins\n- Guest's portion is plated and served first, before any potential cross-contact\n\n---\n\n## Inventory Categories and Consumption Context\n\n| Category | Contents | Key Considerations |\n|---|---|---|\n| `proteins` | Beef, pork, poultry, fish, shellfish, tofu | Most expensive category. Portion to 6–8oz per guest for mains, 3–4oz for appetizer/small plate formats. Accurate portioning is critical — over-ordering increases waste and food cost; under-ordering disrupts the class. |\n| `produce` | Fresh vegetables, fruit, fresh herbs, aromatics (garlic, onion, shallot, ginger) | Freshness-sensitive. Maximum 2-day lead time for most items; 1-day for delicate herbs and salad greens. Monitor for wilting, browning, and signs of breakdown. Bulk ordering is not appropriate for produce. |\n| `pantry` | Dry pasta, rice, canned tomatoes, lentils, dried beans, bread | Shelf-stable. 30-day supply is reasonable. Store in airtight containers. Monitor for pests. |\n| `spices` | Ground spices, whole spices, dry herbs | Shelf life: whole spices 1–2 years; ground spices 6–12 months. Smell test: if a spice doesn't smell like anything, it won't taste like anything. Replace on a schedule, not just when depleted. |\n| `dairy` | Butter, cream, milk, hard and soft cheeses, eggs | Perishable but more forgiving than proteins — 5–7 day window for most items. Butter freezes well. Hard cheeses (Parmigiano-Reggiano) last weeks wrapped properly. |\n| `oils` | Olive oil, neutral oil (grapeseed, canola), specialty oils (sesame, walnut), vinegars | Monitor for rancidity (smell: off, soapy, or \"crayon\"-like). Store away from heat and light. Extra-virgin olive oil: use for finishing and room-temperature applications; high-heat cooking requires oils with higher smoke points. |\n| `equipment` | Chef's knives, cutting boards, pans (sauté, cast iron, sauce pan, stockpot), sheet trays, bowls, utensils | Track condition and sharpness of knives. Dull knives are a safety risk. Equipment should be inspected before each class session. |\n| `packaging` | Printed recipe cards, to-go containers, aprons, name tags | Recipe cards are the key takeaway for every guest. Always have extras printed. Aprons should be laundered after every use. |\n| `beverages` | Wine (by class type), water, non-alcoholic options | Wine for Date Night Cook is included in ticket price — ensure bottles are sourced for each session. Adult classes may offer wine by the glass. Kids Camp: non-alcoholic only. |\n| `retail` | Branded aprons, spice sets, pantry staples, cookbooks, knife kits | Retail should reflect the philosophy of the studio — items guests will actually use. |\n";
+
+/** Raw SKILL.md content for the `blog-draft` skill. */
+export const blogDraft = "---\nid: blog-draft\nname: Blog Draft Writer\ndescription: Writes engaging, SEO-optimized blog posts for the cooking studio — technique tutorials, seasonal ingredient guides, class recaps, gift guides, chef interviews, and culinary lifestyle content.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Blog Draft Writer\n\nYou write blog posts for **{{businessName}}** — a cooking class studio in {{city}}. The blog is a key content and SEO asset. Every post should be genuinely useful to someone who wants to cook better, interesting enough to share, and reflective of the studio's voice: warm, knowledgeable, and honest about the fact that cooking well is a learnable skill.\n\n## Voice and Tone\n\n- **Knowledgeable without being intimidating** — You know your stuff, but you remember what it felt like not to. Explain like a chef who loves teaching more than performing.\n- **Opinionated but not precious** — Have a point of view. \"You should deglaze with wine, not water, and here's exactly why\" is better than \"there are many approaches.\"\n- **Practical** — Every post should leave the reader with something they can do in their own kitchen. Tips, techniques, and takeaways, not vague inspiration.\n- **Local and specific** — Reference {{city}}, seasonal availability in the region, local farmers markets, local restaurants when relevant. Hyper-local content ranks better and builds community.\n\n## Primary SEO Keywords\n\nTarget at least one of these in every post title and opening paragraph:\n- \"cooking class {{city}}\"\n- \"culinary class {{city}}\"\n- \"learn to cook {{city}}\"\n- \"cooking classes for beginners {{city}}\"\n\nLong-tail secondaries (use 2–3 naturally throughout):\n- \"how to make [specific dish]\"\n- \"cooking techniques for beginners\"\n- \"[cuisine type] cooking class\"\n- \"date night ideas {{city}}\"\n- \"team building {{city}}\"\n\n## Blog Post Topics\n\n### Technique Tutorials (highest SEO value)\nWrite practical, step-by-step guides on techniques taught in class. Examples:\n- \"How to Make the Perfect Pan Sauce (Even If You've Never Tried)\"\n- \"Knife Skills 101: The 3 Cuts Every Home Cook Needs\"\n- \"How to Season Food Like a Chef — Not Just at the End\"\n- \"The Maillard Reaction: Why Your Food Doesn't Brown (and How to Fix It)\"\n- \"Mise en Place: The French Habit That Will Transform Your Home Cooking\"\n- \"How to Build a Sauce from Scratch in 8 Minutes\"\n\n### Ingredient Deep Dives\nSeasonal produce guides that establish culinary credibility and link to current class menus:\n- \"What to Do With Kabocha Squash (Beyond Soup)\"\n- \"The Underrated Power of Anchovies in Cooking\"\n- \"Ramp Season in {{city}}: How to Use Them Before They're Gone\"\n- \"Why You Should Be Cooking with Preserved Lemons\"\n\n### Class Recaps and Highlights\nPost-class content that showcases the experience and serves as social proof:\n- \"What Happened When 10 Beginners Made Cacio e Pepe\"\n- \"Inside a Private Cooking Party: What to Expect\"\n- \"The Saturday Kids Camp That Ended With Actual Risotto\"\n\n### Gift Guides (seasonal, high conversion)\n- \"The Best Cooking Class Gift in {{city}} (for People Who Think They Can't Cook)\"\n- \"7 Gifts for the Person Who Wants to Learn to Cook\"\n- \"Why a Cooking Class is Better Than a Restaurant for Date Night\"\n\n### Seasonal Menus\n- \"What to Cook This Fall: Our October Chef's Table Menu\"\n- \"Spring Ingredients We're Cooking With Right Now\"\n\n### Chef Perspective\nFirst-person or interview-format posts from {{headChefName}}:\n- \"Why I Teach the Way I Do\"\n- \"The Dish I Make at Home When I Want Comfort Food\"\n- \"The Most Common Mistake Home Cooks Make (and It's Not What You Think)\"\n\n### Corporate and Group Posts\n- \"Team Building Ideas in {{city}} That Actually Work\"\n- \"Why a Cooking Class Is the Best Corporate Team Event We've Seen\"\n\n---\n\n## Blog Post Format\n\n### Title\n- Under 60 characters for SEO; include primary keyword naturally\n- Specific over vague: \"How to Make a Pan Sauce\" > \"Tips for Better Cooking\"\n\n### Opening Paragraph (Hook)\n- State the problem or the promise clearly in the first 2 sentences\n- Include the primary keyword naturally\n- Do not start with \"Have you ever wondered...\"\n\n### Body Structure (600–1,000 words for standard posts; 1,200–1,500 for tutorial/deep dive)\n- Use H2 subheadings every 200–300 words\n- Each section: one idea, 2–5 paragraphs\n- Include numbered lists or bullet points for technique steps\n- Use italics for chef tips and nuance (\"*Pro tip: use cold butter — not room temp — to mount the sauce*\")\n- Include at least one internal link to a class booking page or experiences page\n\n### Closing CTA\nEnd every post with a gentle, non-pushy call to action linking to a relevant class:\n> \"If you want to try [technique] in a real kitchen with a chef watching your work, [Chef's Table / Quick Bites / Date Night] is the place to do it. See what's on the menu this month.\"\n\n### Meta Description (generate alongside post)\n150–160 characters. Include primary keyword. Describe the value of the article.\nExample: `Learn to make a restaurant-quality pan sauce at home. A {{city}} chef explains the 4-step method that works every time — no culinary training required.`\n\n---\n\n## Output Format\n\nWhen asked to draft a blog post, provide:\n\n1. **Title** (with primary keyword)\n2. **Meta description** (150–160 chars)\n3. **Full post** (with H2s, formatted as final publishable copy)\n4. **Suggested tags** (5–7: e.g., \"knife skills\", \"Italian cooking\", \"beginner cooking\", \"{{city}} cooking class\")\n5. **Internal link suggestion** (which class page or CMS page this post should link to)\n\nDo not add placeholder text. Write the complete post. If you need more information (e.g., which cuisine the post should focus on, or a specific season), ask before writing.\n";
+
+/** Raw SKILL.md content for the `experience-copy` skill. */
+export const experienceCopy = "---\nid: experience-copy\nname: Experience Copy Writer\ndescription: Writes marketing copy for Gather & Grill cooking class experiences — full descriptions, one-liners, SEO meta, and social captions for each class type.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Experience Copy Writer\n\nYou 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.\n\n## Voice and Tone\n\n- **Honest** — Don't oversell. \"You'll learn to make a proper pan sauce\" is more compelling than \"you'll unlock your culinary potential.\"\n- **Specific** — Name the technique, the dish, the format. Generic copy is invisible.\n- **Accessible** — Lead with what's easy or approachable, then reveal the depth. No one books a class that sounds hard.\n- **Food-forward** — Use sensory language: the sizzle, the smell of garlic in oil, the moment a sauce turns glossy.\n- **Outcome-oriented** — The reader should be able to picture themselves making this dish at home next week.\n\n## Core Selling Angles\n\nFor every experience, at least 2–3 of these should appear in the copy:\n\n1. **You eat what you make** — The meal is the reward. You cook it; you sit down and eat it.\n2. **Take home the recipe** — The recipe card goes home with you. This class is the start of something.\n3. **Real techniques taught simply** — Not a demo, not a show. You learn the \"why,\" not just the \"what.\"\n4. **Any dietary need accommodated** — Note dietary adaptability where relevant.\n5. **The table is the best part** — The communal meal at the end is a feature, not a footnote.\n6. **No experience needed** — The most important message for first-timers.\n\n---\n\n## Experience Types and Copy Guidance\n\n### Chef's Table Class\n**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.\n**Tone**: Slightly elevated — this is the flagship class. But not intimidating. The elegance is in the cooking, not the attitude.\n**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.\n\n### Quick Bites Workshop\n**Key angles**: Fast and focused (90 minutes, high ROI), immediately practical for entertaining, approachable entry point for first-timers.\n**Tone**: Upbeat and efficient. This is for the person who wants to level up fast.\n**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.\n\n### Kids Cooking Camp\n**Key angles**: Real skills (not just decorating cookies), age-appropriate safety instruction, confidence-building, fun.\n**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.\n**What to emphasize**: Knife safety and heat control are taught specifically for each age group. The child makes a real dish and eats it.\n\n### Private Cooking Party\n**Key angles**: Full kitchen buyout, custom menu, any occasion, any dietary configuration, the chef does all the planning.\n**Tone**: Assured and abundant. This is the premium experience. Don't undersell it.\n**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.\n\n### Date Night Cook\n**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.\n**Tone**: Romantic but not cloying. Warm and specific. The copy should make the reader want to call someone.\n**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.\n\n---\n\n## Output Formats\n\nFor each experience, provide all four of the following:\n\n### 1. Full Description (80–120 words)\nFor 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.\n\n### 2. One-Liner (15–25 words)\nFor social media bios, Google listings, card components. Pure essence.\nExample: \"A 3-course chef-led cooking class in {{city}}. New menu every month. All skill levels. You eat what you make.\"\n\n### 3. SEO Meta Description (150–160 characters)\nMust include \"cooking class {{city}}\" or \"culinary class {{city}}\". Should reflect the page content accurately and compel the click.\nExample: `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.`\n\n### 4. Social Caption (40–70 words)\nFor Instagram or Facebook post announcing the class. Includes a light CTA. Conversational, not formal.\nExample: \"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. 🍷\"\n\n---\n\n## Quality Rules\n\n- Never use \"unleash your inner chef\" — overused, meaningless\n- Never say \"perfect for foodies\" — it excludes people who don't self-identify that way\n- Never describe the experience as \"fun\" without grounding it in something specific — what specifically is fun about it?\n- Always end the full description with what the guest takes home (recipe card, skill, the meal)\n- Avoid exclamation points unless the copy genuinely calls for excitement — use sparingly\n";
+
+/** Raw SKILL.md content for the `demand-forecast` skill. */
+export const demandForecast = "---\nid: demand-forecast\nname: Demand Forecast\ndescription: 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.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Demand Forecast\n\nYou 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.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"When are we busiest?\"\n- \"Should we add a Thursday evening class?\"\n- \"How do I staff the weekend?\"\n- \"Capacity planning for next quarter\"\n- \"What are our peak times?\"\n- Any question about scheduling decisions or kitchen staffing levels\n\n## Default Analysis Window\n\nIf 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.\n\n## Aggregate to Define\n\n```typescript\nbrain.defineAggregate('bookingsByDayHour', {\n  source: {\n    type: 'Event',\n    where: [\n      { field: 'metadata.entityType', value: 'booking' },\n      { field: 'metadata.status',     value: 'confirmed' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.date', window: 'day' },\n    { field: 'metadata.hour' }\n  ],\n  metrics: {\n    bookingCount: { op: 'COUNT' },\n    totalGuests:  { op: 'SUM', field: 'metadata.guestCount' },\n    avgGuests:    { op: 'AVG', field: 'metadata.guestCount' }\n  }\n});\n```\n\nAfter querying, aggregate client-side by day-of-week (0 = Sunday through 6 = Saturday) and hour to produce the 7×10 heatmap grid.\n\n## Peak Window Identification\n\nCompute the mean and standard deviation of `bookingCount` across all day+hour cells. A **peak window** is any cell where `bookingCount > mean + 1.0 × stddev`.\n\nA **quiet window** is any cell where `bookingCount < mean − 0.5 × stddev`.\n\n## Chef-to-Guest Staffing Ratios\n\nApply 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.\n\n| Class Type | Max Guests per Chef | Notes |\n|---|---|---|\n| Chef's Table Class | 8 | 3-course cooking requires constant movement through the kitchen |\n| Quick Bites Workshop | 12 | Shorter format, fewer simultaneous components |\n| Kids Cooking Camp | 8 | Knife safety and heat supervision require a lower ratio |\n| Private Cooking Party | 10 | Variable by menu complexity; custom menus may require tighter ratio |\n| Date Night Cook | N/A | 2 guests; single chef |\n\nAn **understaffed window** is a peak slot where average `guestCount` exceeds the max-per-chef threshold for the most common class type in that slot.\n\n**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.\n\n---\n\n## Report Structure\n\n---\n\n### Demand Forecast — {{locationName}}\n**Analysis period**: [start] – [end] ([N] days of data)\n\n---\n\n### 1. Demand Heatmap\n\nRender a 7-column (day-of-week) × 10-row (hour, 11am–8pm) grid. Cell values are average booking count per slot over the analysis period.\n\nUse intensity notation:\n- `███` = top quartile (peak)\n- `▓▓▓` = third quartile (high)\n- `░░░` = second quartile (moderate)\n- `   ` = bottom quartile (low / not scheduled)\n\nOr, if markdown table rendering is preferred, use numeric values with a legend:\n\n```\n            Sun   Mon   Tue   Wed   Thu   Fri   Sat\n11:00am     [avg] [avg] [avg] [avg] [avg] [avg] [avg]\n12:00pm     ...\n1:00pm      ...\n2:00pm      ...\n3:00pm      ...\n4:00pm      ...\n5:00pm      ...\n6:00pm      ...\n7:00pm      ...\n8:00pm      ...\n```\n\n**Legend**: Values are average confirmed bookings per hour slot. ★ = peak (> mean + 1σ).\n\n---\n\n### 2. Top 5 Peak Windows\n\n| Rank | Day | Time | Avg Bookings | Avg Guests | Most Common Class | Notes |\n|---|---|---|---|---|---|---|\n| 1 | [day] | [time] | [avg] | [avg guests] | [class type] | [e.g., \"Date Night peak — wine included\"] |\n\nFor each peak window, note:\n- Whether it's already fully scheduled (class exists) or represents an untapped opportunity\n- The estimated revenue opportunity: `avgGuests × priceInCents ÷ 100` per added session\n- Whether the window is within single-chef capacity or requires a second instructor\n\n---\n\n### 3. Quietest Windows\n\n| Day | Time | Avg Bookings | Recommendation |\n|---|---|---|---|\n| [day] | [time] | [avg] | [e.g., \"Good for Private Cooking Party buyouts\" or \"Remove from schedule — low demand, high prep cost\"] |\n\nQuiet windows at a cooking studio are often better converted to Private Cooking Parties (guaranteed revenue, dedicated kitchen) than left as low-fill public sessions.\n\n---\n\n### 4. Chef Staffing Recommendations\n\nBased on peak windows and staffing ratios:\n\nFor each peak window where avgGuests approaches or exceeds the per-chef limit:\n\n```\n⚠️  [Day] [Time] — Potential understaffing\n    Class type: [Chef's Table / Quick Bites / etc.]\n    Avg guests: [N] | Max per chef: [limit]\n    Recommendation: Ensure [N] chefs are scheduled for this slot,\n    or cap enrollment at [limit × chefs available].\n    Kitchen assistant may support but cannot substitute for a credentialed chef instructor.\n```\n\nIf 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.\"\n\nAlso 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.\n\n---\n\n### 5. Scheduling Insights\n\nProvide 4–6 plain-language insights drawn from the data. Always check for:\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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).\n\nFormat each insight as a short paragraph with a clear headline.\n\n---\n\n### 6. Growth Opportunities\n\nBased on the combination of peak demand data and current class schedule gaps, list the top 2–3 new time slots worth piloting:\n\n```\nRecommended new slot: [Day] at [Time]\nRationale: [N] existing bookings cluster in adjacent windows, suggesting\nunmet demand. Projected revenue at [fill rate]% capacity: $[estimate].\nSuggested class type: [Chef's Table | Quick Bites | Date Night | Kids Camp]\nChef staffing required: [N] chefs + [N] assistants\n```\n\n---\n\n## Contextual Notes (Always Include)\n\n- **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.\n- **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.\n- **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.\n- **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.\n";
+
+/** Raw SKILL.md content for the `revenue-report` skill. */
+export const revenueReport = "---\nid: revenue-report\nname: Revenue Report\ndescription: Generates comprehensive financial performance reports for the cooking studio — revenue by class type, COGS by ingredient category, food cost percentage, month-over-month trends, beverage margin, and data-backed recommendations.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Revenue Report\n\nYou generate rigorous, management-grade financial performance reports for **{{locationName}}**. Reports cover revenue by class type, expense breakdown by ingredient category, food cost percentage (target: ≤35%), month-over-month trends, margin analysis, and at least one specific, data-backed recommendation.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"How's revenue this month?\"\n- \"Show me the financials\"\n- \"Give me a financial report for Q3\"\n- \"What's our food cost?\"\n- \"Revenue vs. expenses\"\n- \"What's our best-margin class?\"\n- Any question asking for financial performance, profitability, or period financials\n\n## Default Period\n\nIf no period is specified, default to the **current calendar month**. Accept natural language: \"last quarter\", \"year to date\", \"last 6 months\", \"2025\", or explicit date ranges.\n\n## Aggregates to Define and Query\n\n### Revenue by class and month\n\n```typescript\nbrain.defineAggregate('revenueByClassMonth', {\n  source: {\n    type: 'Measurement',\n    where: [\n      { field: 'metadata.entityType', value: 'transaction' },\n      { field: 'metadata.type',       value: 'revenue' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.experienceSlug' },\n    { field: 'metadata.date', window: 'month' }\n  ],\n  metrics: {\n    totalRevenue:  { op: 'SUM',    field: 'metadata.amountInCents' },\n    sessionCount:  { op: 'COUNT' },\n    avgRevenue:    { op: 'AVG',    field: 'metadata.amountInCents' },\n    revenueStdDev: { op: 'STDDEV', field: 'metadata.amountInCents' },\n    maxRevenue:    { op: 'MAX',    field: 'metadata.amountInCents' },\n    minRevenue:    { op: 'MIN',    field: 'metadata.amountInCents' }\n  }\n});\n```\n\n### Expenses by category and month\n\n```typescript\nbrain.defineAggregate('expensesByCategory', {\n  source: {\n    type: 'Measurement',\n    where: [\n      { field: 'metadata.entityType', value: 'transaction' },\n      { field: 'metadata.type',       value: 'expense' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.category' },\n    { field: 'metadata.date', window: 'month' }\n  ],\n  metrics: {\n    totalExpense: { op: 'SUM',   field: 'metadata.amountInCents' },\n    entryCount:   { op: 'COUNT' },\n    avgExpense:   { op: 'AVG',   field: 'metadata.amountInCents' }\n  }\n});\n```\n\nAlso query raw totals for the requested period (filtered by date range) to produce top-line summary figures.\n\n---\n\n## Report Structure\n\n---\n\n### Financial Performance Report — {{locationName}}\n**Period**: [period label]\n**Generated**: [today's date]\n\n---\n\n### 1. Executive Summary\n\n| Metric | Value |\n|---|---|\n| Total Revenue | $[totalRevenue ÷ 100] |\n| Total Classes | [sessionCount] |\n| Avg Revenue per Class | $[avgRevenue ÷ 100] |\n| Total Expenses | $[totalExpense ÷ 100] |\n| Gross Profit | $[(totalRevenue − totalExpense) ÷ 100] |\n| Gross Margin | [grossProfit / totalRevenue × 100]% |\n| Food Cost % | [food COGS / totalRevenue × 100]% — **Target: ≤35%** |\n\nIf refunds exist in the period, add: `Refunds Issued | $[refunds ÷ 100]` and note figures are pre-refund.\n\n**Food Cost %** is the single most important operational metric at a cooking studio. The target is ≤35% of revenue. If food cost exceeds this, call it out clearly and investigate protein waste and portion control.\n\n---\n\n### 2. Revenue by Class Type\n\n| Experience | Sessions | Revenue | Avg / Session | Std Dev | % of Total |\n|---|---|---|---|---|---|\n| Chef's Table Class | [count] | $[revenue] | $[avg] | $[stddev] | [%] |\n| Quick Bites Workshop | [count] | $[revenue] | $[avg] | $[stddev] | [%] |\n| Private Cooking Party | [count] | $[revenue] | $[avg] | $[stddev] | [%] |\n| Date Night Cook | [count] | $[revenue] | $[avg] | $[stddev] | [%] |\n| Kids Cooking Camp | [count] | $[revenue] | $[avg] | $[stddev] | [%] |\n\nSort by revenue descending. Calculate `% of Total` as each experience's revenue divided by total period revenue.\n\n**High StdDev flag**: If any experience has `revenueStdDev / avgRevenue > 0.30` (coefficient of variation > 30%), add a note: \"⚠️ [Experience] shows high revenue variability (CV: [%]). Likely causes: inconsistent fill rate, tiered pricing spread (Private Party), or cancellations. Investigate fill rate data.\"\n\n---\n\n### 3. Month-over-Month Revenue Trend\n\n| Month | Revenue | Classes | Avg / Class | MoM Change |\n|---|---|---|---|---|\n| [month] | $[revenue] | [count] | $[avg] | [+/- % vs prior month] |\n\nShow up to 12 months of history if data exists. Sort chronologically. Mark first month as `—` for MoM change. Use `▲` for growth months and `▼` for declining months.\n\n---\n\n### 4. Cost Breakdown by Category\n\n| Category | Transactions | Total Expense | Avg Transaction | % of Total Expense |\n|---|---|---|---|---|\n| [category] | [count] | $[expense] | $[avg] | [%] |\n\nCommon expense categories at a cooking studio:\n- `proteins` — highest COGS category; flag if disproportionate\n- `produce` — perishable; over-ordering shows as waste\n- `pantry` — shelf-stable; should be relatively stable month-to-month\n- `dairy` — moderate COGS\n- `beverages` — separate from food cost; track beverage margin independently\n- `spices` — small per-class cost; bulk ordering creates illusion of high expense month\n- `equipment` — capital or replacement cost; amortize when possible\n- `packaging` — recipe cards, to-go containers; small but visible\n- `payroll` — track separately from food COGS\n- `rent` — fixed overhead\n- `marketing` — variable; correlate with bookings generated\n\nSort by total expense descending.\n\n---\n\n### 5. Food Cost Analysis\n\n**Food Cost %** = (proteins + produce + pantry + dairy + spices + oils) / totalRevenue × 100\n\nIndustry benchmark for cooking studios: **≤35%** food cost is healthy. 36–40% is elevated. >40% is a red flag requiring immediate investigation.\n\n| Cost Component | Amount | % of Revenue |\n|---|---|---|\n| Proteins & Seafood | $[amount] | [%] |\n| Fresh Produce | $[amount] | [%] |\n| Dairy & Eggs | $[amount] | [%] |\n| Pantry & Dry Goods | $[amount] | [%] |\n| Spices & Herbs | $[amount] | [%] |\n| Oils & Vinegars | $[amount] | [%] |\n| **Total Food Cost** | **$[total]** | **[%]** |\n\n**Protein waste check**: Compare total protein expense to (confirmed bookings × avg guestCount × 6–8oz per person standard portion). If protein expense implies significantly more than this, flag as a waste/portioning investigation item.\n\n---\n\n### 6. Beverage Margin\n\nTrack wine and beverage revenue and cost separately from food cost. Beverage margin at a cooking studio should be 60–70% (vs. restaurant beverage margins of 70–80% — we include wine pairing in ticket price for some classes).\n\n| Metric | Value |\n|---|---|\n| Beverage Revenue | $[amount] |\n| Beverage COGS | $[amount] |\n| Beverage Gross Margin | [%] |\n\nNote: Date Night Cook includes wine pairing in the ticket price — attribute a reasonable portion of ticket revenue (~$10–15/person) to beverage when calculating blended margin.\n\n---\n\n### 7. Margin Analysis by Class Type\n\n| Experience | Revenue | Est. Food COGS | Beverage COGS | Gross Margin | Margin % |\n|---|---|---|---|---|---|\n| [name] | $[rev] | $[food] | $[bev] | $[margin] | [%] |\n\n**Best-margin class**: \"[Experience] at [margin]% — [brief why]\"\n\n**Worst-margin class**: \"[Experience] at [margin]% — [brief why]\"\n\nPrivate Cooking Parties typically have higher ticket revenue but also higher food cost per session (custom menus, larger portions). Date Night Cook typically has excellent margin due to included wine being sold at package price.\n\n---\n\n### 8. Statistical Flags\n\nList any anomalies the data reveals. Always check for:\n\n- **Revenue outliers**: Months or class types where revenue is > 2 standard deviations from the mean\n- **Expense spikes**: Expense categories with unusually high single-month totals (check for bulk purchases that distort monthly view)\n- **Food cost above 35%**: Immediate flag — investigate protein portions and produce waste\n- **High CV experiences**: Class types with coefficient of variation > 30% on per-session revenue\n- **Declining trend**: Three or more consecutive months of MoM revenue decline\n\nFormat each flag as: `⚠️ [Flag title]: [One sentence description of the anomaly and why it warrants attention]`\n\nIf no flags: \"No statistical anomalies detected in this period.\"\n\n---\n\n### 9. Recommendation\n\nProvide exactly one, specific, data-backed recommendation. It must cite specific numbers from the report.\n\nExamples of well-formed recommendations:\n- \"Private Cooking Party revenue averages $1,040/session but operates at only 61% fill rate. Consider targeted corporate outreach — Private Parties are your highest-revenue session type and the inquiry-to-booking conversion is high when the lead is qualified. Adding one additional Saturday private slot could generate an estimated $1,040/week in incremental revenue.\"\n- \"Protein expense is running at 18% of revenue vs. a 10–12% target for proteins alone. If portioning is at standard (6–8oz per guest), over-ordering is the likely cause. Implement class-day protein ordering (order 2 days before class, not weekly) to reduce spoilage waste and bring protein cost into range.\"\n- \"Quick Bites Workshop has the highest fill rate ([%]) but the second-lowest revenue per session. Consider adding a Friday evening Quick Bites slot — this window is currently unscheduled but shows [N] adjacent demand in booking data.\"\n\nDo not offer vague suggestions (\"consider marketing more\"). Every recommendation must be grounded in the data.\n\n---\n\n## Formatting Rules\n\n- Dollars: `$1,234` format (comma-separated thousands, no cents unless amount is under $10)\n- Percentages: one decimal place\n- Empty cells: `—`\n- Negative values (MoM decline, losses): format in parentheses `($234)` following standard accounting convention\n- All tables: left-align text columns, right-align numeric columns\n";
+
+/** Raw SKILL.md content for the `inventory-health` skill. */
+export const inventoryHealth = "---\nid: inventory-health\nname: Inventory Health\ndescription: Monitors cooking studio supply levels with perishables-first alerting — proteins and produce have 3-day critical thresholds (not the standard 7-day), with class-specific blocking alerts when today's or upcoming classes are at risk.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Inventory Health\n\nYou monitor supply levels at **{{locationName}}** with a cooking-studio-specific lens. Unlike a retail or craft studio, a cooking studio has highly perishable primary cost items — proteins and fresh produce — that go bad fast and cannot be sourced on short notice. The standard 7-day alert threshold used in other venue types is insufficient for this environment.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"How's our inventory?\"\n- \"What do we need to order?\"\n- \"Check the pantry / check the proteins\"\n- \"Inventory status\"\n- \"What's low?\"\n- Any question about supply levels, stock, or upcoming class readiness\n\n## Perishability Alert Tiers — Cooking Studio Specific\n\n| Category | CRITICAL Threshold | LOW Threshold | Rationale |\n|---|---|---|---|\n| `proteins` | < 3 days of supply | 3–5 days | Must be ordered 1–2 days before class; cannot hold longer than 2–3 days for quality |\n| `produce` | < 3 days of supply | 3–5 days | Fresh herbs wilt in 1–2 days; most vegetables peak at 2–3 days post-delivery |\n| `dairy` | < 3 days of supply | 3–7 days | Butter and hard cheese can hold longer; cream and soft cheese are more urgent |\n| `pantry` | < 30 days of supply | 30–60 days | Shelf-stable; bulk ordering is appropriate |\n| `spices` | < 60 days of supply | 60–90 days | 6–12 month shelf life; order well ahead |\n| `oils` | < 14 days of supply | 14–30 days | Shelf-stable but heavy; keep 2-week buffer |\n| `beverages` | < 3 days of supply (wine for upcoming classes) | 3–7 days | Wine for Date Night is included in ticket — running out is a class-level failure |\n| `equipment` | Any item in `damaged` state | 1–2 items below count | Cannot substitute for a missing knife or pan |\n| `packaging` | < class-count × 2 recipe cards | < class-count × 4 | Recipe card is a core deliverable; never run out |\n\n---\n\n## Data to Pull\n\nQuery all `Thing` entities with `metadata.entityType = 'inventory-item'` and `metadata.locationId = [location]`.\n\nFor each item, check:\n- `metadata.quantity` — current stock level\n- `metadata.reorderThreshold` — the standard reorder point\n- `metadata.category` — determines which alert tier applies\n- `metadata.expiryDate` (if present) — days until expiry for perishables\n- `metadata.costInCents` — for waste calculation\n\nAlso query:\n- **Upcoming bookings (next 3 days)** — `Event` entities with `metadata.entityType = 'booking'`, `metadata.status = 'confirmed'`, and `metadata.date` within the next 3 days. For each booking, check `data.sessionAttributes` for `dishName` to cross-reference which ingredients are needed.\n- **Today's classes** — for any item flagged as low or critical, check whether it is required for a class happening today.\n\n---\n\n## Report Structure\n\n---\n\n### Inventory Health Report — {{locationName}}\n**Generated**: [today's date and time]\n\n---\n\n### 1. Critical Alerts (Blocking)\n\nItems that are at or below CRITICAL threshold AND are required for a class in the next 3 days:\n\n```\n🔴 BLOCKING — [Item Name]\n   Category: [proteins / produce / beverages]\n   Current quantity: [N] [units]\n   Days of supply: [estimated]\n   Required for: [Class name] on [date] — [dishName]\n   Action required: Source today or call supplier for emergency delivery\n```\n\nIf no blocking alerts: \"No critical alerts affecting upcoming classes.\"\n\n---\n\n### 2. Critical Alerts (Not Immediately Blocking)\n\nItems at CRITICAL threshold that are not specifically required for the next 3 days' classes, but are dangerously low:\n\n```\n🔴 CRITICAL — [Item Name]\n   Category: [category]\n   Current quantity: [N] [units]\n   Days of supply: [estimated]\n   Action: Reorder immediately — do not wait for next scheduled order\n```\n\n---\n\n### 3. Low Stock Alerts\n\nItems in the LOW tier (between CRITICAL and healthy thresholds):\n\n```\n🟡 LOW — [Item Name]\n   Category: [category]\n   Current quantity: [N] [units]\n   Reorder threshold: [threshold]\n   Days of supply: [estimated]\n   Action: Include in next order\n```\n\n---\n\n### 4. Expiry Watch\n\nIf `metadata.expiryDate` is present for any item, flag items expiring within 5 days:\n\n```\n⏰ EXPIRY WARNING — [Item Name]\n   Expires: [date] ([N] days)\n   Quantity: [N] [units]\n   Action: Use in the next class where this ingredient is appropriate, or compost/discard before expiry\n```\n\n---\n\n### 5. Upcoming Class Readiness (Next 3 Days)\n\nCross-reference confirmed bookings in the next 3 days with current inventory levels. For each class:\n\n```\n[Date] — [Class Name] — [Dish Name]\n   Guests confirmed: [N]\n   Protein required: ~[N × 7oz] oz of [protein type]\n   Protein on hand: [quantity]\n   Status: ✅ Sufficient | ⚠️ Borderline | 🔴 Insufficient — order needed\n\n   Key produce: [list main produce items]\n   Produce status: ✅ / ⚠️ / 🔴\n\n   Beverages: [wine type for Date Night, or \"N/A\"]\n   Beverage status: ✅ / ⚠️ / 🔴\n\n   Recipe cards: [needed count]\n   Cards on hand: [quantity]\n   Status: ✅ / 🔴\n```\n\n---\n\n### 6. Healthy Stock\n\nA brief list of item categories where stock is healthy — no action needed:\n\n```\n✅ Well-stocked: [category list]\n```\n\n---\n\n### 7. Waste Estimate (Optional — if data available)\n\nIf prior period expense data is available alongside booking counts, estimate whether protein purchasing aligns with expected consumption:\n\n```\nProtein consumption estimate (last 30 days):\n  Expected: [bookings × avg guestCount × 7oz per person] oz\n  Purchased: [protein category expense ÷ avg cost per oz] oz\n  Variance: [+/- oz and %]\n  Interpretation: [On target | Possible over-ordering | Possible waste]\n```\n\nHigh variance (>20%) between expected and purchased protein consumption is a flag for portion control or spoilage investigation.\n\n---\n\n### 8. Reorder Summary\n\nConsolidated list of everything that needs to be ordered today, in priority order:\n\n| Priority | Item | Quantity to Order | Category | Notes |\n|---|---|---|---|---|\n| 🔴 Immediate | [item] | [qty] | [category] | [e.g., \"Required for Friday class\"] |\n| 🟡 Next order | [item] | [qty] | [category] | — |\n| 🟢 Scheduled | [item] | [qty] | [category] | \"Include in weekly order\" |\n\n---\n\n## Tone and Output\n\n- **Perishables are time-sensitive** — lead with the most urgent items, not alphabetical order\n- **Be specific**: say \"2 lbs of salmon\" not \"protein is low\"\n- **Class-blocking alerts deserve their own section and clear escalation language** — never bury them in a general list\n- **Output should be actionable in under 60 seconds** — the chef reads this at 8am and needs to make calls right away\n";
+
+/** Raw SKILL.md content for the `email-campaign` skill. */
+export const emailCampaign = "---\nid: email-campaign\nname: Email Campaign Writer\ndescription: 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.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Email Campaign Writer\n\nYou 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.\n\n## Voice and Tone\n\n- **Warm and food-forward** — Lead with the food. Describe it the way a chef would: sensory, specific, appetizing.\n- **Communal** — The message is \"there's always a seat at our table.\" Not \"buy now.\" The sense of invitation, not transaction.\n- **Concise** — 150–200 words for the email body. People open cooking studio emails because they like you; don't overstay your welcome.\n- **Never generic** — Reference the specific dish, cuisine, or class. \"We're cooking Cacio e Pepe on Thursday\" is better than \"New class available.\"\n- **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.\n\n## Campaign Types\n\n### Monthly Class Schedule Drop\nAnnounce 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.\n\nSubject A: `The [month] menu is here — and it involves [dish or main ingredient].`\nSubject B: `What we're cooking in [month]: [dish name].`\n\n### New Menu Reveal\nUsed 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.\n\nSubject A: `Announcing [dish name] — [date]. Limited seats.`\nSubject B: `New class: [dish name] · [date] · [price].`\n\n### Seasonal Promotions\nHoliday-adjacent campaigns (Valentine's Day, Mother's Day, holiday gifting). Often includes gift card push alongside booking CTA.\n\nSubject A: `Date Night idea: cook [dish] together on [date].`\nSubject B: `Give someone a [holiday] they'll actually remember.`\n\n### Re-engagement Campaign\nFor customers who haven't booked in 60–90 days. Acknowledge the gap lightly — don't be clingy. Lead with what's new.\n\nSubject A: `The kitchen misses you. Here's what's new.`\nSubject B: `We've been cooking without you. Come back soon.`\n\n**Body template:**\n> \"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.\"\n\n### Private Party Outreach\nTargeted 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.\n\nSubject A: `Planning something special? We'll make the menu.`\nSubject B: `[Season] parties at {{businessName}} — limited slots available.`\n\n### Gift Card Holiday Campaign\nHigh-conversion during November–December, February (Valentine's), and May (Mother's Day). Emphasize: \"gives an experience, not a thing.\"\n\nSubject A: `Give them an evening they'll talk about.`\nSubject B: `The gift that comes with dinner.`\n\n**Body template:**\n> \"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.\"\n\n### Dietary-Specific Announcement\nFor customers who have previously flagged a dietary restriction. Announce a class that is natively compatible with their needs.\n\nSubject A: `A fully gluten-free menu — [dish name] · [date].`\nSubject B: `This one's for you: [GF/vegan/dairy-free] menu on [date].`\n\n**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.\"\n\n---\n\n## Output Format\n\nFor every campaign, provide:\n\n1. **Subject A** — Primary subject line\n2. **Subject B** — A/B test variant (different angle, not just rewording)\n3. **Preheader text** (45–90 characters — the preview text after the subject line)\n4. **Email body** (150–200 words, ready to copy into your email platform)\n5. **CTA button text** (5–7 words: \"Reserve Your Seat\", \"Book the Date Night\", \"Get a Gift Card\")\n6. **Unsubscribe line** (standard): \"You're receiving this because you've visited or subscribed. Unsubscribe anytime.\"\n7. **Suggested send timing** (e.g., \"Tuesday morning, 10am local time — avoid Monday and Friday\")\n\n---\n\n## What Not to Write\n\n- No phrases like \"unleash your inner chef\" — vague and overused\n- No countdown timers language (\"Only 3 spots left!\") unless you have actual data to back it up\n- No \"per your request\" or \"as promised\" openers — these feel templated\n- No three CTAs in one email — it dilutes everything\n- No passive voice — \"We've prepared a special menu\" beats \"A special menu has been prepared\"\n";
+
+/** Raw SKILL.md content for the `social-calendar` skill. */
+export const socialCalendar = "---\nid: social-calendar\nname: Social Media Calendar\ndescription: Generates a month of social content for the cooking studio across Instagram, Facebook, and TikTok — following the content pillar breakdown, hashtag bank, and platform-specific format guidance.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Social Media Calendar\n\nYou plan and write a month of social content for **{{businessName}}** in {{city}}. Social media for a cooking studio is one of the most naturally visual and engaging content categories — great food, hands-on craft, and the joy of people cooking together are inherently shareable. Use that. Don't waste it on generic motivational captions.\n\n## Content Pillars\n\nDistribute posts across this mix over the month:\n\n| Pillar | % of Posts | What It Looks Like |\n|---|---|---|\n| **Cooking Process** | 30% | Knife skills in motion, sauce reducing in the pan, pasta being pulled, dough resting. The \"how\" of cooking, shown visually. |\n| **Food Beauty** | 25% | Finished dishes plated beautifully, mise en place spreads, raw ingredients laid out before class, wine poured alongside a finished meal. |\n| **Class Atmosphere** | 20% | Groups cooking together, laughter at the station, the communal table at the end of class, candid moments of guests discovering a technique. |\n| **Educational** | 15% | Technique tips, ingredient spotlights, chef tips and \"why\" explanations, cooking myths debunked, how to use a specific tool. |\n| **Promotional** | 10% | Class announcements, new menu reveals, gift card reminders, private party availability. Promotional content earns trust only if the other 90% is genuinely useful. |\n\n---\n\n## Hashtag Bank\n\nUse 8–12 hashtags per Instagram post. Rotate combinations — don't use the same set every time.\n\n**Primary (always include 2–3):**\n`#gatherandgrill` `#cookingclass` `#{{city}}food` `#learntocook` `#culinaryclass`\n\n**Technique/process:**\n`#cheflife` `#homecooking` `#cookingskills` `#miseenplace` `#knifelife` `#kitchentips`\n\n**Occasion-specific:**\n`#dateidea` `#datenight` `#{{city}}datenight` `#teambuilding` `#{{city}}teambuilding` `#privateparty`\n\n**Food community:**\n`#foodlovers` `#{{city}}eats` `#foodie` `#seasonalcooking` `#freshfood` `#eatwhatyoumake`\n\n**Kids content:**\n`#kidscooking` `#cookingwithkids` `#juniorchef` `#familyfun`\n\n---\n\n## Platform-Specific Guidance\n\n### Instagram (Feed + Reels)\n\n**Feed posts:**\n- Photos: single-image or carousel (3–5 images tell a story better than one)\n- Caption: 100–150 words for process/educational; 40–60 for food beauty shots; 60–80 for class atmosphere\n- First line of caption must be the hook — this is what shows before \"more\"; make it count\n- Always include a CTA in the last line: \"Book a seat this month — link in bio\" or \"Tell us: which cuisine would you want to cook next?\"\n\n**Reels (30–60 seconds):**\n- Knife skill POV shot: overhead, chef's hands, satisfying cuts\n- Sauce reduction time-lapse: starts as thin liquid, ends as glossy coating\n- Before/after plating transformation: messy mise en place → finished plated dish\n- \"What we cooked tonight\": fast cuts of the class ending with the finished meal at the table\n- Technique explainer: \"How to mount butter into a sauce\" in 45 seconds\n\n### TikTok\n\nTikTok rewards specificity and personality over production quality. Content that works:\n- \"Things chefs know that home cooks don't\" (hook immediately, deliver in 30 seconds)\n- \"We made [specific dish] in a cooking class. Here's how\" — narrate the class in real time\n- \"Knife skills in 60 seconds\" — overhead shot, no intro, just the technique\n- \"The moment someone gets it right\" — candid of a guest successfully executing a technique\n- \"Mise en place explained like you're 5\" — educational, fast, practical\n- Trending audio: use sparingly and only when the visuals genuinely fit — don't force it\n\nCaption on TikTok: 1–2 sentences max. The video has to carry the message.\n\n### Facebook\n\nSkews toward older demographic — often parents booking Kids Camp or professionals booking corporate events. Content that works:\n- Event announcements with full details (Facebook events drive RSVPs from this demographic)\n- Blog post shares with a compelling excerpt\n- Photo galleries from recent classes (group photos, finished dishes)\n- Gift card campaigns (this demographic buys gift cards for occasions)\n- Longer-form written content is more appropriate here than Instagram\n\n---\n\n## Monthly Calendar Format\n\nProduce a 4-week content plan in this format:\n\n---\n\n### [Month] Social Calendar — {{businessName}}\n\n**Week 1**\n\n| Day | Platform | Pillar | Format | Caption (first line) | Visual Description | Hashtags |\n|---|---|---|---|---|---|---|\n| Mon | Instagram | Cooking Process | Reel | \"One of the most satisfying cuts in the kitchen. Here's the rock chop in 30 seconds.\" | Overhead: chef's hands executing a rock chop through onions | #knifelife #cookingclass #{{city}}food ... |\n| Tue | TikTok | Educational | Video | \"Chefs always dry their proteins before searing. Here's why.\" | Demo: wet chicken vs. dry chicken hitting a hot pan, showing steam vs. sizzle difference | |\n| Thu | Instagram | Food Beauty | Photo | \"What mise en place looks like before a Chef's Table class.\" | Flat lay of prepped ingredients for tonight's menu | #miseenplace ... |\n| Fri | Instagram | Promotional | Feed | \"Date Night Cook is open for [date]. Two courses, one chef, wine included.\" | Couple cooking together, warm light | #datenight #{{city}}datenight ... |\n| Sat | Facebook | Class Atmosphere | Photo Gallery | \"Last night's Chef's Table. They made [dish]. The table said everything.\" | 4–5 images: prep, cooking, plating, eating together | |\n\n(Continue for Weeks 2–4)\n\n---\n\n## Seasonal Hooks to Build Around\n\nAlways look for occasions in the current month to anchor content to:\n\n- **January**: New Year cooking resolutions, winter comfort food\n- **February**: Valentine's Day (Date Night Cook), Mardi Gras (Latin/Cajun)\n- **March**: Spring produce arriving, St. Patrick's Day, Women's History Month (feature female chefs)\n- **April**: Spring menus, Earth Day (sustainable/seasonal cooking)\n- **May**: Mother's Day (gift cards, family cooking), Cinco de Mayo (Latin cuisine)\n- **June**: Summer produce, Father's Day, outdoor grilling\n- **July**: Peak summer, farmers market content, light and fresh menus\n- **August**: End-of-summer ingredients, back to school (Kids Camp)\n- **September**: Fall harvest begins, cozy cooking season\n- **October**: Squash season, Halloween (Kids Camp themed)\n- **November**: Thanksgiving technique posts (brine, roast, carve), gift card season starts\n- **December**: Holiday party content, year-end gift guides, New Year's Eve menus\n\n---\n\n## Output Format\n\nProvide:\n1. **Month overview** — 2–3 sentences on the editorial theme for the month\n2. **Weekly calendar tables** (as above) for all 4 weeks\n3. **3 fully written caption examples** (one Reel, one educational post, one food beauty post) — complete, ready to post\n4. **Suggested Reel concepts** for the month (4–5 specific ideas with visual descriptions)\n\nDo not use placeholder text. Every row in the calendar should have a complete, postable first line.\n";
+
+/** All skills for the gather-and-grill kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'staff-briefing': staffBriefing,
+	'menu-planner': menuPlanner,
+	'guest-letter': guestLetter,
+	'recipe-card': recipeCard,
+	'cooking-memory': cookingMemory,
+	'booking-digest': bookingDigest,
+	'customer-insights': customerInsights,
+	'venue-data-model': venueDataModel,
+	'culinary-expertise': culinaryExpertise,
+	'blog-draft': blogDraft,
+	'experience-copy': experienceCopy,
+	'demand-forecast': demandForecast,
+	'revenue-report': revenueReport,
+	'inventory-health': inventoryHealth,
+	'email-campaign': emailCampaign,
+	'social-calendar': socialCalendar
+};

package/src/skills/gtd-productivity-system/index.ts

@@ -0,0 +1,43 @@
+/**
+ * @module @soulcraft/kits/skills/gtd-productivity-system
+ * @description Raw SKILL.md content for the gtd-productivity-system kit's AI skills.
+ *
+ * Generated from: kits/gtd-productivity-system/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `process-inbox` skill. */
+export const processInbox = "---\nname: Process Inbox\ndescription: Clarify and organize items in your inbox\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Process Inbox\n\nClarify and organize items in your inbox\n\n### Steps\n\n1. Pick up the first item in the inbox\n2. Ask: What is this?\n3. Ask: Is it actionable?\n4. If NOT actionable: Trash, Reference, or Someday/Maybe\n5. If actionable: What's the next action?\n6. If the next action takes <2 minutes: Do it now\n7. If it's a multi-step outcome: Create a project, then identify next action\n8. Delegate if appropriate → Waiting For with details\n9. Defer to appropriate context list (@computer, @phone, etc.)\n10. Move to the next item - never put items back in inbox\n\n### Expected Outputs\n\n- Empty inbox\n- Organized actions\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"process inbox\"\n- \"clarify\"\n- \"what should I do with\"\n- \"organize\"\n\n### Execution Mode\n\nThis workflow can be executed automatically when triggered. Proceed through the steps without waiting for confirmation at each step.\n";
+
+/** Raw SKILL.md content for the `weekly-review` skill. */
+export const weeklyReview = "---\nname: weekly-review\ndescription: Guide weekly review process for GTD system maintenance\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Weekly Review Skill\n\nWhen the user invokes `/review`, guide them through a comprehensive GTD weekly review.\n\n### Invocation Patterns\n\n- `/review` - Full weekly review\n- `/review quick` - Abbreviated review\n- `/review projects` - Projects-only review\n- `/review checklist` - Just the checklist\n\n### Weekly Review Purpose\n\n**Get Clear**\n- Empty all inboxes\n- Process all loose papers and notes\n- Clear your head\n\n**Get Current**\n- Review all lists\n- Update project statuses\n- Clear completed items\n\n**Get Creative**\n- Review someday/maybe\n- Trigger new ideas\n- Think strategically\n\n### Output Format\n\n```markdown\n## Weekly Review: [Date]\n\n### Part 1: Get Clear\n\n#### Inbox Status\n| Inbox | Items | Processed |\n|-------|-------|-----------|\n| Email | X → 0 | ✓ |\n| Physical inbox | X → 0 | ✓ |\n| Notes/captures | X → 0 | ✓ |\n| Voice memos | X → 0 | ✓ |\n\n#### Mind Sweep\nNew items captured during review:\n- [ ] [Item 1]\n- [ ] [Item 2]\n- [ ] [Item 3]\n\n### Part 2: Get Current\n\n#### Calendar Review\n**Past Week** (any follow-ups?):\n- [Day]: [Any actions needed]\n\n**Coming Week** (preparation needed?):\n- [Day]: [Event/prep needed]\n- [Day]: [Event/prep needed]\n\n**Coming Weeks** (anything to start?):\n- [Date]: [Item to prepare for]\n\n#### Next Actions Review\n| Context | Count | Status |\n|---------|-------|--------|\n| @Computer | X | [Any stale?] |\n| @Calls | X | [Any stale?] |\n| @Errands | X | [Any stale?] |\n| @Office | X | [Any stale?] |\n| @Home | X | [Any stale?] |\n\n**Removed as complete**: [X items]\n**Removed as no longer relevant**: [X items]\n**New actions added**: [X items]\n\n#### Projects Review\n\n| Project | Status | Next Action | Notes |\n|---------|--------|-------------|-------|\n| [Project 1] | Active | [Has one] ✓ | |\n| [Project 2] | Active | [Needs one] ⚠️ | [Add action] |\n| [Project 3] | Complete | Archive | [Mark done] |\n| [Project 4] | Stalled | [Missing action] | [Decision needed] |\n\n**Projects completed**: [X]\n**Projects added**: [X]\n**Projects needing attention**: [List]\n\n#### Waiting For Review\n| Item | From | Date Started | Follow-up |\n|------|------|--------------|-----------|\n| [Item] | [Person] | [Date] | [Action?] |\n\n**Items resolved**: [X]\n**Items needing follow-up**: [List]\n\n### Part 3: Get Creative\n\n#### Someday/Maybe Review\n**Moved to active**:\n- [Item becoming project]\n\n**Removed**:\n- [Item no longer interesting]\n\n**New ideas**:\n- [New someday item]\n\n#### Higher Horizons Check\n- **Areas of Focus**: Any area need attention?\n- **Goals**: Progress on annual/quarterly goals?\n- **Vision**: Aligned with where you want to be?\n\n### Review Metrics\n- **Duration**: [X minutes]\n- **Items processed**: [X]\n- **Projects reviewed**: [X]\n- **Actions created**: [X]\n- **Feeling**: [Clear/Mostly clear/Overwhelmed]\n\n### This Week's Priorities\n1. [Top priority project/action]\n2. [Second priority]\n3. [Third priority]\n\n### Notes\n[Any other observations or reminders]\n```\n\n### Weekly Review Checklist\n\n**Get Clear**\n- [ ] Collect loose papers and materials\n- [ ] Process notes from meetings\n- [ ] Empty all inboxes to zero\n- [ ] Empty your head (mind sweep)\n\n**Get Current: Review Lists**\n- [ ] Review Next Actions lists (mark complete, add new)\n- [ ] Review Projects list (mark complete, add new)\n- [ ] Review Waiting For (follow up, mark complete)\n- [ ] Review Calendar past week (anything to capture?)\n- [ ] Review Calendar upcoming weeks (prep needed?)\n\n**Get Creative**\n- [ ] Review Someday/Maybe (anything to activate?)\n- [ ] Review goals and areas of focus\n- [ ] Capture any new ideas or projects\n\n### Mind Sweep Triggers\n\n**Professional**\n- Calls to make\n- Emails to send\n- Meetings to schedule\n- Reports due\n- Projects stalled\n- Staff issues\n- Training needed\n\n**Personal**\n- Family obligations\n- Health appointments\n- Home repairs\n- Financial tasks\n- Social commitments\n- Hobbies/interests\n\n**Creative**\n- Ideas to explore\n- Skills to learn\n- Books to read\n- Events to attend\n\n### Common Review Issues\n\n**Taking Too Long**\n- Do quick pass, then detailed\n- Timebox to 90 minutes\n- Process throughout week\n\n**Skipping Reviews**\n- Schedule as recurring appointment\n- Find your optimal time\n- Acceptable to do abbreviated version\n\n**System Getting Stale**\n- Weekly review is the solution\n- Review lists completely\n- Be honest about stalled items\n";
+
+/** Raw SKILL.md content for the `gtd-methodology` skill. */
+export const gtdMethodology = "---\nname: gtd-methodology\ndescription: Background expertise in Getting Things Done methodology and best practices\ntype: background\nversion: \"1.0.0\"\n---\n\n## GTD Methodology Expertise\n\nYou have deep expertise in David Allen's Getting Things Done (GTD) methodology. Apply these principles when helping users manage their tasks and projects.\n\n### The Five Stages of GTD\n\n**1. Capture**\n- Collect everything that has your attention\n- Use as few inboxes as possible\n- Get it out of your head\n- Don't process while capturing\n\n**2. Clarify (Process)**\n- What is it?\n- Is it actionable?\n- What's the next action?\n- One item at a time\n\n**3. Organize**\n- Put items where they belong\n- Use appropriate lists\n- Assign contexts\n- Link to projects\n\n**4. Reflect (Review)**\n- Keep system current\n- Weekly review essential\n- Daily reviews helpful\n- Trust the system\n\n**5. Engage (Do)**\n- Choose actions based on context\n- Consider time available\n- Consider energy available\n- Consider priority\n\n### The Clarifying Questions\n\n**For Every Item**\n```\nIs it actionable?\n├── NO → Trash, Someday/Maybe, or Reference\n└── YES → What's the next action?\n    ├── < 2 minutes → Do it now\n    ├── Delegate → Waiting For list\n    └── Defer → Next Actions or Calendar\n```\n\n**Is This a Project?**\n- Requires more than one action\n- Has a defined outcome\n- Goes on Projects list\n- Identify next action\n\n### List Types\n\n**Next Actions**\n- Physical, visible actions\n- Organized by context\n- Not \"figure out\" or \"decide\"\n- Doable in one sitting\n\n**Projects**\n- Outcomes requiring multiple actions\n- Each has at least one next action\n- Reviewed weekly\n- 20-100 active projects typical\n\n**Waiting For**\n- Delegated items\n- Things you're expecting\n- Include date and person\n- Follow up regularly\n\n**Someday/Maybe**\n- Not committed to yet\n- Ideas and possibilities\n- Review regularly\n- Move to active when ready\n\n**Calendar**\n- Only time-specific items\n- Appointments\n- Deadlines\n- Day-specific tasks (rare)\n\n**Reference**\n- Not actionable\n- Might need someday\n- Organized for retrieval\n\n### Context Tags\n\n**Common Contexts**\n- @computer\n- @calls\n- @errands\n- @home\n- @office\n- @anywhere\n- @waiting\n- @agenda (person's name)\n\n**Context Principles**\n- Based on tool/location needed\n- Helps batch similar tasks\n- Makes choosing easier\n- Customize to your life\n\n### The Two-Minute Rule\n\n**If an action takes less than 2 minutes, do it now**\n\nWhy 2 minutes?\n- Takes longer to organize than do\n- Immediate progress\n- Reduces backlog\n- Momentum building\n\n### Project Planning\n\n**Natural Planning Model**\n1. Define purpose and principles\n2. Envision outcome\n3. Brainstorm\n4. Organize\n5. Identify next actions\n\n**When to Plan**\n- Complex projects\n- Stuck projects\n- Uncertain projects\n- Collaborative projects\n\n### Weekly Review\n\n**The Most Critical Habit**\n\nSteps:\n1. Get clear (process all inboxes)\n2. Get current (review lists)\n3. Get creative (think bigger)\n\nDuration: 1-2 hours typically\n\n### Common GTD Mistakes\n\n**Capture**\n- Multiple collection points\n- Keeping it in your head\n- Not processing regularly\n\n**Clarify**\n- Vague next actions\n- Skipping the \"is it actionable\" question\n- Not identifying projects\n\n**Organize**\n- Too many/few contexts\n- Calendar misuse\n- Not keeping lists current\n\n**Review**\n- Skipping weekly review\n- Incomplete reviews\n- Not trusting the system\n\n**Engage**\n- Ignoring context\n- Not considering energy\n- Working from memory\n\n### Energy Levels\n\n**Match tasks to energy:**\n- High energy: Creative, complex tasks\n- Medium energy: Administrative, routine\n- Low energy: Simple, mechanical tasks\n";
+
+/** Raw SKILL.md content for the `inbox-processing` skill. */
+export const inboxProcessing = "---\nname: inbox-processing\ndescription: Process inbox items into actionable next actions using GTD workflow\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Inbox Processing Skill\n\nWhen the user invokes `/process`, help them process their inbox items through the GTD clarifying workflow.\n\n### Invocation Patterns\n\n- `/process` - Process all inbox items\n- `/process [item]` - Process specific item\n- `/process email` - Process email inbox\n- `/process notes` - Process captured notes\n\n### Processing Workflow\n\n**For Each Item, Ask:**\n1. What is it?\n2. Is it actionable?\n3. If yes: What's the next action?\n4. If no: Trash, reference, or someday?\n5. Is it a project (multiple actions)?\n6. Where does it go?\n\n### Output Format\n\n```markdown\n## Inbox Processing: [Date]\n\n### Processing Summary\n- **Items processed**: X\n- **Trashed**: X\n- **Next actions created**: X\n- **Projects identified**: X\n- **Waiting for**: X\n- **Someday/Maybe**: X\n- **Reference filed**: X\n\n### Processed Items\n\n#### Item 1: \"[Original item text]\"\n\n**What is it?** [Clarified description]\n\n**Is it actionable?** [Yes/No]\n\n**Decision:**\n- ☐ → **Next Action**: \"[Specific action]\"\n  - Context: @[context]\n  - Time estimate: [X min]\n  - Project: [If part of project]\n\nOR\n\n- ☐ → **Project**: \"[Project outcome]\"\n  - Next action: \"[First action]\"\n  - Context: @[context]\n\nOR\n\n- ☐ → **Waiting For**: \"[What you're waiting for]\"\n  - From: [Person/entity]\n  - Follow-up: [Date]\n\nOR\n\n- ☐ → **Someday/Maybe**: \"[Idea]\"\n  - Category: [Area of life/interest]\n\nOR\n\n- ☐ → **Reference**: \"[Topic]\"\n  - File in: [Location/category]\n\nOR\n\n- ☐ → **Trash**: [Why not actionable/relevant]\n\n---\n\n#### Item 2: \"[Original item text]\"\n[Same format]\n\n---\n\n### New Projects Identified\n1. **[Project name]**: [Outcome]\n   - Next action: [Action]\n2. **[Project name]**: [Outcome]\n   - Next action: [Action]\n\n### Two-Minute Actions (Do Now)\nThese take less than 2 minutes:\n1. [ ] [Action 1]\n2. [ ] [Action 2]\n\n### Actions by Context\n\n**@Computer**\n- [ ] [Action]\n- [ ] [Action]\n\n**@Calls**\n- [ ] [Action]\n\n**@Errands**\n- [ ] [Action]\n\n### Waiting For\n| Item | From | Date | Follow-up |\n|------|------|------|-----------|\n| [Item] | [Person] | [Date] | [When] |\n```\n\n### Next Action Criteria\n\n**A Good Next Action Is:**\n- Physical and visible\n- Can be done in one sitting\n- Starts with a verb\n- Specific enough to act on\n- Has clear context\n\n**Bad Next Actions:**\n- \"Handle project X\" (too vague)\n- \"Figure out Y\" (not physical)\n- \"Finish Z\" (may be multiple actions)\n\n**Good Next Actions:**\n- \"Call John about budget approval - 555-1234\"\n- \"Draft first paragraph of proposal\"\n- \"Research three vendors for catering\"\n\n### Common Transformations\n\n**Vague → Specific**\n- \"Mom's birthday\" → \"Order flowers for mom from LocalFlorist.com\"\n- \"Meeting prep\" → \"Print agenda and attendee list for Thursday meeting\"\n\n**Multi-Step → Next Action Only**\n- \"Plan vacation\" → \"Research flight prices to Hawaii for March\"\n- \"Taxes\" → \"Gather W-2 forms from filing cabinet\"\n\n### Processing Speed Tips\n\n**Keep Moving**\n- Don't over-think\n- Trust your gut\n- You can revise later\n- 30 seconds per item average\n\n**When Stuck**\n- Ask \"What would done look like?\"\n- Ask \"What's blocking this?\"\n- Someday/Maybe is valid\n- Trash liberally\n\n### Project Detection\n\n**Signs It's a Project**\n- Feels big or complex\n- Has multiple obvious steps\n- Will take multiple sessions\n- Has a specific end state\n\n**Project Examples**\n- \"Hire new assistant\" (many steps)\n- \"Organize garage\" (multiple actions)\n- \"Launch website\" (complex outcome)\n";
+
+/** Raw SKILL.md content for the `mind-sweep` skill. */
+export const mindSweep = "---\nname: Mind Sweep\ndescription: Comprehensive capture of everything on your mind\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Mind Sweep\n\nComprehensive capture of everything on your mind\n\n### Steps\n\n1. Find a quiet moment with no interruptions\n2. Set a timer for 15-20 minutes\n3. Write down EVERYTHING that has your attention\n4. Don't filter or organize - just capture\n5. Include work, personal, health, relationships, finances, etc.\n6. Check trigger lists: projects, waiting for, someday ideas\n7. Review physical spaces: desk, car, home - anything undone?\n8. Review digital spaces: emails, messages, bookmarks\n9. Continue until nothing new comes to mind\n10. All items go to inbox for later processing\n\n### Expected Outputs\n\n- Comprehensive inbox of captured items\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"mind sweep\"\n- \"brain dump\"\n- \"capture everything\"\n- \"clear my head\"\n";
+
+/** Raw SKILL.md content for the `clarify-task` skill. */
+export const clarifyTask = "---\nname: Clarify Fuzzy Task\ndescription: Turn a vague item into a concrete next action\ntype: invocable\nversion: \"1.0.0\"\nparameters: [fuzzyTask]\n---\n\n## Clarify Fuzzy Task\n\nTurn a vague item into a concrete next action\n\n### Steps\n\n1. Read the fuzzy task or item\n2. Ask: What is the desired outcome here?\n3. Ask: Is this actually actionable, or is it reference/someday?\n4. If actionable: What is the VERY NEXT physical action?\n5. The next action should start with a verb: Call, Email, Draft, Review, etc.\n6. Determine the context: Where/what do you need to do this?\n7. If it's part of a larger project, identify or create that project\n8. Replace the fuzzy task with the clear next action\n\n### Inputs Required\n\n- **fuzzyTask** (required): The unclear task or item to clarify\n\n### Expected Outputs\n\n- Clear next action\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"clarify\"\n- \"what's the next action\"\n- \"this is unclear\"\n- \"help me understand\"\n\n### Execution Mode\n\nThis workflow can be executed automatically when triggered. Proceed through the steps without waiting for confirmation at each step.\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nname: kit-expertise\ndescription: Domain expertise for GTD Productivity System - applied automatically when working in this kit\ntype: background\nversion: \"1.0.0\"\n---\n\n## Your Role\n\nYou are a productivity coach deeply familiar with David Allen's Getting Things Done methodology. You help users capture, clarify, organize, and execute their commitments effectively. You understand the psychology of task management, the importance of trusted systems, and how to maintain stress-free productivity.\n\n## Your Expertise\n\n- GTD five-step workflow\n- project vs next action distinction\n- context-based organization\n- weekly review process\n- inbox processing and clarification\n- natural planning model\n- horizons of focus\n- two-minute rule\n\n## Your Approach\n\nGuide and teach the user, helping them understand concepts deeply\n\n## Things to Avoid\n\n- Don't overcomplicate the system with unnecessary structure\n- Don't add actions without clarifying what \"done\" looks like\n- Never skip the clarify step - ensure everything is actionable\n- Don't create projects without identifying a next action\n\n## Domain Knowledge\n\n### Key Terms\n\n**next action**\nThe very next physical, visible action needed to move something forward\n\n**project**\nAny desired outcome requiring more than one action step\n\n**inbox**\nCollection point for anything that has your attention until processed\n\n**context**\nThe tool, location, or person needed to complete an action (@phone, @computer, @home)\n\n**waiting for**\nActions delegated to others that you need to track\n\n**someday/maybe**\nThings you might want to do but aren't committed to yet\n\n**two-minute rule**\nIf an action takes less than two minutes, do it now during processing\n\n**weekly review**\nRegular ritual to get clear, current, and creative about your system\n\n**horizons of focus**\nLevels from runway (actions) to 50,000ft (life purpose)\n\n**open loop**\nAnything pulling at your attention that hasn't been captured or clarified\n\n**natural planning model**\nPurpose → Vision → Brainstorm → Organize → Next Actions\n\n**mind sweep**\nComprehensive capture of everything on your mind into the inbox\n\n**clarify**\nProcessing inbox items to determine what they are and what to do with them\n\n**reference**\nInformation with no action required but potentially useful later\n\n### Best Practices\n\n- Capture everything that has your attention - don't rely on memory\n- Process inbox to zero regularly - clarify each item completely\n- Every project needs at least one next action\n- Next actions must be physical, visible activities\n- Organize by context, not by project, for doing mode\n- Weekly review is non-negotiable for system trust\n- Keep project support materials separate from action lists\n- Someday/maybe is a valid home - not everything needs to be active\n- Two minutes is the threshold - do it or defer it\n- Waiting for items need who and when captured\n\n### Common Mistakes to Avoid\n\n- Keeping things in your head instead of capturing\n- Having vague tasks like \"Work on project\" instead of specific next actions\n- Skipping the weekly review\n- Overloading today's list with unrealistic commitments\n- Not distinguishing projects from single actions\n- Using inbox as a to-do list instead of processing it\n- Context lists with non-actionable items\n- Projects without clear outcomes defined\n- Waiting for items without follow-up dates\n- Letting someday/maybe become a graveyard\n\n### Recommended References\n\n- [Getting Things Done](https://gettingthingsdone.com): David Allen's foundational book on the GTD methodology\n- **Making It All Work**: David Allen's follow-up on horizons of focus and life management\n- **GTD Podcast**: Regular discussions on GTD implementation and best practices\n- **The GTD Roadmap**: Official course structure for learning GTD systematically\n";
+
+/** Raw SKILL.md content for the `break-down-project` skill. */
+export const breakDownProject = "---\nname: Break Down Project\ndescription: Transform a project into actionable next steps\ntype: invocable\nversion: \"1.0.0\"\nparameters: [projectName]\n---\n\n## Break Down Project\n\nTransform a project into actionable next steps\n\n### Steps\n\n1. Review the project to understand the desired outcome\n2. Ask: What does \"done\" look like? Define clear success criteria\n3. Use natural planning: What's the purpose and vision?\n4. Brainstorm: What are all the things that might need to happen?\n5. Organize the brainstorm into logical sequences or categories\n6. Identify the very next physical action\n7. Add the next action to the appropriate context list\n8. Note any waiting for items or delegations needed\n9. Update the project file with the plan and next action\n\n### Inputs Required\n\n- **projectName** (required): The project to break down\n\n### Expected Outputs\n\n- Project plan\n- Identified next actions\n- Waiting for items\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"break down\"\n- \"plan project\"\n- \"next actions for\"\n- \"what should I do for\"\n";
+
+/** All skills for the gtd-productivity-system kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'process-inbox': processInbox,
+	'weekly-review': weeklyReview,
+	'gtd-methodology': gtdMethodology,
+	'inbox-processing': inboxProcessing,
+	'mind-sweep': mindSweep,
+	'clarify-task': clarifyTask,
+	'kit-expertise': kitExpertise,
+	'break-down-project': breakDownProject
+};

package/src/skills/index.ts

@@ -0,0 +1,109 @@
+/**
+ * @module @soulcraft/kits/skills
+ * @description Registry of all skill content across all kits.
+ *
+ * Generated from: kits/{kitId}/skills/{skillId}/SKILL.md
+ * Do not edit directly — re-run `bun run build:skills`.
+ *
+ * @example
+ * ```ts
+ * import { skillRegistry } from '@soulcraft/kits/skills';
+ * const skill = skillRegistry['wicks-and-whiskers']?.['inventory-health'];
+ * ```
+ */
+
+import * as apiDocumentationSkills from './api-documentation/index.js';
+import * as axeHouseSkills from './axe-house/index.js';
+import * as blogSeriesSkills from './blog-series/index.js';
+import * as businessPlanSkills from './business-plan/index.js';
+import * as canvasAndCorksSkills from './canvas-and-corks/index.js';
+import * as characterRelationshipMapSkills from './character-relationship-map/index.js';
+import * as clayAndCoSkills from './clay-and-co/index.js';
+import * as conceptMapSkills from './concept-map/index.js';
+import * as contentCalendarSkills from './content-calendar/index.js';
+import * as escapeVaultSkills from './escape-vault/index.js';
+import * as familyTreeSkills from './family-tree/index.js';
+import * as farkleDiceGameSkills from './farkle-dice-game/index.js';
+import * as gameDesignDocSkills from './game-design-doc/index.js';
+import * as gatherAndGrillSkills from './gather-and-grill/index.js';
+import * as gtdProductivitySystemSkills from './gtd-productivity-system/index.js';
+import * as marketingPlanSkills from './marketing-plan/index.js';
+import * as marketingSiteSkills from './marketing-site/index.js';
+import * as match3PuzzleSkills from './match-3-puzzle/index.js';
+import * as mindMapSkills from './mind-map/index.js';
+import * as musicCollectionSkills from './music-collection/index.js';
+import * as novelWritingSystemSkills from './novel-writing-system/index.js';
+import * as organizationChartSkills from './organization-chart/index.js';
+import * as pawsAndPourSkills from './paws-and-pour/index.js';
+import * as personaDrivenStrategySkills from './persona-driven-strategy/index.js';
+import * as personalCrmSkills from './personal-crm/index.js';
+import * as personalWikiSkills from './personal-wiki/index.js';
+import * as petalPressSkills from './petal-press/index.js';
+import * as pitchDeckSkills from './pitch-deck/index.js';
+import * as podcastSeriesSkills from './podcast-series/index.js';
+import * as pourHouseSkills from './pour-house/index.js';
+import * as productRequirementsDocSkills from './product-requirements-doc/index.js';
+import * as projectTimelineSkills from './project-timeline/index.js';
+import * as readingTrackerSkills from './reading-tracker/index.js';
+import * as recipeManagerSkills from './recipe-manager/index.js';
+import * as saasAppSkills from './saas-app/index.js';
+import * as screenplayWritingSkills from './screenplay-writing/index.js';
+import * as teacherLessonPlanSkills from './teacher-lesson-plan/index.js';
+import * as technicalSpecificationSkills from './technical-specification/index.js';
+import * as wanderlandsSkills from './wanderlands/index.js';
+import * as webApplicationSkills from './web-application/index.js';
+import * as wicksAndWhiskersSkills from './wicks-and-whiskers/index.js';
+import * as worldBuildingSkills from './world-building/index.js';
+import * as youtubeContentPlanSkills from './youtube-content-plan/index.js';
+
+/**
+ * All SKILL.md content across all kits, keyed by kit ID then skill ID.
+ *
+ * @description Each value is the raw SKILL.md string (frontmatter + body),
+ * ready for injection into AI system prompts.
+ */
+export const skillRegistry: Record<string, Record<string, string>> = {
+	'api-documentation': apiDocumentationSkills.allSkills,
+	'axe-house': axeHouseSkills.allSkills,
+	'blog-series': blogSeriesSkills.allSkills,
+	'business-plan': businessPlanSkills.allSkills,
+	'canvas-and-corks': canvasAndCorksSkills.allSkills,
+	'character-relationship-map': characterRelationshipMapSkills.allSkills,
+	'clay-and-co': clayAndCoSkills.allSkills,
+	'concept-map': conceptMapSkills.allSkills,
+	'content-calendar': contentCalendarSkills.allSkills,
+	'escape-vault': escapeVaultSkills.allSkills,
+	'family-tree': familyTreeSkills.allSkills,
+	'farkle-dice-game': farkleDiceGameSkills.allSkills,
+	'game-design-doc': gameDesignDocSkills.allSkills,
+	'gather-and-grill': gatherAndGrillSkills.allSkills,
+	'gtd-productivity-system': gtdProductivitySystemSkills.allSkills,
+	'marketing-plan': marketingPlanSkills.allSkills,
+	'marketing-site': marketingSiteSkills.allSkills,
+	'match-3-puzzle': match3PuzzleSkills.allSkills,
+	'mind-map': mindMapSkills.allSkills,
+	'music-collection': musicCollectionSkills.allSkills,
+	'novel-writing-system': novelWritingSystemSkills.allSkills,
+	'organization-chart': organizationChartSkills.allSkills,
+	'paws-and-pour': pawsAndPourSkills.allSkills,
+	'persona-driven-strategy': personaDrivenStrategySkills.allSkills,
+	'personal-crm': personalCrmSkills.allSkills,
+	'personal-wiki': personalWikiSkills.allSkills,
+	'petal-press': petalPressSkills.allSkills,
+	'pitch-deck': pitchDeckSkills.allSkills,
+	'podcast-series': podcastSeriesSkills.allSkills,
+	'pour-house': pourHouseSkills.allSkills,
+	'product-requirements-doc': productRequirementsDocSkills.allSkills,
+	'project-timeline': projectTimelineSkills.allSkills,
+	'reading-tracker': readingTrackerSkills.allSkills,
+	'recipe-manager': recipeManagerSkills.allSkills,
+	'saas-app': saasAppSkills.allSkills,
+	'screenplay-writing': screenplayWritingSkills.allSkills,
+	'teacher-lesson-plan': teacherLessonPlanSkills.allSkills,
+	'technical-specification': technicalSpecificationSkills.allSkills,
+	'wanderlands': wanderlandsSkills.allSkills,
+	'web-application': webApplicationSkills.allSkills,
+	'wicks-and-whiskers': wicksAndWhiskersSkills.allSkills,
+	'world-building': worldBuildingSkills.allSkills,
+	'youtube-content-plan': youtubeContentPlanSkills.allSkills
+};