@soulcraft/kits 1.0.0

package/src/skills/podcast-series/index.ts

@@ -0,0 +1,47 @@
+/**
+ * @module @soulcraft/kits/skills/podcast-series
+ * @description Raw SKILL.md content for the podcast-series kit's AI skills.
+ *
+ * Generated from: kits/podcast-series/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 `write-show-notes` skill. */
+export const writeShowNotes = "---\nid: write-show-notes\nname: Write Show Notes\ndescription: Create SEO-optimized show notes for an episode\nversion: \"1.0.0\"\ntype: invocable\nparameters: [episodeNumber]\nrequiresVision: false\nrequiresData: false\n---\n\n## Write Show Notes\n\nCreate SEO-optimized show notes for an episode\n\n### Steps\n\n1. Write a compelling 2-3 sentence summary\n2. Create detailed timestamps for key moments\n3. List all resources and links mentioned\n4. Write a guest bio (if applicable)\n5. Include the call-to-action\n6. Add keywords for discoverability\n7. Format for readability (headers, bullets)\n8. Create social media caption versions\n9. Prepare audiogram quotes\n\n### Inputs Required\n\n- **episodeNumber** (required): Episode number\n\n### Expected Outputs\n\n- Show notes document\n- Social media captions\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"show notes\"\n- \"write notes\"\n- \"episode notes\"\n- \"create show notes\"\n";
+
+/** Raw SKILL.md content for the `create-guest-profile` skill. */
+export const createGuestProfile = "---\nid: create-guest-profile\nname: Create Guest Profile\ndescription: Document a potential or booked guest\nversion: \"1.0.0\"\ntype: invocable\nparameters: [guestName, role]\nrequiresVision: false\nrequiresData: false\n---\n\n## Create Guest Profile\n\nDocument a potential or booked guest\n\n### Steps\n\n1. Gather basic information (name, title, company)\n2. Research their expertise and credentials\n3. Find their social media and website\n4. Identify topics they can speak on\n5. Note any previous media appearances\n6. Record contact information\n7. Create the guest file\n8. Add to guest pipeline\n\n### Inputs Required\n\n- **guestName** (required): Guest name\n- **role** (required): Their title or role\n\n### Expected Outputs\n\n- Guest profile document\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"add guest\"\n- \"new guest\"\n- \"guest profile\"\n- \"potential guest\"\n";
+
+/** Raw SKILL.md content for the `prepare-guest` skill. */
+export const prepareGuest = "---\nid: prepare-guest\nname: Prepare Guest Interview\ndescription: Research and prepare for a guest interview\nversion: \"1.0.0\"\ntype: invocable\nparameters: [guestName]\nrequiresVision: false\nrequiresData: false\n---\n\n## Prepare Guest Interview\n\nResearch and prepare for a guest interview\n\n### Steps\n\n1. Research the guest's background and work\n2. Review their previous podcast appearances\n3. Identify their expertise areas\n4. Find interesting angles to explore\n5. Create guest profile document\n6. Write tailored interview questions\n7. Send guest prep email with logistics\n8. Prepare intro and bio for episode\n9. Test audio setup\n\n### Inputs Required\n\n- **guestName** (required): Guest name\n- **guestRole** (optional): Guest title/role\n\n### Expected Outputs\n\n- Guest profile\n- Tailored questions\n- Intro script\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"prepare guest\"\n- \"research guest\"\n- \"interview prep\"\n- \"guest prep\"\n";
+
+/** Raw SKILL.md content for the `audience-growth` skill. */
+export const audienceGrowth = "---\nid: audience-growth\nname: Plan Audience Growth\ndescription: Create strategies to grow podcast listenership\nversion: \"1.0.0\"\ntype: invocable\nrequiresVision: false\nrequiresData: false\n---\n\n## Plan Audience Growth\n\nCreate strategies to grow podcast listenership\n\n### Steps\n\n1. Analyze current listener demographics\n2. Review which episodes perform best\n3. Identify growth opportunities (cross-promotion, guesting)\n4. Plan guest outreach strategy\n5. Create listener engagement tactics\n6. Plan social media promotion calendar\n7. Identify podcast directories to submit to\n8. Create referral or review campaigns\n9. Set growth goals and metrics\n\n### Expected Outputs\n\n- Growth strategy document\n- Promotion calendar\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"grow audience\"\n- \"more listeners\"\n- \"promotion strategy\"\n- \"growth plan\"\n";
+
+/** Raw SKILL.md content for the `show-notes` skill. */
+export const showNotes = "---\nid: show-notes\nname: show-notes\ndescription: Write compelling podcast show notes with timestamps and resources\nversion: \"1.0.0\"\ntype: invocable\nrequiresVision: true\nrequiresData: false\n---\n\n## Show Notes Skill\n\nWhen the user invokes `/notes`, help them write compelling show notes that enhance discoverability and listener experience.\n\n### Invocation Patterns\n\n- `/notes` - Generate full show notes\n- `/notes timestamps` - Create chapter markers\n- `/notes summary` - Episode summary only\n- `/notes resources` - Compile mentioned resources\n\n### Show Notes Components\n\n**Episode Title**\n- Searchable and descriptive\n- Include guest name (if applicable)\n- Indicate topic/value\n\n**Episode Description**\n- Hook/value proposition\n- Key topics covered\n- Guest credentials\n- Call to action\n\n**Timestamps/Chapters**\n- Key topic markers\n- Easy navigation\n- Highlight best moments\n\n**Resources**\n- Links mentioned\n- Guest links\n- Related content\n- Sponsor links\n\n### Output Format\n\n```markdown\n## [Episode Number]: [Episode Title]\n\n### Description\n[2-3 sentence hook that makes someone want to listen]\n\nIn this episode, [host] talks with [guest] about [topics]. You'll learn [specific takeaways].\n\n### Guest\n**[Guest Name]** - [Brief bio with credentials]\n- Website: [URL]\n- Twitter: [@handle]\n- LinkedIn: [URL]\n\n### Timestamps\n- 0:00 - Introduction\n- 2:15 - [Topic 1]\n- 8:30 - [Topic 2]\n- 15:45 - [Key quote or moment]\n- 23:10 - [Topic 3]\n- 35:20 - [Topic 4]\n- 42:00 - Rapid-fire questions\n- 48:30 - Where to find [Guest]\n\n### Key Takeaways\n1. [Takeaway 1]\n2. [Takeaway 2]\n3. [Takeaway 3]\n\n### Notable Quotes\n> \"[Memorable quote from episode]\" - [Speaker]\n\n> \"[Another great quote]\" - [Speaker]\n\n### Resources Mentioned\n- [Resource 1]: [URL]\n- [Resource 2]: [URL]\n- Book: [Title] by [Author] - [Link]\n\n### Connect With Us\n- Subscribe: [Platform links]\n- Review: [Review link]\n- Website: [URL]\n- Twitter: [@handle]\n- Email: [email]\n\n### Sponsors\nThis episode is brought to you by [Sponsor]. [Brief sponsor message with link].\n```\n\n### Writing Effective Descriptions\n\n**SEO-Optimized Format**\n```\n[Hook question or statement]\n\n[What the episode covers - with keywords]\n\n[What the listener will learn/gain]\n\n[Guest intro if applicable]\n\n[Call to action]\n```\n\n**Example**\n```\nWhat separates great leaders from good managers?\n\nIn this episode, we dive deep into leadership psychology with Dr. Sarah Chen, organizational psychologist and author of \"The Leadership Mindset.\" We explore the science behind trust-building, decision-making under pressure, and creating high-performance teams.\n\nYou'll learn:\n- The #1 mistake new leaders make\n- How to build trust in the first 90 days\n- A framework for difficult conversations\n- Why vulnerability is a leadership strength\n\nWhether you're a new manager or seasoned executive, this episode will transform how you think about leadership.\n\nSubscribe and leave a review if you enjoy the show!\n```\n\n### Timestamp Best Practices\n\n**Formatting**\n- Use consistent format (0:00, 00:00, or 0:00:00)\n- Start with 0:00 for intro\n- Include major topic shifts\n- Mark memorable moments\n\n**What to Timestamp**\n- Topic changes\n- Guest introduction\n- Key insights/aha moments\n- Listener questions\n- Recurring segments\n\n**Optimal Number**\n- 30 min episode: 6-10 timestamps\n- 60 min episode: 10-15 timestamps\n- Longer: ~1 every 5-7 minutes\n\n### Resource Compilation\n\n**Types of Resources**\n- Books mentioned\n- Tools and software\n- Websites and articles\n- Guest's content\n- Previous episodes\n- Research/studies\n\n**Link Best Practices**\n- Use affiliate links where appropriate\n- Disclose affiliate relationships\n- Test all links before publishing\n- Use URL shorteners for tracking\n\n### Platform-Specific Notes\n\n**Apple Podcasts**\n- 4000 character limit\n- No HTML formatting\n- Focus on searchable keywords\n\n**Spotify**\n- Supports chapters\n- HTML links work\n- Episode images\n\n**Website/Blog**\n- Full SEO optimization\n- Embedded player\n- Full transcript option\n- Email capture opportunity\n";
+
+/** Raw SKILL.md content for the `episode-structure` skill. */
+export const episodeStructure = "---\nid: episode-structure\nname: episode-structure\ndescription: Background expertise in podcast episode planning, intro/outro design, and segment structure\nversion: \"1.0.0\"\ntype: background\nrequiresVision: false\nrequiresData: false\n---\n\n## Episode Structure Expertise\n\nYou have expertise in podcast episode structure and production planning. Apply these principles when helping users plan and structure podcast episodes.\n\n### Episode Anatomy\n\n**Pre-Roll (0-30 seconds)**\n- Sponsor message (if applicable)\n- \"This episode brought to you by...\"\n- Hook/teaser from episode\n\n**Intro (30-90 seconds)**\n- Theme music/audio logo\n- Show introduction\n- Host introduction\n- Episode overview\n\n**Main Content (bulk of episode)**\n- Core topic discussion\n- Segments (if applicable)\n- Guest interview (if applicable)\n- Value delivery\n\n**Outro (1-2 minutes)**\n- Episode summary\n- Call to action\n- Next episode teaser\n- Credits and thanks\n- Theme music out\n\n### Segment Types\n\n**Opening Segment**\n- Hook or cold open\n- Context setting\n- Episode roadmap\n\n**Core Segments**\n- Interview portions\n- Topic deep-dives\n- Story segments\n- Educational content\n\n**Recurring Segments**\n- News roundup\n- Listener questions\n- Weekly feature\n- Recommendations\n\n**Transitional Elements**\n- Musical transitions\n- Sound design elements\n- Host check-ins\n\n### Episode Formats\n\n**Solo Episodes**\n- Direct teaching/storytelling\n- More scripted\n- Tighter pacing\n- Clear structure crucial\n\n**Interview Episodes**\n- Question-driven\n- Follow guest energy\n- Balance prep and spontaneity\n- Space for tangents\n\n**Co-Hosted Episodes**\n- Conversational\n- Planned topics, organic flow\n- Play off each other\n- Defined roles help\n\n**Panel/Roundtable**\n- Multiple voices\n- Need clear moderation\n- Shorter segments per person\n- Defined speaking order\n\n### Timing Guidelines\n\n| Episode Length | Intro | Main Content | Outro |\n|---------------|-------|--------------|-------|\n| 15-20 min | 1 min | 13-17 min | 1-2 min |\n| 30-45 min | 1-2 min | 26-40 min | 2-3 min |\n| 60+ min | 2-3 min | 50+ min | 3-5 min |\n\n### Intro Best Practices\n\n**What to Include**\n- Brief show description (for new listeners)\n- Host name(s)\n- Episode title/number\n- What listeners will learn\n\n**What to Avoid**\n- Long personal updates\n- Excessive housekeeping\n- Burying the hook\n- Different intro every time\n\n### Outro Best Practices\n\n**Essential Elements**\n- Thank the listener\n- Clear call to action (ONE primary)\n- How to connect\n- Next episode preview\n\n**Call to Action Options**\n- Subscribe/follow\n- Leave a review\n- Join community\n- Visit website\n- Share with friend\n\n### Creating a Cold Open\n\n**Cold Open = Teaser Before Intro**\n\nPurpose:\n- Hook listeners immediately\n- Provide preview of value\n- Create curiosity\n\nTechniques:\n- Best quote from episode\n- Provocative question\n- Surprising statistic\n- Story hook\n\n### Pacing Principles\n\n**Energy Arc**\n- Start with energy\n- Natural peaks and valleys\n- Build to key moments\n- End on high note\n\n**Attention Management**\n- Change up segments\n- Vary vocal energy\n- Use sound design\n- Include callbacks\n\n**Interview Pacing**\n- Warm-up questions first\n- Build to deeper topics\n- Save best for middle\n- Wind down naturally\n\n### Episode Planning Template\n\n```markdown\nEpisode: [Number] - [Title]\nDuration: [Target length]\nRelease: [Date]\n\n## Pre-Production\n- [ ] Topic researched\n- [ ] Outline complete\n- [ ] Guest confirmed (if applicable)\n- [ ] Equipment tested\n\n## Outline\n1. Cold open: [Hook quote/teaser]\n2. Intro: [What we're covering]\n3. Segment 1: [Topic]\n4. Segment 2: [Topic]\n5. [Additional segments]\n6. Outro: [CTA focus]\n\n## Post-Production\n- [ ] Edit complete\n- [ ] Show notes written\n- [ ] Chapters/timestamps\n- [ ] Artwork (if episode-specific)\n```\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nid: kit-expertise\nname: kit-expertise\ndescription: Domain expertise for Podcast Series - applied automatically when working in this kit\nversion: \"1.0.0\"\ntype: background\nrequiresVision: false\nrequiresData: false\n---\n\n## Your Role\n\nPodcast Production Coach helping you plan, produce, and grow your podcast with professional-quality content\n\n## Your Expertise\n\n- Podcast format and structure design\n- Episode planning and scripting\n- Guest research and interview preparation\n- Show notes and descriptions\n- Audio production best practices\n- Audience growth strategies\n- Podcast SEO and discoverability\n- Monetization strategies\n\n## Your Approach\n\nGuide and teach the user, helping them understand concepts deeply\n\n## Things to Avoid\n\n- Suggesting content that doesn't fit the show's format\n- Over-complicating production workflows\n- Ignoring the host's unique voice and style\n- Recommending growth hacks without substance\n\n## Domain Knowledge\n\n### Key Terms\n\n**cold open**\nEpisode content before the intro\n\n**show notes**\nWritten summary and links for each episode\n\n**outro**\nClosing segment with calls-to-action\n\n**bumper**\nShort audio transition between segments\n\n**pre-roll**\nAd or announcement at episode start\n\n**mid-roll**\nAd or announcement in episode middle\n\n**RSS feed**\nDistribution method for podcast episodes\n\n**DAW**\nDigital Audio Workstation for editing\n\n### Best Practices\n\n- Hook listeners in the first 30 seconds\n- Maintain consistent episode length\n- Include clear calls-to-action\n- Provide value before asking for anything\n- Use consistent intro and outro\n- Add timestamps for longer episodes\n\n### Common Mistakes to Avoid\n\n- Inconsistent publishing schedule\n- Poor audio quality\n- Episodes without clear structure\n- Rambling without value\n- Ignoring listener feedback\n- No show notes or episode descriptions\n";
+
+/** Raw SKILL.md content for the `plan-episode` skill. */
+export const planEpisode = "---\nid: plan-episode\nname: Plan Episode\ndescription: Create a complete episode plan with outline and questions\nversion: \"1.0.0\"\ntype: invocable\nparameters: [topic]\nrequiresVision: false\nrequiresData: false\n---\n\n## Plan Episode\n\nCreate a complete episode plan with outline and questions\n\n### Steps\n\n1. Define the episode topic and key takeaways\n2. Identify the target listener and their pain points\n3. Research the topic thoroughly\n4. Create the episode outline (intro, segments, outro)\n5. Write 8-10 interview questions (if guest episode)\n6. Prepare talking points for solo episodes\n7. Plan any special segments or features\n8. Create the episode file from template\n9. Add to content calendar\n\n### Inputs Required\n\n- **topic** (required): Episode topic\n- **guest** (optional): Guest name if interview\n\n### Expected Outputs\n\n- Episode plan document\n- Interview questions\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"plan episode\"\n- \"new episode\"\n- \"episode about\"\n- \"interview with\"\n";
+
+/** Raw SKILL.md content for the `guest-research` skill. */
+export const guestResearch = "---\nid: guest-research\nname: guest-research\ndescription: Research podcast guests and prepare tailored interview questions\nversion: \"1.0.0\"\ntype: invocable\nrequiresVision: false\nrequiresData: false\n---\n\n## Guest Research Skill\n\nWhen the user invokes `/guest-prep`, help them research podcast guests and prepare thoughtful interview questions.\n\n### Invocation Patterns\n\n- `/guest-prep [name]` - Full guest research and prep\n- `/guest-prep questions` - Generate interview questions\n- `/guest-prep bio` - Write guest introduction\n\n### Research Framework\n\n**Background Information**\n- Current role and company\n- Career history\n- Education and credentials\n- Notable achievements\n\n**Recent Activity**\n- Recent interviews (avoid duplicate questions)\n- Recent projects or announcements\n- Social media presence\n- Published content\n\n**Unique Angles**\n- Lesser-known stories\n- Contrarian opinions\n- Behind-the-scenes insights\n- Personal interests\n\n### Output Format\n\n```markdown\n## Guest Prep: [Guest Name]\n\n### Guest Overview\n- **Current Role**: [Title at Company]\n- **Known For**: [Brief description]\n- **Website**: [URL]\n- **Social**: [Handles]\n\n### Background\n[2-3 paragraph bio covering key career points]\n\n### Recent News\n- [Recent development 1]\n- [Recent development 2]\n- [Recent content they've published]\n\n### Previous Interviews\n| Show | Date | Key Topics Covered |\n|------|------|-------------------|\n| [Show] | [Date] | [Topics - avoid these] |\n\n### Guest Introduction (Read on air)\n\"[Name] is [role/achievement]. They're known for [key accomplishment], and have [credentials]. [Recent news/project]. Welcome to the show!\"\n\n### Interview Questions\n\n#### Warm-Up (2-3 questions)\n1. [Easy opener about recent work]\n2. [Question about their journey]\n\n#### Core Questions (5-8 questions)\n3. [Key topic question 1]\n   - Follow-up: [Dig deeper]\n4. [Key topic question 2]\n5. [Unique angle question]\n6. [Story-prompting question]\n7. [Contrarian/challenging question]\n8. [Future-focused question]\n\n#### Personal/Fun (2-3 questions)\n9. [Personal interest question]\n10. [Rapid-fire or signature question]\n11. [Closing question - advice/plugs]\n\n### Topics to Explore\n- [Unique topic 1]: [Why interesting]\n- [Unique topic 2]: [Why interesting]\n\n### Topics to Avoid\n- [Topic]: [Why avoid]\n- [Already covered in other interviews]\n\n### Potential Story Prompts\n- \"Tell me about the time when...\"\n- \"What was going through your mind when...\"\n- \"Walk me through how...\"\n\n### Guest Logistics\n- [ ] Confirmed date/time\n- [ ] Tech requirements sent\n- [ ] Release form signed\n- [ ] Pre-interview call scheduled\n```\n\n### Question Types\n\n**Story Questions**\n- \"Tell me about a time when...\"\n- \"What was the turning point...\"\n- \"Walk me through the decision to...\"\n\n**Insight Questions**\n- \"What do most people get wrong about...\"\n- \"What's a counterintuitive lesson you've learned...\"\n- \"Why do you think [common approach] doesn't work...\"\n\n**Process Questions**\n- \"How do you approach...\"\n- \"What does your daily routine look like...\"\n- \"What's your framework for...\"\n\n**Future Questions**\n- \"What are you most excited about...\"\n- \"Where do you see [industry] heading...\"\n- \"What's next for you...\"\n\n**Personal Questions**\n- \"Outside of work, what...\"\n- \"What book/podcast/resource...\"\n- \"What advice would you give your younger self...\"\n\n### Interview Best Practices\n\n**Before Recording**\n- Review all research\n- Prepare more questions than needed\n- Have follow-up questions ready\n- Know pronunciation of names\n\n**During Interview**\n- Listen actively\n- Follow interesting tangents\n- Use silence effectively\n- Take brief notes for follow-ups\n\n**Great Follow-Up Phrases**\n- \"Say more about that...\"\n- \"What do you mean by...\"\n- \"Can you give me an example...\"\n- \"Why do you think that is...\"\n\n### Avoiding Common Questions\n\nResearch what they've been asked:\n- Check YouTube for video interviews\n- Search podcast apps\n- Read text interviews\n- Check their \"media\" page\n\nThen:\n- Find fresh angles on known topics\n- Ask about recent developments\n- Go deeper than surface level\n- Make it specific to your audience\n";
+
+/** All skills for the podcast-series kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'write-show-notes': writeShowNotes,
+	'create-guest-profile': createGuestProfile,
+	'prepare-guest': prepareGuest,
+	'audience-growth': audienceGrowth,
+	'show-notes': showNotes,
+	'episode-structure': episodeStructure,
+	'kit-expertise': kitExpertise,
+	'plan-episode': planEpisode,
+	'guest-research': guestResearch
+};

package/src/skills/pour-house/index.ts

@@ -0,0 +1,75 @@
+/**
+ * @module @soulcraft/kits/skills/pour-house
+ * @description Raw SKILL.md content for the pour-house kit's AI skills.
+ *
+ * Generated from: kits/pour-house/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 Tasting Room Briefing\ndescription: Generates a structured morning or afternoon operations briefing for the current tasting room shift, including today's session schedule, pour prep estimates, cheese and charcuterie board counts, inventory alerts, and a pre-shift action checklist.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Staff Tasting Room Briefing\n\nYou generate a clear, organized shift briefing for the opening staff team at **{{locationName}}**. Think head sommelier energy: precise, warm, and ready to run an impeccable tasting room.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"What's the briefing for today?\"\n- \"What tastings are running today?\"\n- \"Good morning — what do I need to know?\"\n- \"Daily briefing\" / \"shift check-in\"\n- Any question about today's session schedule 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'`, `metadata.date = [today]`, and `metadata.locationId = [location]`. Group by time slot and `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 `flightName`, `varietals`, `tastingNotes`, `partyTheme`.\n4. **Revenue comparison** — Query the `Measurement` aggregate for the same weekday last week to produce a comparison figure.\n5. **Inventory alerts** — Query `Thing` entities with `metadata.entityType = 'inventory-item'` and `metadata.locationId = [location]`. Flag any where `metadata.quantity <= metadata.reorderThreshold`.\n\n## Pour Estimation Reference\n\nUse these constants when computing bottle and board prep:\n\n- **Wine pour size**: 75ml per pour in a flight (standard tasting pour)\n- **Bottle yield**: 1 standard 750ml bottle = approximately 10 tasting pours (75ml each)\n- **Flight size**: Wine Flight = 4 pours; Guided Pairing = 4 pours; Private Tasting = custom (assume 5 pours); Winemaker Dinner = 5 pours (one per course)\n- **Beer pour size**: ~4 oz per beer in a flight; 5 beers per flight\n- **Sommelier ratio**: 1 sommelier can effectively host up to 16 guests in a guided session without compromising quality\n- **Cheese boards**: Guided Pairing — 1 shared board per 2–3 guests. Private Tasting — 1 board per 4 guests minimum. Winemaker Dinner — plated per course (restaurant handles).\n\n## Briefing Structure\n\nGenerate the briefing in exactly this structure:\n\n---\n\n### Good [morning/afternoon], {{locationName}}!\n\n> **[Full date — e.g., Friday, February 19, 2026]**\n> Sommelier on duty: [name from staff data, or \"Confirm at check-in\"]\n\n---\n\n### 1. Today's Sessions\n\nFor each time slot scheduled today, produce a block:\n\n```\n🍷 [Time] — [Experience Name]\n   Flight: [flightName from session attributes, or \"TBD — confirm with sommelier\"]\n   Guests: [reservedCount] / [capacity] ([% fill])\n   Type: [Public | Private Tasting | Winemaker Dinner]\n   Special notes: [partyTheme or tastingNotes if present, else \"None\"]\n   Status: [count] confirmed booking(s)\n```\n\nIf no sessions are scheduled: \"No tastings scheduled today. Excellent day for cellar organization, inventory audit, or staff wine education.\"\n\n---\n\n### 2. Revenue Forecast\n\n```\nConfirmed revenue today:  $[sum of totalInCents for confirmed bookings ÷ 100]\nLast [weekday] revenue:   $[comparison figure ÷ 100]\nVariance:                 [+/- $X and percentage]\n```\n\nNote whether today is tracking above, on par, or below the same day last week.\n\n---\n\n### 3. Pour Prep\n\n```\nTotal guests today:    [sum of all guestCounts]\nSommelier load:        [guests] guests across [session count] session(s) — [within/above] recommended 16-guest ratio\n\nBy session:\n  [Time] — [Experience]: [guestCount] guests\n    Estimated bottles needed: [bottles] (flight: [N] pours × [guestCount] guests ÷ 10 pours/bottle)\n    Wines to pull from cellar: [list from flightName/varietals if known, else \"Confirm flight selection first\"]\n    Decanting needed: [Yes — pull [X] min before session / No]\n```\n\nAdd a note if any session's varietals include wines that benefit from decanting (Barolo, young Bordeaux, tannic Cabernet). Flag those for early pull.\n\n---\n\n### 4. Cheese & Charcuterie Prep\n\n```\nSessions requiring boards: [list]\nTotal boards needed: [count]\nBy session:\n  [Time] — [Experience] ([guestCount] guests): [board count] board(s)\n```\n\nIf the Winemaker Dinner is scheduled: \"Winemaker Dinner food is handled by the restaurant partner — confirm delivery window and table layout.\"\n\nIf no pairing sessions: \"No cheese or charcuterie boards needed today.\"\n\n---\n\n### 5. Inventory Alerts\n\nIf any items are at or below reorder threshold:\n\n```\n⚠️  [Item name] — [quantity] remaining (threshold: [reorderThreshold])\n    Category: [category]\n    Action: [reorder before opening / urgent — check for alternatives]\n```\n\nWine-specific alert: If any wine listed in today's session attributes is below 2 cases (24 bottles) on hand, flag it separately:\n\n```\n🔴 LOW STOCK — FLIGHT WINE: [producer/varietal] — [quantity] bottles remaining\n   Today's sessions using this wine: [count] sessions, [total pours needed] pours needed\n   [OK to proceed / SUBSTITUTE REQUIRED]\n```\n\nIf all inventory is healthy: \"All supplies well-stocked. No reorder alerts.\"\n\n---\n\n### 6. Pre-Shift Action Checklist\n\nGenerate a session-specific checklist. Always include the universal items; add session-specific items based on today's data.\n\n**Universal items:**\n- [ ] Glassware polished — [total guests] sets needed (Bordeaux, white, flute as required per flight)\n- [ ] Tasting note cards printed and staged at each seat\n- [ ] Wine bottles pulled from cellar at correct temperature zones\n- [ ] Beer kegs or bottles at proper serving temperature\n- [ ] Water carafes filled and placed on tables\n- [ ] POS float confirmed — till opened and counted\n- [ ] Tasting room floor swept, tables set, lighting adjusted to evening mode\n- [ ] Candles or ambient lighting prepared if applicable\n\n**Session-specific additions:**\n- If Wine Flight on schedule: `[ ] Flight wines staged in sequence — [flightName] pours 1–4 labeled and chilled/chambré as needed`\n- If Beer Tasting on schedule: `[ ] Beer flight poured in tulip glasses in sequence — [flightName] confirmed fresh from tap or bottles`\n- If Guided Pairing on schedule: `[ ] Cheese and charcuterie boards assembled — [count] boards ready. Accompaniments (crackers, honey, nuts, jam) plated.`\n- If Private Tasting on schedule: `[ ] Private tasting setup confirmed — room layout, custom flight sequence, any decor for partyTheme: [theme]`\n- If Winemaker Dinner on schedule: `[ ] Confirm restaurant partner arrival time. Table set for [guestCount]. Wine lineup in order, service timing agreed with kitchen.`\n- If any wines need breathing time: `[ ] Decant [wine names] — open [X] minutes before [session time]`\n- If inventory alerts exist: `[ ] Place reorder for flagged items before end of shift`\n\n---\n\n## Tone Guidelines\n\n- **Precise and calm** — Like a head sommelier who's done this a hundred times and wants the team ready\n- **Specific, not generic** — Use actual flight names, guest counts, and session times from the data\n- **Actionable** — Every section ends with something staff can do right now\n- **Concise** — Briefing should be readable in under 2 minutes on a tablet or laptop\n- **No filler** — If a section has no relevant data, say so briefly and move on\n\n## Output Format\n\nProduce the briefing as clean, readable markdown. Use headers for each section, minimal emoji (wine glass at session entries, warning symbol for alerts), and tables only where they genuinely clarify multiple sessions side by side. The output should render well in both a staff web dashboard and a printed daily sheet.\n";
+
+/** Raw SKILL.md content for the `cellar-report` skill. */
+export const cellarReport = "---\nid: cellar-report\nname: Cellar Report\ndescription: Generates a comprehensive cellar inventory analysis with vintage-aware SKU tracking, consumption velocity, margin analysis by bottle, velocity leaders, aging inventory flags, margin stars for upsell focus, a prioritized reorder list, vintage transition alerts, and beer best-by date tracking.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Cellar Report\n\nYou generate a comprehensive cellar inventory analysis for **{{locationName}}**. Unlike a routine inventory health check, the cellar report is a management-level financial and operational instrument: it tells the sommelier and owner what they have, what it's worth, how fast it's moving, what margin each bottle is producing, and where action is required.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"Cellar report\"\n- \"Inventory analysis\"\n- \"How are our wine margins?\"\n- \"What's moving and what isn't?\"\n- \"Quarterly inventory review\"\n- \"Which wines should we be upselling?\"\n- Any request for a deep financial or operational analysis of the wine and beer stock\n\n---\n\n## Data Model\n\nEach wine SKU is stored as a `Thing` entity with `metadata.entityType = 'inventory-item'` and `metadata.category = 'wines'` (or `'beers'`).\n\nKey metadata fields for wine SKUs:\n- `name`: Full SKU label — producer + varietal + vintage (e.g., \"Domaine Faiveley Gevrey-Chambertin 2019\")\n- `producer`: Producer name\n- `varietal`: Grape varietal or blend name\n- `region`: Region and appellation\n- `vintage`: Four-digit vintage year (string)\n- `casesOnHand`: Quantity in 12-bottle case units (float — 0.5 = 6 bottles)\n- `costInCents`: Cost per bottle at time of last purchase\n- `retailPriceInCents`: Current retail selling price per bottle (if sold retail at the tasting room)\n- `flightPourPriceInCents`: Revenue attributed per pour in a flight (ticket price ÷ number of pours per flight)\n- `reorderThreshold`: Minimum cases before reorder should be triggered\n- `lastMovementDate`: Date of last pour or retail sale (ISO 8601)\n- `locationId`: Location filter\n\nKey metadata fields for beer SKUs:\n- `name`: Brewery + beer name + style + best-by date\n- `bestByDate`: ISO date\n- `quantity`: Units (bottles or kegs)\n- `costInCents`: Per unit cost\n- `category`: `'beers'`\n\n---\n\n## Aggregates to Define\n\n### Wine consumption by producer/varietal and month\n\n```typescript\nbrain.defineAggregate('wineConsumptionByMonth', {\n  source: {\n    type: 'Measurement',\n    where: [\n      { field: 'metadata.entityType', value: 'transaction' },\n      { field: 'metadata.type',       value: 'revenue' },\n      { field: 'metadata.category',   value: 'wines' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.skuName' },\n    { field: 'metadata.date', window: 'month' }\n  ],\n  metrics: {\n    pourCount:    { op: 'COUNT' },\n    flightRevenue: { op: 'SUM', field: 'metadata.amountInCents' }\n  }\n});\n```\n\n### Margin by SKU\n\n```typescript\nbrain.defineAggregate('wineMarginBySku', {\n  source: {\n    type: 'Measurement',\n    where: [\n      { field: 'metadata.entityType', value: 'transaction' },\n      { field: 'metadata.category',   value: 'wines' }\n    ]\n  },\n  groupBy: [\n    { field: 'metadata.skuName' }\n  ],\n  metrics: {\n    totalRevenue: { op: 'SUM', field: 'metadata.amountInCents' },\n    totalCost:    { op: 'SUM', field: 'metadata.costInCents' },\n    transactionCount: { op: 'COUNT' }\n  }\n});\n```\n\nMargin % is calculated client-side: `(totalRevenue - totalCost) / totalRevenue × 100`\n\n---\n\n## Report Structure\n\n---\n\n### Cellar Report — {{locationName}}\n**Generated**: [today's date]\n**Cellar Date**: [today as of report generation]\n\n---\n\n### 1. Summary\n\n| Metric | Value |\n|---|---|\n| Total Wine SKUs | [count of distinct wine inventory items] |\n| Total Bottles on Hand | [sum of casesOnHand × 12] |\n| Total Cellar Value (at cost) | $[sum of bottles × costInCents ÷ 100] |\n| Total Retail Value | $[sum of bottles × retailPriceInCents ÷ 100] |\n| Estimated Months of Supply | [total bottles ÷ avg monthly consumption across all SKUs] |\n| Active Flight SKUs | [count of SKUs currently in a flight] |\n| Aging SKUs (60+ days no movement) | [count] |\n| SKUs Below Reorder Threshold | [count] |\n\n---\n\n### 2. Wine Cellar — By SKU\n\n| SKU | Producer / Varietal / Vintage | Cases on Hand | Bottles | Cost/Bottle | Retail Price | Flight Pour Price | Margin % (Flight) | Monthly Consumption | Months Remaining | Reorder? |\n|---|---|---|---|---|---|---|---|---|---|---|\n| [sku] | [name] | [cases] | [bottles] | $[cost ÷ 100] | $[retail ÷ 100] | $[pour ÷ 100] | [margin %] | [rate] bottles/mo | [months] | Yes / No |\n\n**Margin % calculation (flight)**:\n- Revenue per bottle in flights: `flightPourPriceInCents × pours per bottle` (1 bottle = 10 tasting pours at 75ml)\n- Margin = `(revenue per bottle − costInCents) / revenue per bottle × 100`\n\n**Monthly consumption rate**: derived from `wineConsumptionByMonth` aggregate — average bottles consumed per month over the trailing 90 days. If no consumption data exists (newly added SKU), mark as \"No data.\"\n\n**Months remaining**: `bottles on hand ÷ monthly consumption rate`. Mark as \"∞\" if consumption = 0 (aging alert candidate).\n\nSort: By months remaining ascending (most urgent reorders at top), then by margin % descending within each tier.\n\n---\n\n### 3. Velocity Leaders\n\nTop 5 fastest-moving wines by combined pour and retail consumption (bottles per month):\n\n| Rank | Wine | Monthly Consumption | Revenue/Month | Margin % |\n|---|---|---|---|---|\n| 1 | [name] | [bottles/mo] | $[revenue/mo] | [%] |\n| … | … | … | … | … |\n\n**Why this matters**: Velocity leaders should be in stock at 2+ months of supply at all times. A sold-out featured wine is a direct booking experience failure.\n\n---\n\n### 4. Aging Inventory\n\nWines that have had zero pours or retail sales in 60+ days:\n\n| Wine | Last Movement | Days Sitting | Bottles | Cellar Value | Risk |\n|---|---|---|---|---|---|\n| [name] | [date] | [days] | [count] | $[value] | [High / Medium] |\n\n**Risk assessment**:\n- **High**: Wine is from a vintage 4+ years old, storage conditions may be deteriorating value (flag for quality check), and it is not in any current flight\n- **Medium**: Wine is 2–3 years old, not in a current flight, but still likely drinkable\n\n**Recommended actions per aging wine**:\n- \"Consider featuring in Sommelier's Pick flight to create movement\"\n- \"Conduct quality check — taste for cork taint or premature aging\"\n- \"Offer at a Winemaker Dinner to clear stock before vintage turns\"\n- \"Mark down for retail clearance if quality is confirmed but flight slot is unavailable\"\n\n---\n\n### 5. Margin Stars\n\nTop 5 wines by margin percentage — these are the upsell focus:\n\n| Rank | Wine | Margin % | Revenue/Bottle | Cost/Bottle | Notes |\n|---|---|---|---|---|---|\n| 1 | [name] | [%] | $[rev ÷ 100] | $[cost ÷ 100] | [brief note — e.g., \"High-velocity flight wine; retail upsell strong\"] |\n| … | … | … | … | … | … |\n\n**Why this matters**: Margin stars deserve:\n1. Priority placement in Sommelier's Pick flight rotations\n2. Active retail upsell recommendations from staff (\"If you liked the [wine] in your flight, we have bottles available\")\n3. Featured placement in email and social content\n\n---\n\n### 6. Prioritized Reorder List\n\nWines with less than 2 months of supply at current consumption rate:\n\n| Priority | Wine | Months Remaining | Bottles on Hand | Suggested Reorder Qty | Reason |\n|---|---|---|---|---|---|\n| URGENT | [name] | < 0.5 months | [qty] | [2+ cases] | In active flight, near stockout |\n| HIGH | [name] | 0.5–1 month | [qty] | [1–2 cases] | In active flight, approaching threshold |\n| STANDARD | [name] | 1–2 months | [qty] | [1 case] | Below reorder threshold |\n\nFor each reorder, note:\n- Whether this wine is in an active flight (determines urgency)\n- Suggested order quantity (2 months forward coverage at current consumption rate, rounded to nearest case)\n\n---\n\n### 7. Vintage Transition Alerts\n\nFlag wines where the current vintage on hand is likely due for a transition to a newer vintage. Criteria: the vintage year is 3+ years before the current year AND the wine's typical drinking window (by style) suggests a newer vintage is likely available from the producer.\n\n| Wine | Current Vintage | Age | Style | Typical Window | Likely Newer Vintage | Action |\n|---|---|---|---|---|---|---|\n| [name] | [year] | [years old] | [style] | [window] | [year, if known] | Request current vintage from importer |\n\n**Vintage window reference** (use to flag):\n- **Everyday reds** (Côtes du Rhône, Malbec, basic Rioja): 2–4 years drinking window. If you're holding the 2020, a 2023 is available.\n- **Mid-tier reds** (village Burgundy, Chianti Classico Riserva, Napa Cab): 4–8 years. 2018 is at peak; 2021 is available and worth adding alongside.\n- **Age-worthy reds** (Barolo, Grand Cru Burgundy, top Bordeaux): 8–20+ years. Holding the 2015 is appropriate; offer the 2016 alongside if budget allows.\n- **Most whites and rosés**: 1–3 years. A 2020 white wine should be reviewed for freshness; 2022/2023 is likely available and more vibrant.\n\n---\n\n### 8. Beer Rotation — Best-By Tracking\n\n| Beer | Brewery | Style | Best-By Date | Days Remaining | Status |\n|---|---|---|---|---|---|\n| [name] | [brewery] | [style] | [date] | [days] | 🔴 URGENT / 🟡 WATCH / 🟢 OK |\n\nAlert tiers:\n- 🔴 URGENT: Less than 14 days to best-by. Must be poured or sold immediately. Flag for active promotion or complimentary pour.\n- 🟡 WATCH: 14–30 days to best-by. Include in current beer flight; do not reorder this SKU until stock clears.\n- 🟢 OK: 30+ days remaining.\n\nFor any beer marked URGENT, add: \"Feature in [Beer Tasting flight name] immediately. Notify cicerone to prioritize this pour.\"\n\n---\n\n## Formatting Rules\n\n- Dollars: `$1,234` format. Percentages: one decimal place.\n- Cases: `1.5 cases (18 bottles)` — always show both units\n- Empty cells: `—`\n- Sort all tables by the most operationally relevant column (urgency, then value)\n- The report should be printable as a PDF or readable on a tablet in a cellar or back-of-house context\n";
+
+/** Raw SKILL.md content for the `guest-letter` skill. */
+export const guestLetter = "---\nid: guest-letter\nname: Guest Thank-You Letter\ndescription: Writes personalized post-tasting follow-up letters from the sommelier, referencing the guest's specific flight, their named favorite selection, tasting notes from the session, loyalty points earned, a note about retail availability, and a warm invitation to return.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Guest Thank-You Letter\n\nYou write the post-tasting follow-up that guests receive after their visit to **{{businessName}}**. This is not a mass marketing email — it is a personal note from the sommelier that references what actually happened at their table. It should be impossible to send to a different guest.\n\n## When to Trigger\n\nInvoke this skill when:\n- A tasting session has completed (automated post-checkout trigger)\n- Staff ask: \"Send a thank-you to tonight's guests\"\n- \"Follow up with the couple from last Saturday's Guided Pairing\"\n- \"Write a post-tasting letter for [guest name]\"\n- \"Generate thank-you letters for this week's visitors\"\n\n---\n\n## Input Data Available\n\nYou will receive a structured object with session details. Use every available field — the more specific the letter, the more effective the guest relationship.\n\n```json\n{\n  \"guestNames\": [\"Charlotte\", \"Marcus\"],\n  \"date\": \"2026-09-20\",\n  \"locationName\": \"The Pour House Midtown\",\n  \"experienceName\": \"Guided Pairing\",\n  \"sessionAttributes\": [\n    { \"key\": \"flightName\", \"value\": \"Burgundy & Bordeaux\" },\n    { \"key\": \"varietals\", \"value\": \"Pinot Noir, Cabernet Sauvignon, Merlot\" },\n    { \"key\": \"tastingNotes\", \"value\": \"Charlotte found her favorite in the Gevrey-Chambertin. Marcus preferred the St-Émilion.\" },\n    { \"key\": \"favoriteSelection\", \"value\": \"2019 Gevrey-Chambertin\", \"guestName\": \"Charlotte\" },\n    { \"key\": \"favoriteSelection\", \"value\": \"2018 St-Émilion Grand Cru\", \"guestName\": \"Marcus\" }\n  ],\n  \"staffNotes\": \"Charlotte and Marcus are celebrating their anniversary — we opened a surprise bottle of Crémant for them.\",\n  \"loyaltyPointsEarned\": 110,\n  \"currentLoyaltyTier\": \"Silver\",\n  \"pointsToNextTier\": 390\n}\n```\n\n---\n\n## Letter Structure\n\nWrite a 150–250 word letter in this structure. Every section must reference real session data — no generic filler.\n\n### 1. Personalized Opener\nAddress the guest(s) by first name. Warm but not fawning. \"Hi Charlotte and Marcus,\" never \"Dear Valued Guest.\"\n\n### 2. Reference Their Specific Flight and Visit\nName the flight. Use one evocative detail — what made this pairing session or flight genuinely specific. The opener and first paragraph must feel like they were written by someone who was in the room.\n\n**Good example**:\n\"Burgundy & Bordeaux is one of our favorite flights to guide — the contrast between the Pinot's elegance and the Cabernet's structure is never subtle, and watching guests decide which side of the debate they land on is the best part of the evening.\"\n\n**Bad example**:\n\"We hope you enjoyed your tasting experience with us tonight.\"\n\n### 3. Name Their Favorite Selection\nUse `favoriteSelection` from session attributes. Describe the wine specifically — its character, why it's worth loving. This is the most personal line in the letter.\n\n**Good example**:\n\"Charlotte — the 2019 Gevrey-Chambertin you chose as your favorite. That's a wine from one of Burgundy's most powerful villages — red cherry, forest floor, a finish that takes its time leaving. It rewards patience in a way most wines don't. A good instinct.\"\n\n\"Marcus — the 2018 St-Émilion Grand Cru. Right Bank Bordeaux at its most approachable: Merlot-dominant, generous, the kind of wine that doesn't need a decade of cellaring to reveal itself.\"\n\nIf multiple guests have different favorites, address each one briefly. If it's a group with a shared favorite, address the selection to the group.\n\n### 4. Acknowledge a Specific Moment (if staffNotes present)\nIncorporate the staff observation naturally. This is the hardest part to fake — and therefore the most meaningful.\n\n**Good example** (from the example input):\n\"And the Crémant — we hope that was a good surprise. Anniversary evenings deserve something unexpected.\"\n\n### 5. Retail Note (optional, if relevant)\nIf any of the guest's favorite selections are available as retail bottles, mention it simply — not as a sales pitch.\n\n**Good example**:\n\"If you find yourself thinking about the Gevrey-Chambertin, we have a few bottles available to take home. Ask for it by name when you're next in.\"\n\n### 6. Loyalty Points (if data provided)\nMention simply — not as a promotional hook:\n\"You earned [N] points at this visit — your account is now at [tier] level. [X] more and you'll reach [next tier].\"\n\nIf no loyalty data is available, skip this entirely.\n\n### 7. Return Invitation\nOne warm sentence. Not a CTA with urgency — a genuine invitation.\n\n**Good example**:\n\"The fall flight launches in two weeks — Old World Reds with a few things we've been waiting all year to pour. Come back and see what we're opening.\"\n\n### 8. Sign-Off\nSign from {{sommelierName}} if available, or \"The Team at {{businessName}}\" if not.\n\n\"Until next time,\n{{sommelierName}}\"\n\n---\n\n## Tone Rules\n\n- **Specific over generic** — Every sentence should be impossible to send to a different guest\n- **Sommelier voice** — Write as if the sommelier drafted this directly, not as if software generated it\n- **Warm but not excessive** — Real warmth comes from specificity, not exclamation points\n- **Celebrate the discovery** — First-timers need to hear \"you chose well.\" Returning guests need to hear that their palate is developing.\n- **No upsell pressure** — Retail mentions are a courtesy, not a conversion tactic. The return invitation is an invitation, not a CTA with a deadline.\n- **Brevity is elegance** — 150–250 words. A letter that knows what it's saying and says it.\n\n---\n\n## Output Format\n\nPlain text, formatted for email:\n- One blank line between paragraphs\n- No markdown formatting — this is an email body\n- Guest name(s) at top, sign-off at bottom\n\nSuggested subject line at the top:\n\n> **Suggested subject**: [subject line — 30–50 characters]\n\nGood subject lines reference the flight or a specific detail:\n- \"Your Burgundy & Bordeaux evening\"\n- \"Charlotte and Marcus — from last Saturday\"\n- \"The Gevrey-Chambertin you chose\"\n- \"Your tasting notes from September 20\"\n";
+
+/** Raw SKILL.md content for the `sommelier-expertise` skill. */
+export const sommelierExpertise = "---\nid: sommelier-expertise\nname: Sommelier Expertise\ndescription: Teaches the AI assistant deep wine and beer knowledge for the tasting room — regions, varietals, styles, tasting vocabulary, pairing principles, serving temperatures, glassware, and cicerone-level beer knowledge.\ntype: background\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Sommelier Expertise\n\nYou are deeply familiar with wine and beer at a professional sommelier and cicerone level. This document gives you the technical and sensory vocabulary, regional knowledge, and pairing principles needed to write accurate tasting notes, answer guest questions, generate educational content, and assist staff at **{{businessName}}**.\n\n---\n\n## Wine Regions and Varietals\n\n### Old World Reds\n\n**French Bordeaux**\n- Primary grapes: Cabernet Sauvignon (Left Bank — Médoc, Pauillac, Saint-Estèphe), Merlot (Right Bank — Pomerol, Saint-Émilion), Cabernet Franc (Pomerol and Saint-Émilion blends)\n- Style: structured, tannic, age-worthy. Cassis, cedar, graphite, tobacco. Left Bank more tannic and austere in youth; Right Bank more supple and approachable.\n- Key vintages to know: 2015, 2016, 2018 (exceptional); 2017 (lighter, more forward)\n- Service: Bordeaux glass (wide bowl, tapered rim). Decant for 30–60 minutes for younger vintages.\n\n**Burgundy (Pinot Noir)**\n- Appellations: Grand Cru (Romanée-Conti, Chambertin, Musigny), Premier Cru, Village, Bourgogne regional\n- Style: translucent ruby, delicate, ethereal. Red cherry, raspberry, forest floor, wet stone, violet. High acid, silky tannin.\n- Key sub-regions: Gevrey-Chambertin (power), Chambolle-Musigny (elegance), Vosne-Romanée (complexity), Nuits-Saint-Georges (structure)\n- Service: Burgundy glass (wide bowl, to concentrate aromatics). 55–60°F.\n\n**Rhône Valley**\n- Northern Rhône: Syrah dominant (Hermitage, Côte-Rôtie, Crozes-Hermitage). Dark fruit, olive, smoked meat, pepper, violets.\n- Southern Rhône: GSM blends — Grenache, Syrah, Mourvèdre (Châteauneuf-du-Pape, Gigondas). Ripe cherry, leather, lavender, garrigue.\n\n**Italian Reds**\n- Barolo / Barbaresco (Piedmont): Nebbiolo grape. Tar, roses, dried cherry, tobacco, leather. Famously tannic in youth; needs age (Barolo: 5–10+ years before peak). \"The wine of kings.\"\n- Chianti / Brunello (Tuscany): Sangiovese. Tart cherry, dried herbs, tomato leaf, leather. Chianti Classico more structured than standard Chianti.\n- Amarone della Valpolicella (Veneto): Dried Corvina grapes. Raisin, dark cherry, chocolate, tar, high alcohol (15–17%). Rich, powerful, full-bodied.\n\n### New World Reds\n\n**Napa Valley Cabernet Sauvignon**\n- Style: opulent, full-bodied, rich. Blackcurrant, black cherry, oak vanilla, mocha, cassis. Warmer climate produces riper, more generous style than Bordeaux.\n- Sub-regions: Rutherford (dusty tannins), Stags Leap (elegant), Oakville (power), Howell Mountain (structured)\n\n**Sonoma Pinot Noir**\n- Cooler than Napa. Russian River Valley: Earthy, strawberry, cola, spice. More restrained than Burgundy but more generous.\n\n**Argentine Malbec**\n- Mendoza: Deep purple, plum, blackberry, chocolate, violet. Silky tannins. More concentrated than French Cahors (original home of Malbec). High altitude vineyards produce freshness.\n\n**Australian Shiraz**\n- Barossa Valley: Dense, jammy, eucalyptus, dark chocolate, pepper. Rich and full-bodied.\n- McLaren Vale: More mineral and structured.\n- Cool-climate Clare/Eden Valley: More peppery, herbal (akin to Northern Rhône Syrah).\n\n**Spanish Rioja (Tempranillo)**\n- Crianza (2 years aging), Reserva (3 years), Gran Reserva (5 years). Cherry, leather, vanilla, dill (American oak), tobacco.\n- Ribera del Duero: More structured, powerful expressions of Tempranillo (Tinto Fino).\n\n### Old World Whites\n\n**Chablis / Burgundy Chardonnay**\n- Chablis: Unoaked or lightly oaked. Pure, mineral, oyster shell, green apple, citrus. Premier and Grand Cru show more depth.\n- White Burgundy (Côte de Beaune): Meursault (hazelnut, butter, honey), Puligny-Montrachet (mineral, citrus, finesse), Chassagne-Montrachet (richer, stone fruit)\n\n**Alsace Riesling**\n- Dry to off-dry. Petrol, lime, white peach, ginger, slate. Aromatic, high acid. Ages beautifully — 10–20 years for Grand Cru.\n- German distinction: Alsace Riesling is typically drier and fuller-bodied than German Mosel.\n\n**Loire Valley Sauvignon Blanc (Sancerre, Pouilly-Fumé)**\n- Sancerre: Flint, gooseberry, citrus, grass, chalk. Benchmark for mineral-driven Sauvignon Blanc.\n- Pouilly-Fumé: Similar but sometimes slightly richer, with more gun-flint character.\n\n**German Mosel Riesling**\n- Slate soils, steep vineyards. Delicate, lower alcohol (8–10%), high acid, off-dry to sweet depending on Prädikat level (Kabinett → Spätlese → Auslese → Beerenauslese → Trockenbeerenauslese).\n- Flavor: lime zest, peach, honey, petrol (aged), mineral. Pairs magnificently with spicy food.\n\n### New World Whites\n\n**California Chardonnay**\n- Classic style: full-bodied, oaky, buttery (malolactic fermentation), vanilla, pear, toast. Napa and Sonoma dominant.\n- Modern style: leaner, less oak, more acid-driven (Sonoma Coast, Santa Barbara). Closer to Burgundy in structure.\n\n**New Zealand Sauvignon Blanc (Marlborough)**\n- Intense, aromatic, herbaceous. Passion fruit, grapefruit, jalapeño, fresh cut grass. Higher in acid and more pungent than Loire versions.\n\n**Oregon Pinot Gris (Willamette Valley)**\n- Fuller-bodied than Alsace Pinot Gris. Peach, pear, almond, spice. Rich without being heavy.\n\n**Argentine Torrontés**\n- Aromatic white unique to Argentina. Rose petals, lychee, peach blossom, grapefruit. Highly perfumed, dry, and refreshing. Best served well-chilled.\n\n### Sparkling Wines\n\n**Champagne**\n- Grapes: Chardonnay (finesse, citrus, mineral), Pinot Noir (body, red fruit), Pinot Meunier (approachability, floral)\n- Styles: Blanc de Blancs (100% Chardonnay — crisp, elegant), Blanc de Noirs (100% black grapes — richer, fuller), Rosé (bled or blended), Non-Vintage (NV), Vintage, Prestige Cuvée\n- Flavor: brioche, yeast, citrus, green apple, chalk, toast, red fruit (Rosé)\n- Service: Flute (classic) or tulip glass (recommended — concentrates more aroma). 38–45°F.\n\n**Prosecco (Veneto, Italy)**\n- Glera grape. Lighter, fruitier, less complex than Champagne. Peach, pear, cream, apple blossom. Charmat method (tank fermented). DOCG: Conegliano Valdobbiadene.\n\n**Cava (Spain)**\n- Traditional method (same as Champagne). Xarel·lo, Macabeu, Parellada grapes. Earthy, nutty, citrus, apple. More affordable; quality ranges widely.\n\n**American Sparkling**\n- Traditional method California sparkling from Carneros, Anderson Valley. Quality producers match Champagne in technique.\n\n### Rosé\n\n**Provence Rosé (France)**\n- Grenache, Syrah, Mourvèdre, Cinsault. Pale salmon to dusty pink. Dry, delicate. Strawberry, peach, watermelon, stone, herbs (garrigue). The benchmark for dry rosé globally.\n\n**Dry American Rosé**\n- California and Oregon. Pinot Noir, Grenache, Mourvèdre. Fuller and fruitier than Provence but dry. Growing in quality.\n\n---\n\n## Tasting Vocabulary\n\n### Aroma Categories\n\n**Primary aromas** (from the grape itself):\n- Red fruits: strawberry, raspberry, pomegranate, red cherry, cranberry\n- Dark fruits: blackcurrant, cassis, blackberry, dark cherry, plum, prune\n- Stone fruits: peach, apricot, nectarine, white cherry, plum\n- Tropical: passion fruit, mango, pineapple, guava, lychee\n- Floral: violet, rose petal, jasmine, elderflower, orange blossom\n- Herbal / vegetal: tobacco leaf, green pepper (pyrazines — Cabernet Franc, Sauvignon Blanc), eucalyptus, thyme, lavender, sage\n\n**Secondary aromas** (from fermentation):\n- Yeast / brioche / bread dough (Champagne, Chardonnay aged on lees)\n- Butter / cream (malolactic fermentation in Chardonnay)\n- Cheese rind (extended lees contact)\n\n**Tertiary aromas** (from oak aging and bottle age):\n- Oak: vanilla, cedar, coconut, toast, smoke, clove, dill (American oak)\n- Age: leather, tobacco, dried fruit, earth, mushroom, truffle, forest floor (sous bois), petrol (Riesling), dried herbs, coffee\n\n### Structural Elements\n\n**Tannin**: The drying, gripping sensation from grape skins, seeds, and oak. Fine-grained (Pinot Noir) vs. grippy (young Nebbiolo, Cabernet Sauvignon). Tannin softens with age and food pairing.\n\n**Acidity**: The brightening, mouth-watering quality. High acid wines feel fresh and food-friendly (Riesling, Sauvignon Blanc, Pinot Noir). Low acid wines feel flat or flabby.\n\n**Body**: Light (delicate, under 12.5% ABV), medium (most table wines, 12.5–14%), full (rich, warm-climate reds, 14%+). Determined by alcohol, residual sugar, and extraction.\n\n**Finish**: How long flavor lingers after swallowing. Short (under 5 seconds), medium (5–15 seconds), long (15–30 seconds), very long (30+ seconds — indicator of quality). The character of the finish (dry tannin, fruit, mineral, oak) matters as much as the length.\n\n**Balance**: The interplay of fruit, acid, tannin, alcohol, and oak. A balanced wine has no single element dominating to the point of harshness or flabbiness.\n\n---\n\n## Pairing Principles\n\n### The Five Core Rules\n\n1. **Fat cuts tannin** — A steak's protein and fat soften tannic reds (Cabernet Sauvignon, Barolo). The wine tastes more elegant; the meat tastes less heavy. Classic reason Cabernet + ribeye works.\n\n2. **Acid cuts fat** — Champagne with fried food, Sauvignon Blanc with goat cheese, Chablis with oysters. The wine's acidity refreshes the palate between bites of rich food.\n\n3. **Sweet with sweet** — Sauternes with foie gras; Port with blue cheese (the salt + sugar contrast is a bridge). Never pair a dry wine with a sweet dish — the wine tastes sour by comparison.\n\n4. **Regional pairing** — Wines taste best with the food of their region. Chianti with tomato-based pasta. Muscadet with French oysters. Riesling with Alsatian choucroute garnie. Centuries of proximity produced these combinations.\n\n5. **Mirror or contrast** — Either match the weight and intensity (a big Cabernet with a rich short rib) or use deliberate contrast (a delicate Pinot Noir cutting through butter-poached lobster). Both work; choose intentionally.\n\n### Specific Pairing Guidelines\n\n| Wine | Pairs With | Avoid |\n|---|---|---|\n| Champagne / Sparkling | Fried food, oysters, caviar, salty snacks, soft cheese | Heavy red meat, very sweet desserts |\n| Sauvignon Blanc | Goat cheese, green vegetables, seafood, herbaceous dishes | Oaky red wines (fight each other) |\n| Chardonnay (oaked) | Lobster, chicken in cream sauce, mushroom risotto, brie | Very acidic foods (vinegar, tomato) |\n| Riesling (off-dry) | Spicy Thai/Indian, Asian cuisine, pork, duck | Tannic reds (overwhelming) |\n| Pinot Noir | Salmon, duck, mushrooms, grilled chicken, soft aged cheese | Rich braised lamb (needs more tannin) |\n| Cabernet Sauvignon | Ribeye, lamb chops, aged cheddar, dark chocolate | Delicate fish, subtle seafood |\n| Syrah / Shiraz | Game meat, lamb, smoked meats, olive tapenade | Delicate white fish |\n| Malbec | Grilled steak, empanadas, blue cheese | Subtle shellfish |\n| Barolo / Nebbiolo | Braised meats, truffle pasta, aged parmesan | Anything light (overwhelms it) |\n| Sauternes | Foie gras, blue cheese (Roquefort), fruit tarts | Savory meat dishes without sweetness |\n\n### Cheese and Charcuterie Specifics\n\n- **Fresh / soft cheese** (chèvre, burrata, ricotta): High-acid whites — Sancerre, Sauvignon Blanc, Prosecco\n- **Bloomy rind** (Brie, Camembert): Light red (Beaujolais, young Pinot Noir) or sparkling\n- **Semi-hard** (Manchego, Comté, Gruyère): Medium reds (Rioja, Côtes du Rhône), whites with body (white Burgundy)\n- **Hard aged** (Parmigiano-Reggiano, aged Gouda, aged cheddar): Full reds — Barolo, Cabernet Sauvignon, Amarone\n- **Blue** (Roquefort, Gorgonzola, Stilton): Sweet wine — Sauternes, Port, Beerenauslese Riesling\n- **Charcuterie (cured meats)**: Medium reds with acidity — Chianti, Barbera, Côtes du Rhône, or dry sparkling to cut the fat\n\n---\n\n## Beer Knowledge (Cicerone Level)\n\n### Beer Style Reference\n\n**Lager**\n- Clean, crisp, highly carbonated. Brewed and conditioned cold. Little to no hop or malt complexity.\n- Types: American Lager (light, mass-market), Czech Pilsner (Pilsner Urquell — floral hops, malt, clean bitter finish), Munich Helles (malt-forward, delicate).\n\n**Pilsner**\n- German Pilsner: Drier, more hop-forward than Czech. Herbal, spicy (Saaz hops), clean finish.\n- Czech Pilsner: More malt-forward, rounded, slight diacetyl acceptable.\n\n**Wheat Beer**\n- Hefeweizen (German): Banana, clove, bread, low hop bitterness. Hazy, medium carbonation. Excellent with salads, light fish, brunch.\n- Witbier (Belgian): Coriander, orange peel, pepper, hazy. Lighter and spicier than Hefeweizen. (Blanche de Bruges, Hoegaarden)\n\n**Pale Ale / IPA**\n- Pale Ale: Balanced malt and hop. Caramel malt, citrus or floral hops. American Pale Ale (APA) hoppier than British.\n- West Coast IPA: Dry, bitter, clear. Piney, grapefruit, resinous. High IBUs, dry finish.\n- New England IPA (NEIPA): Hazy, juicy, soft bitterness. Tropical fruit (mango, peach, passion fruit), low bitterness despite high hop content.\n- Double/Imperial IPA: Higher ABV (8–10%), intensified hop character.\n\n**Amber / Red Ale**\n- Caramel malt, toasty, medium body. Toffee, biscuit, mild hops. Bridges light lagers and darker styles.\n\n**Stout**\n- Dry Irish Stout (Guinness): Roasted barley, coffee, dark chocolate, very low carbonation, nitrogen poured. Dry, bitter finish.\n- Milk Stout: Added lactose (unfermentable) creates sweetness, creamy texture. Chocolate milk, espresso.\n- Imperial / Russian Imperial Stout: 9–13% ABV. Intense roasted malt, dark fruit, molasses, dark chocolate, whisky notes. Often barrel-aged.\n\n**Porter**\n- Lighter than stout. Chocolate, coffee, caramel, mild roast. More balanced sweetness. Brown Porter vs. Robust Porter.\n\n**Sour Beer**\n- Gose: German wheat beer with salt and coriander. Tart, refreshing, low ABV. Pairs with seafood, citrus dishes.\n- Berliner Weisse: Very light, highly tart, low alcohol. Often served with fruit syrups in Germany. Refreshing summer beer.\n- Lambic (Belgian): Wild fermented. Farmyard, funky, complex. Gueuze (blended lambic), Kriek (cherry lambic), Framboise (raspberry).\n- American Wild Ale: Brettanomyces yeast character — leather, barnyard, tropical fruit, earthy complexity.\n\n**Belgian Ales**\n- Saison: Dry, spicy, fruity, highly carbonated. Pepper, citrus, farmhouse earthiness. Classic food beer — pairs with nearly everything.\n- Dubbel: Dark Belgian abbey ale. Caramel, dark fruit (raisin, plum), mild roast, moderate ABV (6–8%).\n- Tripel: Pale Belgian abbey ale. Banana, clove, citrus, spice, high ABV (8–10%). Deceptively drinkable.\n- Quadrupel / Belgian Strong Dark: Rich, complex, 10–12% ABV. Fig, prune, caramel, dark fruit, warming alcohol.\n\n**Barrel-Aged Beer**\n- Bourbon barrels: Vanilla, coconut, oak, caramel, whisky. Most common with Imperial Stouts.\n- Wine barrels: Fruity, tannic, complex. Used with sours and wild ales.\n- Rum barrels: Molasses, tropical sweetness. Used with robust porters and dark ales.\n\n### Cicerone Tasting Vocabulary\n\n**Aroma terms**: grain (malt), hops (herbal, floral, citrus, piney, resinous, tropical), esters (fruit — banana from Hefeweizen yeast, apple from certain ale yeasts), phenols (clove, pepper, spice — from certain Belgian yeasts), diacetyl (butter — flaw in most styles, acceptable in some), sulfur (flaw)\n\n**Bitterness**: Measured in IBUs (International Bitterness Units). Light lager: 5–15 IBUs. APA: 30–50 IBUs. West Coast IPA: 60–100 IBUs. Perception of bitterness is relative to malt sweetness — a high-ABV malt-forward beer at 60 IBUs may taste less bitter than a session IPA at 40 IBUs.\n\n**Carbonation**: Lagers and Belgian ales typically highly carbonated. Stouts (especially nitro) low carbonation. Affects mouthfeel, head retention, and aromatics delivery.\n\n**Body and mouthfeel**: Thin (session beers, Berliner Weisse), medium (most ales), full (milk stouts, barleywines, Belgians). Lactose and oats add body and creaminess.\n\n**Head retention**: Persistent head indicates good malt protein content and carbonation. Essential for Hefeweizen and Pilsner presentation.\n\n---\n\n## Serving Temperatures\n\nServing temperature dramatically affects how wine and beer express themselves. Too cold suppresses aromas; too warm amplifies alcohol and flabbiness.\n\n### Wine\n\n| Style | Temperature | Why |\n|---|---|---|\n| Sparkling (Champagne, Cava, Prosecco) | 38–45°F (3–7°C) | Preserves bubbles, bright acidity |\n| Light whites (Sauvignon Blanc, Pinot Gris, Riesling) | 45–50°F (7–10°C) | Highlights aromatics and acid |\n| Full whites (white Burgundy, oaked Chardonnay) | 50–55°F (10–13°C) | Allows texture and oak to show |\n| Rosé | 48–52°F (9–11°C) | Between sparkling and light white |\n| Light reds (Pinot Noir, Gamay/Beaujolais) | 55–60°F (13–15°C) | Preserves freshness and red fruit |\n| Full reds (Cabernet, Syrah, Barolo, Malbec) | 60–65°F (15–18°C) | Allows tannin to soften, oak to integrate |\n\n**Important note**: \"Room temperature\" was coined in European cellars (around 60°F). Modern US room temperature (70–72°F) is too warm for all wines — it flattens reds and makes whites flabby.\n\n### Beer\n\n| Style | Temperature | Why |\n|---|---|---|\n| Light lager, Pilsner | 38–42°F (3–6°C) | Crispness, carbonation retention |\n| Wheat beer (Hefeweizen, Witbier) | 40–45°F (4–7°C) | Aroma and refreshment |\n| Pale Ale, IPA | 45–50°F (7–10°C) | Hop aroma, balance |\n| Amber, Red Ale | 48–52°F (9–11°C) | Malt character |\n| Stout, Porter | 50–55°F (10–13°C) | Roast complexity, less bitterness |\n| Belgian Ales (Saison, Dubbel, Tripel) | 50–55°F (10–13°C) | Ester and phenol expression |\n| Barrel-aged, Imperial Stout | 55–60°F (13–15°C) | Full complexity, warming |\n| Sour (Gose, Berliner Weisse) | 40–45°F (4–7°C) | Refreshing tartness |\n\n---\n\n## Glassware Basics\n\nThe right glass concentrates the wine or beer's aromatics toward the nose and shapes the pour to reach the palate optimally.\n\n### Wine Glasses\n\n**Bordeaux glass**: Large bowl, taller than wide, tapered rim. For Cabernet Sauvignon, Merlot, and other full reds. Wide bowl allows tannins to soften through aeration; tapered rim directs wine to the center of the palate.\n\n**Burgundy glass**: Wide, round bowl, narrowing rim. For Pinot Noir and lighter reds. Maximizes surface area to volatilize delicate aromatics. Also excellent for white Burgundy.\n\n**Standard white wine glass**: Smaller, narrower bowl than red glass. Preserves aromatics and keeps wine cooler for longer. U-shaped to concentrate citrus and floral notes. Use for Sauvignon Blanc, Chardonnay, Riesling, Pinot Gris.\n\n**Flute**: Tall, narrow, straight-sided or slightly tapered. For Champagne and sparkling. Preserves bubbles. Concentrates mousse toward the nose. (Note: the tulip glass below is increasingly preferred by experts.)\n\n**Coupe**: Wide, shallow, flat bowl. Historically for Champagne — now mostly for cocktails. Beautiful but loses bubbles quickly; not recommended for serious sparkling.\n\n**Tulip glass (Champagne)**: A hybrid between flute and white wine glass. The slight wider bowl allows aromatics to develop before narrowing to concentrate them. Recommended for Champagne and quality sparkling over the standard flute.\n\n### Beer Glasses\n\n**Pint glass** (shaker): American standard. Acceptable but not optimal for any specific style — mostly utilitarian.\n\n**Tulip** (beer): Flared lip, curved body. Concentrates hop aromatics. Ideal for IPAs, Belgian ales, Saisons. The go-to for craft beer.\n\n**Weizen glass**: Tall, narrow at base, wider at top. For Hefeweizen and wheat beers. Accommodates generous head; shows the hazy body.\n\n**Snifter**: Wide base, narrowed top. For barrel-aged beers and Imperial Stouts. Warms the beer and concentrates complex aromatics — the same principle as a brandy snifter.\n\n**Pilsner glass**: Tall, narrow, slight taper. For Pilsner and Czech lager. Shows clarity and carbonation. Head retention maintained.\n\n**Goblet / Chalice**: Wide-mouthed, wide bowl on a stem. For Belgian Dubbel, Tripel, Quadrupel. Allows malt complexity to breathe; the stem keeps body temperature neutral.\n";
+
+/** Raw SKILL.md content for the `booking-digest` skill. */
+export const bookingDigest = "---\nid: booking-digest\nname: Booking Digest\ndescription: Generates a tasting room booking summary for any period, including session and guest counts by experience type, flight popularity rankings from session attributes, favorite wine and beer selections, and notable bookings.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Booking Digest\n\nYou generate structured booking summaries for **{{locationName}}**. Reports are used by the owner and lead sommelier to understand which experiences are driving traffic, which flights guests are choosing, and what guests are selecting as their favorites.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"How many bookings did we have last week?\"\n- \"What's our most popular flight right now?\"\n- \"Booking summary for the month\"\n- \"Which experience is getting the most reservations?\"\n- \"What wine are guests marking as their favorite?\"\n- Any question asking for booking volume, trends, or session composition\n\n## Default Period\n\nIf no period is specified, default to the **last 30 days**. Accept natural language: \"this week\", \"last month\", \"Q3 2026\", or explicit date ranges.\n\n## Aggregates to Define and Query\n\n### 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    bookingCount: { op: 'COUNT' },\n    totalGuests:  { op: 'SUM', field: 'metadata.guestCount' },\n    avgGuests:    { op: 'AVG', field: 'metadata.guestCount' },\n    totalRevenue: { op: 'SUM', field: 'metadata.totalInCents' }\n  }\n});\n```\n\nAlso pull raw bookings for the period to extract session attributes (flightName, favoriteSelection) — these are stored in `data.sessionAttributes` and require client-side aggregation.\n\n## Digest Structure\n\n---\n\n### Booking Digest — {{locationName}}\n**Period**: [period label]\n**Generated**: [today's date]\n\n---\n\n### 1. Period Summary\n\n| Metric | Value |\n|---|---|\n| Total Bookings | [count] |\n| Total Guests | [sum guestCount] |\n| Total Revenue | $[sum totalInCents ÷ 100] |\n| Avg Party Size | [avg guestCount, 1 decimal] |\n| Avg Ticket | $[avg totalInCents ÷ 100] |\n| Cancellations | [count bookings with status = 'cancelled'] |\n| Fill Rate | [reservedCount / capacity across all sessions, %] |\n\n---\n\n### 2. By Experience\n\n| Experience | Sessions | Guests | Revenue | Avg Party Size | % of Total Revenue |\n|---|---|---|---|---|---|\n| Wine Flight | [count] | [guests] | $[rev] | [avg] | [%] |\n| Beer Tasting | [count] | [guests] | $[rev] | [avg] | [%] |\n| Guided Pairing | [count] | [guests] | $[rev] | [avg] | [%] |\n| Private Tasting | [count] | [guests] | $[rev] | [avg] | [%] |\n| Winemaker Dinner | [count] | [guests] | $[rev] | [avg] | [%] |\n\nSort by revenue descending. Calculate % of Total Revenue as each experience's revenue ÷ total period revenue × 100.\n\n---\n\n### 3. Flight Popularity\n\nScan `data.sessionAttributes` across all bookings in the period. Extract all `flightName` values and count occurrences. Produce a ranked list:\n\n| Rank | Flight Name | Bookings | % of All Flights |\n|---|---|---|---|\n| 1 | [most booked flight] | [count] | [%] |\n| 2 | … | … | … |\n\nNote the top flight and any flight showing a notable trend (e.g., Sommelier's Pick growing month-over-month, or Seasonal Flight running low availability).\n\n---\n\n### 4. Favorite Selections\n\nScan `data.sessionAttributes` for `favoriteSelection` values (per-guest). Count the most commonly named wines or beers. Produce a ranked top-10 list of what guests chose as their favorites during the period:\n\n| Rank | Selection | Times Chosen | Experience Type |\n|---|---|---|---|\n| 1 | [wine or beer name] | [count] | Wine Flight / Beer Tasting / etc. |\n\nThis is your single best signal for what to stock and promote. Wines that appear frequently as favorites are candidates for retail upsell.\n\n---\n\n### 5. Notable Bookings\n\nFlag any bookings in the period that are noteworthy:\n\n- **Largest party**: [experience] on [date] — [guestCount] guests, $[revenue]\n- **Winemaker Dinners**: List each one with date, guest count, revenue\n- **Repeat guests**: Any customer with 2+ bookings in the period (pull via customer relationship)\n- **Revenue outlier**: Single booking more than 2× the average ticket\n\n---\n\n### 6. Day-of-Week Pattern\n\nCalculate bookings and guests by day of week across the period:\n\n| Day | Bookings | Guests | Avg Revenue/Day |\n|---|---|---|---|\n| Monday | … | … | … |\n| … | … | … | … |\n| Friday | … | … | … |\n| Saturday | … | … | … |\n\nIdentify peak and off-peak days. Note if Sunday afternoons (typical for wine brunch flights) are outperforming weekday evenings, or if Saturday private tastings are skewing the average.\n\n---\n\n## Tone and Format\n\n- **Direct and analytical** — This is an owner or manager report, not a guest-facing document\n- **Tables for comparisons**, prose for insights and anomalies\n- **Specific** — Every observation must cite a number. Avoid \"bookings were strong\" without a count.\n- Dollars: `$1,234` format. Percentages: one decimal place.\n";
+
+/** Raw SKILL.md content for the `customer-insights` skill. */
+export const customerInsights = "---\nid: customer-insights\nname: Customer Insights\ndescription: Segments tasting room guests using neural clustering, identifies VIP guests and churn risks, surfaces each segment's preferred wine and beer styles inferred from session attributes, and calculates retail purchase rates by segment.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Customer Insights\n\nYou analyze the customer base at **{{locationName}}** using Brainy's neural clustering API to produce data-driven guest segmentation, VIP identification, churn risk detection, and preference analysis inferred from session attributes.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"Who are our best customers?\"\n- \"What type of guests do we attract?\"\n- \"Which customers haven't been back in a while?\"\n- \"Who's at risk of churning?\"\n- \"What do our regulars tend to order?\"\n- \"Corporate client overview\"\n- Any question about guest behavior, segmentation, loyalty, or retention\n\n## Data to Pull\n\n### Neural clustering — behavioral segments\n\n```typescript\nconst segments = await brain.neural().clusters({\n  numClusters: 5,\n  entityType: 'Person',\n  where: [\n    { field: 'metadata.entityType', value: 'customer' },\n    { field: 'metadata.locationId', value: locationId }\n  ]\n});\n```\n\n### Outlier detection — VIPs and anomalies\n\n```typescript\nconst outliers = await brain.neural().outliers({\n  threshold: 2.5,\n  method: 'zscore',\n  entityType: 'Person',\n  where: [\n    { field: 'metadata.entityType', value: 'customer' },\n    { field: 'metadata.locationId', value: locationId }\n  ]\n});\n```\n\nAlso query raw customer records for the top 50 by `metadata.totalSpentInCents` to produce the VIP list. Pull session attributes across all bookings to count `flightName` and `favoriteSelection` values per customer cluster.\n\n## Known Segment Profiles\n\nThese are the expected natural clusters in a tasting room customer base. Validate and refine against actual neural cluster output — do not hard-code segments if the data shows different groupings.\n\n### Wine Explorers\n- **Behavior**: High booking frequency (4+ visits per year), always try different flights. Tend to book Sommelier's Pick disproportionately. Often the first to book a new Winemaker Dinner.\n- **Favorite selections**: Varied across visits — Old World Reds one month, New World Whites the next. The diversity of their selections is the signal.\n- **Retail behavior**: High retail purchase rate. They buy bottles to continue exploring at home.\n- **Loyalty tier**: Typically Gold or Platinum after 18+ months.\n- **What they need**: First access to new flight launches, Winemaker Dinner invites before public announcement, sommelier recognition when they arrive.\n\n### Celebration Guests\n- **Behavior**: Low frequency (1–2 visits per year), typically booking for birthdays, anniversaries, or special occasions. High party size (4–8+ guests). Private Tastings over-indexed.\n- **Favorite selections**: Tend toward approachable, crowd-pleasing selections — Napa Cabernet, Rosé & Sparkling. Selections correlate with group consensus rather than individual preference.\n- **Retail behavior**: Often purchase a retail bottle as a keepsake of the occasion.\n- **What they need**: Private room confirmation, acknowledgment of the occasion, photographs, smooth experience for a group that may include non-wine-drinkers.\n\n### Corporate Clients\n- **Behavior**: 2–4 visits per year, always booking Private Tastings for 10+ guests. Often billed to a company card. Consistent, predictable revenue.\n- **Favorite selections**: Tend toward prestigious Old World selections (Burgundy, Barolo, top Bordeaux) that signal quality to clients. Or they delegate entirely to the sommelier for a themed experience.\n- **Retail behavior**: Sometimes purchase retail bottles as client gifts.\n- **What they need**: Invoicing flexibility, reliability, easy rebooking, a seamless experience that reflects well on the host. Not price-sensitive but very quality-sensitive.\n\n### Beer People\n- **Behavior**: Exclusively or primarily book the Beer Tasting. May never have booked a wine experience. Loyal within the beer category.\n- **Favorite selections**: Consistently mark hop-forward styles (NEIPA, West Coast IPA) or Dark & Complex flights as favorites. Some are sour beer enthusiasts.\n- **Retail behavior**: Lower wine retail purchase rate; if the tasting room stocks retail craft beer, this is the segment to stock for.\n- **What they need**: Seasonal flight updates, visibility into new brewery partnerships, and — if you want to cross-sell — a bridge experience (\"If you love the Dark & Complex flight, you might enjoy an Old World Red pairing — the similarities are real\").\n\n### First-Timers\n- **Behavior**: Single visit, no repeat. Could become any other segment if properly nurtured. Typically self-identified as beginners or not sure where to start.\n- **Favorite selections**: Often default to the most familiar-sounding flight option (New World Red, Rosé & Sparkling). Rarely choose Old World or Sommelier's Pick on the first visit.\n- **Retail behavior**: Low retail purchase rate — they haven't yet built confidence in their preferences.\n- **What they need**: A great first experience (the most important visit is the first), a personalized follow-up from the sommelier referencing their specific session, and a gentle nudge to return with the next seasonal flight launch.\n\n---\n\n## Insights Report Structure\n\n---\n\n### Customer Insights — {{locationName}}\n**Generated**: [today's date]\n**Total Active Customers**: [count in period, last 12 months]\n\n---\n\n### 1. Segment Overview\n\n| Segment | Customers | % of Base | Avg Visits/Year | Avg Annual Spend | Dominant Experience |\n|---|---|---|---|---|---|\n| Wine Explorers | [count] | [%] | [avg] | $[avg spend ÷ 100] | Sommelier's Pick / all flights |\n| Celebration Guests | [count] | [%] | [avg] | $[avg] | Private Tasting |\n| Corporate Clients | [count] | [%] | [avg] | $[avg] | Private Tasting |\n| Beer People | [count] | [%] | [avg] | $[avg] | Beer Tasting |\n| First-Timers | [count] | [%] | 1 | $[avg] | Wine Flight / Beer Tasting |\n\nNote which segment the neural clusters most closely match, and flag any unexpected cluster (e.g., a \"Rosé loyalists\" cluster that's distinct from Celebration Guests, or a \"solo evening regular\" cluster distinct from Wine Explorers).\n\n---\n\n### 2. VIP Guest List\n\nTop 20 customers by total lifetime spend at {{locationName}}. Query outliers from neural analysis and top-N by `metadata.totalSpentInCents`.\n\n| Rank | Guest Name | Total Visits | Lifetime Spend | Loyalty Tier | Last Visit | Segment |\n|---|---|---|---|---|---|---|\n| 1 | [name] | [count] | $[spend] | Gold/Platinum | [date] | Wine Explorer |\n| … | … | … | … | … | … | … |\n\nNote any VIPs who haven't visited in 60+ days — these are the highest-priority outreach targets.\n\n---\n\n### 3. Churn Risk\n\nIdentify customers who:\n- Were active (2+ visits/year) for 12+ months AND\n- Have not visited in 90+ days\n\n```\n⚠️ [N] formerly active guests have not returned in 90+ days.\nTop churn risks by expected annual value:\n  1. [Name] — last visit [date], avg [N] visits/year, estimated annual value $[amount]\n  2. …\n```\n\nRecommended action: \"Send a personalized re-engagement email from {{sommelierName}} referencing their last visit and the new seasonal flight. The guest-letter skill can generate these individually.\"\n\n---\n\n### 4. Preference Analysis by Segment\n\nFor each segment, show the top 3 `flightName` choices and top 3 `favoriteSelection` entries:\n\n**Wine Explorers**\n- Top flights: [1. flight, 2. flight, 3. flight]\n- Most-loved wines: [1. wine, 2. wine, 3. wine]\n- Retail purchase rate: [%]\n\n**Celebration Guests**\n- Top flights: [...]\n- Most-loved wines: [...]\n- Retail purchase rate: [%]\n\n[Repeat for each segment]\n\n---\n\n### 5. Retail Purchase Rate by Segment\n\n| Segment | Guests | Retail Buyers | Retail Rate | Avg Retail Spend |\n|---|---|---|---|---|\n| Wine Explorers | [count] | [count] | [%] | $[avg] |\n| Celebration Guests | [count] | [count] | [%] | $[avg] |\n| Corporate Clients | [count] | [count] | [%] | $[avg] |\n| Beer People | [count] | [count] | [%] | $[avg] |\n| First-Timers | [count] | [count] | [%] | $[avg] |\n\nNote the segment with the highest retail conversion and the one with the lowest (and whether targeted outreach could move it).\n\n---\n\n### 6. Recommendation\n\nOne specific, data-backed recommendation for customer relationship action:\n\nExample: \"Wine Explorers are [%] of your customer base but [%] of total revenue. Of your [N] Wine Explorers, [N] have not been specifically invited to the Winemaker Dinner mailing list. Given their median annual spend of $[amount], a direct invitation from {{sommelierName}} — not a mass email — for the next Winemaker Dinner would likely convert [estimated N] additional attendees.\"\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). $55.00 = `5500`. 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 tasting room location | `address`, `hours`, `timezone`, `stripeAccountId`, `locationId` |\n| `Product` | `experience` | Experience type / ticket 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 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` | Beverage, glassware, or food 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---\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\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    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: 880, Person: 630, ... }\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('burgundy pinot noir', { 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('old world red burgundy pinot noir', {\n  type: 'Event',\n  limit: 20\n});\n```\n\n---\n\n## Rules Summary\n\n1. **Amounts in cents** — `5500` = $55.00. Always divide by 100 before displaying.\n2. **Always filter `metadata.locationId`** when the user's question is about a specific tasting room 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 `blog-draft` skill. */
+export const blogDraft = "---\nid: blog-draft\nname: Blog Draft\ndescription: Writes fully developed blog posts for The Pour House covering wine and beer education, varietal guides, pairing tutorials, seasonal selections, local craft beer scene coverage, date night guides, and corporate entertaining — with SEO optimization for local search and a knowledgeable but never condescending voice.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Blog Draft\n\nYou write polished, publication-ready blog posts for **{{businessName}}** in {{city}}. The blog voice is that of an expert who genuinely wants readers to enjoy wine and beer — knowledgeable but never condescending, educational without being academic, specific without being alienating to beginners.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"Write a blog post about [topic]\"\n- \"Draft a post for the wine blog\"\n- \"I need content about [varietal / pairing / season]\"\n- \"Write a beginner wine post\"\n- Any request for blog content, article drafts, or web editorial content\n\n## Blog Topic Library\n\nUse these as starting points. If the user specifies a topic, use it; if not, suggest one from this list based on context (current season, upcoming event, current featured flight).\n\n### Wine Education\n- \"Understanding Old World vs. New World Wine\" — The philosophy, climate, and style differences that shape every bottle\n- \"Why Burgundy Is the Most Confusing Wine Region in the World (And Why That's Worth It)\"\n- \"Five Things That Actually Determine Wine Quality\" — Demystifying price, terroir, vintage, and production\n- \"How to Taste Wine Like a Sommelier Without Taking Yourself Too Seriously\"\n- \"What Does 'Dry' Mean in Wine? (And Other Terms You've Been Nodding At)\"\n\n### Varietal Guides\n- \"Everything You Need to Know About Pinot Noir\" — From Burgundy to Oregon to why it's so unpredictable\n- \"The Sommelier's Defense of Chardonnay\" — Why the most mocked grape is also one of the most rewarding\n- \"Nebbiolo: The Grape Behind Barolo and Why It Demands Patience\"\n- \"Sauvignon Blanc vs. Chardonnay: Which White Wine Is Right for You?\"\n- \"Malbec 101: Argentina's Signature Grape and Why It Works\"\n- \"Riesling Is Not Sweet (And Other Misconceptions We're Correcting)\"\n\n### Pairing Guides\n- \"Wine and Cheese Pairing 101: The Five Rules That Actually Work\"\n- \"Why Champagne and Fried Food Is the Best Pairing You've Never Tried\"\n- \"The Complete Guide to Pairing Wine with Charcuterie\"\n- \"What Wine Goes with Spicy Food? (It's Not Cabernet)\"\n- \"Beer and Cheese: The Pairing Guide Wine Drinkers Never Read\"\n- \"Building the Perfect Cheese Board: A Sommelier's Framework\"\n\n### Seasonal and Current\n- \"Our Fall Wine List Is Here: What We're Pouring and Why\"\n- \"The Case for Rosé Beyond Summer: A Defense of Year-Round Pink Wine\"\n- \"Beaujolais Nouveau Day: A {{city}} Guide to the World's Most Fun Wine Tradition\"\n- \"What Harvest Season Means for the Wines You're Drinking Right Now\"\n- \"Why We're Obsessed with [Current Sommelier's Pick]: Tasting Notes and the Story Behind It\"\n\n### Local Craft Beer\n- \"The Best Craft Breweries in {{city}}: A Tasting Room Perspective\"\n- \"Why We Partner with [Local Brewery]: What Makes Their [Beer Style] Exceptional\"\n- \"West Coast IPA vs. New England IPA: Which Style Is Right for You?\"\n- \"Barrel-Aged Stouts: The Most Complex Beer Style You Haven't Tried Yet\"\n- \"A Beginner's Guide to Craft Beer Styles (From a Wine Bar That Loves Beer)\"\n\n### Experience and Lifestyle\n- \"The Perfect {{city}} Wine Date: A Guide to an Evening at {{businessName}}\"\n- \"How to Throw a Wine Tasting Party That Guests Will Actually Remember\"\n- \"Corporate Wine Tastings: Why Your Next Team Event Should Be at a Tasting Room\"\n- \"What to Expect at a Guided Wine and Cheese Pairing (First-Timer's Guide)\"\n- \"Five Reasons You Don't Need Wine Knowledge to Love a Wine Tasting\"\n\n---\n\n## SEO Guidance\n\nEvery post should incorporate these terms naturally — never as keyword stuffing:\n\n**Primary local terms**:\n- \"wine tasting {{city}}\"\n- \"wine bar {{city}}\"\n- \"guided wine tasting {{city}}\"\n- \"wine flight {{city}}\"\n\n**Secondary terms** (use where relevant):\n- \"beer tasting {{city}}\"\n- \"sommelier {{city}}\"\n- \"wine and cheese pairing {{city}}\"\n- \"private tasting room {{city}}\"\n- \"wine education {{city}}\"\n\nThe article's title and first paragraph should naturally include the primary local term where it fits. Don't force it into every sentence.\n\n---\n\n## Blog Post Structure\n\nEvery post should follow this structure:\n\n### 1. Title\nSpecific, specific, specific. \"Wine and Cheese Pairing\" is weak. \"The Five Rules for Wine and Cheese Pairing (And the One Pairing That Breaks Them All)\" is strong. Use a number if you're listing. Make a promise the post will fulfill.\n\n### 2. Opening Paragraph (The Hook)\nDo not start with \"Wine is one of humanity's oldest beverages.\" Start with something specific: a moment, a surprising fact, a question the reader is probably already asking, or a counterintuitive claim you'll support. The opening must make a reader want to keep going.\n\n### 3. Body (800–1,400 words)\nDevelop the topic with real depth. For educational posts: teach the thing, not just about the thing. Use concrete examples, specific producers, real pairings. For seasonal posts: be specific about what's in the glass right now. For experience posts: be specific about what happens when a guest walks through the door.\n\nUse headers (H2, H3) to break the content into scannable sections. Use short paragraphs. No paragraph longer than 5 sentences.\n\n### 4. {{businessName}} Connection (2–3 sentences)\nNear the end, naturally bridge the content to {{businessName}}'s offerings. Not a hard sales pitch — a relevant invitation. \"If you want to taste the contrast between Old World and New World Pinot Noir in the same evening, our Old World Red and New World Red flights were built exactly for this.\"\n\n### 5. Closing Call-to-Action\nOne sentence. Direct. \"Book a wine flight or guided pairing at {{businessName}} in {{city}} — no prior knowledge required.\" Or a softer version for educational posts: \"The best way to understand what we've described here is to taste it. Reserve your seat.\"\n\n---\n\n## Voice Rules\n\n- **Knowledgeable, never condescending** — The reader is a curious adult, not a student. Never talk down to them.\n- **Specific over general** — Name producers, regions, vintages. \"A wine from Burgundy\" is weaker than \"a 2020 Gevrey-Chambertin.\"\n- **Opinionated where appropriate** — The sommelier has a point of view. \"Cabernet Sauvignon is often overrated as a pairing for seafood\" is more interesting than \"some wines pair well with seafood.\"\n- **Genuinely educational** — Every post should leave the reader knowing something real. Not a tip list that says nothing.\n- **From the sommelier** — Voice the post as if {{sommelierName}} is writing it directly. The perspective is first-person plural (\"we pour,\" \"our selections\") or first-person singular where it adds authenticity.\n- **No fluff** — Every sentence earns its place. Delete anything that could be removed without losing information or character.\n\n---\n\n## Output Format\n\nReturn:\n1. **Title** (finalized, not a draft)\n2. **Meta description** (150–160 characters, includes primary local keyword)\n3. **Blog post body** (800–1,400 words, formatted with markdown headers)\n4. **Suggested tags**: [2–5 tags for blog category filtering]\n5. **Social caption**: 1–2 sentences for Instagram or Facebook, with 3–5 hashtags\n\nDo not include author byline, publication date, or image suggestions — those are handled by the CMS.\n";
+
+/** Raw SKILL.md content for the `tasting-notes` skill. */
+export const tastingNotes = "---\nid: tasting-notes\nname: Tasting Note Generator\ndescription: Generates elegant, complete tasting note cards for each wine or beer in a flight, formatted for printing or digital display at 3×5 landscape table cards. Covers appearance, aroma (primary/secondary/tertiary categories), palate structure, food pairings, serving temperature, glassware, and a one-line memorable hook per wine.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Tasting Note Generator\n\nYou generate complete, print-ready tasting note cards for each wine or beer in a flight at **{{businessName}}**. Tasting notes are placed at guest seats before each session and serve as guided reference cards during the tasting. They should be authoritative without being intimidating, and specific enough to give guests real vocabulary for what they're tasting.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"Generate tasting notes for tonight's flight\"\n- \"Tasting cards for the Old World Red flight\"\n- \"Write notes for the Guided Pairing wines\"\n- \"Tasting note cards before the Winemaker Dinner\"\n- \"Notes for the beer flight\"\n- Any request for tasting cards, printed notes, or pre-session wine/beer descriptions\n\n---\n\n## Input Format\n\nYou will receive a flight description with wine or beer details:\n\n```json\n{\n  \"flightName\": \"Old World Red Flight\",\n  \"experienceSlug\": \"wine-flight\",\n  \"locationName\": \"The Pour House Midtown\",\n  \"date\": \"2026-10-15\",\n  \"wines\": [\n    {\n      \"position\": 1,\n      \"producer\": \"Château Léoville-Barton\",\n      \"varietal\": \"Cabernet Sauvignon / Merlot / Cabernet Franc\",\n      \"region\": \"Saint-Julien, Bordeaux\",\n      \"vintage\": \"2018\",\n      \"abv\": \"13.5%\",\n      \"staffDescription\": \"Classic Left Bank Bordeaux, structured but approachable for a 2018. Cassis, cedar, some tobacco.\"\n    },\n    {\n      \"position\": 2,\n      \"producer\": \"Domaine Faiveley\",\n      \"varietal\": \"Pinot Noir\",\n      \"region\": \"Gevrey-Chambertin, Burgundy\",\n      \"vintage\": \"2019\",\n      \"abv\": \"13.0%\",\n      \"staffDescription\": \"Village-level Gevrey. Cherry, forest floor, silky tannin. Great intro to the Côte de Nuits.\"\n    },\n    {\n      \"position\": 3,\n      \"producer\": \"Château Rayas\",\n      \"varietal\": \"Grenache\",\n      \"region\": \"Châteauneuf-du-Pape, Southern Rhône\",\n      \"vintage\": \"2017\",\n      \"abv\": \"14.5%\",\n      \"staffDescription\": \"Legendary estate. Old-vine Grenache — wild herbs, garrigue, ripe cherry, terrific length.\"\n    },\n    {\n      \"position\": 4,\n      \"producer\": \"Mastroberardino\",\n      \"varietal\": \"Aglianico\",\n      \"region\": \"Taurasi, Campania, Italy\",\n      \"vintage\": \"2016\",\n      \"abv\": \"14.0%\",\n      \"staffDescription\": \"The Barolo of the South. Tar, dark cherry, iron, massive structure. Needs food.\"\n    }\n  ]\n}\n```\n\nFor beer flights, the input will use `style`, `brewery`, `abv`, and `ibu` instead of `varietal`, `vintage`.\n\n---\n\n## Tasting Note Format (Per Wine)\n\nGenerate each note in this exact structure. This is the layout for a 3\" × 5\" landscape table card:\n\n---\n\n**[Position number]. [Producer] — [Varietal] — [Region] — [Vintage]**\nABV: [abv]%\n\n**Appearance**\n[Color and clarity description. Use precise color language: pale straw, medium lemon, deep ruby, opaque purple, translucent brick-red, etc. Note clarity: clear, slightly hazy, or note if sediment is expected in an aged wine.]\n\n**On the Nose**\n[3–5 aromatic descriptors drawn from primary, secondary, and tertiary categories as appropriate. Write as a natural sentence, not a bullet list.]\n\nExample: \"On the nose: cassis and dark cherry (primary fruit), giving way to cedar and cigar box (oak aging), with a faint pencil shaving lift that signals the wine's structure.\"\n\n**On the Palate**\n[Body description + tannin or carbonation character + acidity + dominant flavor + finish length and character. Write as 2–3 connected sentences.]\n\nExample: \"Full-bodied with firm, well-integrated tannins and fresh acid that keeps the wine from feeling heavy. Blackcurrant and plum dominate the mid-palate with a hint of graphite on the finish. Long — flavors linger for 20+ seconds.\"\n\n**Pairs With**\n[2–3 specific food pairings. Be concrete. Not \"red meat\" — \"grilled ribeye, lamb shoulder braised with rosemary, or aged manchego.\"]\n\n**Serve At**\n[Temperature in °F and °C] in a [glass type] glass. [Decant if relevant: \"Decant 30 minutes before serving to soften young tannins.\" or \"Ready to pour from the bottle.\"]\n\n**The Hook**\n[One memorable sentence that captures this wine's personality without being purple prose. The hook is a gift to guests — something to repeat when describing the wine to someone else.]\n\nExamples of good hooks:\n- \"The wine that makes Bordeaux skeptics reconsider.\" (for an approachable, elegant Bordeaux)\n- \"If Burgundy is the quiet one at dinner, Gevrey-Chambertin is the one who has everything to say and takes their time saying it.\"\n- \"Châteauneuf at its most wild — a wine that smells like a Provençal hillside in August.\"\n- \"Taurasi earns its nickname: the Barolo of the South, which means patience is the price of admission.\"\n\n**Avoid**: \"liquid sunshine,\" \"a symphony in a glass,\" \"a perfect marriage of fruit and earth,\" \"notes of oak\" (oak is not a primary note — name the tertiary descriptor specifically: vanilla, cedar, toast, coconut), \"complex\" without explaining the complexity.\n\n---\n\n## Beer Tasting Note Format (Per Beer)\n\nFor beer flights, use this adapted structure:\n\n---\n\n**[Position]. [Brewery] — [Beer Name] — [Style]**\nABV: [abv]% | IBU: [ibu]\n\n**Appearance**\n[Color (pale straw, golden, amber, brown, black, hazy), clarity (clear, hazy, opaque), head (white, off-white, tan; persistent, moderate, minimal).]\n\n**On the Nose**\n[Aroma descriptors using cicerone vocabulary: grain, hops (herbal, citrus, tropical, pine, resinous), esters (fruit from yeast), phenols (spice, clove from Belgian yeasts). 3–4 descriptors.]\n\n**On the Palate**\n[Bitterness (low/medium/high, relative to style), carbonation (gentle/moderate/high), body (light/medium/full), dominant flavors, finish (dry/sweet, length).]\n\n**Pairs With**\n[2–3 specific food pairings appropriate to the style.]\n\n**Serve At**\n[Temperature] in a [glass type] glass.\n\n**The Hook**\n[One memorable line that captures the beer's character.]\n\n---\n\n## Flight Card Format\n\nWhen producing notes for a complete flight, output all notes in sequence with consistent formatting. The complete set of notes for a flight should be presented as:\n\n---\n\n**[flightName] — {{locationName}}**\n*[Date] | [experienceName]*\n\n---\n[Note 1 through Note N in sequence]\n\n---\n\nAt the bottom of the flight card set, add:\n\n**About This Flight**\n[2–3 sentences describing what makes this particular sequence meaningful — why these wines or beers were chosen together, what story they tell in order, what contrast or theme runs through the flight. This is what the sommelier will say when introducing the flight to the table.]\n\n---\n\n## Tone Rules\n\n- **Authoritative but accessible** — Write for a curious adult who is tasting attentively, not for a Masters of Wine exam\n- **Vivid, concrete descriptors** — \"Ripe black cherry and cassis\" is specific; \"fruity\" is not\n- **No filler adjectives**: \"elegant,\" \"sophisticated,\" \"extraordinary\" add nothing. Describe what's actually there.\n- **Consistent vocabulary** — Use the same structural terms (body, tannin, acidity, finish) across all notes so guests can compare wines using the same framework\n- **The hook must be memorable** — If a guest quotes the hook to a friend later, it worked. If it sounds like every other wine description they've ever read, it failed.\n";
+
+/** Raw SKILL.md content for the `experience-copy` skill. */
+export const experienceCopy = "---\nid: experience-copy\nname: Experience Copy\ndescription: Writes marketing copy for each tasting room experience type — Wine Flight, Beer Tasting, Guided Pairing, Private Tasting, and Winemaker Dinner — producing a full 80–120 word description, a one-liner, SEO meta description, and social caption for each.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Experience Copy\n\nYou write compelling, accurate marketing copy for each experience offered at **{{businessName}}** in {{city}}. Copy must sell the experience without overpromising, convey what actually happens, and make both first-timers and experienced tasters feel equally welcomed.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"Write copy for the wine flight\"\n- \"I need a description for the guided pairing\"\n- \"Update the private tasting description\"\n- \"Give me a one-liner for the beer tasting\"\n- \"Write SEO copy for our experiences page\"\n- Any request for experience descriptions, landing page copy, or booking page text\n\n## Selling Angles\n\nEvery piece of experience copy should incorporate at least two of these angles. Choose based on which are most natural for the specific experience:\n\n1. **Expert guidance**: \"Guided by our sommelier\" / \"our cicerone walks you through each pour\" — the knowledge is included; you don't need to bring your own\n2. **No prior knowledge needed**: \"No wine background required\" / \"perfect for first-timers and enthusiasts alike\" — remove the intimidation barrier explicitly\n3. **Walk away with something**: \"Leave knowing a new favorite\" / \"you'll understand why you love what you love\" — a specific, lasting outcome\n4. **Intimate atmosphere**: \"A small, unhurried room\" / \"designed for conversation\" — quality of experience, not a bar\n5. **Perfect for [occasion]**: \"Ideal for dates, celebrations, and curious minds\" — help the guest see where they fit\n6. **The sommelier relationship**: Positioned as a host and teacher, not a gatekeeper\n\n---\n\n## Experience Copy Templates\n\nFor each experience, produce all four content types.\n\n---\n\n### Wine Flight\n\n**Full description (80–120 words)**:\nFour wines, guided by your sommelier. Choose your flight — Old World Reds, New World Reds, delicate whites, Rosé & Sparkling, or let the sommelier choose for you. Each pour arrives with printed tasting notes and food pairing suggestions, and your sommelier is here to answer anything your palate is trying to tell you. An hour that teaches you more about what you love than a year of drinking alone.\n\nNo prior wine knowledge required. This is where wine education actually starts — not in a textbook, but in a glass.\n\n**One-liner**: Four guided pours, one new favorite. No wine knowledge required.\n\n**SEO meta (150–160 characters)**: Reserve a guided wine flight at {{businessName}} in {{city}}. Four wines, expert tasting notes, and a sommelier to guide every pour. From $30/person.\n\n**Social caption**: Four wines. Your sommelier. An hour that changes how you drink. Reserve a wine flight at {{businessName}} — link in bio. #winetasting #wineflight #{{city}}wine #sommelier\n\n---\n\n### Beer Tasting\n\n**Full description (80–120 words)**:\nFive craft beers, selected to take you across the full range of what beer can be — from crisp, delicate lagers to complex, roasted barrel-aged stouts. Our cicerone introduces each pour: the brewery, the style, what to look for in the aroma and flavor, and why this beer is worth paying attention to.\n\nYou don't need to know the difference between a Hefeweizen and a Saison before you arrive. You will by the time you leave.\n\n**One-liner**: Five craft beers, one cicerone, and the vocabulary to understand every one.\n\n**SEO meta (150–160 characters)**: Guided craft beer tasting in {{city}} at {{businessName}}. Five beers, expert guidance from our cicerone. From $25/person. No beer knowledge required.\n\n**Social caption**: Five beers. One flight. A cicerone who makes every style make sense. Book a beer tasting at {{businessName}}. #craftbeer #beertasting #craftbeerlovers #{{city}}\n\n---\n\n### Guided Pairing\n\n**Full description (80–120 words)**:\nFour wines. An artisan cheese and charcuterie board. Ninety minutes with our sommelier explaining why the acidity in a Sancerre cuts through goat cheese the way nothing else does, why aged Parmesan transforms a tannic Barolo, and why blue cheese belongs with something sweet.\n\nPairing isn't about rules — it's about understanding how flavors interact. By the end of this session, you'll have a framework that works at every dinner table for the rest of your life.\n\n**One-liner**: Four wines, a composed cheese board, and the pairing principles that change how you eat.\n\n**SEO meta (150–160 characters)**: Wine and cheese pairing class in {{city}} at {{businessName}}. Four wines, artisan cheese board, sommelier-led. $55/person. Perfect for dates and groups to 12.\n\n**Social caption**: The Guided Pairing is the one where guests say \"I finally understand why that works.\" Four wines, a cheese board, and a sommelier who makes the principles click. Reserve at {{businessName}}. #winepairing #cheeseandwine #sommelier #{{city}}wine\n\n---\n\n### Private Tasting\n\n**Full description (80–120 words)**:\nThe tasting room, reserved exclusively for your group. Tell us your preferences — or give us a theme — and we design the flight around you. Want to explore a single region in depth? Compare a varietal across three producers? Celebrate a milestone with wines chosen for the occasion? We build it.\n\nIdeal for birthdays, anniversaries, corporate entertaining, and groups of 6 to 20 who want something genuinely memorable rather than just another night out.\n\n**One-liner**: The room is yours. The flight is built for you. Six to twenty guests.\n\n**SEO meta (150–160 characters)**: Private wine tasting in {{city}} at {{businessName}}. Custom flight, exclusive room, sommelier host. From $65/person. Book for 6–20 guests.\n\n**Social caption**: The private tasting is how you make a birthday, anniversary, or corporate event impossible to forget. Custom flight, the room to yourselves, your sommelier for the evening. {{businessName}} in {{city}} — link in bio. #privatetasting #winetasting #{{city}}wine #corporateevents\n\n---\n\n### Winemaker Dinner\n\n**Full description (80–120 words)**:\nFive courses. Five wines. One long, unhurried evening. Our Winemaker Dinner is a partnership between {{businessName}} and a rotating cast of {{city}}'s finest chefs — they bring the courses, we bring the wines, and your sommelier guides every pairing decision at the table.\n\nThis is the evening where wine stops being background and becomes the point. Capacity is 24 seats — they sell out. Join our mailing list to hear about the next one before it goes public.\n\n**One-liner**: Five courses, five wines, one evening that earns a story worth telling.\n\n**SEO meta (150–160 characters)**: Winemaker Dinner in {{city}} at {{businessName}}. Five-course dinner with paired wines, led by our sommelier. $95/person. Capacity: 24 seats.\n\n**Social caption**: Five courses. Five wines. A dinner where the sommelier is as important as the chef. The Winemaker Dinner at {{businessName}} — 24 seats, sold out most months. Join the list. #winemakerdinner #privatedining #{{city}}dining #sommelier #finedining\n\n---\n\n## General Copy Rules\n\n- **Second person is optional** — \"You'll discover\" is fine; so is describing the experience in the third: \"Guests work through four pours...\"\n- **No hollow adjectives**: Never use \"exquisite,\" \"unforgettable,\" \"world-class,\" \"amazing\" — these mean nothing. Use specific sensory details instead.\n- **Active, present tense**: \"Your sommelier guides each pour\" not \"guests will be guided by...\"\n- **Price is part of the value proposition**: Include price in the description where specified — it manages expectations and filters appropriately.\n- **Length discipline**: Full descriptions must be 80–120 words. One-liners must be one sentence. Do not exceed these limits — brevity is a feature.\n";
+
+/** Raw SKILL.md content for the `demand-forecast` skill. */
+export const demandForecast = "---\nid: demand-forecast\nname: Demand Forecast\ndescription: Analyzes tasting room booking patterns to produce a demand heatmap by day and hour, identify peak windows, generate staffing recommendations based on sommelier capacity ratios, and forecast seasonal demand shifts including holiday spikes, harvest season, and rosé season.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Demand Forecast\n\nYou analyze historical booking patterns at **{{locationName}}** to forecast demand, identify peak and off-peak windows, and produce staffing and scheduling recommendations grounded in the data.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"When are we busiest?\"\n- \"Do I need more staff on Saturday?\"\n- \"Forecast for next month\"\n- \"Should we add another Friday evening slot?\"\n- \"What does our demand look like going into the holidays?\"\n- Any question about capacity planning, staffing levels, or scheduling optimization\n\n## Data to Pull\n\n### Bookings by experience, day of week, and hour\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.experienceSlug' },\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    fillRate:     { op: 'AVG', field: 'metadata.fillRate' }\n  }\n});\n```\n\nAlso pull time-slot data to identify which slots are offered vs. which actually book, and the fill rate for each.\n\n## Tasting Room Demand Patterns\n\nUse these known patterns as context when interpreting the data and producing recommendations:\n\n### Peak Windows\n- **Friday evenings (6–9 PM)**: Highest demand. Date nights, group outings, end-of-week celebrations. Private tastings typically concentrate here.\n- **Saturday evenings (6–9 PM)**: Second highest. Similar profile to Friday.\n- **Saturday afternoons (2–5 PM)**: Strong. Ideal for Guided Pairings with groups who prefer earlier starts.\n- **Sunday afternoons (1–4 PM)**: Reliable \"wine brunch\" window. Lighter, social atmosphere. Wine Flights and Beer Tastings dominate; good for solo guests and small couples.\n\n### Off-Peak Windows\n- **Weekday evenings (Monday–Thursday)**: Lower volume but loyal repeat guests. Winemaker Dinners often scheduled on Wednesday or Thursday to avoid weekend competition.\n- **Early afternoons (12–2 PM)**: Very low unless a private event has booked.\n\n### Staffing Capacity Rule\n- **1 sommelier can effectively host up to 16 guests in a guided session** without compromising the quality of guidance.\n- For sessions above 16 guests, a second host (Tasting Host role) should be scheduled to handle pour service and floor support while the sommelier maintains narrative continuity.\n- For Winemaker Dinners (12–24 guests), minimum staffing: 1 sommelier + 1 tasting host + restaurant staff (restaurant partner handles food service).\n\n### Seasonal Demand Shifts\n\n| Season | Pattern | Opportunity |\n|---|---|---|\n| January | Post-holiday slump. Gift card redemptions elevate otherwise soft demand. | Promote gift card redemption via email. Run educational \"wine fundamentals\" flights to attract new-to-wine guests. |\n| February | Valentine's Day spike (entire week). Date-night flights and private tastings at maximum demand. | Book Valentine's week private tastings 3–4 weeks in advance. Add extra Friday/Saturday slots. |\n| March–April | Rosé season launch. Demand for light whites and sparkling increases. | Launch Rosé & Sparkling flight prominently. Social content around rosé season drives awareness. |\n| May–June | Corporate entertaining season begins. Private tastings for Q2 team events. | Target LinkedIn/email campaigns at corporate event planners. |\n| July–August | Heat suppresses wine interest; Beer Tasting sees relative uptick. Summer seasonal flight grows. | Feature beer tasting in summer marketing. Light and refreshing wines (Albariño, Grüner Veltliner) as summer Sommelier's Pick. |\n| September | Back-to-school softness in first 2 weeks, then harvest season excitement builds. | Announce fall wine selections. Harvest-theme flights (Beaujolais Nouveau in November, new Barolo releases). |\n| October | Fall flight launch. Demand for full reds increases sharply. | Old World Red and New World Red flights near capacity. Winemaker Dinner ideal for October/November. |\n| November | Holiday buying season begins. Gift card sales spike. Winemaker Dinner at peak demand. | Feature Winemaker Dinner prominently in November email. Gift card promotions for Black Friday week. |\n| December | Holiday party private tastings. Champagne and sparkling demand peaks. Corporate year-end entertaining. | Book December private tastings by early October. Launch Rosé & Sparkling flight and Sommelier's Pick featuring Champagne. |\n\n---\n\n## Forecast Output Structure\n\n---\n\n### Demand Forecast — {{locationName}}\n**Forecast Period**: [next 30 days / specified period]\n**Based On**: [trailing 90 days / specified lookback window]\n**Generated**: [today's date]\n\n---\n\n### 1. Demand Heatmap\n\nProduce a day-of-week × time-of-day grid showing average booking volume and fill rate for each cell:\n\n| Time | Mon | Tue | Wed | Thu | Fri | Sat | Sun |\n|---|---|---|---|---|---|---|---|\n| 1–3 PM | — | — | — | — | [avg guests] | [avg guests] | [avg guests] |\n| 4–6 PM | [avg] | [avg] | [avg] | [avg] | [avg] | [avg] | [avg] |\n| 6–8 PM | [avg] | [avg] | [avg] | [avg] | **[peak]** | **[peak]** | [avg] |\n| 8–10 PM | — | — | [avg] | [avg] | [avg] | [avg] | — |\n\nUse bold to indicate peak cells (above 75% capacity fill rate). Use `—` for time windows with no scheduled slots.\n\n---\n\n### 2. Peak Windows\n\nRank your top 5 highest-demand time windows by avg fill rate:\n\n| Rank | Day + Time | Avg Fill Rate | Avg Guests | Dominant Experience |\n|---|---|---|---|---|\n| 1 | Saturday 6 PM | [%] | [avg] | [exp slug] |\n| … | … | … | … | … |\n\nFor each peak window, note whether current capacity is meeting demand or whether unfulfilled demand exists (requests that couldn't be accommodated due to capacity limits — infer from cancelled bookings or early sellouts).\n\n---\n\n### 3. Staffing Recommendations\n\nBased on confirmed bookings for the forecast period and the 16-guest sommelier ratio rule:\n\n| Date | Sessions | Peak Guest Load | Sommeliers Needed | Tasting Hosts Needed |\n|---|---|---|---|---|\n| [date] | [count] | [peak single-session guest count] | [1 or 2] | [0 or 1] |\n\nFlag any days where current confirmed bookings already require a second sommelier. Flag any Winemaker Dinners for mandatory dual staffing.\n\n---\n\n### 4. Slot Opportunities\n\nBased on fill rate analysis, identify underutilized time slots and suggest additions or removals:\n\n- **Add a slot**: \"Sunday afternoon (2 PM) fill rate is [%] — above the 70% trigger for adding capacity. Adding a second Sunday afternoon Wine Flight slot would accommodate an estimated [N] additional guests per month.\"\n- **Remove a slot**: \"Wednesday evening (7 PM) fill rate is [%] over the past 90 days. Consider removing this slot and redirecting marketing spend to Saturday afternoon where demand remains unfulfilled.\"\n- **Upsell opportunity**: \"Friday evening Beer Tasting has a [%] fill rate — consider converting one Beer Tasting slot to a Guided Pairing, which commands $30 more per guest.\"\n\n---\n\n### 5. Upcoming Seasonal Events to Prepare For\n\nList any known demand drivers in the next 60 days and recommended actions:\n\n- [Event/season] on [date range]: \"[Recommended inventory, staffing, or marketing action]\"\n\nExample: \"Valentine's Day (Feb 14 ± 3 days): Private tastings should be bookable by now. If not yet available, add private tasting slots immediately — fill rate for this window historically [peak %]. Pre-order extra Champagne and sparkling for the Rosé & Sparkling flight and sommelier pours.\"\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 tasting room, covering revenue by experience type with standard deviation analysis, expense breakdown by category, beverage cost percentage, food attachment rate, bottle retail uptake, month-over-month trends, and one data-backed recommendation.\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 include revenue by experience type, expense breakdown by category, margin analysis, beverage cost percentages, food attachment rates, bottle retail uptake, and at least one 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 best-margin experience?\"\n- \"Beverage cost percentage\"\n- \"How much retail bottle revenue are we generating?\"\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 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    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 full requested period (date-filtered) to produce top-line summary figures.\n\n## Industry Benchmarks for Tasting Rooms\n\nUse these when computing and flagging margin performance:\n\n- **Beverage cost target (wine)**: 28–32% of wine revenue. Below 28% indicates thin selection or over-pricing; above 35% is a margin problem.\n- **Beverage cost target (beer)**: 20–25% of beer revenue. Craft beer cost is typically lower than wine.\n- **Food attachment rate**: % of tasting bookings that include a cheese/charcuterie board. Target: 60%+ for Guided Pairings (board is included); 25%+ voluntary add-on rate for Wine Flights.\n- **Bottle retail uptake**: % of tasting guests who purchase a retail bottle. Target: 15–25%. A well-executed guided tasting should reliably convert curiosity into a take-home bottle.\n- **Private tasting fill rate**: % of available private tasting capacity (20 guests max) actually used. Below 60% indicates pricing, awareness, or day-of-week mismatch.\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 Sessions | [sessionCount] |\n| Avg Revenue per Session | $[avgRevenue ÷ 100] |\n| Total Expenses | $[totalExpense ÷ 100] |\n| Gross Profit | $[(totalRevenue − totalExpense) ÷ 100] |\n| Gross Margin | [grossProfit / totalRevenue × 100]% |\n\nIf refunds exist in the period, add: `Refunds Issued | $[refunds ÷ 100]` and note that gross figures are pre-refund.\n\n---\n\n### 2. Revenue by Experience Type\n\n| Experience | Sessions | Revenue | Avg / Session | Std Dev | CV | % of Total |\n|---|---|---|---|---|---|---|\n| [name] | [count] | $[revenue] | $[avg] | $[stddev] | [stddev/avg × 100]% | [%] |\n\nSort by revenue descending.\n\n**Coefficient of Variation (CV) interpretation for tasting rooms**: Tasting room bottle-service economics are remarkably consistent — Wine Flights and Guided Pairings should show CV < 20% because price is fixed per person. If CV exceeds 30% on any experience, flag it:\n\n> \"⚠️ [Experience] shows high revenue variability (CV: [%]). Fixed-price tasting experiences typically show CV < 20%. Investigate for: partial-group no-shows (booking for 8, showing up as 4), inconsistent add-on attachment, or promotional discounting applied unevenly.\"\n\n---\n\n### 3. Month-over-Month Revenue Trend\n\n| Month | Revenue | Sessions | Avg / Session | 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 growth months with `▲` and declining months with `▼`. Calculate MoM change as `(current − prior) / prior × 100`.\n\nSeasonal context for tasting rooms:\n- **Peak months**: November–December (holiday gift card redemptions, Winemaker Dinners), February (Valentine's tastings), October (harvest season, fall flight launches)\n- **Shoulder months**: March–April (rosé season begins), September (back-to-school slowdown then harvest recovery)\n- **Soft months**: January (post-holiday), late summer (heat suppresses wine interest, beer tasting picks up)\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 tasting room: `wines` (bottle purchases), `beers` (keg/bottle stock), `cheese-charcuterie` (food COGS), `glassware` (replacement/breakage), `payroll` (sommelier and host hours), `rent`, `marketing`, `utilities`, `retail-cogs` (bottles purchased for retail resale), `supplies` (tasting note printing, candles, décor).\n\nSort by total expense descending.\n\n---\n\n### 5. Beverage Cost Analysis\n\n| Beverage | Revenue | Beverage Cost | Cost % | Target | Status |\n|---|---|---|---|---|---|\n| Wine | $[wine revenue] | $[wine cost] | [%] | 28–32% | [Within / Above / Below target] |\n| Beer | $[beer revenue] | $[beer cost] | [%] | 20–25% | [Within / Above / Below target] |\n\n**If wine cost % > 35%**: \"Wine beverage cost is above target. Review current pour cost per flight against ticket price. With 75ml pours × 4 per flight, one 750ml bottle yields ~10 pours. At $30/ticket, revenue per bottle used = ~$75. If cost per bottle exceeds $24 (32%), margins compress quickly. Consider whether the premium selections in the Sommelier's Pick flights are priced appropriately.\"\n\n---\n\n### 6. Food Attachment Rate\n\n```\nGuided Pairings with board (included):    [count] / [total guided pairings] = [%]\nWine Flights with voluntary board add-on: [count] / [total wine flights] = [% attachment rate]\nTarget:                                   25%+ for voluntary add-ons\n```\n\nIf below target: \"Cheese and charcuterie board attachment on Wine Flights is [%] — below the 25% target. Boards increase per-guest spend by $12–15 and improve the tasting experience. Train staff to suggest the board at check-in: 'Would you like to add a cheese and charcuterie board? It pairs beautifully with the [flightName] flight.'\"\n\n---\n\n### 7. Bottle Retail Uptake\n\n```\nTotal guests in period:      [count]\nRetail bottle purchases:     [count]\nRetail uptake rate:          [%] (target: 15–25%)\nRetail bottle revenue:       $[amount]\nAvg retail bottle price:     $[avg]\nTop retail seller:           [producer/varietal] — [count] units sold\n```\n\nIf uptake below 15%: \"Bottle retail conversion is [%] — below the 15% baseline. Guests who just discovered a wine they love in a guided tasting are the warmest retail prospect you'll ever have. Ensure sommeliers close every tasting with: 'We have bottles of the [favorite wine] available to take home — would you like to see the price?'\"\n\n---\n\n### 8. Statistical Flags\n\nList any anomalies the data reveals. Always check:\n- **Revenue outliers**: Months or experience types where revenue is > 2 standard deviations from the mean\n- **Expense spikes**: Expense categories with unusually high single-month totals\n- **High CV experiences**: Any experience with coefficient of variation > 30% on per-session revenue\n- **Declining trend**: Three or more consecutive months of MoM revenue decline\n- **Beverage cost creep**: Wine cost % trending upward over 3 months even without a price change\n\nFormat each flag as: `⚠️ [Flag title]: [One sentence description 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\nWell-formed examples for a tasting room:\n- \"Guided Pairing revenue averages $312/session with a 91% fill rate — it's your most reliably full and highest-margin experience. Yet it represents only [%] of total sessions booked. Adding a second Saturday Guided Pairing slot would likely fill at the same rate and add approximately $[monthly addition] in recurring monthly revenue.\"\n- \"Beer Tasting wine-cost percentage is [%] — well within target — but its per-session revenue ($[avg]) is 16% below the Wine Flight despite the same 60-minute format and time slot. Consider increasing Beer Tasting pricing by $3–5/person. At current volume, a $4 increase adds $[annual impact] annually with minimal booking sensitivity given the price differential from craft beer bars.\"\n\nDo not offer vague suggestions. Every recommendation must be grounded in the numbers.\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 Report\ndescription: Monitors tasting room beverage and board inventory with vintage-aware wine tracking by SKU, three-tier alert levels for wines and cheeses, glassware counts against scheduled guests, and a prioritized reorder list.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Inventory Health Report\n\nYou monitor and report on beverage, food, and glassware inventory at **{{locationName}}**. Wine inventory is tracked at the SKU level (producer + varietal + vintage) because vintages are not interchangeable in a tasting context — running out of the 2019 Barolo and substituting a 2021 is a meaningful program change, not a like-for-like swap.\n\n## When to Trigger\n\nInvoke this skill when staff or owners ask:\n- \"How's our inventory looking?\"\n- \"Do we have enough wine for this week?\"\n- \"What do we need to reorder?\"\n- \"Inventory health check\"\n- \"Are we going to run out of anything before the Winemaker Dinner?\"\n- Any question about stock levels, reorder needs, or supply status\n\n## Data to Pull\n\nQuery all `Thing` entities with `metadata.entityType = 'inventory-item'` and `metadata.locationId = [location]`.\n\nKey metadata fields for wine SKUs:\n- `name`: Producer + varietal + vintage (e.g., \"Domaine Faiveley Gevrey-Chambertin 2019\")\n- `category`: One of `wines`, `beers`, `spirits`, `glassware`, `cheese`, `accompaniments`, `retail`\n- `quantity`: Current bottles on hand (for wine); units for other items\n- `reorderThreshold`: Minimum before reorder is triggered\n- `costInCents`: Per-bottle cost\n- `retailPriceInCents`: Retail selling price (if sold as retail)\n- `flightPourPriceInCents`: Revenue per pour in a flight (ticket price ÷ pours per flight)\n\nAlso query upcoming bookings (`Event`, `metadata.entityType = 'booking'`, next 14 days) and their session attributes (`flightName`, `varietals`) to cross-reference which wines are committed to upcoming sessions.\n\n## Alert Tiers\n\n### Wine (by SKU)\n\n| Tier | Condition | Symbol |\n|---|---|---|\n| CRITICAL | < 1 case (12 bottles) AND wine is featured in a current or upcoming flight | 🔴 CRITICAL |\n| LOW | 1–2 cases (12–24 bottles) for a featured flight wine | 🟡 LOW |\n| OK | ≥ 2 cases, or not currently featured in a flight | 🟢 OK |\n| AGING ALERT | No movement in 60+ days AND vintage is 3+ years old | ⚠️ AGING |\n\n**Critical rule**: Never let a featured flight wine run out mid-season. Flag any wine that at current consumption velocity will reach zero before the end of the current seasonal flight window. \"Flight window\" defaults to the next 6 weeks unless a seasonal rotation date is stored.\n\n### Cheese and Fresh Inventory\n\n| Tier | Condition | Symbol |\n|---|---|---|\n| CRITICAL | < 3 days supply at current booking pace | 🔴 CRITICAL |\n| LOW | 3–5 days supply | 🟡 LOW |\n| OK | > 5 days supply | 🟢 OK |\n\nCheese supply estimate: 1 cheese board serves 2–3 guests for Guided Pairings; 4 guests for Private Tastings (larger portions). Calculate days of supply based on upcoming bookings with boards.\n\n### Glassware\n\nCount polished, undamaged glasses by type (Bordeaux/red, white wine, flute/sparkling, tulip beer, pint).\n\nCompare against:\n- Scheduled guests in the next 7 days\n- Type requirements per experience (Wine Flight: Bordeaux or white glass; Beer Tasting: tulip; Guided Pairing: white + red; Winemaker Dinner: full set)\n\nFlag if any glass type count is within 20% of scheduled need — one breakage incident could leave the session short.\n\n---\n\n## Report Structure\n\n---\n\n### Inventory Health Report — {{locationName}}\n**Generated**: [today's date]\n**Next 14 Days of Bookings**: [count sessions] sessions, [count guests] guests\n\n---\n\n### 1. Wine Inventory — by SKU\n\n| Status | Producer / Varietal / Vintage | Bottles on Hand | Cases | Monthly Use Rate | Months Remaining | In Active Flight? | Reorder? |\n|---|---|---|---|---|---|---|---|\n| 🔴 CRITICAL | [name] | [qty] | [qty÷12, 1 dec] | [rate] | [months] | Yes | URGENT |\n| 🟡 LOW | [name] | [qty] | [qty÷12] | [rate] | [months] | Yes | Soon |\n| 🟢 OK | [name] | [qty] | [qty÷12] | [rate] | [months] | Yes / No | No |\n| ⚠️ AGING | [name] | [qty] | [qty÷12] | 0 | N/A | No | Review |\n\nSort: CRITICAL first, then LOW, then OK, then AGING.\n\nFor each CRITICAL or LOW wine in an active flight, add a note:\n> \"🔴 [Wine name] — [bottles] bottles remaining. At [use rate] bottles/week, supply exhausts in [weeks]. Next flight refresh date: [date]. REORDER IMMEDIATELY or identify substitute.\"\n\n---\n\n### 2. Beer Inventory\n\n| Status | Beer / Style / Brewery | Units/Kegs | Est. Days Remaining | Best-By Date | In Active Flight? |\n|---|---|---|---|---|---|\n| 🔴 | [beer] | [qty] | [days] | [date] | Yes |\n| 🟡 | [beer] | [qty] | [days] | [date] | Yes |\n| 🟢 | [beer] | [qty] | [days] | [date] | Yes/No |\n\nDays remaining calculation: (units on hand × ml per unit) ÷ (avg daily ml poured per session × sessions per day).\n\nFor kegged beers, flag if best-by date is within 14 days and stock has not been consumed — this is a forced reorder or discard situation.\n\n---\n\n### 3. Cheese & Fresh Inventory\n\n| Item | Current Stock | Daily Usage (estimate) | Days Remaining | Status |\n|---|---|---|---|---|\n| Aged Cheddar | [weight/units] | [est.] | [days] | 🟢/🟡/🔴 |\n| Brie / Camembert | [qty] | [est.] | [days] | 🟢/🟡/🔴 |\n| Blue (Roquefort / Gorgonzola) | [qty] | [est.] | [days] | 🟢/🟡/🔴 |\n| Manchego / Semi-hard | [qty] | [est.] | [days] | 🟢/🟡/🔴 |\n| Charcuterie (cured meats) | [weight/units] | [est.] | [days] | 🟢/🟡/🔴 |\n| Crackers / Accompaniments | [units] | [est.] | [days] | 🟢/🟡/🔴 |\n| Honey, Nuts, Jam | [units] | [est.] | [days] | 🟢/🟡/🔴 |\n\n---\n\n### 4. Glassware Count\n\n| Glass Type | On Hand | Needed (Next 7 Days) | Buffer | Status |\n|---|---|---|---|---|\n| Bordeaux / Red wine | [count] | [count] | [count] | 🟢/🟡/🔴 |\n| White wine | [count] | [count] | [count] | 🟢/🟡/🔴 |\n| Flute / Sparkling tulip | [count] | [count] | [count] | 🟢/🟡/🔴 |\n| Tulip (beer) | [count] | [count] | [count] | 🟢/🟡/🔴 |\n| Water glass | [count] | [count] | [count] | 🟢/🟡/🔴 |\n\nFlag any glass type where buffer (on hand minus needed) is negative or below 20%.\n\n---\n\n### 5. Prioritized Reorder List\n\n| Priority | Item | Category | Quantity to Order | Urgency |\n|---|---|---|---|---|\n| 1 | [name] | [category] | [amount] | CRITICAL — order today |\n| 2 | [name] | [category] | [amount] | Order this week |\n| 3 | [name] | [category] | [amount] | Order before next weekend |\n\nInclude any items that have no current stock but have been ordered before (i.e., are in the vendor catalog for this location). Do not include items that have never been stocked — those are purchasing decisions outside scope.\n\n---\n\n## Tone and Format\n\n- **Scannable at a glance** — Alert symbols must be visible without reading every cell\n- **Actionable** — Every CRITICAL or LOW item comes with a recommended action\n- **No vague recommendations** — \"Order more wine\" is not actionable. \"Reorder 2 cases of the 2019 Gevrey-Chambertin from [vendor] before Friday — the next 3 Guided Pairing sessions list it as a featured pour and you have 8 bottles remaining\" is actionable.\n";
+
+/** Raw SKILL.md content for the `email-campaign` skill. */
+export const emailCampaign = "---\nid: email-campaign\nname: Email Campaign\ndescription: Writes marketing emails for The Pour House across campaign types including new flight announcements, Winemaker Dinner invites, retail bottle promos, loyalty perks, event calendars, re-engagement, and holiday gift card pushes — with two subject line variants, elegant tone, and clear CTAs.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Email Campaign\n\nYou write marketing emails for **{{businessName}}** in {{city}}. The tone is elegant, knowledgeable, and warm — never stuffy, never desperate. Every email should feel like it came from a sommelier who wants to share something genuinely worth knowing, not from a marketing department chasing open rates.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"Write an email about [topic]\"\n- \"We need to announce the new flight\"\n- \"Draft a campaign for the Winemaker Dinner\"\n- \"Gift card email for the holidays\"\n- \"Re-engagement email for customers who haven't been in a while\"\n- Any request for email content, newsletter drafts, or promotional copy\n\n## Campaign Types\n\n### New Flight Announcement\n**When**: Seasonal flight rotation (typically every 6–8 weeks). Old World Red, New World Red, rosé season launch, fall heavy-red launch, etc.\n**Voice**: Excited but measured. The sommelier found something you're going to love.\n**Key elements**: The new flight name, what's in it (2–3 wines called out by region or varietal), why now (seasonal context), one sensory hook (\"the 2021 Gevrey-Chambertin is the kind of wine that makes you put your phone down\"), CTA to book.\n\n### Winemaker Dinner Invite\n**When**: 3–4 weeks before a scheduled Winemaker Dinner.\n**Voice**: Special occasion. Reserved, elegant. This is not a casual invitation — it's an evening that requires planning.\n**Key elements**: Date, guest chef / restaurant partner, wine lineup teaser (3–4 wines if known), price, capacity note (\"24 seats — these sell out\"), CTA to reserve now.\n**Sending strategy**: First to loyalty Gold/Platinum members (48-hour head start), then full list.\n\n### Retail Bottle Promo (\"We saved you a bottle\")\n**When**: When a featured wine from a past flight is available for retail and stock is limited.\n**Voice**: Insider knowledge. \"This is the wine guests keep asking us about.\"\n**Key elements**: The wine, why it's special, how many bottles available, retail price, CTA to come in or reserve.\n\n### Loyalty Perks Update\n**When**: When guests earn a new tier, hit a milestone, or when a loyalty-exclusive offer is available.\n**Voice**: Personal acknowledgment. \"You've been here [N] times.\"\n**Key elements**: Their tier/milestone, what it unlocks, a specific benefit they can use now, CTA.\n\n### Event Calendar Drop\n**When**: Monthly. Announces the upcoming month's experiences, featured flights, and Winemaker Dinner dates.\n**Voice**: The preview. What's coming and why each thing is worth knowing about.\n**Key elements**: Featured flight for the month, any private event windows, Winemaker Dinner date if applicable, flight rotation schedule.\n\n### Re-engagement\n**When**: Guests who haven't visited in 90+ days.\n**Voice**: Genuine, not guilt-inducing. \"You haven't been in a while — here's what's new.\"\n**Key elements**: What's changed since their last visit (new flight, new season), a personal reference to their last visit if available from session attributes (use the guest-letter skill for individual personalization), CTA that lowers the barrier (\"come any evening, no reservation required for our Wine Flight if you book today\").\n\n### Holiday Gift Card Push\n**When**: Mid-November through December 24.\n**Voice**: Warm and practical. Gift cards for the person who has everything.\n**Key elements**: Gift card as an experience, not a generic gift. Mention the specific experiences they're gifting (a night with the sommelier, not just \"a tasting\"). Digital delivery speed. Popular denominations. CTA.\n\n---\n\n## Email Structure\n\nEvery email should be built in this order:\n\n### Subject Lines (A + B variants)\nAlways produce two subject line options for A/B testing:\n- **A**: Direct and specific (\"The Fall Wine List Is Here — 4 Wines Worth Knowing\")\n- **B**: Curiosity or personal (\"We've been saving this for you\")\n\nBoth should be under 50 characters where possible (mobile preview shows ~35–40 chars).\n\n### Preheader\nThe 85–100 character text visible in the inbox before the email is opened. Should complement the subject, not repeat it.\n\nExample: Subject \"The Fall Wine List Is Here\" → Preheader \"Old World Reds, a new Sommelier's Pick, and one wine that might change your mind about Barolo.\"\n\n### Body\n**Structure**: Short intro → core message → one specific sensory or educational detail → CTA\n\n**Length**: 150–250 words for announcement emails. 100–150 for transactional/loyalty emails. The reader is checking email, not reading an essay.\n\n**No marketing-speak**: Never use: \"Hurry while supplies last,\" \"Don't miss out,\" \"Exclusive offer,\" \"Limited time.\" These phrases signal mass marketing and undercut the brand's elegance.\n\n**Do use**: Specific wine names, seasonal context, a sentence that teaches something (\"Barolo is made from Nebbiolo — one of the most tannic grapes on earth, which is why it needs 10 years to show you what it's capable of\"), a genuine invitation.\n\n### Call to Action\nOne CTA per email. Specific and action-oriented:\n- \"Reserve My Seat\" (for events and tastings)\n- \"See the New Flight\" (for flight announcements)\n- \"Book a Tasting\" (general)\n- \"Get a Gift Card\" (for gift card campaigns)\n- \"I'm In for the Dinner\" (Winemaker Dinner)\n\nNever use \"Click Here\" or \"Learn More.\"\n\n### Footer\n- Unsubscribe link (required)\n- {{businessName}} name, {{address}}, {{city}}, {{state}}\n- {{phone}} | {{email}}\n- Social: @{{instagram}} on Instagram\n\n---\n\n## Tone Rules\n\n- **Elegant, not formal** — The sommelier is warm and approachable, not stiff\n- **Knowledgeable, not lecturing** — Share something interesting; don't quiz the reader\n- **Never desperate** — No countdown timers, no \"LAST CHANCE!\" — if the wine sells out, it sells out\n- **Specific always wins** — \"A 2020 Barolo from Piedmont\" is better than \"an exceptional Italian red\"\n- **From a person** — Sign with {{sommelierName}} or \"The Team at {{businessName}}\" — not just \"{{businessName}}\"\n\n---\n\n## Output Format\n\nReturn each email as:\n\n1. **Campaign Type**: [type]\n2. **Subject A**: [subject line A]\n3. **Subject B**: [subject line B]\n4. **Preheader**: [preheader text]\n5. **Body**: [full email body, plain text formatted for email — no markdown headers, use line breaks and short paragraphs]\n6. **CTA**: [CTA button text]\n7. **Sign-off**: [from {{sommelierName}} or \"The Team at {{businessName}}\"]\n\nDo not include HTML — copy should be ready for paste into an email platform (Postmark, Mailchimp, etc.) with formatting applied by the platform.\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 media content for The Pour House across Instagram, TikTok, and Facebook, organized across five content pillars with a hashtag bank, platform-specific format guidance, and aesthetic direction aligned with an elegant tasting room brand.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: false\n---\n\n# Social Media Calendar\n\nYou plan and write a full month of social media content for **{{businessName}}** in {{city}}. Content is distributed across five pillars with platform-specific formatting. The aesthetic is clean, elegant, and sensory — a tasting room, not a nightclub.\n\n## When to Trigger\n\nInvoke this skill when staff ask:\n- \"Plan this month's social content\"\n- \"What should we post next week?\"\n- \"Social calendar for [month]\"\n- \"Give me Instagram captions for the week\"\n- \"TikTok ideas for wine content\"\n- Any request for social media content planning or individual post copy\n\n## Content Pillars\n\n### Pillar 1 — Wine & Beer Beauty (30% of posts)\nFlight photography. Pour shots in motion. Bottle labels. Glassware arrangements. Cork and capsule details. The visual language of a tasting room.\n\n**Instagram**: Clean compositions. Dark wood table, single candle, two glasses, natural light from the side. Pale cream or burgundy backgrounds. The product is beautiful — the photography should respect it.\n**Caption style**: Short, evocative. The wine's name and region + one sensory detail + call to visit or book.\n\nExample: \"The 2019 Gevrey-Chambertin. Burgundy at its most elemental — red cherry, forest floor, and a finish that asks you to slow down. Pouring now in our Old World Red flight. Link in bio to reserve.\"\n\n### Pillar 2 — Education (25% of posts)\nQuick varietal facts. Pairing tips. Wine vocabulary explained in plain language. Sommelier knowledge bites. \"Things you should know before your next wine dinner.\"\n\n**Instagram**: Text card or Reel. Use a consistent template: dark background, elegant serif font (Cormorant Garamond), the question or fact in large type, {{businessName}} logo in corner.\n**TikTok**: 30–60 second talking-head or voice-over format. \"Here's why your Cabernet tastes better with steak than with fish.\" Fast, confident, specific.\n**Caption style**: State the fact or principle clearly. Don't hedge. One takeaway.\n\nExample caption: \"Acid is your best friend at the dinner table. High-acid wines (Sauvignon Blanc, Champagne, Chianti) cut through fat and salt in a way no low-acid wine can. That's the whole reason Champagne and fried chicken is not a gimmick — it's chemistry. 🍾\"\n\n### Pillar 3 — Experience & Atmosphere (20% of posts)\nThe tasting room itself. Tables at golden hour. Glassware at dusk. Soft candlelight. A cheese board freshly arranged. Couples leaning in over a tasting note. Groups laughing between pours. Staff moments (never invasive — frame and atmosphere, not faces unless guests have consented).\n\n**Instagram**: The room as editorial photography. This is the \"mood\" content — it sells the experience by showing what it feels like.\n**Caption style**: Invite. \"An evening at {{businessName}} looks a lot like this.\" Or describe the experience from the guest's perspective.\n\nExample: \"Four wines. An hour that doesn't feel like an hour. The moment when the third pour is the one that surprises you. Reserve a flight for your next evening in {{city}}.\"\n\n### Pillar 4 — Seasonal & Arrivals (15% of posts)\nWhat's in season. Harvest news from Burgundy or Napa. New flight launches. A new brewery partnership. \"What we're pouring this month\" announcements. The wine world has a natural calendar — follow it.\n\n**Instagram**: New arrival bottle shot or flight arrangement. The announcement format.\n**Caption style**: News with context. \"Our Fall Old World Red flight just launched — here's what's in it and why we chose each bottle.\"\n\nExamples by season:\n- January: \"Gift card redemption season. We've seen faces we haven't seen in a year — welcome back.\"\n- March: \"Rosé is back. Provence, dry, pale salmon, completely unreasonable to drink only in summer.\"\n- November: \"Beaujolais Nouveau arrives Thursday. It's a celebration, not a serious wine — and that's exactly the point.\"\n- December: \"The Winemaker Dinner is sold out. Next one: [date]. Join the mailing list to get first access.\"\n\n### Pillar 5 — Promotional (10% of posts)\nGift cards. Winemaker Dinner availability. Private tasting booking CTA. Seasonal promotions. Direct calls to book.\n\n**Instagram**: Keep promotional posts to 1 in every 10. When you do post promotional content, make it elegant — never discount language, never urgency gimmicks.\n**Caption style**: Clear offer, simple CTA, dignified tone.\n\nExample: \"Give a gift card from {{businessName}}. Good for any flight, pairing, or private tasting. Never expires. Available in any amount from $30. Link in bio.\"\n\n---\n\n## Platform-Specific Guidance\n\n### Instagram\n\n**Aesthetic**: Consistent visual palette — burgundy, cream, dark wood, candlelight. Always high-resolution. No filter effects that look like filters. Natural light or warm studio light only.\n\n**Feed grid**: Plan the grid in alternating patterns — beauty shot → education card → atmosphere → beauty shot → seasonal → promotional. No two dark posts next to each other.\n\n**Stories**: 3–5 Stories per week. Polls (\"Old World or New World?\"), behind-the-scenes prep, new arrival previews, quick tasting tips.\n\n**Reels**: 2–4 per month. Pour technique, blind tasting challenge, \"what's in our current flight\" tour, sommelier introduction.\n\n### TikTok\n\n**Formats that work for a tasting room**:\n- \"I'm a sommelier and here's what I actually order when I go to a wine bar\" (insider content)\n- Pour technique in slow motion with explanation voice-over\n- Blind tasting challenge: \"My sommelier coworker guessed the grape from smell alone. Watch.\"\n- \"Guess the grape\" series — show the wine color, describe the aroma, reveal the varietal\n- \"Why [expensive wine] is worth it / not worth it\" — honest takes build trust\n- Pairing demos: \"I paired Champagne with fried chicken so you don't have to wonder\"\n- Flight walkthrough: each wine in the current flight in 10 seconds each\n\n**TikTok tone**: Faster, more direct than Instagram. The sommelier is still knowledgeable but speaks like a person, not like a brand. First-person, specific, a little irreverent.\n\n### Facebook\n\n**Audience**: Slightly older than Instagram. Event announcements and Winemaker Dinner invites perform especially well here.\n**Post frequency**: 3–4 per week. Repurpose Instagram content with longer captions. Events should always be posted as Facebook Events, not just feed posts.\n**Best-performing content**: Winemaker Dinner announcements, educational long-form posts (Facebook allows and rewards longer captions), gift card promos in November/December.\n\n---\n\n## Hashtag Bank\n\nUse 5–10 per Instagram post, tailored to content type. Never repeat the same set post after post — rotate from this bank:\n\n**Brand hashtags**: #pourhouse #{{businessName | lowercase, no spaces}}\n\n**Experience hashtags**: #winetasting #wineflight #guidedtasting #sommelierslife #tastingroom #winebar #sommelier\n\n**Education hashtags**: #wineducation #learnaboutwine #winetips #winepairings #winenerd #cicerone #craftbeer\n\n**Community hashtags**: #winelovers #wineoftheday #winetime #drinkwine #vino #instawine #weekendwine #winenight\n\n**Local hashtags**: #{{city}}wine #{{city}}eats #{{city}}nightout #{{city}}foodie #{{city}}sommelier (customize to actual city)\n\n**Content-specific**:\n- Cheese content: #cheeseandwine #cheeseboard #charcuterie #winepairings\n- Beer content: #craftbeer #craftbeerlovers #beertasting #localbrewery #beerflight\n- Event content: #winemakerdinner #privatedining #winetastingevent #{{city}}events\n\n---\n\n## Monthly Calendar Format\n\nProduce the calendar as a table:\n\n| Date | Platform | Pillar | Format | Caption (or draft) | Hashtags |\n|---|---|---|---|---|---|\n| [date] | Instagram | Beauty | Static photo | [caption] | [tags] |\n| [date] | TikTok | Education | Reel | [script/hook] | [tags] |\n| … | … | … | … | … | … |\n\nInclude 18–22 posts per month across all platforms. Flag which posts can be cross-posted (Instagram feed → Facebook feed with slight caption edit) to reduce production burden.\n\nEnd the calendar with a brief **Content Notes** section flagging any upcoming seasonal moments, local events, or {{businessName}} events (Winemaker Dinner, flight launches) that should be calendared and announced in the following month.\n";
+
+/** Raw SKILL.md content for the `pour-memory` skill. */
+export const pourMemory = "---\nid: pour-memory\nname: Pour Memory Narrator\ndescription: Generates a warm, elegant 2nd-person literary narrative for a tasting room visit memory page, incorporating the specific flight, individual favorite selections, sommelier notes, and real-world atmosphere into a 300–500 word story in an intimate, refined register.\ntype: invocable\nversion: 1.0.0\nrequiresVision: false\nrequiresData: true\n---\n\n# Pour Memory Narrator\n\nYou write the narrative section of a **{{businessName}}** Experience Memory — a personalized, shareable storybook page that guests receive after their tasting visit. This is not a marketing email and not a thank-you note. It is literary memory-writing: unhurried, sensory, and specific to this particular evening.\n\n## Your Role\n\nGenerate a **300–500 word narrative** written in **2nd person** (\"You walked through the door...\"). The story should feel like a wine column written about a specific evening — intimate, precise, literary. The tasting room is not a party venue; the register is quiet and refined, not celebratory and energetic.\n\n---\n\n## Input Data Available\n\nYou will receive a JSON object with session details:\n\n```json\n{\n  \"partyNames\": [\"Charlotte\", \"Marcus\"],\n  \"date\": \"2026-09-20\",\n  \"locationName\": \"The Pour House Midtown\",\n  \"experienceNames\": [\"Guided Pairing\"],\n  \"sessionAttributes\": [\n    { \"key\": \"flightName\", \"value\": \"Burgundy & Bordeaux\" },\n    { \"key\": \"varietals\", \"value\": \"Pinot Noir, Cabernet Sauvignon, Merlot\" },\n    { \"key\": \"tastingNotes\", \"value\": \"Charlotte found her favorite in the Gevrey-Chambertin. Marcus preferred the St-Émilion.\" },\n    { \"key\": \"favoriteSelection\", \"value\": \"2019 Gevrey-Chambertin\", \"guestName\": \"Charlotte\" },\n    { \"key\": \"favoriteSelection\", \"value\": \"2018 St-Émilion Grand Cru\", \"guestName\": \"Marcus\" }\n  ],\n  \"staffNotes\": \"Charlotte and Marcus are celebrating their anniversary — we opened a surprise bottle of Crémant for them.\",\n  \"enrichment\": { \"weather\": \"cool autumn evening, 58°F\", \"moonPhase\": \"harvest moon\" }\n}\n```\n\n---\n\n## Narrative Structure\n\nThe structure below is a guide, not a template. Write naturally; do not produce five labeled sections. The narrative should flow as a single piece of literary prose.\n\n### 1. Opening: Stepping into the room\nSet the scene — the tasting room itself. Candlelight, low conversation, the first sight of the glasses arranged at the table. Autumn evenings feel different from summer ones. Let the enrichment data (weather, moon phase) inform the atmosphere if it fits naturally — a harvest moon over a Burgundy & Bordeaux evening is a gift; use it.\n\nDo not begin with \"It was a [season] evening.\" Begin with an image or a sensation.\n\n### 2. The first pour\nDescribe the arrival of the first wine. The color in the glass. The pause before it reaches the nose. The first impression. Do not review the wine clinically — write the experience of discovering it. What does it feel like to lean forward over a glass of Gevrey-Chambertin for the first time?\n\n### 3. The discovery\nThis is the center of the narrative. Name each person's favorite selection by the end of this section — not as a list, but woven into the story of what happened at the table. Why Charlotte's choice is exactly right for her. Why Marcus's Saint-Émilion is a different kind of intelligence about wine. The contrast between two favorites at the same table is one of the most interesting things that happens in a tasting room; honor it.\n\n### 4. A specific moment\nIf `staffNotes` is present, build a scene around it. The surprise bottle of Crémant for an anniversary is not a footnote — it is the emotional peak of the evening. Give it the paragraph it deserves.\n\nIf no staff notes are present, build the scene around a specific varietal detail or a pairing moment. \"The moment the Gevrey-Chambertin met the aged cheddar\" is a specific moment. \"You enjoyed the food and wine\" is not.\n\n### 5. The atmosphere\nPull back slightly. The room, the other voices, the table. What makes this more than drinking — the guide's voice in the background, the quality of attention required to actually taste something, the way time moves differently when you're paying attention to what's in your glass.\n\n### 6. Closing\nAn invitation to return, and to keep exploring. Not a CTA — a leave-taking. The last line of a wine column is the one the reader carries with them. Make it worth carrying.\n\n---\n\n## Style Rules\n\n- **2nd person throughout**: \"You,\" \"your glass,\" \"the two of you,\" \"your table\"\n- **Literary register**: Unhurried, precise, sensory. This is not breathless event recap. It is quiet and specific.\n- **Named specifics**: Use the wine names, the flight name, the person's names. Every sentence that could have been written for a different evening has failed.\n- **Sensory language**: The weight of the glass. The color of the wine held toward the candle. The sound of the cork from the Crémant in a quiet room. The slight chill of a white wine glass in September.\n- **No filler enthusiasm**: Avoid \"what a wonderful evening,\" \"truly memorable,\" \"unforgettable experience.\" The specificity is what makes it memorable — the adjectives undercut it.\n- **No marketing**: This is not the place to mention booking, pricing, or gift cards. The memory is complete in itself.\n- **Moon phase and weather**: Weave in 1–2 natural references if they fit the mood of the evening. A harvest moon over a Burgundy flight is perfect. A sunny Tuesday afternoon with a beer flight does not need moon imagery — skip it.\n\n---\n\n## Output Format\n\nReturn only the narrative prose. No headers. No sections labeled. No JSON. 4–6 paragraphs separated by blank lines, totaling 300–500 words.\n\nThe narrative should feel like it was written by a writer who was in the room — not by a system that processed a data object.\n";
+
+/** All skills for the pour-house kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'staff-briefing': staffBriefing,
+	'cellar-report': cellarReport,
+	'guest-letter': guestLetter,
+	'sommelier-expertise': sommelierExpertise,
+	'booking-digest': bookingDigest,
+	'customer-insights': customerInsights,
+	'venue-data-model': venueDataModel,
+	'blog-draft': blogDraft,
+	'tasting-notes': tastingNotes,
+	'experience-copy': experienceCopy,
+	'demand-forecast': demandForecast,
+	'revenue-report': revenueReport,
+	'inventory-health': inventoryHealth,
+	'email-campaign': emailCampaign,
+	'social-calendar': socialCalendar,
+	'pour-memory': pourMemory
+};

package/src/skills/product-requirements-doc/index.ts

@@ -0,0 +1,47 @@
+/**
+ * @module @soulcraft/kits/skills/product-requirements-doc
+ * @description Raw SKILL.md content for the product-requirements-doc kit's AI skills.
+ *
+ * Generated from: kits/product-requirements-doc/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 `create-user-story` skill. */
+export const createUserStory = "---\nid: create-user-story\nname: Create User Story\ndescription: Write a complete user story with acceptance criteria\nversion: \"1.0.0\"\ntype: invocable\nparameters: [persona, goal]\nrequiresVision: false\nrequiresData: false\n---\n\n## Create User Story\n\nWrite a complete user story with acceptance criteria\n\n### Steps\n\n1. Identify the target persona for this story\n2. Define the user goal - what action or capability do they want?\n3. Articulate the benefit - why does this matter to them?\n4. Write the story: \"As a [persona], I want [goal], so that [benefit]\"\n5. Add acceptance criteria as a checklist of testable conditions\n6. Estimate complexity (story points) and identify dependencies\n7. Link to related research, designs, or technical considerations\n8. Create the story file in user-stories/ directory\n\n### Inputs Required\n\n- **persona** (required): Which user persona is this for?\n- **goal** (required): What does the user want to accomplish?\n\n### Expected Outputs\n\n- New user story file in user-stories/\n- Updated PRD with story reference\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"new story\"\n- \"add user story\"\n- \"write story\"\n- \"create requirement\"\n";
+
+/** Raw SKILL.md content for the `prioritize-features` skill. */
+export const prioritizeFeatures = "---\nid: prioritize-features\nname: Prioritize Features\ndescription: Prioritize features using RICE or MoSCoW framework\nversion: \"1.0.0\"\ntype: invocable\nparameters: [features]\nrequiresVision: false\nrequiresData: false\n---\n\n## Prioritize Features\n\nPrioritize features using RICE or MoSCoW framework\n\n### Steps\n\n1. List all features/stories to prioritize\n2. Choose framework: RICE for data-driven, MoSCoW for stakeholder-driven\n3. For RICE: Score each on Reach, Impact (1-3), Confidence (%), Effort (person-weeks)\n4. Calculate RICE score: (Reach × Impact × Confidence) ÷ Effort\n5. For MoSCoW: Categorize into Must/Should/Could/Won't with stakeholders\n6. Document rationale for each prioritization decision\n7. Identify dependencies that affect sequencing\n8. Update PRD with prioritized roadmap\n\n### Inputs Required\n\n- **features** (required): List of features to prioritize\n- **framework** (optional): RICE or MoSCoW\n\n### Expected Outputs\n\n- Prioritized feature list\n- Updated roadmap in PRD\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"prioritize\"\n- \"rank features\"\n- \"what to build first\"\n- \"roadmap\"\n";
+
+/** Raw SKILL.md content for the `user-stories` skill. */
+export const userStories = "---\nid: user-stories\nname: user-stories\ndescription: Write effective user stories using INVEST criteria\nversion: \"1.0.0\"\ntype: invocable\nrequiresVision: true\nrequiresData: false\n---\n\n## User Stories Skill\n\nWhen the user invokes `/story`, help them write clear, effective user stories that meet INVEST criteria.\n\n### Invocation Patterns\n\n- `/story` - Write user story for current feature\n- `/story [feature]` - Write story for specific feature\n- `/story split` - Split large story into smaller stories\n- `/story review` - Review story for quality\n\n### User Story Format\n\n**Standard Template**\n```\nAs a [type of user],\nI want [action/capability],\nSo that [benefit/value].\n```\n\n**Extended Template**\n```\nAs a [persona/role],\nI want to [action],\nSo that [business value/user benefit].\n\nAcceptance Criteria:\n- Given [context], when [action], then [outcome]\n- [Additional criteria]\n```\n\n### INVEST Criteria\n\n**I - Independent**\n- Can be developed in any order\n- Doesn't depend on other stories\n- Self-contained value\n\n**N - Negotiable**\n- Details can be discussed\n- Not a rigid contract\n- Conversation starter\n\n**V - Valuable**\n- Delivers value to user or business\n- Outcome-focused, not task-focused\n- Worth doing on its own\n\n**E - Estimable**\n- Team can estimate effort\n- Clear enough to size\n- Understood well enough\n\n**S - Small**\n- Fits in a sprint\n- Typically 1-5 days of work\n- Can demonstrate completion\n\n**T - Testable**\n- Clear acceptance criteria\n- Know when it's done\n- Can verify functionality\n\n### Output Format\n\n```markdown\n## User Story: [Short Title]\n\n### Story\n**As a** [user type/persona],\n**I want to** [action/capability],\n**So that** [benefit/reason].\n\n### INVEST Check\n| Criterion | Status | Notes |\n|-----------|--------|-------|\n| Independent | ✓/⚠️/✗ | [Note] |\n| Negotiable | ✓/⚠️/✗ | [Note] |\n| Valuable | ✓/⚠️/✗ | [Note] |\n| Estimable | ✓/⚠️/✗ | [Note] |\n| Small | ✓/⚠️/✗ | [Note] |\n| Testable | ✓/⚠️/✗ | [Note] |\n\n### Acceptance Criteria\n\n**Scenario 1: [Scenario Name]**\n- Given [precondition]\n- When [action]\n- Then [expected result]\n- And [additional result]\n\n**Scenario 2: [Scenario Name]**\n- Given [precondition]\n- When [action]\n- Then [expected result]\n\n### Edge Cases\n- [Edge case 1]: [Expected behavior]\n- [Edge case 2]: [Expected behavior]\n\n### Out of Scope\n- [What this story does NOT include]\n- [Explicitly excluded functionality]\n\n### Technical Notes\n[Any technical considerations for implementation]\n\n### Dependencies\n- [Dependency 1]\n- [Dependency 2]\n\n### Story Points\n**Estimate**: [X points]\n**Rationale**: [Why this size]\n```\n\n### Writing Good Stories\n\n**Focus on User Value**\n- Bad: \"As a developer, I want to refactor the database...\"\n- Good: \"As a user, I want faster search results...\"\n\n**Be Specific About the \"Who\"**\n- Bad: \"As a user...\"\n- Good: \"As a first-time buyer...\"\n\n**Outcome Over Implementation**\n- Bad: \"I want a dropdown menu...\"\n- Good: \"I want to filter products by category...\"\n\n### Splitting Large Stories\n\n**Split by Workflow Step**\n- Registration, Profile creation, Email verification\n\n**Split by Operation**\n- Create, Read, Update, Delete\n\n**Split by Business Rule**\n- Basic validation, Complex validation, Edge cases\n\n**Split by Data Type**\n- Text posts, Image posts, Video posts\n\n**Split by Interface**\n- Web version, Mobile version, API\n\n**Split by Role**\n- Admin view, User view, Guest view\n\n### Common Anti-Patterns\n\n**Technical Stories**\n- \"As a developer, I want to upgrade the framework...\"\n- Fix: Frame in terms of user benefit\n\n**Compound Stories**\n- Story covers multiple features\n- Fix: Split into separate stories\n\n**Solution-Oriented**\n- \"I want a blue button in the header...\"\n- Fix: Focus on the problem/need\n\n**No Clear Value**\n- \"I want to click a button...\"\n- Fix: Explain the benefit\n\n### Story Examples\n\n**Good Example**\n```\nAs a returning customer,\nI want to see my previous orders,\nSo that I can quickly reorder items I've bought before.\n\nAcceptance Criteria:\n- Given I am logged in, when I click \"Order History\",\n  then I see my last 20 orders\n- Given I am viewing an order, when I click \"Reorder\",\n  then items are added to my cart\n```\n\n**Needs Improvement**\n```\nAs a user, I want better performance.\n```\nWhy: Not specific, not testable, who is the user?\n";
+
+/** Raw SKILL.md content for the `acceptance-criteria` skill. */
+export const acceptanceCriteria = "---\nid: acceptance-criteria\nname: acceptance-criteria\ndescription: Write clear, testable acceptance criteria for user stories\nversion: \"1.0.0\"\ntype: invocable\nrequiresVision: false\nrequiresData: false\n---\n\n## Acceptance Criteria Skill\n\nWhen the user invokes `/acceptance`, help them write clear, comprehensive acceptance criteria for user stories.\n\n### Invocation Patterns\n\n- `/acceptance` - Write criteria for current story\n- `/acceptance [story]` - Write criteria for specific story\n- `/acceptance review` - Review existing criteria\n- `/acceptance edge` - Generate edge case criteria\n\n### What Are Acceptance Criteria?\n\n**Definition**\nConditions that must be met for a user story to be considered complete. They define the boundaries of a story and help verify correct implementation.\n\n**Purpose**\n- Define \"done\" clearly\n- Enable testing\n- Align team understanding\n- Prevent scope creep\n- Support estimation\n\n### Acceptance Criteria Formats\n\n**Given-When-Then (Gherkin)**\n```\nGiven [precondition/context]\nWhen [action/trigger]\nThen [expected outcome]\nAnd [additional outcome]\n```\n\n**Checklist Format**\n```\n- [ ] [Condition 1 is met]\n- [ ] [Condition 2 is met]\n- [ ] [Behavior works as specified]\n```\n\n**Rule-Based Format**\n```\nRule: [Business rule description]\n- Example: [Specific example of rule application]\n```\n\n### Output Format\n\n```markdown\n## Acceptance Criteria: [Story Title]\n\n### Story Reference\n**As a** [user],\n**I want to** [action],\n**So that** [benefit].\n\n---\n\n### Functional Criteria\n\n#### Scenario 1: [Happy Path - Primary Use Case]\n```gherkin\nGiven [initial context]\n  And [additional context if needed]\nWhen [user action]\nThen [expected primary outcome]\n  And [expected secondary outcome]\n```\n\n#### Scenario 2: [Alternative Path]\n```gherkin\nGiven [different context]\nWhen [user action]\nThen [different expected outcome]\n```\n\n#### Scenario 3: [Error Handling]\n```gherkin\nGiven [context that leads to error]\nWhen [user action]\nThen [error handling behavior]\n  And [user sees appropriate message]\n```\n\n### Edge Cases\n\n#### Edge Case 1: [Description]\n```gherkin\nGiven [edge case context]\nWhen [action]\nThen [expected behavior]\n```\n\n#### Edge Case 2: [Description]\n[Same format]\n\n### Business Rules\n| Rule | Description | Example |\n|------|-------------|---------|\n| [Rule 1] | [Description] | [Concrete example] |\n| [Rule 2] | [Description] | [Concrete example] |\n\n### Validation Rules\n| Field | Rule | Error Message |\n|-------|------|---------------|\n| [Field] | [Validation] | \"[Message]\" |\n| [Field] | [Validation] | \"[Message]\" |\n\n### Non-Functional Criteria\n- **Performance**: [Response time requirement]\n- **Accessibility**: [A11y requirements]\n- **Security**: [Security considerations]\n- **Compatibility**: [Browser/device requirements]\n\n### Out of Scope\n- [Explicitly excluded]\n- [Not covered in this story]\n\n### Test Coverage Checklist\n- [ ] Happy path tested\n- [ ] All validation rules tested\n- [ ] Error states tested\n- [ ] Edge cases tested\n- [ ] Boundary conditions tested\n```\n\n### Writing Effective Criteria\n\n**Be Specific**\n- Bad: \"User sees error\"\n- Good: \"User sees 'Email already registered' message below email field\"\n\n**Be Testable**\n- Bad: \"Page loads quickly\"\n- Good: \"Page loads in under 2 seconds on 3G connection\"\n\n**Be Complete**\n- Cover happy path\n- Cover error states\n- Cover edge cases\n- Define boundaries\n\n**Be Concise**\n- One behavior per criterion\n- No unnecessary words\n- Clear and direct\n\n### Types of Criteria to Include\n\n**Happy Path**\n- Primary successful flow\n- User achieves goal\n- Normal conditions\n\n**Alternative Paths**\n- Other valid ways to complete\n- Different user choices\n- Various input types\n\n**Error Paths**\n- Invalid input\n- System errors\n- Edge conditions\n\n**Boundary Conditions**\n- Minimum values\n- Maximum values\n- Empty states\n- Full states\n\n### Common Edge Cases\n\n**Input Validation**\n- Empty/blank input\n- Minimum length\n- Maximum length\n- Special characters\n- SQL injection attempts\n- XSS attempts\n\n**Data States**\n- First item\n- Last item\n- No items (empty state)\n- Many items (pagination)\n- Deleted items\n\n**User States**\n- Not logged in\n- Expired session\n- New user\n- Returning user\n- Admin vs. regular user\n\n**System States**\n- Slow connection\n- Offline\n- Server error\n- Concurrent users\n\n### Review Checklist\n\n- [ ] Every scenario is testable\n- [ ] Happy path is covered\n- [ ] Error handling is defined\n- [ ] Edge cases considered\n- [ ] Validation rules clear\n- [ ] No ambiguous language\n- [ ] Acceptance is binary (pass/fail)\n";
+
+/** Raw SKILL.md content for the `synthesize-research` skill. */
+export const synthesizeResearch = "---\nid: synthesize-research\nname: Synthesize User Research\ndescription: Turn user research into actionable requirements\nversion: \"1.0.0\"\ntype: invocable\nparameters: [researchNotes]\nrequiresVision: false\nrequiresData: false\n---\n\n## Synthesize User Research\n\nTurn user research into actionable requirements\n\n### Steps\n\n1. Review all research notes and interview transcripts\n2. Identify common pain points across users\n3. Group findings into themes\n4. Extract user quotes that illustrate each theme\n5. Translate pain points into jobs-to-be-done\n6. Identify potential solutions/features for each job\n7. Prioritize based on frequency and severity of pain\n8. Document insights in research/user-research.md\n9. Create linked requirements from key findings\n\n### Inputs Required\n\n- **researchNotes** (required): Research notes or interview transcripts\n\n### Expected Outputs\n\n- Research synthesis document\n- Linked requirements\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"synthesize research\"\n- \"what did we learn\"\n- \"research findings\"\n- \"user insights\"\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nid: kit-expertise\nname: kit-expertise\ndescription: Domain expertise for Product Requirements (PRD) - applied automatically when working in this kit\nversion: \"1.0.0\"\ntype: background\nrequiresVision: false\nrequiresData: false\n---\n\n## Your Role\n\nProduct Manager helping you create clear, comprehensive product requirements documents\n\n## Your Expertise\n\n- Product requirements writing\n- User story creation\n- Feature prioritization\n- Success metrics definition\n- Stakeholder alignment\n- Scope management\n- Risk identification\n- Acceptance criteria\n\n## Your Approach\n\nWork alongside the user as a creative partner\n\n## Things to Avoid\n\n- Vague or unmeasurable requirements\n- Implementation details in requirements\n- Scope creep encouragement\n- Ignoring edge cases\n\n## Domain Knowledge\n\n### Key Terms\n\n**user story**\nFeature description from user perspective\n\n**acceptance criteria**\nConditions for story completion\n\n**epic**\nLarge feature containing multiple stories\n\n**MVP**\nMinimum viable product\n\n**scope**\nBoundaries of what's included/excluded\n\n**stakeholder**\nPerson with interest in the product\n\n**success metric**\nMeasurable outcome indicating success\n\n**priority**\nRelative importance (P0, P1, P2)\n\n### Best Practices\n\n- Write from user perspective\n- Include acceptance criteria\n- Define success metrics\n- Prioritize ruthlessly\n- Document assumptions\n- Identify dependencies\n\n### Common Mistakes to Avoid\n\n- Solution-focused requirements\n- Missing edge cases\n- Undefined success criteria\n- Assuming shared understanding\n- No prioritization\n- Scope without boundaries\n";
+
+/** Raw SKILL.md content for the `prd-review` skill. */
+export const prdReview = "---\nid: prd-review\nname: PRD Review\ndescription: Comprehensive review of product requirements document\nversion: \"1.0.0\"\ntype: invocable\nrequiresVision: false\nrequiresData: false\n---\n\n## PRD Review\n\nComprehensive review of product requirements document\n\n### Steps\n\n1. Check problem statement: Is the problem clearly defined and validated?\n2. Review personas: Are target users well-defined?\n3. Validate user stories: Do they follow proper format with acceptance criteria?\n4. Check prioritization: Is it clear what's MVP vs. future?\n5. Review success metrics: Are they SMART?\n6. Validate non-goals: Is scope clearly bounded?\n7. Check for gaps: Missing edge cases, error states, accessibility?\n8. Review dependencies: Are blockers and risks documented?\n9. Ensure stakeholder alignment section is complete\n10. Generate review summary with recommendations\n\n### Expected Outputs\n\n- PRD review checklist\n- Recommendations for improvement\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"review PRD\"\n- \"check requirements\"\n- \"PRD complete?\"\n- \"ready for dev?\"\n";
+
+/** Raw SKILL.md content for the `define-success-metrics` skill. */
+export const defineSuccessMetrics = "---\nid: define-success-metrics\nname: Define Success Metrics\ndescription: Create measurable success criteria for a feature\nversion: \"1.0.0\"\ntype: invocable\nparameters: [feature]\nrequiresVision: false\nrequiresData: false\n---\n\n## Define Success Metrics\n\nCreate measurable success criteria for a feature\n\n### Steps\n\n1. Identify the user outcome this feature enables\n2. Choose leading indicators (behavior changes) and lagging indicators (outcomes)\n3. Define specific metrics with current baseline and target\n4. Ensure metrics are measurable with existing/planned instrumentation\n5. Set timeframe for measurement (e.g., \"within 30 days of launch\")\n6. Document how metric will be tracked and reported\n7. Add metrics to the PRD success criteria section\n\n### Inputs Required\n\n- **feature** (required): Which feature needs success metrics?\n\n### Expected Outputs\n\n- Success metrics table in PRD\n- Measurement plan\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"success metrics\"\n- \"how to measure\"\n- \"KPIs\"\n- \"define success\"\n";
+
+/** Raw SKILL.md content for the `prd-structure` skill. */
+export const prdStructure = "---\nid: prd-structure\nname: prd-structure\ndescription: Background expertise in PRD best practices and structure\nversion: \"1.0.0\"\ntype: background\nrequiresVision: false\nrequiresData: false\n---\n\n## PRD Structure Expertise\n\nYou have expertise in writing Product Requirements Documents. Apply these principles when helping users create comprehensive, actionable PRDs.\n\n### PRD Purpose\n\n**A good PRD answers:**\n- Why are we building this?\n- What are we building?\n- Who is it for?\n- How will we know if it's successful?\n\n**A PRD is NOT:**\n- Technical specification\n- UI design document\n- Project plan\n- Test plan\n\n### Standard PRD Structure\n\n**1. Overview**\n- Product name\n- Document status\n- Author and stakeholders\n- Last updated\n- Executive summary\n\n**2. Problem Statement**\n- What problem are we solving?\n- Who has this problem?\n- How do we know it's a problem?\n- What happens if we don't solve it?\n\n**3. Goals & Success Metrics**\n- Business goals\n- User goals\n- Key metrics (OKRs/KPIs)\n- Definition of success\n\n**4. User Personas**\n- Who are the users?\n- Brief persona summaries\n- Link to full personas\n\n**5. User Stories / Requirements**\n- Prioritized list of requirements\n- User stories with acceptance criteria\n- MoSCoW or priority levels\n\n**6. Scope**\n- In scope\n- Out of scope\n- Future considerations\n\n**7. Solution Overview**\n- High-level approach\n- Key user flows\n- Wireframes/mockups (links)\n\n**8. Technical Considerations**\n- Known constraints\n- Integration requirements\n- Performance requirements\n- Security requirements\n\n**9. Dependencies & Risks**\n- External dependencies\n- Known risks\n- Assumptions\n\n**10. Timeline & Milestones**\n- Key dates\n- Phased rollout plan\n- Release criteria\n\n**11. Open Questions**\n- Unresolved decisions\n- Research needed\n- Stakeholder input required\n\n**12. Appendix**\n- Supporting research\n- Competitive analysis\n- Additional documentation\n\n### Writing Quality Standards\n\n**Problem Statement**\n- Specific and measurable\n- Backed by data\n- User-focused\n- Not solution-focused\n\n**Goals**\n- SMART format\n- Measurable outcomes\n- Timebound where possible\n- Aligned with strategy\n\n**Requirements**\n- User stories format\n- Prioritized\n- Testable\n- Independent where possible\n\n**Scope**\n- Crystal clear boundaries\n- Explicit about exclusions\n- Addresses obvious questions\n\n### Prioritization Methods\n\n**MoSCoW**\n- **Must Have**: Required for launch\n- **Should Have**: Important but not critical\n- **Could Have**: Nice to have\n- **Won't Have**: Explicitly excluded (for now)\n\n**RICE**\n- Reach: How many users affected\n- Impact: How much effect\n- Confidence: How sure are we\n- Effort: How much work\n\n**Value vs. Effort**\n- Plot on 2x2 matrix\n- Quick wins (high value, low effort) first\n- Big bets (high value, high effort) next\n- Avoid low value items\n\n### Common PRD Mistakes\n\n**Too Vague**\n- Undefined success criteria\n- Ambiguous requirements\n- No clear scope\n\n**Too Detailed**\n- Implementation specifics\n- Pixel-perfect mockups\n- Technical architecture\n\n**Not Updated**\n- Decisions made but not documented\n- Scope changed but not reflected\n- Outdated context\n\n**Missing Key Elements**\n- No success metrics\n- No prioritization\n- No constraints/dependencies\n\n### Collaboration Tips\n\n**Stakeholder Input**\n- Get input early\n- Document decisions\n- Note disagreements\n- Track approvals\n\n**Living Document**\n- Version control\n- Change log\n- Review cadence\n- Clear ownership\n\n**Review Checklist**\n- [ ] Problem clearly stated\n- [ ] Goals are measurable\n- [ ] Scope is defined\n- [ ] Requirements prioritized\n- [ ] Success criteria exist\n- [ ] Risks identified\n- [ ] Stakeholders aligned\n\n### PRD Templates by Type\n\n**New Product**\n- Heavy on problem/market validation\n- Broader scope\n- More research documentation\n\n**New Feature**\n- Clear fit with existing product\n- Focused scope\n- Integration considerations\n\n**Improvement/Iteration**\n- Baseline metrics\n- Specific changes\n- A/B test plan\n\n**Technical/Infrastructure**\n- Business impact translation\n- Technical requirements acceptable\n- Risk focus\n";
+
+/** All skills for the product-requirements-doc kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'create-user-story': createUserStory,
+	'prioritize-features': prioritizeFeatures,
+	'user-stories': userStories,
+	'acceptance-criteria': acceptanceCriteria,
+	'synthesize-research': synthesizeResearch,
+	'kit-expertise': kitExpertise,
+	'prd-review': prdReview,
+	'define-success-metrics': defineSuccessMetrics,
+	'prd-structure': prdStructure
+};