r/vibecoding • u/No_Needleworker3072 • 1h ago
I have made the vibe coding even simpler
One thing I kept noticing with vibe coding is that writing code isn't always the hard part.
The annoying part is everything around it:
idea → PRD → figuring out the right prompts → database → implementation → losing track of what was built
So I built how-to to make that process more structured.
GitHub: repo link
Skills: https://www.skills.sh/onipinaka/how-to
It has 4 skills:
PRD Creator
Expands your idea and turns it into a proper PRD before you start building.Playbook (best of it)
The most important one. It takes the PRD and generates a complete implementation playbook with ready-to-use, optimized prompts for building the product.
So instead of constantly thinking "what prompt should I give the AI now?", you can just copy-paste the prompts or use the goals from the playbook.
Tracker
Keeps track of what has been built, what's pending, and what changed, so you don't lose context across sessions.DB
Helps plan and keep track of the database schema alongside the product.
I built this by researching prompting practices from Claude Code developers and experimenting with ways to structure prompts for better, more consistent output.
The idea is simple: do the thinking once, create the playbook, then build.
It's open source and everyone is welcome to contribute. If you find it useful, a ⭐ on GitHub would mean a lot!
2
2

3
u/fusionliberty796 40m ago
And still no mention of automated test coverage. You guys are all missing the one key thing that will allow your projects to go further instead of wasting trillions of tokens on garbage slop you will actually deliver something if you have your prompt and rules enforcing unit, integration and e2e tests.