if you are a coder, this isn't for you.
you see everyone around you building apps and think to yourself what if i could also do that. i have this idea-
this idea which could be the next
@calai_app
but what's next? how do you actually convert your idea to a working product?
i'm going to explain to you few simple principles and soft skills to learn how to vibe code that ACTUALLY works.
1. planning: strictly start your first prompt to build any app, feature with "don't code", blabber everything you want from the app, the more the better( voice) and towards the end just ask the tool to research and create a plan(phases). go through the plan, suggest changes for each small phase.
2. context: you are not supposed to know the documentation but ai agents do. for every piece of software mentioned, ask the coding tool to "get relevant info from official documentation".
3. implementation: you have the phases already from 1, now start asking the model to build one phase at a time, if possible test out those singular phases. if not, take it to the next possible testing stage and test it out.
4. bug finding: mention the thing that's failing, do NOT ask it to solve it just yet. ask it to "research all possible sources from this error and add logs to pin point, make your recommendation" to find why something fails.
5. bug solving: provide every log that you have from frontend, backend and dev tools from browser(cmd+shift+i in mac to see what requests the app is making what are failing) to solve the bug. if it is unable to do so, do NOT prolong the conversation. end it, new thread: repeat.
6. git: create a new github repo from instructions on official page, "git add ." to add all files, "git commit -m {message}" + "git push" to save it on github. that's all you need to know for the time being. its a lifesaver when ai messes things up. use the graphical interface and not cli.
soft skills:
1. perseverance: iterate, iterate and iterate. there are no shortcuts, you are not going to get the app up and running in the first attempt. do not aim for that.
2. curiosity: be curious about how pieces work together. what failure would lead to what breakage. its always better to have an idea about what's really happening.
3. low ego: ask for help. the internet is filled with people who want to help you(dm me). try to figure things out but also be ready to ask for help
that's all there is. don't give up before you've actually spent enough time persevering, being curious and low ego-ing. you can not fail. tools have gotten good enough. you can do it. just
keep goingggg.