vibecode

One really useful way that AI has changed my coding workflow is that now I rarely start constructing a component, file, system, UI, etc from scratch. I'll usually give Claude Opus a ton of context and have it write a good v1, then go in and rewrite it myself or with AI so that it works properly, considers all edge cases, looks right, etc.

A recent example of this is a component we're in the process of implementing now called <TokenBalance />. It's an easy drop-in component that takes a contract address, account address, and chain id, and produces a consistently formatted and stylized balance for that token—USD value + token amount + token ticker.

I spent a week on-and-off writing a full spec, getting feedback from other engineers, and tweaking it to exactly what I wanted.

Once it was bulletproof, I had Claude write the v1. there were a few small things it got wrong, but it was mostly correct, and soooooo much easier than building it myself from scratch.

I went through and tweaked various things, and each time had the AI tweak all my examples and documentation to match my changes. Again—so helpful to eliminate much of the effort of staying consistent.

All in all the building part of this took about a day, easily 2-3x faster than I would've been able to do on my own. And most of my involvement was in reviewing the work of the AI, rewriting things it got wrong, judging the difference in variations and tweaking to match my taste, etc.

design @splits | /wireframe /latenightcrew /event-pass /feud