Hi all!
Hope everyone is well.
I’ve “vibed” a couple of projects, but am always looking for ways to improve.
My main question right now is: How are you planning and starting to build your projects? How are you making sure the stack you use is correct / current? I’d love to see if there’s a way I can improve my workflow.
Thanks!
Coming from the handroll world, take the same planning structure that we use and apply it to vibe coding.
These platforms are built on hundreds of millions examples based on how we've scoped and planned things for decades, do it like it should be done and you'll get good results.
Hell, you can even get AI to do this for you, if you wanted to take it to the next level, use something like Jira to track what you are doing.
In handroll and will AI, this approach has always worked well
Ideas Stage : - Come up with core functionality - Explore new ideas to expand this - Determine an ideal end user and how they'd use it
High Level Overview : - Wireframe your UI - Build user flows - Use these to validate a product idea - Determine your MVP
Design & Planning : - With your MVP, in detail, write what the application should do - Split this into separate tasks for design and functionality with as much detail as possible - Use something like Jira, Monday etc to track these
Development : - Using the tasks you have created, start working.
Take each task one by one and use the detailed description of what you are trying to do as your prompts, user stories help with this.
An example. If I want a page that allows me to enter some text and a file, leave nothing to guess work.
"As a user, when I enter the file upload page I should be able to select a file and add a short description. The description field should be shown top, the file bottom. All error and success logic should be handled here too. Files should be stored using AWS S3, details for these should be stored in environment variables"
This is really great. It's a sound outline and structured. Everyone vibing should read this.
This is really useful. Thank you so much.
I started doing intense design documents for vibe coding projects of any reasonable size. I usually start with a paragraph, let AI expand it to fill in the gaps, look it over, make some changes, and then get AI to look it over again and add more stuff. The more... the better. And even then, most vibe coding platforms will add things that you didn't think about.
I've built my own PRD and spec builder that can either start you at square one or you can drop in what you have at any stage. Ideate to PRD with user stories, designs edge stack blueprint based on parameters, with TDD checklist then creation of ADRs for sprint building. I can export a zip of all of it and drop it a mostly full spec prior to build start.
For big builds I start with a crisp vision and goals, then lock an MVP. Draft a PRD with user stories, edge cases and NFRs; capture ADRs for tech choices and keep a TDD checklist for quality. Choose the stack by constraints (team fluency, ecosystem, maintainability) and de‑risk with small spikes. Track in Linear/Jira and run weekly review–plan–build–retro loops to steadily burn down uncertainty.
Keep it modular. Brush in small strokes. Ensure LOC is not more than 800.
I build detailed PRDs and prompt documents and then feed them to the agent in planning mode (I use Warp for this). I also have a suite of global and project based rules that I use to keep the agent on track.
Recently i love speckit's constitution and prd concept, but the specs itself generated by openspec
use existing frameworks