Purpose
Capture exactly what the Redfin gym UI shows, organized so an AI can generate tasks. No guessing, no screenshots— please write the fields, options, and constraints as text.
Deliverable (Google Doc)
Environment (region, snapshot counts, sample tables) Actions (with limitations) (nav path + fields + constraints) UI Description (UI mapping) (nav path + field tables)/Feature Availability table (for anything missing/disabled)
1. Tools Overview
What to do
Go to the Redfin gym home/results page. In one sentence, describe what the tool does. List core entities visible in the gym (e.g., Listings, Saved Searches, Favorites, Map Polygons, Mortgage Calculator Inputs, Schools/Neighborhoods). If an entity is missing here, write “Not exposed in this gym UI.” If hotkeys are shown, mention them (otherwise omit). What to write (template)
Scope note: “This is a gym/clone; some original features are disabled.” Example
One-paragraph summary: Redfin lets you search homes on a map, filter/sort results, save searches, favorite homes, and open listing details (price history, schools, neighborhood, and mortgage estimates).
Core entities: Listings, Saved Searches, Favorites (Saved Homes), Map Regions/Polygons, Mortgage Calculator Inputs, Schools, Neighborhood/Market Stats, Users/Accounts.
Scope note: This gym is a simplified clone; some flows (e.g., tour requests/agent chat) may be disabled.
2. Environment
What to do
Record the region/market scope (e.g., San Francisco Bay Area). Capture a current snapshot with counts (write numbers): listings in view, saved searches, favorites, polygons, any alerts, etc. Create small tables for Listings (15-20 sample rows), Saved Searches, Favorites, and Polygons. If users/teams/settings exist in the gym, list them; if not, say “Not exposed in this gym UI.” What to write (templates)
2.1 Region & Preferences
Alerts/Commute defaults: … 2.2 Current Data Snapshot (counts)
Listings in current view: … Tour Requests: … (likely 0 / Not exposed) Integrations/Notifications: Not exposed in this gym UI 2.3 Tables
Listings (sample 5 rows)
Saved Searches (sample 3)
Favorites (sample)
Map Polygons (sample)
Assignments & Relationships
What to do
Write a few bullet examples that connect entities:
Example
Listing → Saved Search: SF-002 appears in SOMA Condos. Saved Search → Polygon: SF $1.2–1.5M uses Noe Valley Drawn polygon. Favorite → Listing: Saved Homes contains SF-002.
3. Actions (and limitations)
What to do
For each action that changes data or user state:
Write the Navigation Path (exact clicks). List Required fields and Constraints (e.g., ranges, mandatory, mutually exclusive). Note any observed limitations (if it doesn’t work or is missing). Use exact UI text (verbatim) if shown. If something is missing/disabled, also add it later to the Feature Availability table. What to write (examples)
3.1 Search
Navigation Path: Header → Search → type “San Francisco” → Enter Required fields: None (free text) Constraints: Autocomplete may be limited Limitations: If query doesn’t resolve, write: “No results for this query” (verbatim) 3.2 Filters (apply/clear)
Required: None (apply works with any subset) Constraints: Numeric ranges enforce Min ≤ Max; multi-selects allowed for Home Type Limitations: If Schools/Commute tabs are absent, write: “Control not shown in this gym UI” 3.3 Sort
Options: Newest; Price (Low→High/High→Low); Beds (Most→Fewest); Baths (Most→Fewest); Sq Ft (Most→Least); Lot Size (Largest→Smallest); Days on Redfin (Fewest→Most) Limitations: If any option missing, say: “Option ‘Days on Redfin’ not shown in this gym UI” 3.4 Map (draw polygon)
Path: Map → Draw → close polygon → Apply Required: Complete the polygon to enable Apply Constraints: One active polygon at a time Limitations: Climate overlays not present → “Control not shown in this gym UI” 3.5 Save Search
Path: Results (with filters) → Save Search Constraints: 3–100 chars; Alerts optional (Instant/Daily/Never); Include map area optional Limitations: Email delivery not active in gym 3.6 Favorite / Unfavorite
Path: Listing card → Heart toggle Constraints: Immediate toggle; appears under Saved Homes Limitations: Favorite notes may be absent 3.7 Listing → Mortgage Calculator
Path: Listing → Mortgage → Calculator Required: Home Price (prefilled) Constraints: Numeric only; % vs $ toggle for Down Payment Limitations: Pre-approval flow disabled → “Not implemented” 3.8 Listing → Schedule Tour / Contact Agent (if present)
Path: Listing → “Schedule Tour” / “Contact Agent” Required: Name, Email, Phone, Message (if forms appear) Constraints: Valid email format (if validated) Limitations: Submit does nothing → record exact message or “no response” 4. UI Description (UI mapping) — guideline
What to do
For each screen or form, write:
Navigation Path (one line) A field table with these exact columns:
Field Label | Type | Mandatory | Allowed Inputs | Options | Constraints
List every control and option exactly as strings from the UI. What to write (examples)
4.1 Global Navigation (Header & Sidebar)
Navigation Path: Any page → Header/Sidebar
4.2 Results → Filters — Price
Navigation Path: Results → Filters → Price
4.3 Results → Filters — Beds & Baths
4.4 Results → Sort
Navigation Path: Results → Sort
4.5 Map Canvas
Navigation Path: Results → Map
4.6 Listing → Mortgage Calculator
Navigation Path: Listing → Mortgage → Calculator
4.7 Saved Search — Create/Edit
Navigation Path: Results (filters applied) → Save Search
4.8 Favorites (Saved Homes)
Navigation Path: Header → Saved Homes
If a screen or control is missing, write that and log it in Feature Availability.
Feature Availability (Disabled/Errors Log)
What to do
Whenever a feature is missing, disabled, or errors:
Try the action (write the Navigation Path). Note what you clicked (UI element exact label). Write the Observed Behavior and Error Text (verbatim) (or “no control present”). Mark Status: Available / Disabled / Stubbed / Hidden. Add Repro Steps and Expected Behavior. What to write (table template)
Example rows
Expected Behavior (original tool)