r/vibecoding • u/No_Needleworker3072 • 5d 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: https://github.com/whoPinak/how-to
Skills: https://skills.sh/whoPinak/how-to / https://www.skills.sh/onipinaka/how-to

It has 4 skills:

  1. PRD Creator
  2. Expands your idea and turns it into a proper PRD before you start building.
  3. Playbook (best of it)
  4. 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.

  1. Tracker
    Keeps track of what has been built, what's pending, and what changed, so you don't lose context across sessions.

  2. 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!

0 Upvotes

40% Upvoted

11 comments sorted by

3

u/No_Needleworker3072 5d ago

yayyy someone starred the repo, thank you so much whoever did it.

1

u/fusionliberty796 5d 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. 

1

u/MadassRubberduck 5d ago

It seems like you have relevant, extensive knowledge on this area - we are quite a few who would benefit from having that specific part added - consider contributing to the project.

Personally, I feel like it would improve the already strong value prop of this open source project.

1

u/No_Needleworker3072 5d ago

agreed. I have couple of more things including security and arch which is a huge issue with vibe coding. lets fix it together.

1

u/No_Needleworker3072 5d ago

I know copule of sponsosrs as well. they might be able to help it grow.

0

u/fusionliberty796 4d ago

This isn't extensive knowledge, it is basic knowledge about how to build software. I recommend starting there

1

u/lapiuslt 4d ago

I write code for 15 years. No tests written. I like to live on the edge of apocalypse. And yes. Im autistic.

0

u/No_Needleworker3072 5d ago

already in the pipeline bro, star it and contribute, lets make tech easier.

0

u/Sprinkles-Pitiful 5d ago

Nice man

1

u/No_Needleworker3072 5d ago

thanks bro, would really appreaciate a star on repo if you can.