Some thoughts:
1) I think you could simplify the onboarding - I don't think I actually need to make an account up front. It somewhat contradicts the way the landing page presents things.
2) The AI prompt does a good job - I really like the output it provides.
3) It doesn't seem like there's a super straightforward way to separate local & production logs - would be nice.
I implemented it - I'll see how it cooks the next couple of days & check back.
Side note, if you want to try that project, since you're a vibe coder, I'd appreciate the feedback too - vibescaffold.dev.
Great, you're the first user then! If don't mind sharing your metrics, feel free to DM me on discord, I've joined yours.
1) Good point, I wanted to avoid the complexity of this for the first version, but you're 100% right, it would be great for someone to try first then upgrade when they register an account.
2) Thanks. Great to hear!
3) The best way to do this right now would be to create a project for each env and then give each env the API key from the corresponding project. Another way could be to put the env in the tags, but I think that's a bit messier as both lines would appear on the same chart (plus I've not even tested that works yet).
vibescaffold.dev looks interesting. Let me spend a bit of time and I'll feed back in your discord.
Thanks a lot! I agree (obviously) - this workflow really helped me structure my projects.
> If you're looking for feedback, you could include a tiny section on the homepage about how to run the output docs. e.g. put them in a folder, point Claude Code/Codex to it and give it the prompt.
This is great feedback - I totally agree - going to add this asap
https://hn-wrapped.kadoa.com/dang
reply