What problem does it solve? Technical events often feel generic or internally inconsistent: the website is playful, the emails corporate, the MC solemn, and the swag contradicts the stated values. This Skill turns an event's stated purpose into one fixed cultural register and audits every touchpoint against it, so the on-site experience matches what the event claims to stand for. ## Core Features & Use Cases - Register definition: Builds 3-5 "X, but never Y" voice attributes with do's, don'ts, a banned-register list, and an anti-midpoint check that rejects hedged tones like "welcoming but professional, fun but serious". - Tone-modulation matrix: Produces a moments-by-touchpoints matrix (opening, incident, closing across MC script, signage, email, swag) so one identity modulates consistently instead of being redesigned per channel. - Ritual, hosting, and swag design: Scopes ceremonies and traditions to a ranked investment ladder (pop-up rules through self-built ritual worlds), selects a hosting model with a one-page host brief including a pre-written incident script, and sets a swag posture with inclusive sizing rules. - Use Case: A community conference whose site says "hacker spirit" but runs a sponsor-reel opening, a hired MC, and polo-shirt swag gets a cell-by-cell audit naming each contradiction, each fixed or declared a deliberate exception. ## Quick Start Ask the assistant to design or audit your event's cultural identity, for example: "Audit our developer conference - our site says hacker spirit but we have sponsored keynotes and a professional MC."
