Appointment booking
Let customers select a service, time, and provider and receive confirmation.
Customize the recipe
Prompt preview
# Appointment booking Let customers select a service, time, and provider and receive confirmation. ## Deliverable A booking flow with test availability and concurrent booking protection. ## 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. - [shadcn/ui Skill](https://ui.shadcn.com/docs/skills) (Skill) — Inspect the project's component registry and assemble accessible UI primitives. Project with compatible React and styling configuration. Follow the skill's agent-specific setup. Fallback: Reuse established controls in the project, or start with semantic native controls and test keyboard and error states. - [React Hook Form](https://github.com/react-hook-form/react-hook-form) (Repository) — Implement labeled forms with validation, accessible errors and preserved inputs. - [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. Define services, duration, timezones and availability. Reserve a slot atomically, display the customer's local time, and provide confirmation and an appropriate cancellation path. 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 - [ ] Two sessions requesting one slot create one booking. - [ ] Confirmation shows the correct time and timezone, including a DST fixture. - [ ] 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.
shadcn/ui Skill
Inspect the project's component registry and assemble accessible UI primitives.
Project with compatible React and styling configuration. Follow the skill's agent-specific setup.
License · MIT
React Hook Form
Implement labeled forms with validation, accessible errors and preserved inputs.
License · MIT
Supabase
Consider PostgreSQL persistence, authentication and row-level permissions for shared applications.
Use a local stack or configure an authorized project for integration checks.
License · Apache-2.0
Playwright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLI