Manage JD's building library and generate client-facing survey decks (PPTX). Trigger when JD asks to build a survey, create a survey deck, add buildings, process flyers or CoStar exports, upload or manage building photos, query building data, or discusses property tour preparation. Also trigger for building library queries like 'pull buildings in [submarket] with [criteria]', 'what do we have on [address]', or any discussion of available office space inventory. Trigger when JD drops a landlord flyer PDF or CoStar export.
Notion Building Library: f6126421-2178-49d9-993b-8b39e4f21a2f Supabase project: rahvxwwkpzujcnsfjahz Supabase buildings table: 44 rows, keyed by address Supabase spaces table: linked by building_id FK Supabase Storage: survey-images bucket (public read) Template: skills/survey/references/template.pptx
Trigger: "build survey for [client]" or "create survey with [buildings]"
Template rules:
PPTX generation: Use python-pptx locally. Template at skills/survey/references/template.pptx. Images from Supabase Storage (direct access — no proxy needed on Mac Mini).
Trigger: "what do we have on [address]" or "pull buildings in [submarket] with [criteria]"
Query Notion/Supabase by:
Return: building details + all available spaces + image status.
Trigger: JD provides building info or drops a PPT archive
Write to BOTH Notion and Supabase in same operation:
Trigger: JD drops a PDF flyer
Trigger: JD drops a CoStar PDF
After ANY building or space data change:
See references/architecture-v1.2.md for the full original architecture including Make.com scenarios, edge functions, and Vercel proxy details (legacy — mostly replaced by direct access).