Alongside — Wedge

A single-page, no-auth task breakdown tool for people with ADHD who are frozen on a task. Type what you're stuck on, get 4–7 micro-steps small enough to actually start, and optionally leave your email for early access to the full app.

Running locally

npm install
cp .env.example .env.local
# Fill in .env.local with your keys (see below)
npm run dev

Visit http://localhost:3000/wedge

Environment variables

Variable	Where to get it
ANTHROPIC_API_KEY	console.anthropic.com → API Keys
NEXT_PUBLIC_SUPABASE_URL	Supabase project → Settings → API → Project URL
NEXT_PUBLIC_SUPABASE_ANON_KEY	Supabase project → Settings → API → anon/public key
SUPABASE_SERVICE_ROLE_KEY	Supabase project → Settings → API → service_role key (keep secret)
UPSTASH_REDIS_REST_URL	console.upstash.com → Redis database → REST URL
UPSTASH_REDIS_REST_TOKEN	Upstash Redis database → REST Token
NEXT_PUBLIC_POSTHOG_KEY	posthog.com → Project → Settings → Project API Key
NEXT_PUBLIC_POSTHOG_HOST	Default: https://us.i.posthog.com (or your self-hosted URL)
RESEND_API_KEY	resend.com → API Keys (reserved for future use)
RESEND_FROM_EMAIL	The from address for transactional email, e.g. [email protected]
NEXT_PUBLIC_APP_URL	Your production URL, e.g. https://alongside.app

Supabase setup

Run the migration in supabase/migrations/001_wedge_captures.sql in your Supabase SQL editor to create the wedge_captures table.

Deploying to Vercel

1. Push this repo to GitHub
2. Import the project in vercel.com/new
3. Add all environment variables from .env.example in the Vercel project settings
4. Deploy — Vercel auto-detects Next.js from vercel.json