AI Zoning Intelligence for Real Estate Developers

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 "Zonely": scan one city's permit portal every morning, read the filings with AI, and alert investors whose watchlist matches.
   
   Stack: Next.js (App Router), TypeScript, Tailwind, Supabase (Postgres with PostGIS, Row Level Security, Storage, Auth with email magic link), a Playwright scraper in a small separate Node process, Claude (Anthropic API) for the filings, Resend for the alerts. A Vercel cron route runs the nightly pipeline. Deploy the app on Vercel.
   Scope: one US city with a structured permit portal, San Jose, CA.
   
   Tables (Row Level Security on: a user reads only their own watchlists and alerts, zoning events are readable by signed-in users):
   - watchlists(id, user_id, zip_codes, property_types, alert_frequency)
   - zoning_events(id, city, zip, parcel_id, filing_type, filing_date, summary, raw_document_url, investment_relevance, source_url)
   - alerts_sent(id, user_id, event_id, sent_at)
   - scraped_cities(id, city, last_scraped_at, portal_url, scraper_type)
   
   Screens: /login, /watchlist, /alerts.
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), ANTHROPIC_API_KEY, RESEND_API_KEY, CRON_SECRET.
   
   Do not build: billing, plans or tiers, Clerk, Mapbox or a heatmap, more than one city, Trigger.dev, an admin area.
   Done when: npm run dev starts, you can sign in, and the four tables exist with PostGIS on and Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves Zonely: a new filing becomes a plain-English alert for the right person.
   1. A Playwright scraper opens the city's permit portal and extracts the past 24 hours of filings: permit number, address, permit type, description and filing date. Store the raw records.
   2. A PDF fetcher downloads linked documents to Storage.
   3. Ask Claude for strict JSON { filing_type: "zoning_amendment" | "variance" | "conditional_use" | "other", affected_parcels: string[], summary, investment_relevance, confidence }. Never invent anything that is not in the document. Save the result to zoning_events.
   4. Match new events to watchlists by zip code and filing type, and send each match one Resend email and an in-app alert. Record it in alerts_sent so nobody is alerted twice.
   5. A cron route protected by CRON_SECRET runs the whole pipeline at 6am.
   Rules: say "low confidence" in the alert when confidence is under 0.6.
   Empty state: with no watchlist, show the form that adds a zip code and a property type.
   Done when: running the pipeline by hand stores real San Jose filings, a watchlist for a matching zip gets one alert, and running it again sends no duplicate.

3. 3. Landing Page

   Build a one-page landing site for Zonely, AI zoning intelligence for real estate investors.
   Hero: "Find out about zoning changes before the market does." One button: Start monitoring free, which joins the waitlist.
   Sections: the problem (broker networks cover one city, search alerts are noisy, listing tools do not track permits), feature highlights (real-time alerts, AI document summaries, multi-city watchlists), a map or screenshot of 30 days of permit activity, a placeholder for an investor quote to be replaced with a real one, and an FAQ on data accuracy and city coverage.
   Waitlist: store the email in a waitlist table in Supabase. No other service.
   Style: deep slate backgrounds, off-white text, amber or gold for alert states.
   Voice: direct, intelligent, investor to investor, with no hype.
   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 Zonely: a simplified property pin or parcel boundary mark with a subtle radar pulse ring that works as a 20px favicon.
   Colors: deep navy #0F1A2E, amber #F59E0B for alert states, warm white #FAFAF8, green #10B981 for an opportunity found, and neutral #6B7280. Type: Geist for dashboard numbers and addresses and Inter for marketing copy.
   Deliverables: favicon, a sidebar wordmark, a "no watchlists yet" empty-state illustration, an email alert header with an amber accent bar, and a social profile banner for real-estate investor audiences.
   Done when: each deliverable is saved in one folder and the favicon is readable at 20 px.