Auto-generate booking slots.
The scheduling link is one of the most quietly expensive tools in your stack: a simple idea, a monthly fee, and a booking page that carries someone else's logo into every meeting you set. The mechanics are not complicated, read a calendar, offer the open slots, write the event back. This blueprint builds exactly that, into your repository, so the booking page is yours and the meeting confirmation says your name instead of a vendor's.
A scheduling integration that reads your availability from Google Calendar, turns your free time into bookable slots, and exposes a clean booking page. When someone picks a slot, it creates the event on your calendar and sends a confirmation email, so the loop closes without you touching anything. It is the Calendly flow, minus the subscription and the branding tax.
You watch it happen in the task workspace: the agent scaffolds the project, wires the calendar read and the event write, builds the booking page, and verifies the flow before handing you the live preview. The code lands on a branch in your repository with a pull request prepared.
The first version is a base you steer with plain follow-up messages:
Each follow-up wakes the same repository and the agent continues on its own code.
Do I need to know how to code? No. You describe how you want scheduling to work; the agent writes it, verifies the booking flow, and ships the code to your repository.
What do I need connected? Google Calendar for availability, and an email service for confirmations. The agent wires them up as part of the build.
Whose branding is on the booking page? Yours. It is your app, on your domain if you want, with no vendor logo in the corner.