AI Agent Workflow Platform

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 "RelayOS": a runtime where a plain-English job becomes an agent graph that retries, recovers and escalates instead of dying.
   
   Stack: Next.js (App Router), TypeScript, Tailwind, Supabase (Postgres, Row Level Security, Auth with email magic link), Temporal for durable runs, Claude for the compiler. Workers run in a separate Node process that hosts the Temporal activities. Deploy the app on Vercel.
   Tools: two mock tools only, a fake CRM write and a fake chat message. Real Salesforce and HubSpot come later.
   
   Tables (Row Level Security on, each user reads only their own rows):
   - graphs(id, user_id, name, dsl_json, version)
   - runs(id, graph_id, temporal_workflow_id, status, started_at, cost_cents)
   - run_events(id, run_id, seq, type, payload_json)
   - tool_contracts(id, provider, name, json_schema)
   
   Screens: /login, /graphs, /runs/[id] (the run inspector).
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), TEMPORAL_ADDRESS, ANTHROPIC_API_KEY.
   
   Do not build: billing or plans, Salesforce or HubSpot connectors, orgs or SSO, a template gallery, a graph editor.
   Done when: npm run dev starts, the worker connects to Temporal, you can sign in, and the four tables exist with Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves RelayOS: compile a job, run it, and recover when a tool fails.
   1. POST /api/graphs/compile takes a plain-English job and returns a typed graph: trigger, steps, retry policy, compensation and escalate_to. Validate every tool against tool_contracts.
   2. POST /api/runs starts a Temporal workflow for a graph. Each activity calls a mock tool with an idempotency key.
   3. On a 429 or 5xx from a tool, retry with exponential backoff, then use the fallback tool if one is set, then escalate with the run transcript.
   4. /runs/[id] shows every event in order, a Replay from step N button, and a Kill switch.
   Rules: never drop a failed step without writing a run_events row. Do not build a template gallery.
   Empty state: with no graphs, show a text box that takes the first job.
   Done when: a compiled job runs end to end, a mock tool that returns 429 twice still completes, and killing the worker mid-run resumes it when the worker restarts.

3. 3. Landing Page

   Build a one-page landing site for RelayOS, a runtime for agent workflows with error recovery.
   Hero: "The ops OS that recovers." Sub: "Agents that retry, compensate and escalate, not zaps that die in a Slack channel." One button: Join the waitlist.
   Sections: the contrast (template libraries sell recipes, this runs production graphs), how it works in four steps (describe the job, connect systems, run with recovery, operate), a mock run inspector with a Replay button, and a short FAQ (it is not n8n with a skin, Temporal is the spine).
   Waitlist: store the email in a waitlist table in Supabase. No other service.
   Voice: precise and calm, written for an operations lead.
   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 RelayOS: a wordmark and an icon that suggest a relay baton passed between steps.
   Colors: a near-black, off-white and one signal color for a recovered run. Type: one sharp sans for the interface and a mono for run events.
   Deliverables: wordmark, icon, three run-state icons (running, retrying, recovered), and one launch graphic.
   Done when: each deliverable is saved in one folder and the wordmark reads at 18px.