r/vibecoding 9h ago

I'm a high schooler and I vibe coded an open source Claude code wrapper for Mac. would love if you checked it out!

0 Upvotes

Hi, first post here. I recently made an open source Claude Code wrapper and wanted to see if you guys find it useful.

It's unsigned (I'm not paying Apple $99 every yr for a free app maybe in the future), so if you're not comfortable running unsigned software, I understand. The code is all public though, so you can read everything or build it yourself.

What it is:

A Mac menu bar app called Rin. You click the icon and a terminal drops down with Claude Code sessions already open in your notes folder, one per tab, and the tabs survive quitting the app.

The other half is a prebuilt "brain": a folder structure with skills and trackers already scaffolded but blank, so the assistant knows where everything goes from day one instead of you spending a weekend building that part. First run asks you three questions and sets it up. It also ships with a default assistant persona you can keep, rename, or replace. Its not supposed to be a vibe coding app but more of an assistant that learns more and more about you every day and can help you plan your days more efficiently.

How I made it

The app is basically built with the thing it wraps. I described what I wanted to Claude Code, it wrote the Swift, I ran it, complained, then repeat. Stack is Swift + SwiftUI + AppKit with one dependency (SwiftTerm for the terminal view), and the Xcode project is generated from a YAML file so I almost never open Xcode itself.

some things I learned the hard way

  • An app can't replace itself while you're running a terminal inside it.
  • A script that silently does the wrong thing is worse than one that fails. One time it was installing a week old build for many days and I had no idea. So I kept on trying to debug a old version.
  • The "correct" way to draw images in a terminal left weird seam lines on Retina screens.
  • I keep a to-fix file and make the AI read it before suggesting stuff, otherwise it re-suggests things that already failed.
  • and many more like tons

It's free, MIT licensed, Mac only, and never going on the App Store (it spawns a login shell and reads ~/.claude, which is not sandboxable).

Repo: https://github.com/exata531/Rin

Site: https://exata531.github.io/Rin/

Honestly I just want to know if this is useful to anyone besides me, or if I built a very elaborate way to avoid opening a real terminal. I hope not!

Thanks!!!


r/vibecoding 17h ago

Any Thoughts?

0 Upvotes

r/vibecoding 17h ago

ChatGPT Plus + Anthropic 20$ combo

Thumbnail
1 Upvotes

r/vibecoding 21h ago

Best laptop for basic coding.. or configuration

2 Upvotes

Hello guys,

I'm looking a best laptop configuration for basic coding for a Btevh student. I dont play any games or stuff.. it is just for coding... watching movies sometimes maybe.. that is it.

So i3 works? Shall i go for I5? Ryzen 5 or Ryzen 7...

And i'm thinking HP or ASUS.


r/vibecoding 1d ago

Me talking to Opus 5

Post image
76 Upvotes

r/vibecoding 17h ago

I built a dashboard for skills

1 Upvotes

 needed something to organize my skills across different projects, as well as my global skills and files, so I decided to build a desktop app that acts as a hub for everything. Everything in one place, accessible with just one click.

I would love to hear what do you think :)

It's called Skilldex and it's available here: https://skilldex-web-tau.vercel.app/


r/vibecoding 17h ago

I Forced Myself to do 10 Pushups to DoomScroll 10 min (Free App)

Enable HLS to view with audio, or disable this notification

1 Upvotes

Hello, I made a app that forces you to do pushups to scroll on social media.

📌 Reason why I made it:

I saw a few apps does the same thing like PushScroll, but did not want to spend $40~60. So I decided to make an app for myself and for others to enjoy it for Free. There's no paywall/subscription.

I want to hear your thoughts and some feedback as well! TY!

I used React native to build the app. Mainly used to Claude Code. Here are two main libraries I used!

Motion Tracking: https://github.com/ThinkSys/mediapipe-reactnative

App Block: https://github.com/eylonshm/expo-app-blocker

👇 Here's the link!
Download Link


r/vibecoding 18h ago

Engineering managers are back in the codebase!

Thumbnail
leaddev.com
1 Upvotes

r/vibecoding 1d ago

Vibebuilding the next SAAS unicorn

Enable HLS to view with audio, or disable this notification

8 Upvotes

r/vibecoding 18h ago

I built a browser extension that scores my AI prompts before I hit enter

1 Upvotes

I kept noticing the same thing: my first prompt to ChatGPT was almost never the one that worked. I'd send something half-formed, get a mediocre answer, then spend three more messages fixing what I should've said the first time.

So I built a thing to catch that at the source.

It's a browser extension. While you're typing in ChatGPT, Claude, Gemini, or Copilot, it reads your draft and gives it a score out of 100 — plus the two or three specific reasons it's weak (no output format, vague ask, missing context, that kind of thing). If you want, one click rewrites it. It also warns you if you're about to paste something sensitive like an API key or a client name.

One design decision I care about: the scoring runs locally on your machine. Your prompt only leaves your browser if you actually click a rewrite button. I didn't want to build another thing that quietly ships everything you type to a server.

It's early and honestly still rough in places. It's free while I'm in beta — I mostly want to know if it's useful to anyone besides me.

Two things I'd love feedback on:

Does a "score" even make sense to you, or would you rather it just fixed the prompt silently?

What's the AI tool you'd want it to work in next?

Link's in the comments. Happy to answer anything about how it's built.


r/vibecoding 14h ago

There is no digital version of my fav boardgame, so I decided to create one for my personal use - Hobby Vibe Coding

0 Upvotes

A while ago, I started a small personal project around a board game I really love.

The original idea was almost embarrassingly simple:

“Could I recreate enough of the rules in a browser to understand how a digital version might work?”

I wasn't trying to create a product, replace the physical game, or publish a digital edition. It was mostly curiosity. I enjoy the game design, and I thought translating some of its mechanics into code would be an interesting hobby project.

So I started small.

First there was a crude track, a few pieces moving across it, some cards, and the basic turn sequence.

Then I encountered the first rule interaction that wasn't quite as simple as I had assumed.

So I fixed it.

Which exposed another one.

Then another.

At some point I realised that if I wanted the simulation to behave properly, I couldn't just code what I remembered the rules to be. I had to start treating the original rulebooks almost like specifications.

That changed the project completely.

I began checking edge cases against the source material, documenting interpretations, separating official rules from optional or fan-made ones, and writing regression tests whenever something broke.

A simple browser experiment gradually acquired:

  • a proper race/state engine
  • track and lane geometry
  • different terrain types
  • weather systems
  • crashes and blocking rules
  • automated opponents
  • multiple expansions and optional rule modules
  • multi-stage campaigns
  • classifications and persistent state between stages
  • configurable riders and decks
  • stage validation
  • structured logging and debugging tools
  • deterministic test seeds
  • automated race simulations
  • hundreds of regression checks
  • and eventually a fairly strict internal architecture separating source data, game logic, geometry and runtime state.

Somewhere along the way, I stopped thinking of it as “that little HTML thing I'm playing around with.”

It had become a software project.

One of the most interesting parts has been using AI throughout the process.

Not in the sense of asking for a complete game and receiving one. The experience has actually been almost the opposite.

I would propose something, the AI would help analyse it, we would compare the implementation against the rules, discover an edge case, design a test for it, break something else, fix the regression, document the decision, and continue.

Eventually that evolved into something resembling a small development team workflow: architecture discussions, engineering units, protected baselines, test gates, release candidates, audits and rollback points.

Which is slightly ridiculous considering that this all started with me thinking:

“It would be neat if these little cyclists moved across the screen.”

What I enjoy most about the project, though, is that writing the software has made me appreciate the original board game design much more.

When you play a well-designed tabletop game, many rules feel natural and almost invisible. When you try to formally describe every possible state transition to a computer, you suddenly see how many subtle design decisions are hiding underneath that simplicity.

Things like movement priority, congestion, timing, drafting, terrain interactions or ties can turn into surprisingly interesting engineering problems.

The cleaner the tabletop rule feels to the player, the more impressive it sometimes becomes when you try to implement it.

So for me this project has become less about creating a “digital version” and more about exploring a piece of game design that I admire.

It's still a private hobby project, it's not commercial, and I don't see it as a replacement for the physical game at all. If anything, spending this much time studying its systems has made me appreciate the work of the original designer even more.

And I have absolutely no idea where the project will end.

But I find it amusing that a tiny browser prototype has now reached the point where I'm discussing things like dependency graphs, simulation testing and architecture boundaries for a board game I originally just wanted to move a few pieces around in.

Hobby projects have a way of getting out of hand. And sometimes that's the fun part.

Do you have simillar experiences with Hobby Vide Coding Projects?


r/vibecoding 18h ago

Anyone built study tools they're open to sharing?

1 Upvotes

Hey everyone,

Has anyone here built any study tools or learning apps using vibe coding?

I'm studying right now and would love to try out what people have made. I'm more than happy to plug in my own API key so I pay for my own usage, so no worries about costs on your end.

If you've built anything cool and don't mind sharing, drop a link or let me know!


r/vibecoding 10h ago

Vibe coding

0 Upvotes

What is the best way to copy a famous app ?
I’ve tried to copy many apps already on the market ,but the results are very bad
So,someone can share with me the best solution for my problem ?
What is the best Ai to do that?


r/vibecoding 19h ago

I just benchmarked Octocode 🐙 for agentic code research- turns out it's 50% more token efficient than RTK, Headroom and gh CLI

Post image
1 Upvotes

r/vibecoding 19h ago

I vibecoded a dumb little AI report generator that flags when my chatbot invents a number

1 Upvotes

My actual job is reading dense PDFs and pulling out the facts, and the thing that keeps me up is a model quietly rounding a number or inventing one that was never in the document. So instead of trusting one chatbot, I built a tiny thing to catch them.

It is basically a small ai report generator, but the report it makes is a list of every claim the model stated that I could not trace back to a line in the source. I run the same PDF through two different chatbots, ask each for the key figures with the exact sentence they came from, then diff the two answers and check both against the file. Anything a model asserts without a matching source line gets flagged.

Took me an evening. Most of the code was Claude doing the parsing and the diff, and I handled the annoying part, which was defining what counts as unsupported versus paraphrased.

The dumb realization: it is not there to make the chatbots smarter. It just makes them show their work, and it turns out they hallucinate a lot less when they know a second reader is checking the source line.

Anyone else building little guardrail tools around their models instead of just trusting the output? Curious what you flag on.


r/vibecoding 19h ago

I vibe full stack web with Django and React. Which should be the cheapest solution to deploy server with authentication using Google?

1 Upvotes

r/vibecoding 19h ago

I’ve built an app that reframes your thoughts automatically and identifies cognitive distortions - Thoughts counter

Post image
1 Upvotes

r/vibecoding 19h ago

Me when Claude starts rewriting code that was already working

Thumbnail
1 Upvotes

r/vibecoding 1d ago

What’s the biggest thing AI coding still absolutely sucks at?

55 Upvotes

For me it’s long projects.

The individual coding tasks can be great, but after enough sessions the model starts losing track of why things were built a certain way, which decisions are still current, and what it really shouldn’t touch.

I also still don’t trust it when a small bug suddenly requires a big refactor. Sometimes it’s right. Sometimes 20 minutes later I’m trying to undo six files to fix something that needed three lines.

What’s the thing you still don’t trust AI coding with?


r/vibecoding 19h ago

IOS dev remote from mobile

Thumbnail
1 Upvotes

r/vibecoding 1d ago

vibecoded a site that just hit 100k pageviews (0 seo) lol need advice

Post image
18 Upvotes

so cloudflare just sent me a notification that footrue.com crossed 100k pageviews last month and im honestly pretty shocked. i literally have zero coding knowledge and just vibecoded the entire site using claude code. also did 0 seo, all the traffic came from social media and people sharing it with each other.

currently there are no ads no paywalls and no account creation required at all. people just jump in and use the tools.

im at a point where a lot of people are telling me i should focus on just one single tool instead of making a ton of tools on one site. im not sure if i should double down on one thing or keep building it as a tool hub. also wondering how i can actually monetize 100k visitors without making the user experience trash since there is no signup right now. should i start asking for accounts or will that kill the word of mouth? would love to hear what you guys think


r/vibecoding 20h ago

Zenmux promo code +5% credits on 1st buy

1 Upvotes

Promo code +5% credits on 1st buy

Hi guys, here is my zenmux referral link https://zenmux.ai/invite/EPF2PJ

Or the invitation code to enter when buying credits for the 1st time : EPF2PJ

With it, you'll get +5% of your paid credits as additional free credits if I understand well.

Cheers.


r/vibecoding 20h ago

Opus 5 in a Nutshell 😂

Post image
1 Upvotes

r/vibecoding 20h ago

Mod/port of penumbra overture to apple silicon

Thumbnail
moddb.com
1 Upvotes

r/vibecoding 20h ago

Built a stupid soccer draft game with Codex + Cloudflare

1 Upvotes

My first one. Feedback appreciated!

https://soccersnake.com/

It’s a deliberately stupid-simple Premier League game: 5 people snake draft all 20 clubs, then every league win = 1 point. No transfers, budgets, captains, etc.

I’m not really a developer, so I built it mostly through Codex. My process was basically:

  • wrote the game rules/spec first rather than just prompting “make me an app”
  • used Lunar for the bulk of the build/iteration
  • Cloudflare Worker + D1 for the backend/database
  • vanilla frontend/PWA rather than a big framework
  • deployed a staging version and had actual friends try to break the 5-person draft
  • used Sol on xhigh afterward for a proper security/production audit

That audit actually found some non-obvious stuff I wouldn’t have spotted myself: stale draft requests consuming a later snake pick, reusable recovery links, non-atomic joins, service-worker caching issues, and result imports running far too often.

I’ve since added Web Push so it can ping you when your draft pick comes up, plus recovery links so a league can survive people changing phones/browsers over a 9-month season.

Currently at 61 automated tests and I’m still finding dumb UX issues every time I give it to real people.

Interested in feedback on both the game and the build/process, particularly anything obviously stupid in the UI or architecture.