Riley's Ideas
We can add these to a specific place later these are things I want to add.
Riley's Rules for Vibe Coding
Your app idea should revolve around two things. (1) a specific problem, and (2) a halo feature. Your app should solve a specific problem, and you should pick a problem that you can market your product around effectivley.
Start with the easiest features first, save the hardest for last. Build confidence and momentum by tackling what you know before attempting unfamiliar territory like calendar integrations.
Be specific about what you want, but let the AI handle implementation details. Tell it the features and functionality, not how to code them - phrases like "act like the greatest engineer of all time and make this happen" work surprisingly well.
Choose the right tools for your skill level. Vibe coders should use no-code/low-code AI tools that abstract away terminal commands and complex IDEs, while experienced developers can leverage tools like Claude Code directly.
Always specify which APIs and services to use upfront. Mentioning "use OpenAI Whisper" or "use Expo Calendar documentation" prevents the AI from choosing inferior alternatives.
Test after every prompt before moving forward. You can't fix what you don't know is broken, and discovering issues early prevents cascading failures.
Keep UI improvements for the final prompt. Functionality first, styling last - a working ugly app beats a beautiful broken one.
Prepare the AI for future features even if not implementing them yet. Mentioning "we'll add calendar integration later, so build with that in mind" helps create a more extensible architecture.RetryClaude can make mistakes. Please double-check responses.
Last updated