What problem does it solve?
When working on the Cambridge Beer Festival app, you often have to reverse-engineer the meaning of domain-specific fields, data shape quirks, and project jargon from scattered code and comments, which wastes time and leads to incorrect assumptions about how the app is supposed to work.
Core Features & Use Cases
- Domain Context: Explains the real-world Cambridge Beer Festival operations that drive key app design decisions, like burst usage patterns and patchy venue network.
- Drink & Data Reference: Defines drink domain vocabulary (categories, dispense methods, ABV, allergens, availability status), explains why data feed fields use union types, and documents festival registry semantics.
- API & Jargon Guide: Maps the three distinct API surfaces (static feeds, v1alpha Review API, proto CatalogService), and defines project-specific terms like SWR, D1, workerd, and CalVer.
- Use Case: If you are debugging why a drink's availability status is showing as "unknown" even though the volunteer entered "arrived", or need to understand the difference between the static feeds and the proto API contract, this skill provides the context you need without digging through incident records or scattered docs.
Quick Start
Use the reference skill to look up the meaning of the 'dispense' field in the drink model when you are confused why a cider is listed as being served via "cider tub" instead of the default cask method.
