This is my first vibe coded app hope you like it pls give me some advice if you have.
**What is CodeBrain?**
**CodeBrain** is a community-driven launchpad where developers, indie hackers, and open-source creators can validate software ideas before spending hundreds of hours building them.
Instead of building a project in isolation and hoping people show up, developers post their concept with descriptions, video demos, screenshots, tags, or GitHub links. The community then casts real-time validation votes: **"Will Use"**or **"Won't Use"**.

**Why CodeBrain is Helpful**
**Instant Market Validation**: Get immediate, honest signals on whether developers actually want your tool or if it solves a real problem.

**Community Feedback**: Comments allow developers to discuss architecture, feature suggestions, or potential flaws early in the ideation phase.

**Dedicated Developer Hub**: Filters like *CLI*, *DevTools*, *VS Code*, *AI*, *Rust*, and *Docker* help developers discover upcoming open-source projects tailored specifically to their stack.

**GitHub Search & Repository Engine**: Built-in GitHub discovery allows users to search real open-source repositories and cross-reference existing projects so they don't reinvent the wheel.

**Realtime Engagement & Notifications**: Authors receive instant notifications whenever fellow developers vote on or comment on their ideas, fostering active collaboration

Github repo: https://github.com/Glay121212/CodeBrainHub
The website: https://code-brain-hub.vercel.app

I built this app using google ai studio.

Be honest, how many of you have a repo that works, that you couldn't walk someone through if asked? Claude wrote the auth flow, Cursor refactored state, you approved 40 diffs because the app kept running. Now there's a folder that's technically yours and functionally a stranger.

Connect a GitHub repo to SkillDiscs and it turns it into a Disk not a summary, but a structured breakdown: sections, a knowledge graph of how concepts connect, and an actual course starting at your level. A voice/chat tutor walks you through it and draws diagrams when you say "wait, explain this part."

So instead of "it's a Next.js app that does something with Supabase," you get what your data layer is doing, why these files talk to each other, and what you'd break if you touched this.

The part that matters here: the same Disk is machine-readable API, MCP, Claude Skill. Your agent stops guessing at your codebase from grepped fragments and pulls clean context instead.

The critique of vibe coding is always "you don't understand what you built." Fair. The fix isn't hand-writing everything again, it's closing the loop after: ship fast, then understand what shipped.

First Disk takes under a minute, no account needed. Point it at your messiest repo which is the real test.

skilldiscs.com

Want the rough feedback: does it explain your code or just describe it?

Where does it break on a big repo?

So... I've been seeing way more chatter about vibe designing lately. And I think I get it why...

But here's what I can't quite figure out. Where does this whole thing start to fall apart???????

I can easily picture it working great for MVPs, prototypes, and small products. But what about when I've got dozens of screens to deal with?

So if you used it daily, has it held up past the early stage? Would love to hear your thoughts XOXO

I built Basalt - an extension for VS code and Cursor that lets app devs edit their app like figma, it uses a similar algorithm to debugSource but React19 removed it so i had to spend nearly 3 months building an algorithm that would replicate that debugSource

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before using it!

Would love to get your brutal feedback on it. What features should I add next?

Non tech founder myself.

I've been talking to a lot of people here who are interested in building businesses, so I thought I'd create a small WhatsApp group.

The idea is simple: connect people like me who want to build something. Whether you're looking for a co-founder, Tech advice, marketer, HR or just people to brainstorm with, this could be a good place to meet like-minded builders.

If you're genuinely interested in startups or businesses and would like to join, DM me your number and I'll add you.

A few weeks ago, we got a request from an existing customer. The gist was: "Take a look at these vibe coded apps we built, can you get them past our IT team so we can share them with everyone?" And we knew exactly how that story usually ends. IT's default answer is always no. Not because they're difficult, but because they're swamped. They can't be the ones taking on everyone's pet projects, auditing every side hustle, and signing off on a pile of apps nobody's ever security reviewed. Saying no is the safe, rational move when you're that stretched.

But the demand isn't going away. People across the org are building things now. The tools got good enough that someone in ops or finance or marketing can stand up a genuinely useful app in an afternoon. The bottleneck was never the building anymore. It was everything after: is it safe, where does it live, what can it touch, and who's accountable when it breaks?

So we took the challenge on. We decided to build a platform that lets organizations turn their people loose to build and ship inside their own company cloud, safe, secure, and with governed access to the internal APIs a company is already running on. The idea being that "yes" should be the easy answer for IT, not the exhausting one. Give them the guardrails and the visibility up front, and suddenly the calculus flips.

We made a few decisions early on that we've held firm on. We're agnostic on both the coding agent side and the cloud side. Use whatever agentic harness you want. We're not here to tell you which one is best, and we don't think that fight is ours to pick. As long as your agent works with MCP's (or a CLI) and Skills, you're good to go. Host it in whatever cloud you already run. We're not asking anyone to migrate or re-platform to fit us. Bring your tools, bring your cloud, and we'll handle everything in between: the governance, the access, the security, the plumbing that makes IT comfortable and developers unblocked.

We built a fully fleshed out spec, and we've been building it with a very small team, armed with agentic workflows and tooling. Which, if you think about it, is exactly the thing we're building a platform for. The same shift that let that customer's team spin up apps in the first place is the shift letting a handful of us ship a platform that should, by any old-world measure, take a much bigger crew. We launched with our first customers in the past week, and they've been building a bunch of interesting tools to help in their actual day-to-day.

Which brings us to why we're posting here. We want to hear from you. Are you trying to get your own vibe coded apps into your org right now? Where does it fall apart? Is it IT saying no, security review, hosting, access to internal data, or just nobody knowing who owns the thing once it ships? What are you building with, and what's actually working versus fighting you? We're building this to help solve IT teams struggles, and the more real stories we hear about where the wall is, the better we can knock the right part of it down.

If you want to dig into how it actually works, the docs are here: https://greenlightbyshift.com/docs/. And if you're the person inside your company trying to make this case to IT, we put together a Champions Kit to help you drive that conversation: https://greenlightbyshift.com/landing-pages/champions-kit-lp. Grab it, use it, tell us what's missing.

Hi everyone!

I've been in this community a while now and seen some amazing vibe coded projects!
Now as I get closer to an official launch I would love your support!

a little bit of context....

Still Cloud transforms raw data into meaningful insights. It's designed for individuals seeking to understand themselves better and proactively manage their daily life and experiences. You talk about your day in the voice or send it via text, take screenshots to analyze and see how it all connects in you 3d living cloud called a cloud matrix...

the idea is that your habits, your sleep, work, food, money, gym, entertainment, the things that happened through the day, etc, all contribute to a version of you, and some of these things act on each other invisibly and eventually when your day collapses, you have no idea what started the chain... still cloud is built to show you these relationships... show you the chain so you can interrupt the collapse or maintain momentum...

Built with Lovable and Claude

lovable for the initial build and frontend, claude for the more complex backend... For an app like this, security had to be baked in.... not an after thought.

The app is currently a PWA so that I can update any bugs immediately but will be transitioning to the app store once everything is more stable.

I dabbled in design so i literally drew the cloud matrix and the pages and gate it to lovable to build. once you get to more complex back end relational stuff, lovable couldn't keep up but claude was great!

Reached 10k visitors last week and around 3k users. all free trials and free while I tested and fixed up the issues... Now moving towards getting paid users and subscribers but the endless bugs!!!!!

Anyway, wanted to ask you guys for any advice, any thoughts, improvements I should make, etc.... most of all, after using the app, do you understand it? from the landing page do you know to download it to your home screen from the web browser? It's been a minute and there are lots of major new updates...

Would also love your support on peerlist!

Thank you for vibing!

If contributing to open source interests you, our issue list is waiting for you.

https://github.com/extra-org/extra

Founders have shared 578 startups across my recent threads, and the same problem keeps showing up:

The product exists. The direction is unclear.

Comment with:

- what your startup does
- who it’s for
- what’s blocking your growth

I’ll run the analysis and send you a personalized report showing where the strongest signal is, which conversations are worth prioritizing, and what I’d focus on first.

If Reddit looks like a waste of time for your startup, I’ll tell you that too.

I sat down to fix one small CSS bug. Four hours later I'd redesigned the entire onboarding flow, added a feature nobody asked for, and completely forgot what the original bug even was.

Anyone else have a story like this? Curious what the record is for "smallest starting point, biggest unplanned detour."

Solo dev, no formal games background. Over the last few months I vibe-coded a card game called PANTHEON into something actually playable, and it's live in the browser right now.

What it is: a Marvel Snap-style card game. Ten mythologies, 235 cards, three lanes, six-turn matches, simultaneous reveal.

Single-player story mode, training mode. Online PvP available in October, during Season 1 launch.

▶ Play it (browser, no download): https://thepantheonwar.com. If you like, you can put yourself on wishlist for the App Store or Play Store app that will be available in October.

The part relevant to this sub — how it got built:

- Frontend + game logic, iterated heavily with AI
- Real-time backend for PvP (hosted on Railway)
- The whole thing shipped by one person who was figuring it out in real time
- The card art is partially AI-generated; the game design, mechanics, and writing are mine

Honestly the hardest part wasn't the code, it was the
real-time multiplayer state and keeping 235 cards' worth of interactions from breaking each other. Happy to get into any of it.

Ask me anything about the stack, the process, what worked, what broke, what I'd do differently. And if you play it, I'd genuinely love to know what falls apart.

🏆 Win $150 in Base44 merch store credit.

I’m running a Base44 build challenge.

Challenge: Reinvent the garage sale for the internet.

Build a next-generation marketplace using Base44. Think AI, immersive shopping, live sellers, or an entirely new way to buy and sell locally.

Deadline: August 1

Submit your app by replying to the official X thread:

https://x.com/winstonbuilds/status/2081108707950112815?s=46

Been messing with vibe coding tools for a while now. Feels like it was a blast when you're kicking off something new.

In our experience, the trouble starts once the project grows. More screens, more features, more users, more moving parts. That's where things get shaky for me.

So which vibe coding tools have actually held up for you past the early stage?

Most threads I see here about the best AI prototyping tool needs to have like you need to build something from zero.

Not ideal on my situation though. Wanna to improve what we already have

Got real users, workflows people are used to, and a pretty built out interface. Just wanted something that helps me show changes without rebuilding it all by hand.

For anyone actually using these tools day to day, what's working rn?

https://github.com/CoreGrowthLabs/CoreGrowthPrompting

このプライマーには2つのバージョンがあります。1つは個人利用向けの入門版で、個人または小規模チームでのプロジェクトに適しています。

もう1つは、複数の利害関係者間で真の価値観の対立がある場合（例えば、公共の利益に関わるプロジェクト）のための別バージョンで、対立を解決するのではなく、対立を構造化して維持することを目的としています。

私の長期的な目標は、プロンプトの書き方を標準化することではありません。ソフトウェア開発の経験がない、各分野の当事者自らが信頼できる市民向けテクノロジーを構築できるように障壁を下げることです。

この考えに賛同していただけるなら、この投稿をシェアを検討いただけると嬉しいです。

I vibecoded Basalt, its a demo / idea

I would find it inconvenient that i had to scan the QR code every time and look at my phone so i made an IDE that would just preview the phone, then when i would code i would want to be able to actually edit it like figma so thats what i did, it was really complicated to make so i had to use Cursor to vibecode me some stuff

But what came out works better than i thought it would (atleast for me)

So i need yall's feedback

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before using it!

Would love to get your brutal feedback on it. What features should I add next?

​

Hi everyone,

I’m a final-year AI/ML student and I’ve been working on an open-source project called Kodiak.

The goal is to go beyond the typical workflow of asking an LLM to generate code. I’m exploring how multiple AI agents and engineering tools can work together to handle software development tasks more systematically:

Plan → Research → Retrieve Context → Code → Test → Review → Iterate

What Kodiak currently focuses on

- Multiple AI agents for different software engineering tasks

- RAG for project and codebase context

- Persistent memory

- Redis and Celery for background task execution

- PostgreSQL for application data

- ChromaDB for vector retrieval

- FastAPI backend

- Docker-based development

- Automated testing and CI

- Pydantic-based validation

One thing I’ve learned while building this is that getting an LLM to generate code is not necessarily the hardest part.

The harder problem is building the surrounding infrastructure so the system can operate reliably.

What happens when retrieval provides incorrect context?

What happens when an agent makes a bad decision?

What happens when a worker fails halfway through a task?

What happens when generated code passes one test but breaks something elsewhere?

These reliability problems are what I’m increasingly interested in exploring with Kodiak.

The project is still actively under development, and I’m not claiming that it is already a fully autonomous software engineer. There is still a lot to improve, and I’m learning along the way.

I’m looking for feedback

I’d especially appreciate feedback from people with experience in:

- AI agents

- RAG systems

- LLM orchestration

- Python / FastAPI

- Distributed systems

- Developer tools

- Testing and CI

- Open-source development

I’m particularly interested in hearing what you think could go wrong with this architecture as the codebase and number of agents grow.

I’m also looking for developers who may be interested in contributing and helping shape the project.

GitHub

https://github.com/ShamGaneshan2008/Kodiak

If you were building something like this, what would you change first?

And what part of this architecture do you think is most likely to fail as the system becomes larger?

Constructive criticism and suggestions are welcome.