Hey everyone! 👋
I’m a 17-year-old solo dev, and I’ve spent the last few weeks building VibeCodingFlow—an MIT-licensed, drop-in CLI AI-IDE that takes one plain-English prompt and spits out a fully configured project skeleton (folders, files, and working code).
🚀 Why VibeCodingFlow?
Modern development often feels like endless boilerplate, config files, and copy-paste. I wanted to bring back that dopamine hit of idea → code without the faff of setup and boilerplate.
“Make a Flask app with login and SQLite”
…and boom, it appears.
🏁 Quick Start
# 1. Install the CLI
pip install vibecodingflow
# 2. Create a brand-new project
vibe new blog_site "simple blog with posts and an About page"
# 3. Jump into your project
vibe go blog_site
# 4. Iteratively add features
vibe do "add comment section under posts"
Each command only regenerates the files you changed, and your project’s state is tracked in a tiny SQLite database—so you can iterate quickly without losing context.
🧠 Under the Hood
Prompt ─▶ GPT-4o ─▶ JSON spec ─▶ GPT-4o (code gen) ─▶ File writer
↓
SQLite memory (history & state)
- Prompt & Spec: You describe what you need; VibeCodingFlow turns it into a structured JSON spec.
- Code Generation: GPT-4o uses the spec to generate files and boilerplate.
- File Writer: Only diffs are applied.
- Memory: SQLite tracks every request and change, so you can review or roll back.
🔨 Current Status
- Alpha-MVP: CLI only
- No GUI or automated tests yet
- Powered by Python 3.10+ & GPT-4o API
- MIT-licensed
It already handles basic web apps, scripts, and simple REST endpoints—bugs and quirks included! 😅
🌱 Roadmap
- Plugin system for custom generators & verifiers
- Retrieval-augmented specs (RAG) for pulling in docs/snippets
- Optional GUI (Tauri/Electron + Monaco)
- Symbolic logic checks via Z3/Prolog
-
vibe servelocal dev server - Built-in testing commands (
vibe test)
🤝 How You Can Help
- Give it a star on GitHub ★
- Try it out and share your feedback on CLI UX & command naming
- Propose plugin ideas, Docker integrations, or a GUI vision
- Help write tests, improve docs, or build real-world examples
GitHub: github.com/ion-linti/VibeCodingFlow
Thanks for reading—and happy hacking! 💚
I’d love to hear what you think in the comments below.
Top comments (8)
pretty cool seeing stuff like this from a solo dev tbh - always makes me wonder, you think tools like this actually let folks focus more on the fun parts or just end up moving the boring work somewhere else
Thnk u for comm!
By using something like this, can we leverage it to build something bigger and more impactful, or could it make us less skilled in the long run?
If you’re just pressing buttons without thinking, yeah, you’ll lose skills over time. But if you have a goal and you’re thinking, this kind of tool actually helps.
I didn’t make VibeCoding Flow to be some magic button. It’s a way to skip the boring parts and get to the real work faster.
In the end, it depends on the person. Some people fall behind, others grow stronger.
If we use something like this, could it help us create something truly meaningful, or might it slowly take away from the skills we’ve worked hard to build?
It depends how we use it. If it becomes a crutch, we risk losing depth. But if we use it as a tool — like a calculator for thought — it could help us build things we never could alone.
Nice!
Want feedback!!👀