Vibe coders, How do you document your past implementations?
I’m curious! How do you document the different iterations of your app so you can revisit them later for enhancements or debugging?
Do you stick to traditional docs, use wikis, or something more creative?
As a solo dev, my app is getting bigger and more complex with multiple automations and moving parts, and I often struggle to remember all the implementation details. Do you also save the prompts you used to develop certain features, or have your own system for keeping track?
24 views
Replies
I maintain all my prompts in local documents and then update this playbook: https://nocodo.com/playbook
The playbook is part of my own offering and I am working on it more seriously since the traffic has increased. I run lots of code generation experiments, keep updating prompts and then update this page. I always try to create helper scripts which help in static analysis or data management so they do not go through LLMs each time. For example I generated CI pipelines. Pipelines break a lot but now I am vibe coding a management tool to run pipelines directly on Linux VPS or local for each task.
Basically codify everything, distill knowledge from LLMs into code, keep updating them.