eventhub-domain

Provides EventHub platform domain knowledge including business rules, API endpoints, data models, and UI selectors.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/marcocelone/demo-python-ai-agent-project --skill eventhub-domain-marcocelone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eventhub-domain
Source: https://github.com/marcocelone/demo-python-ai-agent-project/tree/main/.claude/skills/eventhub-domain
Command: npx skills add https://github.com/marcocelone/demo-python-ai-agent-project --skill eventhub-domain-marcocelone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing tests, reviewing code, or answering questions about the EventHub ticket booking platform requires deep knowledge of its business rules, API contracts, data models, and UI selectors, which are otherwise scattered and hard to recall. ## Core Features & Use Cases - Business Rules Reference: Documents sandbox isolation, FIFO pruning limits (6 events, 9 bookings), booking reference format, refund eligibility logic, and seat availability computation. - API & Error Reference: Lists all auth, events, and bookings endpoints with request/response shapes and HTTP error codes for scenarios like cross-user access and insufficient seats. - UI Selectors & User Flows: Provides Playwright selectors for every page plus end-to-end user flows and seeded test data for test automation. - Use Case: When writing a pytest-playwright test for booking cancellation, load this Skill to get the exact selectors, the clean_session fixture behavior, and the expected seat-restoration business rule. ## Quick Start Ask the AI to explain EventHub's booking reference format and write a test validating it using the eventhub-domain knowledge.

Frequently Asked Questions about eventhub-domain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write E2E tests for the EventHub booking flow?▼

Use pytest with pytest-playwright against the staging site, following the page object model pattern with fixtures from conftest.py. The clean_session fixture logs in a test user, clears prior bookings, and yields ready-to-use page objects.

What are the EventHub sandbox limits for events and bookings?▼

Each user can have at most 6 user-created events and 9 bookings. When the limit is reached, the oldest item is automatically deleted via FIFO replacement, and static seeded events do not count toward the event limit.

How is the EventHub booking reference format generated?▼

The booking reference follows the pattern [FIRST_LETTER]-[6_RANDOM_ALPHANUMERIC], where the first letter comes from the event title in uppercase. For example, booking 'Tech Summit' produces a reference like T-A3B2C1, with collision retry ensuring uniqueness.

What error codes does the EventHub API return for common failures?▼

Invalid login returns 401, duplicate email registration returns 409, cross-user booking access returns 403, and insufficient seats or past event dates return 400. Editing static seeded events also returns 403.

Which UI selectors should I use for EventHub Playwright tests?▼

Key selectors include getByTestId('event-card') for event cards, getByTestId('book-now-btn') for booking links, #customer-email for the email field, and .confirm-booking-btn for submission. The full selector map covers login, events, booking, and admin pages.