Before you vibe code, be interviewed by AI.

· 2 min read

I’m now calling this the Vibe Interview Method. It was originally Posted on x.

Before you vibe code, be interviewed by AI. Here’s how:

  • Download Claude Code (different from Claude Desktop)
  • Install it with your Command Line (terminal, powershell, wsl, etc)
  • Write a basic project spec file such as Accounting software for YouTube creators in spec.md
  • In your terminal, run claude --model opus to start Claude Code. Make sure it’s next to spec.md
  • In your claude session type:
read the spec.md file and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious

be very in-depth and continue interviewing me continually until it's complete, then write the output spec to the file

Claude will interview you with multi-choice questions. The detail is on point.

Once you have this built out, you can continue to refine it. Bring it to other LLMs to challenge you on it as well. Once you make changes, repeat.

Here’s what it will look like:

Claude AskUserQuestionTool Session Example

A few questions you might have:

  • What’s the AskUserQuestionTool?

  • What’s vibe coding?

  • Regarding the rinse and repeat: what’s the best signal that you’ve reached a point of diminishing returns? og source

    At some point you’ll need to start building.

    I think 2-3 iterations is more than enough to start. I’m sure it’s different for each project based on the level of complexity of the project.

    Those iteration question should be a signal too, if there are questions that are “oh I never thought about that” I’d keep going until you move into “yeah this will be down the line.”