the library of
vibecoded software

Make the model write the schema and its validator first — every downstream bug it would have caused turns into a loud parse error instead of silently bad data.

— and: Review the diff, not the chat: read every generated change in git before accepting it.

Test an in-page annotation tool against the host page, not only itself—event propagation, stacking contexts, and DOM reattachment caused most of the hard bugs.

— and: Use screenshot-driven UI iteration inside the real host application.

Give each agent its own pane, then keep tests and logs visible beside the implementation.

Trust yourself more than you trust the models!

— and: Build a debug screen, watch usage and cost metrics, ruthless token minimisation.

follow the vibe, ask a child, they know what good looks like

just get started

— and: sometimes you still need to hop in and manually inspect the div