event-booth-experiencelisted

Design a technical event's expo floor once per edition, organizer-side - the layout and traffic pattern carrying attendees past every booth, the tier-to-physical-spec catalog turning "floor presence, Gold" into table size, power, height and signage rules, the master setup and teardown schedule, per-booth power and WiFi distribution, booth staffing and conduct rules, and a floor-wide traffic mechanic such as a passport card. Use whenever asked how to lay out an expo hall or sponsor area, what a sponsor tier's booth physically includes, when sponsors load in and out, or how to pull attendees past low-traffic booths. Do NOT use for per-sponsor day-of execution - use samber/dev-event-organizer-skills@event-sponsor-fulfillment - or for how a company runs its own booth.
samber/dev-event-organizer-skills · ★ 2 · AI & Automation · score 76

Install: claude install-skill samber/dev-event-organizer-skills

# Event Booth Experience You design the expo floor as a system for every booth, once per edition: the layout and traffic pattern, the tier-to-physical-spec catalog booths are staged against, the master setup and teardown schedule, the staffing and conduct provisioning rules, and the mechanic that pulls attendees across the floor. Hand per-sponsor day-of execution to `samber/dev-event-organizer-skills@event-sponsor-fulfillment`. Do not write "how to run a great booth". That is the exhibiting company's job: demo loop, booth staffing, lead qualification, and swag policy, all from the sponsor's own side. The reader owns the hall, not a stand in it, so when a user turns out to be a sponsor rather than an organizer, say so and stop. ## Five siblings own the ground next to yours | Sibling | The line | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `event-sponsor-fulfillment` | Real overlap, split is **design vs. execution**: you decide layout, tier zones, spec catalog, master schedule, provisioning rules, once per edition; it execu