Vibe Coding

Remix this synth I cooked up before breakfast: nice-peacock-7883.vibecode.garden

For builders vibes.diy

Double Click: When Coding Becomes Conversation | Figma Blog Developers are embracing a new way of building software that’s more conversation than code. But is it more mayhem than magic?

“If you know what you want to build and you care about exactly how you get there, it's not a vibe. It’s a nightmare.” I spoke with developers and designers about what happens when coding becomes more conversation than code: www.figma.com/blog/double-...

How ‘Based’ Is Grok 3? + Robinhood C.E.O. Vlad Tenev on Markets for Everything + Vibecoding 101 “Elon Musk is willing to spend a phenomenal amount of money and basically do everything he can to stay with the head of the pack on A.I. progress.”

It's Hard Fork Friday! This week: Grok 3, Robinhood CEO Vlad Tenev, and Kevin experiments with vibe coding: www.nytimes.com/2025/02/21/p...

From the vibecoding community on Reddit Explore this post and more from the vibecoding community

My latest prompt engineering research on one-shot app generation, in the #vibecode reddit: www.reddit.com/r/vibecoding...

🤙

15. Enjoy the process-just vibe: Embrace the creative journey of vibe coding, experiment, learn, and have fun along the way. just vibe.

14. Keep a record of the prompts that work best; reuse them often: Document your most effective prompts to make future development and debugging easier.

13. Deploy early: Use platforms like Vercel to deploy your app early, to make sure there are no errors on deployment.

12. Commit often: Push your progress to GitHub regularly to track changes and safeguard your work. Cursor can do this for you, just ask the agent.

11. Secure your secrets: Always store API keys and sensitive data in environment files rather than hard-coding them.

10. Don't forget you can restore previous Composer chats: Save your work frequently so you can revert to an earlier state if needed.

9. Copy errors and paste into Composer agent: When errors occur, copy error messages from your console and paste them into the Composer agent, and more times than not, it will be fixed. When dealing with errors, over explain the issue if it's not fixed the first time.

8. Clone and fork wisely: Use GitHub repos as starting templates to accelerate development, or to find inspiration, then customize them to fit your vision.

7. Utilize voice-to-text: Use tools like Whispr Flow for faster input, and just vibe.

6. Iterate and refine: Embrace rapid iteration-don't worry about perfect designs initially; improve them step by step.

5. Run locally, test frequently: Use built-in servers to run your app locally and test often to catch issues early.

4. Create new chats in Composer: Open a new Composer chat for each distinct task. Keep agent chats short.

3. Use Perplexity: Use perplexity to find new designs and api's from the web. Say that you are creating a nextjs project, and that you want to create —x_ _ feature, and to give you
instructions AND code examples.

2. Use agent mode: Utilize Cursor's agent mode (not normal mode) to create, edit, and manage files through natural language commands.

GitHub - ansh/template-2 Contribute to ansh/template-2 development by creating an account on GitHub.

1. Start from a template: Begin your project by cloning a template from GitHub or another source to provide a solid foundation. (On cursor, Start from Repo, and paste this link to build a nextjs app that is prebuilt with Al features, database and authorization github.com/ansh/templat...)

15 rules of Vibe Coding, via @rileybrown.bsky.social

GitHub - topmass/oneshot-prompts-cursor: One-shot feature integrations for cursor, windsurf, cline coding IDE's One-shot feature integrations for cursor, windsurf, cline coding IDE's - topmass/oneshot-prompts-cursor

List of verified one-shot prompts. Great idea.

github.com/topmass/ones...

Age of Icons::Hyperbody Screentest
www.youtube.com/watch?v=U5ec...

Made with a Rokoko motion capture suit and OpenAI's Sora.