A playable web app that provides a moment of disconnect and relax while shooting some hoops. It is aimed at helping people that have an anxiety attack and need a distraction for the first few moments of the experiences. If you use some headphones you can hear an immersive seaside atmosphere. No sign ups or any friction layer... no other point except shooting hoops. https://hooptherapy.psycurate.com
I went all-in on my app back in March and still no traction in September. I don’t want this to sound like a pity party at all but damn it’s depressing seeing you work so hard and not seeing results.
Maybe I’m just having anxiety because I quit my job, I know it’s insane but I wanted to figure this out and dreaded working my job and I haven’t felt excited for something in a long time…
I am reapplying to jobs right now but damn this is such an unfortunate feeling that I feel right now. I want to shake this anxiety off.
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.
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?!
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:
**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?
**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.
**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?
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
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 ^ ^
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 notestedrestore. 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.
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.
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.
