Productivity and Recovery Dashboard for Solo Founders

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 "Buildline": one weekly score for a solo founder from what they shipped and how they recovered, with one suggested action. It reads GitHub activity and a 10-second daily check-in. It is an operating tool, not a health tool, and never diagnoses.
   
   Stack: Next.js (App Router), TypeScript, Tailwind, Supabase (Postgres, Row Level Security, Auth with email magic link), the GitHub API with a read-only personal access token for commits and merged pull requests, the Anthropic API to write the narrative. The scoring is plain code. Deploy on Vercel.
   
   Tables (Row Level Security on, each user reads only their own rows):
   - connections(id, user_id, provider, token_encrypted, repos text[], status, last_synced_at)
   - events(id, user_id, source, kind, occurred_at, numeric_value)  kind is commit or merged_pr
   - checkins(id, user_id, on_date, sleep_hours, energy, focus_hours)  energy is 1 to 5
   - weekly_scores(id, user_id, week_start, momentum, recovery, flag, confidence, narrative, action)
   
   Screens: /login, /connect (a token and the repos), /checkin (three fields), /week (this week's score and action).
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), ANTHROPIC_API_KEY, TOKEN_ENCRYPTION_KEY.
   
   Do not build: billing, plans or a coach tier, calendar, time tracker or wearable connections, OAuth apps, a weekly email or cron, revenue data.
   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 Buildline: a weekly pair of numbers that is honest about how much it knows.
   1. Connect: save the GitHub token encrypted and the list of repos. A Sync button reads the last 8 weeks of the user's commits and merged pull requests from those repos and saves them as events.
   2. The daily check-in takes sleep hours, energy from 1 to 5 and focus hours. It must take under 10 seconds.
   3. Score in code. Shipping this week is commits plus merged pull requests. Momentum is 50 plus 50 times (this week minus the mean of the previous 4 weeks) over the larger of that mean and 1, clamped to 0 to 100. Recovery is 100 times the average of (average sleep over 8, capped at 1) and (average energy over 5), over the week's check-ins.
   4. Set flag to "recovery_dip" when recovery is more than 15 points below its 4-week mean and shipping is flat or down (up by at most 5 percent). Otherwise "stable" or "up". Confidence is the number of sources with data this week divided by 2, so GitHub only is 0.5.
   5. Send only the numbers to the Anthropic API with a strict JSON schema { narrative: string of at most 3 sentences, action: string (one operational suggestion), rationale: string }. The system prompt says: you are an operations coach for a solo founder, not a clinician; never diagnose; never claim a cause; prefer one action to a list.
   6. Check that every number in the narrative appears in the input and that none of these words appears: diagnosis, disorder, treatment, depression, burnout. If it fails, show a plain template sentence.
   7. /week shows momentum and recovery side by side, the flag in plain words, the narrative and the action, and what is missing when confidence is under 1.
   Rules: always show momentum and recovery as a pair. Never moralize about hustle. Say "not medical advice" on the week page.
   Empty state: before connecting, show the connect form and what is read (counts of commits and pull requests, never code).
   Done when: a sync fills 8 weeks of events, the score matches a hand calculation, a recovery drop with flat shipping sets the flag, a narrative with a clinical word is replaced and confidence is 0.5 with GitHub only.

3. 3. Landing Page

   Build a one-page landing site for Buildline, a weekly operating-health score for solo founders.
   Hero: "One weekly number for you and your company." Sub: "What you shipped and how you recovered, scored together. Ninety seconds on Monday, then ship or rest on purpose." One button: Join the waitlist.
   Sections: a sample score card (momentum 72, recovery 64) with one suggested action, how it works in four steps (connect GitHub, check in daily, get your score, act and compare), and an FAQ on privacy (we count commits and pull requests and never read code), medical claims (we make none) and what happens with missing sources.
   Waitlist: store the email in a waitlist table in Supabase. No other service.
   Style: Geist, an off-white background, near-black type, one emerald accent.
   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 Buildline: a wordmark and a small mark that reads as a single score pip, not a heart or a leaf.
   Colors: near-black, one emerald and two warm neutrals. Type: Geist for the interface, IBM Plex Mono for score digits.
   Deliverables: wordmark, icon, a score card that always shows momentum and recovery as a pair, three Monday-briefing copy variants under 80 words each, and a one-page brand sheet. Voice rules: never moralize about hustle, never use clinical words.
   Done when: each deliverable is saved in one folder and each briefing variant is under 80 words.