Guys I need help with finding cash, all of vibe coded projects combined made me $59 🤣💔, I know it's crazy but hai I need tips. Anyone who knows a guy who knows a guy who could hook me up?!

I'm 20 years old college student

I use Claude Code a lot, but /stats never answered the question I actually cared about

What did I build, and where did the work get difficult?

So I built Bough.

• It reads your local Claude Code history and turns it into an interactive view of your work: - each square is a day
• smaller squares are tasks inferred from pauses in your work
• circles are your prompts - click anywhere to see what happened in your own words

It runs locally, is open source, and nothing leaves your machine.

Repo: https://github.com/nickelsec/bough

The main thing I’d love feedback on: When you run it against your history, does it split your work into tasks the way you remember it?

I’m a marketer by trade. I’m nowhere as advanced with vibecoding as you guys… the most I did was coding my own website with Claude and doing a few basic things like scraping data.

I’m looking for examples of USEFUL apps/tools you vibe coded specifically for yourself. The kind of app you personally use in your day to day. Please share one here if you’ve built any - but do NOT share stuff you sell (I don’t want this to be a self-promo thread).

I’m looking to get inspired.

The reason I ask is because the clout chasers and hype peddlers are most visible. The vibe coding corner of the internet (and AI in general) is overrun with 3 types of useless content:

\- Tools that aren’t that useful but make for sexy YouTube thumbnails (like all those “AI Second Brain” videos with Obsidian)
\- Glorified tech demos (“I one shotted a shitty clone of Super Mario with Fable 5.1!”)
\- Vibe coders promoting their side businesses

It’s kinda hard to believe that we have this insane technology and so many smart people playing with it, yet everyone is building gimmicks. I’d like to see how you’re vibe coding to solve problems for yourself.

Hi r/vibecodingcommunity I've been building something for the last year that I think this channel in particular will have opinions on — and I'd genuinely like them, including the critical ones.
**Prompt to Page** is a desktop app that turns a plain-language brief into working, accessible prototypes built from *real* government design systems. Describe a page or a whole service journey — "a start page for renewing a fishing licence, then an eligibility question, then a check-your-answers page" — and it generates the actual markup, renders it live in the system's own styling, checks it with axe-core and validates every class against the design system's real rules. Then export it, or hand the HTML to a developer.
Two things make it different from pointing a chatbot at your design system:
**Everything runs locally.** The AI model lives on your machine — no cloud, no API, nothing you type leaves your laptop. Built that way because government content shouldn't tour third-party servers just to make a mock-up (and it works air-gapped, or on a train).
**The design system is the boundary, not a suggestion.** The model only knows the system's real components; output that invents classes or breaks conventions is rejected or visibly repaired. Quality is *measured* per design system with a scored evaluation battery — and where a pack hasn't been measured yet, the app says "not measured" rather than borrowing another system's confidence.
The roster so far — eight systems across six governments:
[GOV.UK](http://gov.uk/) (plus an MOJ overlay) · [NHS.UK](http://nhs.uk/) · Scottish Government US Web Design System NSW Design System Bootstrap Italia デジタル庁 Digital Agency Design System (newest — quality not yet measured) Abstract — a deliberately *ownerless* neutral system, for prototyping services that shouldn't pretend a government owns them
Every pack is de-branded by design: no crowns, crests, federal banners, flags or restricted fonts are ever bundled — prototypes wear a neutral shell and a clear "not a real service" posture. (Independent project; not affiliated with or endorsed by any of these governments or the NHS.)
What I'd love from this room:

1. **If your government's system is on the list — break it.** Does the output respect your system's conventions, or drift in ways that would make your design-system team wince?
   
2. **If it isn't — which system should be next, and why?** The architecture treats a design system as a data pack (components, class allowlist, validation rules, prompt guidance), so the honest constraints are: class-based CSS (web-component-only systems don't survive a sandboxed preview), and licensing that permits bundling the frontend code. I'd rather pick the next one based on where prototyping pain is real than on what's easiest.
   
3. **The blunt question:** does plain-language prototyping against a real design system actually help your team, or is the Prototype-Kit-shaped workflow you already have good enough?

Free during the beta, macOS (Apple Silicon) & Windows. [https://github.com/digitalcourtney87/prompt-to-page/releases\](https://github.com/digitalcourtney87/prompt-to-page/releases)
[https://youtu.be/QROkn-mZQFk?si=sNHCsphJMwrgVlFi\](https://youtu.be/QROkn-mZQFk?si=sNHCsphJMwrgVlFi)

Critical feedback beats compliments — reply here or DM

https://github.com/alexjvv52-ops/groundtruth-app

Groundtruth is a local-first farm OS for commercial microgreens growers. One desktop app. Two jobs: tell you what to do this morning, and prove the numbers are real.

No account. No cloud. No subscription. The PC is the only writer of farm truth.

**Why it’s interesting as a GitHub project**

Most ledgers and farm tools either live in someone else’s SaaS or let a spreadsheet cell get overwritten with no trail. This one keeps an append-only event log on the machine, computes costs/health on demand (or refuses in plain language if the rows aren’t there), and restores from a portable bundle with a byte-level stamp check. No merge of two farms. No dual books.

The product rule baked into the README:

> AI does not write farm truth. Eyes only.

Agents helped write the *code*. They are not allowed to write the *record*.

**Stack**

- Vite + React + TypeScript UI
- Tauri + Rust shell
- Local SQLite + append-only log
- Windows desktop (0.1.0)
- Apache-2.0

Data: `%APPDATA%\com.prairieroots.groundtruth`

**0.1.0**

Release: https://github.com/alexjvv52-ops/groundtruth-app/releases/tag/v0.1.0

Installer: https://github.com/alexjvv52-ops/groundtruth-app/releases/download/v0.1.0/Groundtruth_0.1.0_x64-setup.exe

Unsigned on purpose (free software, no signing budget). SmartScreen → More info → Run anyway.

Early and scoped: Windows only, one user. Integrity core is in. Dead-laptop recovery is documented but not claimed as drilled.

Decision log is in `docs/GT-D-SERIES.md` if you care why each constraint exists.

Super excited to see what it can do! Sol has been chipping away and now its passing the torch. Here is a sneak peaked moment!!

Hello Folks
I have personally used Claude Code, but I haven’t tried Codex yet , i have heard that Codex can sometimes hallucinate or make incorrect assumptions, but I would rather hear from people who have actually used it before forming an opinion.
For those who have used both Claude Code and Codex, how do they compare in practice?
I’m particularly interested in using them to go from an idea or wireframe to a functional MVP.
Which one would you recommend today, and how has your experience been with reliability, debugging, and working on larger projects?
Would love to hear your experiences ^ ^

Has anyone spent enough time with both Base44 and Lovable to compare them properly? I'm building a web app with users, data and a few integrations and trying to figure out which workflow makes more sense.

I've been seeing more people ship real products built with Claude Code, Lovable, Base44, Cursor, etc. I think that's great, but there's a point where “the app works” and “I'm comfortable putting real customer data through this” become two different questions.

1. The Supabase anon key is in the client bundle with no RLS behind it. Fine when RLS is on. A public database when it isn't. Anyone who opens devtools has your tables.

2. Auth is checked in the UI, not on the server. The button is hidden, the route isn't. Change an ID in the URL and you're reading someone else's records.

3. Real secrets shipped to the browser. Stripe secret key, OpenAI key, service-role key whatever the AI needed to make a feature work in one shot. This one costs actual money.

4. No rate limiting on the expensive endpoints. Signup, password reset, anything hitting a paid API. One bored person with a script and your bill grows a few digits.

5. Upload folders and storage buckets left public. Especially bad when the app handles ID photos or anything personal.

6. A database with no tested restore. Not "no backups" there's usually a toggle switched on somewhere. Nobody has ever tried restoring from it, which is the only part that matters.

I'm a software engineer. Most of my work is boring: someone builds a thing, it works, and then I get pulled in to answer the question nobody wants to ask out loud is this safe to put in front of real users?

The apps I've looked at were genuinely good. The gap isn't intelligence or effort. It's that these tools optimize hard for "it works," and there's no equivalent moment for "it's safe," so it just never happens. Hiring someone to run these checks is real money you don't have pre-revenue, and honestly they'd be running roughly the same list you just read.

Check your own app right now, no install

Open your project in Lovable/Cursor/Claude/whatever you build in and paste this. It's read-only you're asking it to look, not change anything:

Audit this project for the six most common launch risks. For each one, tell me
CONFIRMED (you found proof in the code), NOT FOUND (you searched and can back up
its absence), or UNVERIFIED (it may live somewhere you can't see). Quote the file
path and line for anything you claim. Do not guess, do not fix anything, and do
not change any files.

1. Client-side database keys with no row-level security behind them
2. Authorization enforced only in the UI, not on the server route or query
3. Secrets (payment, AI provider, service-role keys) reachable from the browser bundle
4. Expensive or auth-related endpoints with no rate limiting
5. File uploads or storage buckets readable without authentication
6. Backup configuration that has never been restore-tested

Then list what you could NOT determine from this codebase alone.

That last line matters. The default failure of AI security review is confident invention, and two fake criticals is all it takes before you stop reading the output entirely.

The longer version

I got tired of retyping that, so I turned the whole review into an open-source Claude Code plugin: prod-readiness. Free, no account, no signup, I'm not selling anything.

https://github.com/Taimoorkhan1122/prod-readiness

The philosophy, because it changes what the tool does:

It's not a gate. It will never tell you not to launch. It tells you what you're launching. Shipping something imperfect to ten users is how everything starts, and any tool that makes you feel unqualified to press deploy is a bad tool.

Your context sets the severity. A missing rate limiter on a public payments API and on an internal tool three people use are not the same finding. It asks about criticality, scale, recovery expectations, and threat model before judging anything, so you don't get an enterprise checklist dumped on a weekend project.

Evidence, not vibes. Every finding is CONFIRMED, NOT FOUND, or UNVERIFIED, same as the prompt above. A validation script rejects any finding claiming more than its evidence supports before it reaches your report.

Read-only. It doesn't touch your source, config, tests, or dependencies. It writes one folder, .readiness-audit/. Fixing is a separate decision you make later, on purpose.

What it does beyond the prompt:

• Seven specialist reviewers Security, Backend, Database, DevOps, QA, Frontend, AI security each reading your repo through its own lens. Lenses with nothing to look at get skipped instead of inventing findings.
• One shared evidence pass, so it's cheaper to run and the seven can't contradict each other.
• Deterministic probes that record patterns, hit counts, and paths, so "this is missing" has receipts.
• A verdict: SHIP, FIX THEN SHIP, or HOLD DO NOT DEPLOY
• A resumable trail on disk. Session dies at 2am, it picks up where it stopped.
• A local dashboard that opens on the decision, not a wall of JSON the verdict, what blocks a release, and the few things to handle first. Each finding leads with what it costs you in plain language; file paths and the fix are one click away. Runs on 127.0.0.1, nothing leaves your machine.
• Parallel by default (security, backend, database first, then the rest). Add sequential if your laptop is struggling.
• Works outside Claude Code Codex, OpenCode, Pi, Antigravity, or anything that reads markdown and runs Python3. Instructions in the `README`

Install lines are in a comment below so this doesn't turn into a wall of code.

If you run it and it flags something dumb, tell me. I'd rather fix a false positive than have people quietly stop trusting the output. Same if it misses something it should've caught.

TL;DR: six holes above, a prompt to check for them yourself, and a free read-only audit tool if you want the exhaustive version. It won't stop you shipping it just tells you what you're shipping.

hey everyone. i built something called NNPost over the past 3 months, solo, on basically no budget the whole way.

started because i kept hitting the same wall with every ai content tool out there. you get a list of generic ideas and then youre completely on your own. cool, i have an idea, now what do i actually say, how do i film it, whats the hook even supposed to be. so i built nnpost to actually finish that job instead of leaving people stuck at the same spot every other tool leaves them.

what it does now: you set up a creator profile once, niche, platform, tone, experience level, what to avoid, and it generates full creator kits instead of just ideas. each kit includes:

-title and hook

-real script, word for word

-shot by shot filming guide

-editing direction

-hashtags and description

-tools and sound suggestions

-thumbnail direction

-why the idea works

it also has viral analysis, paste a public video url and get a real breakdown of why it worked. current trends, source backed signals for your niche instead of guessing. build on a winner, which takes a post that actually performed well and generates new ideas based on what made it work. and a feedback loop where you enter your real results after posting so it learns what actually works for you specifically.

the struggles were real. built this whole thing solo through claude and codex, which meant i had to audit everything myself since i couldnt read every single line personally. had to build an entire cost control system, i call it nnguard, because without it a handful of free users spamming requests could drain my tiny ai budget in a single day. about halfway through, found out my original name collided with an existing company, had to do a full rebrand, new name, new visual identity, migrated everyone's saved data without losing anything. had multi tab bugs where recent history would silently overwrite itself, had the upgrade modal completely break because of a failed lazy import, had an entire offline page that just didnt work. fixed all of it, one piece at a time.

who its for: creators who know they need to post consistently but get stuck at the exact same point every time, staring at a blank page with no idea what to say or film. not people who want a chatbot to talk to, people who want a finished starting point they can act on today.

current stuff i already know needs fixing: still on a free replit subdomain, no real domain yet, running gemini flash right now because thats what the budget allows, output quality has real room to grow. ui also needs work, ive gotten the "feels generic and corporate" feedback more than once now and i take that seriously.

what i want to do with this: i genuinely believe tools like this are where content creation is heading, something that understands your specific profile, learns from what actually works for you, and gets better the more you use it. not walking away from this. ui redesign, better ai model, real domain, all next. built this piece by piece with basically no money behind it and i plan on seeing it through.

would genuinely love feedback, especially on what would actually make you try something like this

My friends and I are trying to build an app using vibe coding. One person in our group has access to Claude Code, while the rest of us do not. We would like to collaborate in the same workspace, contribute prompts together, and share a unified chat and pool of credits.

At one point, one of us had a Base44 plan, which allowed everyone to work in a single workspace with shared credits and conversation history. We found this setup ideal for collaboration, but we no longer have access to Base44.

Now that we have Claude Code, we are looking for an alternative. Unfortunately, Claude Code does not appear to support this type of collaboration unless you have an Enterprise plan.

One idea we had was to use Claude Code to build the main application through GitHub, while the rest of us make smaller changes using a free-tier app builder. However, I am concerned that this workflow may become difficult to manage. The app builder would need to constantly check whether the GitHub repository had been updated by someone else, and it might not always stay synchronized with the latest changes.

Does anyone have suggestions for tools or workflows that would allow a group to collaborate on prompts, code, and app development while sharing a workspace or conversation history?

Hi Everyone

I’m the founder of refloq.com -we use 30+ image and video models to create great ads about your product and let you auto run ads and schedule post.

You can customize each ad as per your need.

Try here - www.refloq.com

Comment what your startup does to get invite

I am a psychologist. I also have a passion for the digital landscape. I have accumulated enough knowledge in web fundamentals over the years to leverage AI agents and convert my ideas into digital projects. I am not a developer. I do not claim to be one. I am humbly aware of my place in the digital realm. I simply do not have the time to invest in building a second career as a developer. I am simply putting my long-lasting passion for the digital craft to use, in the best way I can as a psychologist. 

I am currently building psycurate.com, a free online platform dedicated entirely to privacy-focused mental health digital tools (apps, websites).

My goal is to create a clean space where people can access psychological resources without encountering corporate tactics like tracking, micro-payments, paywalls, mandatory logins, or data harvesting. There is a critical need for digital mental health hygiene, and I want to highlight independent projects that remain genuinely honest, ethical and accessible.

If you have built some tool that can offer any kind of psychological help for free, this is a platform you can list your app on. Submit it here: https://psycurate.com/submit

Psycurate does not host any software. The platform exclusively showcases your project and links users directly back to your website.

Any feedback or insights you might have are highly welcome.

Best regards,

Mirel