KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #developer-tools #ai-agent #claude-code #codex #typescript #ai-agents #deepseek-harness #mcp #cli #rust

property-dashboard

★ 34 Open GitHub ↗

Automated property search and CRM dashboard built with Claude Code. Cloudflare Workers + Pages + D1, React + Vite, RealtyAPI (Zillow).

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Property Dashboard

Automated property search and CRM dashboard built for house hunting near Yosemite National Park. Pulls listings from Zillow via [RealtyAPI](https://realtyapi.io), stores them in Cloudflare D1, and presents them in a triage-style dashboard with stage tracking, price history, and days-on-market analysis.

**Built entirely with [Claude Code](https://docs.anthropic.com/en/docs/claude-code)** (Anthropic's CLI agent). The `CLAUDE.md` file and `docs/spec.md` are the actual instructions Claude worked from -- left in the repo so you can see how the project was scoped and iterated on.

## What It Does

- **Collector Worker** runs on a cron schedule, fetches listings across configurable zip codes, upserts into D1, and tracks price/status changes over time
- **Dashboard** (React + Vite on Cloudflare Pages) lets you triage properties through stages: Inbox, Consider, Untoured, Toured, Pass
- Detects price drops, off-market properties, and resurrected listings
- Days on Market color coding for negotiation leverage
- Detail panel with Zillow links, Google Maps, and driving directions to park entrances
- Bulk select, search, sort, and filter across all properties

## Architecture

```
RealtyAPI (Zillow) --> Collector Worker (cron) --> D1 Database
                            ^                         ^
                            | (service binding)       | (D1 binding)
                            |                         |
                       Dashboard (Pages) -------------+
```

Two Cloudflare projects bound to the same D1 database:
- `collector/` -- Cloudflare Worker with cron trigger + internal REST API
- `dashboard/` -- Cloudflare Pages (React + Vite) with Pages Functions

Pages Functions query D1 directly for reads and proxy writes to the collector via service binding.

## Stack

- **Cloudflare Workers** -- collector cron + API
- **Cloudflare Pages** -- dashboard hosting + Pages Functions
- **Cloudflare D1** -- SQLite database
- **React + Vite** -- frontend
- **RealtyAPI.io** -- Zillow data source ($20/mo plan)

## Setup

1. Create a Cloudflare D1 database: `wrangler d1 create yosemite-properties`
2. Add the database ID to both `collector/wrangler.toml` and `dashboard/wrangler.toml`
3. Run the schema: `cd collector && npx wrangler d1 execute yosemite-properties --remote --file=schema.sql`
4. Set your RealtyAPI key: `echo "YOUR_KEY" | cd collector && npx wrangler secret put REALTY_API_KEY`
5. Deploy the collector: `cd collector && npx wrangler deploy`
6. Deploy the dashboard: `cd dashboard && npm run build && npx wrangler pages deploy --branch main`

See `CLAUDE.md` for detailed configuration, search criteria, and operational notes.

## Adapting for Your Own Search

Edit `collector/src/config.js` to change zip codes, max price, and property types. The search area is fully configurable -- this was built for the Yosemite gateway communities but works for any area with Zillow coverage.

## About the Build Process

This project was built from scratch using Claude Code over several sessions. The workflow:

1. Wrote a detailed spec (`docs/spec.md`) describing the architecture, data model, and UI
2. Gave Claude Code the spec and iterated on implementation
3. Used `CLAUDE.md` as a living reference doc that Claude maintained as the project evolved

Both files are included in the repo as-is. They show how I structured prompts and context for an AI-assisted build of a real, functional tool.

property-dashboard

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README