@soulcraft/kits 1.0.0

package/kits/axe-house/skills/guest-letter/SKILL.md

@@ -0,0 +1,171 @@
+---
+id: guest-letter
+name: Guest Follow-Up Letter
+description: Writes a personalized 150–250 word post-session thank-you email referencing the guest's specific session type, best score, throw style, coach notes, and loyalty points earned — in the brand's energetic, coach-like voice.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: true
+---
+
+# Guest Follow-Up Letter
+
+You write the post-session follow-up email that guests receive after completing a session at {{businessName}}. It is energetic, specific, and reads like a note from a coach who actually remembers them — because the session data behind it does. Every letter must reference real details from the session: throw style, best score, coach notes, team name for league guests.
+
+## When to Trigger
+
+Invoke this skill when:
+
+- A booking is marked as completed / checked out
+- A staff member asks: "Send a thank-you to [booking]"
+- "Follow up with guests from [date]"
+- "Post-session email for booking [number]"
+- Any post-visit guest communication request
+
+## Input Data
+
+Pull these fields from the booking record and related entities. All filtered by `bookingId` and `locationId`.
+
+```typescript
+// Booking record
+const booking = await brain.find({
+  type: 'Event',
+  where: [
+    { field: 'metadata.entityType',    value: 'booking'        },
+    { field: 'metadata.bookingNumber', value: BOOKING_NUMBER   },
+    { field: 'metadata.locationId',    value: LOCATION_ID      }
+  ]
+});
+// booking.metadata: { guestCount, date, experienceSlug, totalInCents, checkedIn }
+// booking.data: { partyNames, sessionAttributes, staffNotes }
+
+// Session attributes (per-guest fields from session)
+// booking.data.sessionAttributes as:
+// [{ guestName, throwStyle, bestScore, laneNumber, teamName, leagueSeason,
+//    competitionFormat, coachNotes }, ...]
+```
+
+```typescript
+// Loyalty points earned on this session
+const loyaltyTx = await brain.find({
+  type: 'Measurement',
+  where: [
+    { field: 'metadata.entityType', value: 'loyalty-transaction' },
+    { field: 'metadata.reason',     value: 'earned'              },
+    { field: 'metadata.bookingId',  value: booking.id            }
+  ]
+});
+// loyaltyTx.metadata: { points, customerId }
+
+// Customer loyalty account for current tier
+const loyaltyAccount = await brain.find({
+  type: 'Person',
+  where: [
+    { field: 'metadata.entityType', value: 'loyalty-account'           },
+    { field: 'metadata.customerId', value: booking.metadata.customerId  }
+  ]
+});
+// loyaltyAccount.metadata: { pointsBalance, tier }
+```
+
+## Letter Structure
+
+Write a **150–250 word** email. Follow this order of beats — but write it as a flowing letter, not a list. No section headers in the output.
+
+### 1. Personalized Opener
+
+Address the guest(s) by first name(s). Never "Dear Valued Customer" or "Hi there."
+
+If multiple guests: use both first names (e.g., "Marcus and Jordan,").
+If party size > 2 and names are available: use "Marcus, Jordan, and the whole crew —".
+For league guests: reference the team name if available (e.g., "Iron Shoulders —").
+
+### 2. Specific Session Callback
+
+Reference exactly what happened in the session. Best score, throw style, a coaching breakthrough, competition result, or a memorable moment from coach notes.
+
+Good: "That hatchet form in the second half of the session was genuinely impressive — from inconsistent sticks to four bullseyes in a row is a big jump for one hour."
+Good for league: "Season 3, Week 5 — and Iron Shoulders just went 2-1 against a team that's been on a 4-week win streak. The standings are tighter than they look."
+Bad: "We hope you enjoyed your time throwing axes with us."
+
+If bestScore is available: "Hitting a [score] in that clutch call takes nerve. You called it, you stuck it."
+
+If no session attribute data is available at all, write around it gracefully: "Whatever happened on Lane [number] Thursday night, the marks on the board tell a story."
+
+### 3. Technique Note (if coach notes exist)
+
+If `coachNotes` is present in session attributes, reference the specific coaching point — the thing they improved or the thing to work on next time. This is what makes the letter feel real.
+
+Good: "Your coach noted that your release timing cleaned up significantly in the back half of the session — that's the single hardest adjustment for hatchet throwers. Come back and see if you can make it the default."
+
+If no coach notes: skip this beat entirely.
+
+### 4. Loyalty Points (if loyalty program active)
+
+If points were earned, mention them with current balance and tier. One sentence, brief.
+
+Example: "You earned 25 points on this visit, bringing your total to 180 — Bronze tier."
+
+If no loyalty account or no points data, omit this beat entirely.
+
+### 5. Return Invitation
+
+One natural sentence that implies they'll be back, not that they should feel obligated. Match the session type:
+
+- Open throw: "Whenever you want to work on that release timing, Lane [number] will be waiting."
+- League: "Week 6 standings update coming {{leagueNights}} — we'll be watching Iron Shoulders."
+- Private party: "If you want to do it again — or if your group wants a rematch — we can set up the same format."
+- Axe 101: "You've got the foundation now. Come back and throw a full session — the difference will be obvious."
+
+### 6. Social Share Invite
+
+One line. Include the handle.
+
+Example: "If you caught your bullseye on video, tag us @{{instagram}} — the good throws deserve an audience."
+
+### 7. Sign-Off
+
+From a named coach if available (use the staff member who ran the session, from booking or session data). Otherwise: "The {{businessName}} team."
+
+## Tone Rules
+
+The letter should feel like a note from a coach who actually ran the session and paid attention — not a CRM automation.
+
+- Energetic and direct — not corporate, not overly casual
+- Specific to the sport: use correct terminology (bullseye, clutch, hatchet, stick)
+- Short paragraphs. Two to four sentences per beat.
+- If coach notes include something exceptional (a guest who hit their first-ever bullseye, a team that came back from a big deficit, a corporate group where the expected performer got dominated by a quiet colleague), build the emotional center of the letter around it
+- Match energy to the session: a league win letter is competitive and celebratory; a first-timer letter is encouraging; a corporate event letter can acknowledge the team dynamic
+
+## Absolute Rules
+
+- NEVER: "Dear Valued Customer"
+- NEVER: Generic coaching praise ("great effort today!")
+- NEVER: Hard sell language ("Book now for 10% off!")
+- NEVER: Reference payment amounts or confirmation IDs
+- NEVER: Describe throw style as "your style of throwing" — use the actual term (hatchet, big axe)
+- NEVER: Make up scores or coaching details that aren't in the session data
+
+## Example Output
+
+```
+Marcus and Jordan,
+
+That session was one of the better first-time showings we've had in a while. Jordan,
+hitting a 38 on your last set — hatchet, two-hand grip, consistent release point from
+throw 8 onward — that's not beginner form anymore. Marcus, the coach noted your stance
+opened up nicely after the first 20 minutes. The fact that you were sticking 4s and 5s
+by the end of the session is exactly what that adjustment is supposed to produce.
+
+Come back with a score target: if Jordan's going to clear 40 in a set, it's going to
+require a consistent clutch call strategy, not just landing rings.
+
+You each earned 25 points this visit — 50 combined if you have a joint account.
+Enough to start thinking about Silver.
+
+Whenever you're ready to run it back, Lane 4 is open most weekday evenings.
+
+If you got the bullseye on video, tag us @{{instagram}}.
+
+— Coach Ryan and the {{businessName}} team
+```

package/kits/axe-house/skills/inventory-health/SKILL.md

@@ -0,0 +1,234 @@
+---
+id: inventory-health
+name: Inventory Health Check
+description: Analyzes axe throwing venue stock levels with special logic for axe maintenance cycles, target board rotation schedules, and beverage par levels — producing tiered alerts and a prioritized action list.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: true
+---
+
+# Inventory Health Check
+
+You analyze {{businessName}} inventory with context-specific logic for an axe throwing venue. Axes are not consumed — they are maintained. Targets are consumed over time. Beverages run on standard par logic. Safety equipment requires its own threshold. This skill handles all three models and produces a clear, tiered alert report.
+
+## When to Trigger
+
+Invoke this skill when someone asks:
+
+- "Check inventory"
+- "What needs restocking?"
+- "Which axes are due for sharpening?"
+- "Target board status"
+- "What are we running low on?"
+- "Inventory alert"
+- Also runs automatically as section 4 of the Staff Briefing skill
+
+## Inventory Categories at {{businessName}}
+
+| Category ID | What It Covers | Tracking Model |
+|---|---|---|
+| `hatchet` | Throwing hatchets — numbered by ID | Maintenance cycle (sharpen every 50 sessions) |
+| `big-axe` | Big axes — numbered by ID | Maintenance cycle (sharpen every 30 sessions) |
+| `targets` | Target boards (2×10 pine) and mounting hardware | Consumption cycle (flip at ~200 sessions, replace at ~400) |
+| `lane-supplies` | Chalk, markers, scorecards, tape, lane barriers | Standard consumption |
+| `safety` | Safety barriers, floor mats, warning signs, first aid | Count + condition check |
+| `beverages` | Draft beer kegs, canned beverages, wine, non-alcoholic | Standard par level |
+| `retail` | Branded merchandise, gift items | Standard par level |
+| `maintenance` | Sharpening stones, axe oil, handle wrap, wood filler | Standard consumption |
+
+## Step 1: Pull Current Stock
+
+```typescript
+const inventoryItems = await brain.find({
+  type: 'Thing',
+  where: [
+    { field: 'metadata.entityType', value: 'inventory-item' },
+    { field: 'metadata.locationId', value: LOCATION_ID      }
+  ]
+});
+// Each item: { metadata: { name, category, quantity, reorderThreshold, costInCents,
+//              lastMaintenanceDate, sessionsSinceMaintenance, locationId } }
+```
+
+## Step 2: Axe Maintenance Logic
+
+Axes are tracked individually by ID. They are not "consumed" — they rotate through a maintenance cycle.
+
+```typescript
+const hatchets = inventoryItems.filter(i => i.metadata.category === 'hatchet');
+const bigAxes  = inventoryItems.filter(i => i.metadata.category === 'big-axe');
+
+// Maintenance thresholds (from axe-expertise skill)
+const HATCHET_SHARPEN_INTERVAL   = 50;  // sessions
+const BIG_AXE_SHARPEN_INTERVAL   = 30;  // sessions
+const HATCHET_FULL_SERVICE       = 200; // sessions
+const BIG_AXE_FULL_SERVICE       = 150; // sessions
+
+// Flag axes where sessionsSinceMaintenance >= threshold
+const hatchetsDue = hatchets.filter(
+  i => (i.metadata.sessionsSinceMaintenance ?? 0) >= HATCHET_SHARPEN_INTERVAL
+);
+const bigAxesDue = bigAxes.filter(
+  i => (i.metadata.sessionsSinceMaintenance ?? 0) >= BIG_AXE_SHARPEN_INTERVAL
+);
+const hatchetsFullService = hatchets.filter(
+  i => (i.metadata.sessionsSinceMaintenance ?? 0) >= HATCHET_FULL_SERVICE
+);
+```
+
+Axes flagged for maintenance should be pulled from rotation before the first session of the day, not after. Safety equipment past its maintenance threshold is a 🔴 CRITICAL alert.
+
+## Step 3: Target Board Logic
+
+Target boards are consumed over time through repeated axe impacts.
+
+```typescript
+const targetBoards = inventoryItems.filter(i => i.metadata.category === 'targets');
+
+// Estimate based on session count metadata on each board item
+const BOARD_FLIP_THRESHOLD    = 200; // sessions — flip to reverse face
+const BOARD_REPLACE_THRESHOLD = 400; // sessions — replace entirely
+
+const boardsToFlip    = targetBoards.filter(b => b.metadata.sessionCount >= BOARD_FLIP_THRESHOLD
+                                               && b.metadata.sessionCount < BOARD_REPLACE_THRESHOLD);
+const boardsToReplace = targetBoards.filter(b => b.metadata.sessionCount >= BOARD_REPLACE_THRESHOLD);
+```
+
+If session count is not tracked per board, check `metadata.lastRotationDate` and estimate based on average sessions per week. Alert if any board has not been rotated in more than 4 weeks (assuming any operational venue runs 50+ sessions per week).
+
+## Step 4: Standard Consumption Rate (Beverages, Lane Supplies, Retail)
+
+```typescript
+brain.defineAggregate('weeklyConsumptionByCategory', {
+  source: {
+    type: 'Measurement',
+    where: [
+      { field: 'metadata.entityType', value: 'transaction' },
+      { field: 'metadata.type',       value: 'expense'     }
+    ]
+  },
+  groupBy: [
+    { field: 'metadata.category' },
+    { field: 'metadata.date', window: 'week' }
+  ],
+  metrics: {
+    weeklyCount: { op: 'COUNT'                                 },
+    weeklySpend: { op: 'SUM', field: 'metadata.amountInCents' },
+    avgPerWeek:  { op: 'AVG', field: 'metadata.amountInCents' }
+  }
+});
+
+const consumption = await brain.find({
+  aggregate: 'weeklyConsumptionByCategory',
+  where: [
+    { field: 'metadata.locationId', value: LOCATION_ID },
+    { field: 'metadata.date', value: { gte: FOUR_WEEKS_AGO, lte: TODAY } }
+  ]
+});
+```
+
+## Alert Tiers
+
+| Tier | Condition | Action Required |
+|---|---|---|
+| 🔴 CRITICAL | Safety equipment below minimum count; axes past full service interval; boards past replace threshold; beverages at zero | Immediate action before opening |
+| 🟡 LOW | Axes due for sharpening (not full service); boards approaching flip threshold; beverages below par; lane supplies running low | Action this week |
+| 🟢 OK | All within safe thresholds | No action needed |
+
+## Output Structure
+
+---
+
+### 1. Status Summary
+
+```
+Inventory Health — {{locationName}}
+As of: [today's date]
+─────────────────────────────────────────
+🔴 CRITICAL:   1 item (action before opening)
+🟡 LOW:        6 items (order or service this week)
+🟢 OK:        28 items
+```
+
+### 2. Critical Items
+
+Items requiring immediate action before any session begins:
+
+| Item | Category | Issue | Action Required |
+|---|---|---|---|
+| Safety Mat — Lane 3 | safety | Torn edge — trip hazard | Replace before opening |
+| Big Axe #4 | big-axe | 148 sessions — past full service interval | Pull from rotation immediately |
+
+Safety category items are always CRITICAL regardless of days-until-empty logic.
+
+### 3. Axe Maintenance Queue
+
+List all axes due for sharpening (not yet critical) in order of urgency:
+
+| Axe ID | Type | Sessions Since Last Maintenance | Threshold | Status |
+|---|---|---|---|---|
+| Hatchet #7 | Hatchet | 52 | 50 | 🟡 Due for sharpening |
+| Hatchet #12 | Hatchet | 56 | 50 | 🟡 Due for sharpening |
+| Big Axe #2 | Big Axe | 28 | 30 | 🟡 Due next week |
+
+**Sharpening action**: Pull from rotation before the day's sessions begin. Return after sharpening is complete. Do not sharpen in-session — remove and replace with a spare.
+
+If no axes are due: "All axes within maintenance thresholds."
+
+### 4. Target Board Rotation Schedule
+
+| Board / Lane | Sessions Used | Flip At | Replace At | Status | Action |
+|---|---|---|---|---|---|
+| Board — Lane 2 | 198 | 200 | 400 | 🟡 Flip this week | Schedule flip before next private party |
+| Board — Lane 6 | 412 | 200 | 400 | 🔴 Replace immediately | Order replacement board |
+| Board — Lane 1 | 87 | 200 | 400 | 🟢 OK | None |
+
+If no boards need attention: "All target boards are within rotation thresholds."
+
+### 5. Beverage Par Status
+
+| Item | Category | In Stock | Par Level | Status |
+|---|---|---|---|---|
+| Pale Ale (1/6 bbl) | beverages | 1 keg | 3 kegs | 🟡 LOW — order this week |
+| IPA (1/2 bbl) | beverages | 2 kegs | 2 kegs | 🟢 OK |
+| Non-Alcoholic Cider | beverages | 4 cans | 24 cans | 🔴 CRITICAL |
+
+### 6. Weekly Consumption Rates (Last 4 Weeks)
+
+| Category | Avg Weekly Spend | Trend |
+|---|---|---|
+| beverages | $680 / week | +12% vs prior 4 wks |
+| targets | $140 / week | stable |
+| lane-supplies | $48 / week | stable |
+| maintenance | $62 / week | +5% vs prior 4 wks |
+| retail | $110 / week | -8% vs prior 4 wks |
+
+A rising beverage trend with low stock is a compounding risk — flag it.
+
+### 7. Recommended Action List
+
+A consolidated prioritized list of all required actions:
+
+| Priority | Item | Action | Urgency |
+|---|---|---|---|
+| 1 | Safety Mat — Lane 3 | Replace torn mat before opening | 🔴 NOW |
+| 2 | Non-Alcoholic Cider | Reorder — stock at critical level | 🔴 TODAY |
+| 3 | Hatchet #7, #12 | Pull from rotation; sharpen and return | 🟡 THIS SESSION |
+| 4 | Board — Lane 6 | Order replacement 2×10 pine board | 🟡 THIS WEEK |
+| 5 | Board — Lane 2 | Schedule flip — before next private party | 🟡 THIS WEEK |
+| 6 | Pale Ale keg | Order 2 additional 1/6 bbl kegs | 🟡 THIS WEEK |
+
+Suggested reorder quantities for consumable items: `(reorderThreshold × 2) − currentQuantity`, rounded up to nearest supplier unit.
+
+### 8. Axe Count Check
+
+Confirm operational readiness:
+
+```
+Axe Availability Summary
+  Total Hatchets: [N]  Available: [N-flagged]  In Maintenance Queue: [N]
+  Total Big Axes: [N]  Available: [N-flagged]  In Maintenance Queue: [N]
+
+Session Readiness: [status — e.g., "Sufficient for all scheduled sessions today" or "Warning: if both flagged hatchets are pulled, open throw capacity is reduced by 2 lanes"]
+```

package/kits/axe-house/skills/league-manager/SKILL.md

@@ -0,0 +1,264 @@
+---
+id: league-manager
+name: League Manager
+description: Manages axe throwing league operations — season scheduling, weekly standings calculation, player stat leaderboards, and playoff bracket generation — using session attribute data stored on League Night bookings.
+type: invocable
+version: 1.0.0
+requiresVision: false
+requiresData: true
+---
+
+# League Manager
+
+You manage axe throwing league operations for {{businessName}}. When triggered, you pull league session data from Brainy, compute standings and player stats using WATL-style scoring logic, and produce formatted reports for staff, coaches, and league participants.
+
+## When to Trigger
+
+Invoke this skill when someone asks:
+
+- "League standings"
+- "Schedule for this season"
+- "Playoff bracket"
+- "How's our league doing?"
+- "Player leaderboard"
+- "Set up the new season schedule"
+- "Which teams are in playoffs?"
+- Any league management, standings, or scheduling request
+
+## League Data Model
+
+League data is stored across three entity types in Brainy:
+
+### 1. Season Document
+
+```typescript
+// Each league season is stored as a Document entity
+const season = await brain.find({
+  type: 'Document',
+  where: [
+    { field: 'metadata.entityType', value: 'league-season'  },
+    { field: 'metadata.locationId', value: LOCATION_ID      },
+    { field: 'metadata.status',     value: 'active'         }  // or 'completed'
+  ]
+});
+// season.metadata: { seasonName, startDate, endDate, format, weekCount, teamCount }
+// season.data: { teams: [{ teamName, playerIds: string[] }] }
+```
+
+### 2. Weekly Match Results
+
+Match results are stored as session attributes on League Night booking records:
+
+```typescript
+const leagueBookings = await brain.find({
+  type: 'Event',
+  where: [
+    { field: 'metadata.entityType',    value: 'booking'      },
+    { field: 'metadata.experienceSlug', value: 'league-night' },
+    { field: 'metadata.locationId',    value: LOCATION_ID    },
+    { field: 'metadata.date',          value: { gte: season.metadata.startDate,
+                                                lte: season.metadata.endDate } }
+  ],
+  orderBy: 'metadata.date',
+  order:   'asc'
+});
+
+// Each booking.data.sessionAttributes contains:
+// {
+//   laneNumber: string,
+//   teamName: string,           // home team for this lane
+//   leagueSeason: string,       // "Season 3"
+//   throwStyle: string,         // 'hatchet' | 'big-axe'
+//   weekNumber: number,
+//   opponentTeam: string,
+//   teamScore: number,          // total points this team scored this match
+//   opponentScore: number,      // total points opponent scored
+//   playerScores: [{ guestName, setScores: number[], totalScore: number, clutchesCalled: number, clutchesHit: number }]
+// }
+```
+
+### 3. Standing Calculation Logic
+
+```typescript
+brain.defineAggregate('leagueStandingsByTeam', {
+  source: {
+    type: 'Event',
+    where: [
+      { field: 'metadata.entityType',    value: 'booking'      },
+      { field: 'metadata.experienceSlug', value: 'league-night' }
+    ]
+  },
+  groupBy: [
+    { field: 'metadata.teamName' }
+  ],
+  metrics: {
+    matchesPlayed: { op: 'COUNT'                                       },
+    totalPoints:   { op: 'SUM', field: 'metadata.teamScore'            },
+    totalOpponent: { op: 'SUM', field: 'metadata.opponentScore'        },
+    avgScore:      { op: 'AVG', field: 'metadata.teamScore'            },
+    maxScore:      { op: 'MAX', field: 'metadata.teamScore'            }
+  }
+});
+```
+
+Wins and losses are computed client-side: for each match record, `teamScore > opponentScore` → win, else loss. Point differential = `SUM(teamScore) - SUM(opponentScore)` across all matches.
+
+**Standings sort order**: wins (desc) → point differential (desc) → total points (desc).
+
+## WATL Scoring Reminder
+
+Every match is 5 throws per player per set, best of 3 sets. Team score = sum of all player scores across all 5 throws in the winning set(s).
+
+Clutch scoring: if a player calls "clutch" before a throw and hits the clutch zone, score 8. If they call it and miss, score 0. If they don't call it, score based on standard ring value (typically 1 for the clutch zone area).
+
+## Output Structure
+
+---
+
+### 1. Season Overview
+
+```
+League — {{locationName}}
+Season: [seasonName]
+Week [N] of [weekCount] | [N] weeks remaining
+Teams: [teamCount] | Format: WATL Head-to-Head, Best of 3
+```
+
+### 2. Current Standings
+
+Full standings table sorted by wins, then point differential, then total points:
+
+| Rank | Team | W | L | Pts For | Pts Against | Diff | Last 3 | Streak |
+|---|---|---|---|---|---|---|---|---|
+| 1 | Iron Shoulders | 7 | 1 | 1,842 | 1,604 | +238 | W-W-W | W3 |
+| 2 | Axe Factors | 6 | 2 | 1,798 | 1,642 | +156 | W-L-W | W1 |
+| 3 | Hatchet Heroes | 5 | 3 | 1,756 | 1,700 | +56 | L-W-W | W2 |
+| 4 | Target Practice | 5 | 3 | 1,710 | 1,724 | -14 | W-W-L | L1 |
+| 5 | The Bullseye Club | 4 | 4 | 1,682 | 1,718 | -36 | L-L-W | W1 |
+| 6 | Stick & Stones | 3 | 5 | 1,640 | 1,780 | -140 | L-W-L | L1 |
+| 7 | No Clutch | 2 | 6 | 1,594 | 1,842 | -248 | L-L-W | W1 |
+| 8 | Wild Hatchets | 0 | 8 | 1,488 | 1,920 | -432 | L-L-L | L8 |
+
+Add a separator line after the playoff cutoff (top 8 advance by default, or configurable per season).
+
+### 3. This Week's Match Results
+
+For the most recent completed week:
+
+```
+Week [N] Results — [Date]
+──────────────────────────
+Lane 1: Iron Shoulders  def.  No Clutch        (442 – 384)
+Lane 2: Axe Factors     def.  Wild Hatchets     (408 – 362)
+Lane 3: Hatchet Heroes  def.  Stick & Stones    (398 – 376)
+Lane 4: Target Practice def.  Bullseye Club     (416 – 398)
+```
+
+### 4. Individual Player Leaderboard
+
+Top 10 players by average score per set this season:
+
+| Rank | Player | Team | Avg Score/Set | Total Throws | Clutches Hit | Clutch % |
+|---|---|---|---|---|---|---|
+| 1 | Marcus T. | Iron Shoulders | 28.4 | 200 | 6 | 60% |
+| 2 | Jordan K. | Axe Factors | 27.8 | 200 | 4 | 44% |
+| 3 | Alex R. | Hatchet Heroes | 26.2 | 200 | 8 | 72% |
+
+Privacy: display first name + last initial only.
+
+Clutch % = clutches hit / clutches called. A player who never calls clutch will show `0 / 0` — display as "—" rather than 0%.
+
+### 5. Notable Stats This Season
+
+```
+Season Records
+  Highest single-match team score: Iron Shoulders, 502 pts (Week 3 vs Wild Hatchets)
+  Most clutches called in a match: Alex R., 4 called (Hatchet Heroes, Week 6)
+  Most clutches hit in a match: Alex R., 3 hit (Hatchet Heroes, Week 6)
+  Longest winning streak: Iron Shoulders, 5 consecutive wins (Weeks 2–6)
+  Highest-scoring individual set: Marcus T., 38 pts (Week 4)
+```
+
+---
+
+## Playoff Bracket Generator
+
+When the regular season is complete (or on request), generate the playoff bracket.
+
+**Top 8 teams by final standings advance.** Single-elimination bracket, seeded by final standings position.
+
+```
+Playoff Bracket — {{businessName}} League [seasonName]
+══════════════════════════════════════════════════
+
+QUARTERFINALS (Week [N])
+  QF1: [1] Iron Shoulders    vs. [8] Wild Hatchets       Lane 1, [time]
+  QF2: [2] Axe Factors       vs. [7] No Clutch           Lane 2, [time]
+  QF3: [3] Hatchet Heroes    vs. [6] Stick & Stones      Lane 3, [time]
+  QF4: [4] Target Practice   vs. [5] Bullseye Club       Lane 4, [time]
+
+SEMIFINALS (Week [N+1])
+  SF1: Winner QF1 vs. Winner QF4                         Lane 1, [time]
+  SF2: Winner QF2 vs. Winner QF3                         Lane 2, [time]
+
+CHAMPIONSHIP (Week [N+2])
+  Champion Match: Winner SF1 vs. Winner SF2              Lane 1, [time]
+  Third Place:    Loser SF1 vs. Loser SF2                Lane 2, [time]
+```
+
+For each bracket position, show the seed number and team name. As playoff results come in, update the bracket with actual results and advance teams appropriately.
+
+---
+
+## Season Schedule Generator
+
+For new season setup, generate a round-robin schedule ensuring each team plays each other once before playoffs.
+
+**Input required**:
+- Number of teams (even number required for clean round-robin; if odd, add a "bye" team)
+- Number of weeks in regular season
+- Nights per week (typically 1)
+- Available lanes ({{laneCount}})
+
+**Algorithm**: Standard round-robin rotation. Fix Team 1's position, rotate all other teams around it. Each rotation produces one week of matchups.
+
+**Output format**:
+
+```
+Season Schedule — [seasonName]
+[N] teams | [N]-week regular season | Playoffs: Weeks [N+1]–[N+3]
+────────────────────────────────────────────────────────────
+
+Week 1 — [Date]
+  Lane 1: Iron Shoulders vs. Wild Hatchets
+  Lane 2: Axe Factors vs. No Clutch
+  Lane 3: Hatchet Heroes vs. Stick & Stones
+  Lane 4: Target Practice vs. Bullseye Club
+
+Week 2 — [Date]
+  Lane 1: [matchup]
+  ...
+```
+
+If the number of teams exceeds `floor({{laneCount}} / 1)` simultaneous matches, split the evening into two time blocks (e.g., 6:00 PM and 8:00 PM) to accommodate all matches.
+
+---
+
+## League Registration Output
+
+When helping set up a new season, produce a registration summary suitable for sharing with prospective teams:
+
+```
+{{businessName}} Axe Throwing League — [seasonName]
+────────────────────────────────────────────────────
+Format: WATL Head-to-Head, Best of 3 Sets
+Teams: 4–8 players per team
+Season Length: 8 weeks + playoffs
+Night: {{leagueNights}} evenings
+Cost: $20/player/night (season registration)
+Registration Opens: [date]
+Season Starts: [date]
+
+How to Register: Email {{email}} or visit [booking link]
+Spots are limited — last season filled in [N] days.
+```