r/VibeCodersNest

I developed an LSP, VS-Code extension and NPM package, please try it out and give me your thoughts!

I'm building Company Brain OS — a unified operating system for businesses that brings every department and workflow into a single, interconnected dashboard.

No more switching between 12 different tools. Sales, HR, finance, projects, communications — all connected, all in one place. Each module talks to the others, so your data actually works together instead of living in silos.

Would love feedback from anyone who's felt the pain of managing a company across too many disconnected apps.

Most founders who hire me are in trouble. They built something with AI, got real users, and now the app is leaking money, leaking data, or both. By the time I get the DM, the app is 6 months past the point where things could have been done cleanly.

Last month was different. A founder reached out for an audit before anything broke. Lovable build, Supabase backend, 30 paying users, charging $19/month, growing about 4 users a week. Total annual revenue at the time was around $7,000. She paid me $1,500 to audit her app before she pushed past 100 users.

That is not normal. Most vibe coders at her stage are still in growth mode, throwing every dollar at ads and features. She paused to invest in engineering hygiene before her revenue justified it. I have done 30+ vibe coded rescues this year and she is the only one who came to me proactively. Wanted to share what set her apart because most of it is mindset, not money.

She treated the AI build as a prototype, not a product. Most founders ship with vibe coding tools and quietly treat the output as the real thing. They run ads, hire support, scale paid users, then panic when the app cracks. She launched her Lovable MVP knowing it was a prototype. She had it written in her launch plan that the rebuild would come when revenue justified it. She did not pretend the AI had given her a production system.

She validated before she scaled. She did not buy ads or chase growth before she knew the product worked. She onboarded users manually for the first 30, talked to each one personally, and only opened up signups once retention was real. By the time she came to me, she knew exactly what was working and what was not. Her audit brief was sharper than most senior product specs I have read.

She tracked the failures the AI could not see. She had a spreadsheet of every weird thing she noticed in her own app. Slow loading on mobile. A user who could not reset her password. A Stripe receipt that sent to the wrong email once. A signup flow that broke on Safari. Most founders ignore these as one-offs. She tracked them and brought them to the audit. Almost every one turned out to be a symptom of a real bug in the codebase that would have killed her at 500 users.

She paid for the audit before she paid for the rebuild. This is the one almost nobody does. Most founders rebuild based on what the AI tells them needs fixing (usually wrong) or based on what a freelancer tells them (usually self-serving). She paid for an independent audit before committing any money to a rebuild. The audit revealed that 60% of what she thought needed rebuilding was actually fine. The other 40% was worse than she thought. That changed her entire rebuild plan and probably saved her $15,000.

She planned for the rebuild in her financial model. She had a column in her cash flow projection labelled "Rebuild Reserve." Every paying user contributed a fixed percentage to this reserve. By the time she crossed the threshold where the rebuild was needed (around 200 users), she had the cash for it. Not from raising, not from credit, not from cutting corners. From revenue. Most founders treat the rebuild as a surprise cost. She treated it as a planned expense from month one.

She did not get attached to her stack. She knew Lovable was the right tool for the prototype phase and that Next.js + Supabase was the right tool for the production phase. She did not see the rebuild as a failure of the original build. She saw it as the planned next step. Founders who get emotionally attached to "I built this on X platform" are the ones who stay on the platform too long and pay 10x to migrate later.

The lesson I take from her, that I wish every vibe coder understood.

The build is not the product. The product is the thing that survives 6 months of real users. The build is the first draft. Smart vibe coders ship the build fast, validate it cheap, and rebuild it properly when the data justifies the investment.

The opposite, which is most founders I see, is to ship the build and hope it survives forever. It does not. Real users break things. The question is whether you plan for that day or get blindsided by it.

She is not getting blindsided. Her audit took 4 days. Her rebuild will take 8 weeks. Her users will never know the difference. That is what good looks like.

jetbuildstudio(dot)com/mvp

Here is the website: https://deckk.app/

I built an AI-powered presentation generator called Deckk. I know there are already many tools in this space, but Deckk focuses on simplicity and speed. The platform is still in development and currently includes a few basic templates to help users create presentations within seconds, without unnecessary complexity.

Many presentation tools today are packed with advanced features, widgets, and content options, which can make even creating a simple deck feel overwhelming or time-consuming. Deckk takes a different approach. It helps you quickly generate clean, usable presentations that are ready to work with immediately. If needed, there are also tools available to further enrich and customize your slides.

The goal of Deckk is straightforward: help users build presentations fast, without spending too much time learning or navigating the platform.

It’s still quite basic at the moment, but I plan to continue improving it by adding more features and making the platform richer, smarter, and more useful over time.

Tools used: Cursor (mostly) and some basic hands-on coding on Pycharm.

Let me know your thoughts. Please don't be hard on me. 😄

Built a yes/no voting site for startup ideas. Free to vote, $4.99/mo to post your idea and get real feedback.

Stuff that surprised me while building it:

• SQLite on a cheap VPS is completely fine for an early product. I was way overthinking the database situation.
• next-auth v5 has basically no real documentation. Had to figure out a lot by trial and error.
• Stripe was somehow the easiest part. Had it working in like 30 min.
• Email verification has way more moving pieces than it should for something so common.r

Would love brutal feedback — on the idea, the UX, the pricing, anything.

https://rate-my-startup.com/

Built a working prototype of a social sports betting league app — looking for a technical cofounder who’s shipped before

The idea is simple — football fans form clubs, pool money together on betting slips, compete in a league system with promotions and relegations, and share the wins and losses on a social feed. The drama is half the fun.

Starting in Ghana but honestly the model works anywhere people watch football and bet together which is everywhere.

The business model is clean. Captains collect pool money directly through their own mobile money — the app never touches any funds. KIN just tracks everything, calculates the captain’s 1% coordination fee, and manages the community. Revenue comes from subscriptions. No licensing headaches because no money ever flows through the app.

The prototype works. It’s not just a figma file or an idea — there’s a real codebase, a private GitHub repo and a demo I can show you.

What I’m looking for is someone who has actually shipped an app before. Not just built one, shipped one. Ideally you’ve worked on something social or fintech related.

If it sounds interesting just DM me

I'm a solo developer and I've been building TourKit for the past 3 weeks. Here's an honest breakdown of what I built, what broke, what I learned, and whether I should launch on Product Hunt.

What I built:

TourKit — a lightweight product tour SDK. One script tag, dashboard-controlled tours, works on any stack.

The core idea: most onboarding tour tools are either too expensive, too heavy, or require installing a library. I wanted something you could drop into any website in 5 minutes.

Stack I used:

- Next.js (App Router) — dashboard + docs + landing page

- Supabase — auth, database, row level security

- Vanilla JS SDK — no framework dependency, bundled with esbuild

- Vercel — hosting and deployments

- Anthropic API (Claude) — AI tour generator for Pro users

---

Biggest bugs I hit and fixed:

1. React 18 StrictMode double injection — SDK was loading twice causing overlapping tooltips. Fixed with an ID guard on the script tag.

2. localStorage seen flag — completing a tour on / was blocking tours on /dashboard. Fixed by making seen flags path-scoped (tourkit_seen_KEY_dashboard instead of tourkit_seen_KEY).

3. Client-side navigation — Next.js and React change URLs without reloading. SDK wasn't detecting this. Fixed by exposing a window.TourKit global API and calling TourKit.startFor(pathname) on route change.

4. Demo mode — needed tours to replay on every page in the sandbox without affecting real user seen flags. Fixed with a demo flag that skips localStorage writes entirely.

---

What I shipped:

- One script tag SDK (HTML, React, Next.js, Vue compatible)

- Dashboard to build and manage tours without redeploying

- URL-based tour triggers (context-aware tours per page)

- Analytics — starts, completions, skips, step drop-off

- Multi-page demo sandbox for testing

- AI tour step generator (Pro feature, powered by Claude)

---

Current status:

- Fully working and tested across React, Next.js, plain HTML

- Free plan: 1 project, basic analytics

- Pro plan: $19/month — unlimited projects + AI generator

- Live at: tourkit-phi.vercel.app

---

My honest questions:

1. What's missing that would make you actually use this?

2. Is $19/month reasonable or too high for a solo-built tool?

3. Should I launch on Product Hunt now or keep building?

Happy to share more about any part of the build. This community has been super helpful watching others build — figured it was time to share my own journey. 🙏

Hi everyone,

Over the past couple of months I've tried bootstrapping applications a few times with AI. I would typically spar with chatGPT a few times and then get it to output text documents that give information about the product or business, and another that contains a plan. I then get a coding agent to implement the plan phase by phase.

My most recent attempt is something I will probably end up releasing for real. I tried even harder to keep some guardrails in place, to really come up with a structured approach for building out various features for an MVP - all while still trying to get AI to do most of the work autonomously. The plan was to review the product first, and then once the product is acceptable, review the code behind it.

The other day I started that review, and oh boy this thing is quite the monstrosity.

There's a ton of taglines and copy all over the application that's unnecessary and sounds really try-hard, clearly AI written.

There's things on nearly every page that looks like a feature, however it turns out it's hardcoded. A user is displayed with a title behind their name, but there's no title field anywhere in the database (and we don't even need to display a title, it makes no sense). There's a "readiness check" somewhere that could be interesting at some point... but not for an MVP, and not if it's hardcoded in the markup.

The list goes on.

I'm just curious, how does everyone else start these projects from scratch and ensure that the things that get built are real, and necessary for an MVP to begin with?

My current plan is to move it all into a "legacy" folder or something, so it can be references... but otherwise just start over and hold it's hand. I'd go through it like a real user would, from registration and sign-in, through onboarding, and really using the application. Basically laying out the rails in front of a moving train, building the next thing a user would use but doesn't exist yet.

It's quite unfortunate because none of this stuff is really that mind blowing, but I just can't seem to stop AI from building mockups rather than proper services. I need better guardrails, or a better approach.

EDIT:

In case the problem I'm running into wasn't clear, here's an example I posted in a comment:

Let's pretend I'm building a social network. There's a phase for registration and authentication, a phase for "friends", etc. We then get to the phase for a timeline, and at that point AI might implement a model for posts, the views to create a post, and the timeline view. However for some reason it seems it might then also start adding sections on the timeline with stuff like engagement statistics... which is great and all except that's a feature that is so far out of scope of an MVP I'm not even thinking about it at all, but what's worse is that the statistics are simply hardcoded - based on nothing. It's just text on the page.

I was surfing through founder interviews on YouTube and found a nice concept which I couldn’t build even if somebody told me the idea first. The reason was I found it super niche and seasonal.
But this guy built a mobile app around it and hit 38k downloads in 6 months while doing $20k per month.

The app (CutCoach) is for combat sport athletes, wrestlers, MMA fighters, and boxers. It creates science-based weight-cutting protocols, tracks nutrition, logs meals, and tells you exactly what to eat to hit your fight weight without crashing.

He found the idea from his hobby as a wrestler.

From most of the videos I watched I found a pattern that ideas comes from real pain you already feel every single day. He didn’t chase trends; he fixed something that annoyed him as a wrestler. This is a reminder of the age-old advice: solve your own itch.

“go broad so you have a bigger market(TAM).”

This proves the opposite: the narrower and more painful the problem, the more loyal and willing to pay your users become. Seasonal? Still worked because the audience cares deeply when it matters.

Ship as fast as possible.

I think this is the best advantage founders have right now.
He used AI tools to go from idea to working app in weeks instead of months.

Talk to your people

He marketed inside wrestling/MMA communities and with small influencers.

And the key lesson for aspiring founders here is that, going as niche as you can is worth it.

Share your app idea (or the annoying problem) here.
Let’s see what useful ideas people drop and learn from each other.

Feels like every founder online talks about growth channels that worked 😅

But honestly I’m more curious what’s ACTUALLY working right now for SaaS in 2026.

Not theory.
Real users.
Real signups.
Real paying customers.

What channel brought you the highest quality users lately?

• SEO?
• Reddit?
• X/Twitter?
• TikTok?
• YouTube?
• Cold DMs?
• Partnerships?
• Product Hunt?
• AI search?
• Communities?
• Something else?

I keep seeing products go viral and still struggle with retention/conversion…

while some boring niche SaaS quietly grow with almost no audience.

Curious what’s genuinely working for people right now and what completely stopped working too 👀

A few weeks ago I missed a Claude release. Didn't know it had dropped until days later, when I'd already posted about something else on Instagram. Felt late, felt dumb, deleted the story.

That's when it hit me, I'm probably not the only one. Most of the people building things with AI right now aren't engineers; they don't live on Twitter or in Discord servers tracking lab announcements. They find out days later, like I did, and feel like they're falling behind.

So I'm a solo founder building something for people like me. Before I commit deeper into the design, I want to make sure I'm not just building it for myself.

5 multiple-choice questions, 3 minutes. Reply with letters (e.g. "B, top2: BD, top2: AC, B, A"). Brutal honesty welcome.

Q1: Which one are you?

• A — Developer / engineer working with AI APIs regularly
• B — Non-technical builder (founder, designer, marketer, vibe coder) shipping things with AI
• C — Curious about AI but not actively building with it
• D — Other (mention in comment)

Q2: How do you currently keep up with new AI releases? (pick top 2)

• A — Twitter / X
• B — Reddit
• C — YouTube / podcasts
• D — Newsletters (mention which if you'd like)
• E — Hacker News
• F — Lab blogs directly (Anthropic, OpenAI, etc.)
• G — Through friends / Discord / Slack
• H — I don't really try to keep up

Q3: When a new AI release drops, the hardest part is — (pick top 2)

• A — Knowing whether it matters at all
• B — Understanding what actually changed
• C — Cutting through hype
• D — Knowing how it affects what I'm building
• E — Finding time to read about it
• F — Following the technical depth
• G — Not getting lost in jargon

Q4: Same release, three formats. Which would you actually read?

• A — The 5-second one:
  • Anthropic just made Figma optional. Claude Design lets you drag-and-drop a website together while Claude writes the code. Available to all Pro/Max/Team users.
• B — The structured one (30 seconds):
  • Anthropic shipped Claude Design, a visual coding tool.
  • WHAT IT IS: Drag-and-drop editor; Claude writes code underneath.
  • WHO IT'S FOR: Builders without designers on staff.
  • WHAT IT REPLACES: The Figma → export → code → iterate loop.
  • WHAT TO WATCH: Pricing for non-Pro tiers.
• C — The 800-word analysis:
  • [Imagine a full essay covering background, what shipped, technical details, market positioning, competitive context, what it means for designers vs builders, what's likely next from Anthropic and competitors.]

Q5: Same release, three voices. Which would you keep reading?

• A — The smart friend:
  • Wait, what?! Anthropic just shipped a design tool — and Figma's been put on notice. If you don't have a designer, this is the moment your workflow changes.
• B — The neutral journalist:
  • Anthropic announced Claude Design today, a visual coding tool integrated with Claude Opus 4.7. The product targets users without dedicated design resources.
• C — The analyst:
  • Claude Design represents Anthropic's first move into the design-tool category, signaling a strategic expansion beyond pure model capability into workflow-adjacent products.

Optional brain dump: What do you wish AI coverage actually told you that nobody does?

Thank you.

been using claude skills for a while now and a few things tripped me up that i didn't see mentioned anywhere so putting them here.

the description field is everything. i kept building skills that weren't triggering and every single time it came back to a vague description. claude reads that field to decide whether to load the skill or not. if it's too generic it never fires, if it's too broad it fires when you don't want it to. i spent way more time than i should have tweaking the actual instructions when the real problem was one sentence at the top.

there's also a 200 character limit on that field. roughly two sentences. if you don't know it exists you'll write something longer, it gets cut off silently, and the skill behaves unpredictably.

a few other things worth knowing:

if your skill isn't triggering after upload, check if code execution is enabled in settings. custom skills need it on. wasted time debugging a perfectly fine skill because of this.

disable-model-invocation in the frontmatter does nothing on Claude AI web interface. it's claude code only. if you add it thinking it'll stop auto-triggering on the web it just silently ignores it.

when zipping the skill, zip the folder not the contents. loose Skill MD at the zip root doesn't work. the folder needs to wrap it.

and skills vs projects, worth being clear on before you start building. skills load automatically across every conversation. projects are scoped to one ongoing context. people mix these up and then wonder why behavior is inconsistent.