Clockwise

Build me a focused booking links and calendar automation workflow for the personal core of Clockwise. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend. Model hosts, availability rules, busy intervals, bookings, and cancellation events; keep stable source IDs and timestamps.
- Paid product context: Rearrange flexible holds around fixed meetings for one user's calendar. Build only this DIY scope: Read one user's calendar, rearrange flexible holds around fixed meetings, create conflict-safe bookings, and send confirmations and reminders.
- Implement one account with configurable working hours, buffers, minimum notice, and booking horizon.
- Connect Google Calendar using OAuth and store refresh tokens encrypted at rest.
- Send confirmation, cancellation, and reminder email with signed management links. Add an admin booking list, event-type editor, audit log, and calendar reconnect flow.
- Use a local web page with input, progress, review, and export views. Required input or access: Google Calendar OAuth credentials; public deploy target. Keep credentials in .env.
- Recovery: Send confirmation, cancellation, and reminder email with signed management links.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A daylight-saving transition cannot create an invalid local time; concurrent reservations must not claim the same slot.
- Out of scope: organization-wide optimization, calendar graph, team adoption, and conflict safety; multiple calendar providers. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Clockwise

## Project scope
Read one user's calendar, rearrange flexible holds around fixed meetings, create conflict-safe bookings, and send confirmations and reminders.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Clockwise, rearrange flexible holds around fixed meetings for one user's calendar. The hard boundary is organization-wide optimization, calendar graph, team adoption, and conflict safety, plus calendar integrations and reliability.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Google Calendar OAuth credentials
- PostgreSQL
- public deploy target
- Resend API key
- domain with HTTPS

## Stack and architecture
- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend.
- Model hosts, availability rules, busy intervals, bookings, and cancellation events; keep stable source IDs and timestamps.
- Interface for this booking links and calendar automation workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Send confirmation, cancellation, and reminder email with signed management links.
- Keep API keys and OAuth secrets in .env; redact them from logs, generated files, and error responses.
- State the practical limit: organization-wide optimization, calendar graph, team adoption, and conflict safety.

## Agent implementation rules
- Project rule, data: Model hosts, availability rules, busy intervals, bookings, and cancellation events; keep stable source IDs and timestamps.
- Project rule, behavior: Implement one account with configurable working hours, buffers, minimum notice, and booking horizon.
- Project rule, recovery: Send confirmation, cancellation, and reminder email with signed management links.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this booking links and calendar automation operation with sample or user-owned data: Implement one account with configurable working hours, buffers, minimum notice, and booking horizon.
- Show a concrete result or export: Add an admin booking list, event-type editor, audit log, and calendar reconnect flow.
- State the practical limit: organization-wide optimization, calendar graph, team adoption, and conflict safety.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend. Model hosts, availability rules, busy intervals, bookings, and cancellation events; keep stable source IDs and timestamps.
2. Phase 2, implement: Implement one account with configurable working hours, buffers, minimum notice, and booking horizon.
3. Phase 3, implement: Connect Google Calendar using OAuth and store refresh tokens encrypted at rest.
4. Phase 4, review and output: Send confirmation, cancellation, and reminder email with signed management links. Add an admin booking list, event-type editor, audit log, and calendar reconnect flow.
5. Phase 5, recovery and acceptance: Send confirmation, cancellation, and reminder email with signed management links. Verify this invariant with a saved fixture: A daylight-saving transition cannot create an invalid local time; concurrent reservations must not claim the same slot. State the practical limit: organization-wide optimization, calendar graph, team adoption, and conflict safety.

## Paid-product capabilities outside this build
- organization-wide optimization, calendar graph, team adoption, and conflict safety
- multiple calendar providers
- team routing and round-robin
- payments
- timezone edge-case maturity

## Implementation prompt
Build me a focused booking links and calendar automation workflow for the personal core of Clockwise. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend. Model hosts, availability rules, busy intervals, bookings, and cancellation events; keep stable source IDs and timestamps.
- Paid product context: Rearrange flexible holds around fixed meetings for one user's calendar. Build only this DIY scope: Read one user's calendar, rearrange flexible holds around fixed meetings, create conflict-safe bookings, and send confirmations and reminders.
- Implement one account with configurable working hours, buffers, minimum notice, and booking horizon.
- Connect Google Calendar using OAuth and store refresh tokens encrypted at rest.
- Send confirmation, cancellation, and reminder email with signed management links. Add an admin booking list, event-type editor, audit log, and calendar reconnect flow.
- Use a local web page with input, progress, review, and export views. Required input or access: Google Calendar OAuth credentials; public deploy target. Keep credentials in .env.
- Recovery: Send confirmation, cancellation, and reminder email with signed management links.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A daylight-saving transition cannot create an invalid local time; concurrent reservations must not claim the same slot.
- Out of scope: organization-wide optimization, calendar graph, team adoption, and conflict safety; multiple calendar providers. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.