David Cho
I build AI agents that help with the repetitive parts of architectural work.
In every firm I've worked in, design was not the slow part. The hours went to the work around it. I don't think AI replaces architects. I think it takes over parts of the workflow, leaving more time for the work only an architect can do. As the tools improve, that gap keeps growing. I help architects apply AI to the parts of the job that eat the day: zoning and code research, project coordination, model checks, and repetitive writing.
Architecture AI Starter Kit
- Where AI actually helps in architecture and where it does not
- How to connect Claude to Revit and Rhino, step by step
- How to build an AI agent that already knows your project
Three cities, firms of every size, the same question.
I have worked in Vancouver, San Francisco, and New York, as a computational designer and architecture intern across a small studio, a mid-sized practice, and a large office. In every one of them, I kept asking the same questions: Which parts of this job are actually painful? Where do the hours really go? And what would it take for AI to absorb that work instead of adding more to it? Those questions led me to build practical AI workflows for architects.
Start with these three.
A few of the Claude Code skills I reach for most. All free, all copy-paste.
Turns a zoning lookup into a structured summary.
Exit count, travel distance, and separation, all verified.
A phase checklist for SD, DD, CD, or IFC.
The library opens soon.
Let's build real AI workflows in architecture.
New skills and workflows go out as I build them. Start with the free kit, follow along for the rest, or just say hi.