Event ticketing

Guide attendees from an event detail page to a valid test ticket.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Event ticketing

Guide attendees from an event detail page to a valid test ticket.

## Deliverable
A seeded event page, sandbox reservation, and attendee ticket view.

## Stack and visual direction
- Recommended starting stack: Next.js and TypeScript. Use server-side validation and sandbox integrations for payment or booking when needed.
- Minimalism: Use deliberate spacing, a compact palette and a clear typographic hierarchy. Retain the labels, feedback and affordances people need to act. Apply this direction to the website.

- Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [Frontend Design](https://github.com/anthropics/skills/tree/main/skills/frontend-design) (Skill) — Plan distinct typography, composition and interaction details before building UI.
  Fallback: Write a short plan for hierarchy, palette, spacing and interaction states, then review the actual screens against it.
- [Stripe Payment Samples](https://github.com/stripe-samples/accept-a-payment) (Repository) — Reference sandbox checkout and confirmation flows with provider-hosted payment collection.
  Use test-mode credentials and test payment fixtures.
- [Supabase](https://github.com/supabase/supabase) (Repository) — Consider PostgreSQL persistence, authentication and row-level permissions for shared applications.
  Use a local stack or configure an authorized project for integration checks.

## Workflow
1. Show event details, access information, ticket tiers and capacity. Reserve quantities for test checkout and issue a unique ticket only after confirmation.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] Capacity cannot be exceeded when multiple test buyers act together.
- [ ] A confirmed ticket can be reopened and shows the matching event and tier.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Check mobile navigation and every key page at narrow and desktop widths. Remove horizontal document overflow and optimize images with stable dimensions and appropriate alternatives.
- [ ] Check working buttons, links and footer destinations, clickable logo and contact paths where applicable, page titles, descriptions, favicon, a useful 404 and the current copyright year. Remove placeholder text and unused navigation.
- [ ] Verify forms with both valid and invalid submissions and useful success and error feedback.

Recipe resources

Source, setup, and compatibility details.