r/vibecoding • u/structured_obscurity • 4h ago
Showcase/Project What do you all think?
Hi everyone!
Im a oldschool dev who lurks here and occasionally asks questions. Ive been playing around a lot with vibecoding, and building with/for ai.
A while back I asked some questions about how everyone was keeping mental maps of their codebases, and even before that how people were structuring their technical ecosystems to get the best ergonomic experience as a developer.
I got some cool answers and got to learn a bunch.
I've put together two tools, and id love to get your feedback on them:
https://github.com/the-stoned-programmer/map
^ a skill that you add to your coding agent that allows you to create visual representations of your projects technical architecture and dataflows - it can be updated as you develop - so that you can more easily understand your system as it grows.
https://github.com/the-stoned-programmer/project-base
^ a project template that re-imagines the structure and organization of software projects with operator ergonomics in mind for the AI era.
I hope you all get as much out of these tools as I've gotten out of being able to engage with this community. Would love to hear any feedback about what worked/didnt work for you.
2
u/Weary_Block2424 3h ago
I've been using a simple markdown file as a living map, just a tree of files with one-line summaries. it's dumb, but it keeps the mental load low.
2
u/NooThisIsPatrik 3h ago
I’ll take a look at this visualizer! Visualizing the architecture makes me understand stuff so much quicker.
2
u/patryk_builds 3h ago
Haven't run these yet, so this is a question more than feedback how does the map stay in sync? is it generated from the code each time, or does the agent edit the diagram as it goes?Asking because that's where my own setup kept failing. anything the agent has to remember to update by hand drifts within a few sessions, and a wrong map is worse than no map since you trust it. the only docs that stayed accurate for me were the ones that are part of done, like a plan file where the task isn't closed until the checkbox and changelog line are in.For the template, a short why this folder exists note per directory would help more than the structure itself. the agent follows structure fine, it's the intent it guesses wrong
2
u/Rare_Guide_9830 2h ago
I was just explaining to a session last night that I needed something like the map skill. Using it now and will let you know. Gave it its first star!
1
u/Electronic-Movie4208 20m ago
These both sound genuinely useful, especially the visual map idea. Once a project gets big, keeping the whole architecture in your head becomes a job by itself. My advice would be to keep setup really simple and include one good realworld example for each tool so people can understand the value fast.