Updates to my project template repo / vibecoding workflows
After getting to experience claude/open code, vibecoding frameworks (spec kit, openspec, gsd), and git worktrees at work, I decided to update my project templates repo.
This is the current config that I used to vibecode a webapp version of the marimo mockup I made a while back
Why Get Shit Done?
I picked Get Shit Done as my vibecoding framework
I found it while browsing vibecoding frameworks
BMad if you are an Engineer. GSD if you wanna prototype or get shit done!
There’s a couple of things I like about gsd over spec-kit and openspec (which is a derivation of speckit)
- Using
.planningfor the folder name and better folder organization- It makes it easy for me to find at the top of my repo.
- Openspec doesn’t yet support a custom name/path GitHub · Where software is built
- There’s less review cycles/steps to create a plan
- The chat context captures all my requirements and feedback, so I don’t have to jump back and forth between the interface and markdown files.
- GSD has 3 steps plan, execute, verify. Spec kit has specify, plan, tasks, and implement this is great in theory, but has too much back and forth.
- Better feedback management
- if you have any feedback, gsd will create a new file for it. Although it makes the planning folder a bit cluttered, it’s nice because the llm context just needs to load a file rather than the full file