Inspiration
A personal challenge that affects me and many people I know, and is projected to become even worse in the future. Whether we were trying to figure out a startup, or even when we were stuck on some coursework - LLMs were always there to save the day and craft the solutions in the blink of an eye. Yes, we'd win, but we'd be left without knowledge at the end of the day. And when you can't choose between the two, why not choose both?
What it does
We allow people to vibe-code as much as they wish. Yes, seriously! But we realise many feel as though they are cheating themselves, taking the easy way out, hence we have a toolkit that automates a Git-like version control to semi-automate the process. We then utilise the power of Gemini to generate a list of concepts based on the code that the LLMs have come up with, and then display this nicely on a fullstack interface with a "brain" - a connection of nodes that shows the user the skills they are building. Furthermore, upon each project completed with our tool, the user will be able to see a project file with the skill checklist generated. Based on their confidence, they can tick off the skills they know, and leave unchecked the ones they do not know. As the user improves over time, their "brain" will grow, fuelled by the vibes!
How we built it
Used CLI and paired it with our fullstack web interface. Based upon a Django framework, with react working for the frontend. Git-like version control to produce Git diffs to detect codebase changes. Gemini-API to receive these Git diffs, and parse them, and breakdown into topics and lists and deliver to our API endpoints. All data is then nicely displayed on the user interface.
Challenges we ran into
Dealing with Gemini API Figuring out how to tackle the CLI Figuring out how any user will be able to utilise our tool without having to share many codebase dependencies. Making sure instructions are clear for users Devising a way to capture effectively the codebase changes without copying full codebase everytime.
Accomplishments that we're proud of
MAKING IT WORK!!! GETTING TO MVP GETTING INSPIRATION TO DEVELOP THIS FURTHER FEELING THE VIBES!!!*
What we learned
How to integrate our vibe-coding tendencies with real learning How to deal with many APIs What Git diffs are and how to use them What CLIs are and how they are used
What's next for Vibrain
For each project, since we currently have a list of topics to learn, we could easily implement a whole personalised tutorial for the user depending on what skills they are good at and which skills they need to learn!
Log in or sign up for Devpost to join the conversation.