Timed tool access that clocks out when the contract does

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Build the weekend MVP of "Tempkey": give a contractor access to a Trello board with an end date, warn two days before, and remove them automatically when the date arrives. One tool this weekend, because it is the one with an open API for adding and removing members.
   
   Stack: Next.js (App Router, TypeScript), Tailwind, Supabase (Postgres, Row Level Security, Auth with email magic link), the Trello REST API with a key and a token you paste in, Resend for the warning emails. A cron route runs the warn and revoke steps (hourly on a plan that allows it, otherwise daily to start). Deploy on Vercel.
   
   Tables (Row Level Security on, each admin reads only their own rows):
   - connections(id, user_id, provider, token_encrypted, status)
   - grants(id, user_id, contractor_name, contractor_email, board_ref, role, starts_at, ends_at, status, created_by) status is pending, active, warned, revoked or failed
   - notices(id, grant_id, kind, sent_at) kind is warning or revoked; unique on grant_id and kind
   - audit_events(id, grant_id, user_id, action, provider, payload jsonb, created_at)
   
   Screens: /login, /connect (the Trello key and token), /grants (who is in, days left, filter by status), /grants/new, /audit (events and a CSV export).
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), RESEND_API_KEY, CRON_SECRET, TOKEN_ENCRYPTION_KEY.
   
   Do not build: billing or plans, Slack, Google Workspace or Notion connections, SCIM, Inngest or a queue, session recording, an enterprise login.
   Done when: npm run dev starts, you can sign in, and the four tables exist with Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves Tempkey: access that ends on the day it was meant to, with a warning first and a record of every step.
   1. The grant form takes a contractor's name and email, a Trello board and a role, and an end date or a 30, 60 or 90 day preset. On submit, add the person to the board through the Trello API, save the grant as active and write an audit event.
   2. A cron route (protected by CRON_SECRET) finds active grants whose end is within 48 hours and sends the warning to the contractor and the owner through Resend. Record it in notices so it is sent once, and set the grant to warned.
   3. The same route finds grants past their end date and removes the member from the board through the Trello API. On success set revoked and send a notice. On failure keep the status failed, retry up to 3 times with backoff on later runs, then email the owner. Never fail silently.
   4. If the stored token stops working, show a banner on the dashboard and email the owner.
   5. The grants page lists every grant with days left and a status filter. /audit exports the events as CSV.
   6. Write the scheduler as a pure function over the grants and a clock. Unit test it with frozen times: nothing before 48 hours, one warning in the window, one revoke after the end, no repeat on a second run.
   Rules: encrypt the token and never log it. Say plainly that this tool only controls what its token can reach. Do not claim it replaces an identity product.
   Empty state: before connecting, show the connect form and how to create a Trello key and token.
   Done when: the scheduler tests pass, a grant with an end date 3 days away is warned and then revoked by two cron runs with the clock moved, a forced Trello error is retried and then emailed to the owner, and the CSV lists every step.

3. 3. Landing Page

   Build a one-page landing site for Tempkey, contractor access that clocks out when the contract does.
   Hero: "Access that ends when the contract does." Sub: "Add a contractor with an end date. We warn them two days before and remove them on the day, with a record of it." One button: Join the waitlist.
   Sections: the problem (lingering guests and a console for every tool), how it works in four steps (connect, grant with an end date, warn, revoke), a sample audit list, and an FAQ on which tools work first (Trello now, others as their admin APIs allow), what happens if a removal fails (you are told) and why this is not a privileged access product.
   Waitlist: store the email in a waitlist table in Supabase. No other service.
   Style: Geist, off-white and near-black, one steel-blue accent, a screenshot of the grant form and no fortress illustration.
   Done when: the page renders on a phone and a submitted email appears in the waitlist table.

4. 4. Branding Package

   Use a design or image tool for this one. A coding agent cannot draw a logo.
   Brand for Tempkey: a wordmark and an icon of a key with a small clock window.
   Colors: near-black, paper off-white and steel blue (#2563eb). Type: Geist for the interface, IBM Plex Mono for grant ids and timestamps.
   Deliverables: wordmark, icon, four grant status chips (active, warned, revoked, failed) that differ by shape as well as color, three Slack-style message variants under 200 characters (grant created, warning, revoked), and one launch graphic. Voice rules: talk to ops managers, always mention the warning before the removal, never claim to replace an identity product.
   Done when: each deliverable is saved in one folder and each message variant is under 200 characters.