Thread

In case this saves you some time (I'd already made these notes for myself in Trilium): Calle's way Calle's guide to vibe coding (Citadel Dispatch 171) Use different AIs, one for making the implementation plan + requirements, the other for coding up. He uses Goose & Cursor (shows him to switch between models - use ppq.ai for same functionality) If wanting to understand existing code, he used Gemini to explore and describe it to him. His work flow: 1) create Implementation plan (list of things that need to be done in order). Steps to achieve overall project 2) create requirements in each step (to fulfil that step) [my addition, after 1st application of this workflow, getting the first AI to produce a simple user manual is also helpful for the next AI & to sanity check that it understands how you want to use your project] 3) pass all of that to a new AI (e.g. Claude) For bitchat, he spent ½ day iterating like this and had a working MVP with basic features. As project scales, or for niche / specialist code (not many examples for AI to learn from) manual coding is required. When project becomes large, AI loses context, large bodies of redundant / unused code etc.