Just do the schema by hand. It forces so much downstream alignment that you can almost prefer to use the schema and any associated comments over prompting the model directly.

If you don't know what your schema should be, then I think this is the dead canary in the vibe coding coal mine. Back up to the design phase and talk to the robot about the domain until you have a really strong conviction about its tuples and relations.

With agents code has gotten really easy to shape, like fabric. If want to build something rigid, you'd want to introduce sturdy architectural structures to stretch out the fabric of agentic code.

Data and its shape is one such rigid structure. It will stay with you long after the code around it has been replaced. You do want to be intentional about it and build intuition for it.

Once you have that in place, you can stretch out a web of agentic fabric across it, and pin it down with tests.

Code is soft nowadays, but data isn't.

[flagged]