Tag: elm

This is more useful than another argument about vibe coding because it is a concrete trace: notes, mockups, data modeling, scaffolding, implementation transcripts, and maintenance around Diggit, a small git-history tool for architecture archaeologists.

The point I want to keep is that good agent work still starts before the agent. Taylor narrows the problem with plaintext design, simple Elm scaffolding, explicit model shapes, fast feedback, and loud states. Claude wrote most of the code, but the product is really the constraint system around Claude.