Non-developers who vibe code: how do you write your specs?

by•

I'm a construction contractor, not a programmer, and I've shipped an Android app with Claude Code. The single thing that made the difference for me wasn't a tool, it was writing a short spec before every feature: input, output, three example cases, and a list of things the code must NEVER do.

I'm curious how others who don't code for a living do it:

  • Do you write the spec yourself, or ask the model to interview you first?

  • - Do you keep a 'never do' list (e.g. never send data without the user tapping a button)?

  • - How do you check the result when you can't really read the code?

Would love to steal your best habits.

16 views

Add a comment

Replies

Best

Asking for a fix and a test together gives a test that still passes when the fix is reverted. It was never checking the bug. The spec now requires writing a test that fails on main first, before letting the model touch any actual application logic.