Flows workflow logoFlows
Booking System
0/6 steps0%

Step 1 of 6

Define the booking model

Slots, durations, and conflict rules must be explicit before building UI.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Define the booking spec. Specify: what is being booked (service/resource) and its schedulable hours; slot duration and how slots are computed for a given date; the booking record (user, resource, start/end datetime, status); the conflict rule (a slot with an active booking is unavailable); and cancellation policy (cancel frees the slot). State that conflicts are enforced at the database/backend level.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A concrete slot and conflict model ready to implement.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent