Tips for Vibe Coding

This is an update-as-vibe-code-along article.

Here are my take-aways for Cursor based Vibe Coding:

requirement is the key, you should have a clear product (experiment) idea, and make it clear in text (prompt)

previous experience helps (a lot), I have good sense of iOS development, so when issue happens, I can give Cursor ideas and my verification is efficient

during debug, give specific example, let AI learn from the example

work with Cursor for Git, save as frequently as possible, many chances you’ll need to roll back

for important milestones, Zip and save, old-school but important to save your life (I deleted sth accidentally, it cost 30min to rebuild, and feels bad)

offer documents, I give Cursor Swift and Apple Design guide ahead of project, it seemed helpful

make sure you let Cursor ready UI/UX design guide first, it makes your app pretty

To try new things, you need to be very specific. Example, I need to ask Cursor to read Apple iOS 26 FoundationModel document and specify use LanguageModelSession.

Cut big tasks to smaller ones, do atomic tasks

Create a VibeLog.md to note your mind, track the CoT of yours

Strongly believe AI is the best solution, think forward, trust AI to resolve issues, even when there is degradation. You can always revert with Git.