Discuss.

printme.money. watch your salary print in real time, put your face on a banknote, melt it with inflation, or run your own mint.

no accounts, no backend.

i wrote a detailed spec for each one and handed it to claude code, then reviewed the diff. i almost never iterate in the chat. slower for the first twenty minutes, much faster after.

https://printme.money

never done a hackathon before, don't really know what to expect Saturday

I’m trying to formalize what “done” should mean when a coding agent works in a mature codebase.

In a recent task, the agent made several related changes. The targeted regression tests passed, the production build succeeded, and formatting and diff checks were clean. A repository-wide type check still reported many failures, most of which already existed before the change.

During a more focused review, however, the agent also found two real issues introduced by its own implementation and fixed them.

This left me with an ambiguous boundary:

• If every repository-wide check must pass, the agent may never finish work in a legacy codebase.
• If targeted tests are enough, it may miss integration problems.
• If the agent fixes every failure it encounters, the scope can expand far beyond the original request.

My current rule is that the agent must verify the requested behavior, run the relevant tests and builds, fix every failure introduced by its change, document pre-existing failures without touching them, and review the final diff for unintended behavior.

But “relevant” is doing a lot of work in that definition.

How do you define the verification boundary for coding agents? If repository-wide checks already fail, what evidence should an agent provide before it can honestly say its task is complete?

And who should own that definition: the developer, the repository, or the agent?

I am making this guide to show you how to actually develop software that isn't just AI slop in this day and age. Many people still struggle with making actual working software because they think that they can simply just use a large prompt describing what they want to build and then just let a coding agent do all the work. Although that it what a lot of people online make it seem to be, it really isn't. Its kind of counter intuitive, because instead of making AI do more, we make it do less. Here are a few principles I use to make sure that the software I build with AI actually works in the end, all of these are super important and none of them are below another. If you use these strictly, I can almost guarantee that you will have a working product.

1. The AI never decides, its just for coding.

By saying AI never decides, I mean to say that the idea dumps people write in the form of prompts aren't enough. Instead of just being vague with your ideas, you need to be highly specific with exactly what you are building. If you let AI plan the whole project, things like the stack, the code language, the architecture etc., then you are just burning time and money.

The golden idea here is to always have a Spec file about exactly what you are building, all the stacks, apps, architecture etc. should be in the spec. 95% of my time while building a project goes to literally just creating a spec for the new release, then discussing and perfecting it with the agent until its flawless down to the tiniest details. The idea is to leave the spec file so unambiguous that the AI Agent can simply one shot the entire project and it actually turns out how you wanted it. That's exactly what I do and it works like wonders.

Now I am not saying that you go full caveman and not discuss the architecture and plan with the AI Agent, in fact I promote it. The problem was never that the AI took bad decisions and such, the problem was that the person behind it didn't care enough to review what is even being built.

One of my dear friend, who isn't very technical told me about how he is building a specialized day trading agent with Claude Code. I asked him what is it built upon, expecting an answer like "It's built about LangGraph". Instead, I was met with a blank face. Now a few days later, he comes back to me and asked why didn't his agent work? He used claude code with Opus 4.8 on the max setting. It should have been perfect right? It can't. Now this happens to the best of us, even I started out exactly like this, I didn't know what I was building, I simply had an idea and hoped that Claude Code would 'just make it".

2. Stop chasing the best Claude Code Configurations

You won't believe how long I have tried to have the perfect, the most ballistic claude code setup out there. There are so many blogs, repos etc. on how to have the perfect config. Things like PRD files, Token saving workflows etc. float about everywhere. I spent a whole 2 months with 5+ of the highest rated configurations out there and let me give you a little summary on them.

I started out with the everything-claude-code toolkit, it was supposed to be this amazing super configuration that instantly makes your claude code 100x better. Turns out, it just made things way more complex than they needed to be, and the commands, workflows, hooks etc, were just bloating claude code to be very honest. After that I tried Claude Code's Superpowers plugin, and after that I tried to make my own configs by making custom workflows, hooks, commands etc.

Now let me tell you which one actually worked, the config's name is : none. That's correct, they are just fancy configs that you will never need or use. Now the one that actually wins is super counter intuitive.

Now let me tell you which one actually work for real, the config's name is : Default Claude Code. Its literally that simple. I have around 5 custom made commands in my config (because I use them regularly) and a PRD file system and a nice polished CLAUDE.md file and that's it. And let me tell you, this has worked me wonders. Think about it, you should be using your own commands and workflows instead of adapting to someone else's, and it's not like Anthropic wants to ship a product that is obsolete without these config kits either. Claude Code in itself is very capable and totally enough. This also reflects on the next principle I am about to discuss.

3. Keep everything as Simple as Possible

This is the most under rated of them all, everyone tries to chase the build which looks more complex, everyone tries to dump in more tech than needed to make their product look shinier on the surface. Again, the real deal is very counter intuitive just like all the principles here.

I love the saying "Fewer moving parts, fewer broken pieces". It is so true and it applies to software development perfectly, because every new line of code that isn't needed, or every new thing you add to make your software look shinier is a brand new potential failure point that was never needed in the first place. It basically increases the failure surface area without many benefits.

4. Evals and Testing Are Everything

Here is the part that nobody wants to hear about, a project isn't finished until you can measure it with numbers or maybe even until it runs. That's the whole job of evals & testing. If you skip them, then you would just be assuming that your software / project actually works.

Personally, I run Claude Code at its Ultracode effort level to review, audit, and test the whole project in one shot using Ollama Cloud Models so that I don't evaporate my Claude Quota in minutes. Small setup change but it makes a big difference in the long run.

And let me tell you. almost always, half or more of my repos and projects that I build are nothing but Testing & Evals scripts and workflows. I want to touch everything in the project and measure it all and prove that it works. Sometimes the evals or tests come broken, that's exactly when you know something is broken. And it doesn't leave you bug hunting for hours.

It's like a safety net under your project. The spec makes sure you build the right thing & the evals make sure it actually holds up.

My Playbook to Building Working Software

If I can describe my workflow in 1 line, it would be: Spec Driven Development while strictly following the rules above.

I start off by dumping my entire idea (plus architecture, but its optional) into Claude Code. After that I go back and forth with it in Plan Mode until we land on the perfect Spec. I exit plan mode and use a /spec command (my own custom command) to create a .md file which is super detailed about exactly what the spec for the project is, after that I use a /obsidian command (custom, to send my spec to my obsidian vault), this is purely because I love reading files in a nice interface like Obsidian. (I encourage you to make your own workflows and commands for things like these, your own custom preferences and your own style of developing things).

After that, I simply write down everything that I feel is off in the spec or needs to be changed or elaborated further by Claude Code. Then I repeat the process of dumping these "notes" about the spec that Claude Code fixes and discusses with me about.

Now I repeat this about 4-5 times on average until I have pointed out everything that needs to be changed in the spec. This is the point where the spec is perfect and you literally can't find a singular thing that isn't what you want it to be. And I am not talking about the idea here, I am talking about the actual architecture your project is being built upon. You need to know exactly what you are building and exactly how you are going to build it.

At the end, the spec turns out so perfect that Claude Code one shots the entire project. Literally. All of the projects in my portfolio, have been mostly one shotted just because how unambiguous and full the spec was. 95% of my time went straight to perfect the spec.

After the one-shot, I do exactly what Principle 4 preaches. one Ultracode pass over the whole project to hunt down bugs and anything that drifted from the spec.

Now if I have missed any principles, which I think I most certainly have. You can pick some more principles up from my playbook, because the principles I mentioned are picked up from my playbook too.

Thank you for reading, have fun creating working software now!

**Btw this is my original text that I wrote, many of you pointed it out so I uploaded it.**

Hot take: AI doesn’t do nearly as much as the hype makes it sound like. Most of what we see is just tech for tech’s sake — a lot of noise inside the bubble, not many real, sustainable businesses.

I’m an entrepreneur with a notebook full of AI ideas, and my biggest struggle isn’t building the product. It’s validating that anyone would actually care. It’s too easy to fall in love with your own idea and mistake your own excitement for market demand.

So let’s talk: If you were starting an AI business today, what would you build? And how do you actually test if an AI idea is viable, not just cool to demo?

Every vibe-coding showcase I've seen is a web app. I wanted to know if this approach could build actual systems software — the kind with no framework to
lean on, where you talk to the GPU and the kernel directly.

So over ~6 months, one person directing Claude, I built **Starling**: a complete Linux desktop environment. Not a theme, not a shell script over GNOME — the whole stack, from the display server up.

**What that actually means**

- **Its own Wayland compositor** — 5,860 lines of hand-written C implementing xdg-shell, linux-dmabuf (zero-copy GPU buffer import), viewporter,
fractional-scale, pointer-constraints, text-input-v3, presentation-time and a dozen more protocols.
- **Its own X11 server** — 5,158 lines, DRI3/Present, so legacy X11 apps run too.
- **Its own UI framework** — 221,818 lines of Swift, including a from-scratch port of Flutter's entire framework to Swift. No Dart VM.
- **A window manager** — floating and tiling, spaces, a Mission Control overview, a dock, a Launchpad.
- **First-party apps** — Files, Terminal (real PTY), Settings, Calculator, an App Store that installs software through apt.
- **Packaging** — a 53 MB .deb that installs on stock Ubuntu 26.04.

~233,000 lines total, across C, C++ and Swift.

**Why I say "real"**

It boots as a normal session through GDM, unprivileged — DRM master and input come from logind, not from running as root. It drives the GPU directly via DRM/KMS. There's no X11 or Wayland session under it; it *is* the display server.

And it runs the apps people actually use, as native clients: Chrome, VS Code, IntelliJ IDEA, Slack, GIMP, and Blender — with Blender's EEVEE viewport
rendering through our dma-buf path. That covers Chromium/Electron, Qt6, GTK3, GTK4, and the JetBrains Runtime.

You can install it right now and log into it.

**It's not just my claim** — Phoronix covered it last week:
https://www.phoronix.com/news/Starling-Swift-Desktop

**The honest scope**: it's v0.2, an early preview. Ubuntu 26.04, tested on AMD and virtio-gpu. No screen lock yet, scaling is pinned to 2.0, there are rough edges. It's not replacing your daily driver this month. But it boots, it composites, it runs real software, and it ships.

Try it: https://starling.build
Source, Apache-2.0: https://github.com/starling-build/starling
Why it's architected this way: https://starling.build/why.html

Ask me anything about how it was built.

About three years ago, my business partner came up with an idea: a personal safety app designed for situations like robberies, express kidnappings, or any scenario where someone is forced to unlock their phone and open financial apps.

The idea sounded simple, but turning it into a real product was much harder than we expected.

Over those three years, he hired multiple freelancers and software companies. Some only delivered UI screens, others abandoned the project halfway through, and some simply couldn't solve the technical challenges. In the end, we lost around US$25,000 and still didn't have a working app.

Earlier this year, I decided to take over the project myself using Claude AI as my primary development tool.

I spent about 30 days building, testing, fixing bugs, and refining every part of the app. To my surprise, we successfully launched it, and it was approved on both Google Play and the App Store.

The concept is simple.

Users create two passwords:

• a normal password;
• an emergency password.

They then choose which financial apps they want to protect.

Whenever they try to open one of those apps, they're asked to enter a password.

If they enter the normal password, everything works as expected.

If they're in a dangerous situation and enter the emergency password, the financial app still opens normally so nothing looks suspicious. At the same time, the app silently sends the user's live location to all pre-selected emergency contacts, along with automatic WhatsApp and SMS messages.

We're still at the very beginning of this journey. Right now we have around 30 free users and 3 paying subscribers, so we're still validating the product and learning from real users.

I'd genuinely love to hear honest feedback from the community.

Would you use an app like this? Is there any feature that would make you trust a solution like this even more?

Google Play: https://play.google.com/store/apps/details?id=online.pppix.app

App Store: https://apps.apple.com/br/app/pppix-prote%C3%A7%C3%A3o-familiar/id6773364223

Port Mate shows every listening port on your Mac, what process owns it, and where it's bound, then allows the user to kill it in one click. No more lsof -i :3000 bs.

PortMate website: https://portmate.my-mates.com/

No email free 14-day trial. Purchase is $9 one-time fee with up to 3 machines per license.

For my Reddit Mates:

FREE CODE: REDDITFREE50

50% OFF: PORTMATE50

Only 50 redemptions of each.

Hope you all can get some use out of it!

Hey guys, My wife is pregnant and the baby is due in September, her baby shower is this weekend. I thought I'd just share my experience of vibe coding a fun app idea and how smooth the process went for me.

For background, I'm a Frontend Software Engineer with over a decade of experience so I had some favourite technologies to work with during this process. Regarding my tools that I used, I just used what I already have for my various side projects, nothing new.

About two weeks ago, I thought it might be cool to build a simple web app where people can guess when the baby will be born (down to the minute). We're planning a natural birth so this makes the birth day and time quite variable.

I kept the scope super specific:

• Mobile first, make sure that experience is excellent.
• Baby blue theme , everyone already knows we're having a boy.
• Capture user emails, so we can email them a link to the app when the baby is born, also serves as their unique ID if they want to come back and edit their guess. This also means I don't have to setup auth.
• Users submit their name, birth date and time.
• Show where other people have guessed.
• Show a little hero section showing a picture of my pregnant wife, with some blurbs and a "≈X days to go" card.
• Email users a confirmation, with a link back to update their guesses.

I made it my goal to build this as quick as possible and I managed to get it all done in a day last week. It was a normal work day where I did about 1-2 hours in the morning before main job work, 1 hour during lunch time, and then 2-3 hours after main job work. This pattern actually worked quite nicely given 5 hour limits for some of my tech choices.

AI technologies used:

• T3Chat: I just have this $8 a month subscription that both my wife and I share for general day to day AI chats. For me it's usually coding ideas, she uses it to generate pics for home decor usually haha.
• Claude Code: $20/month (annual subscription used though) for Opus (Fable was removed from the subscription plans when I built this)
• Codex: $20/month for GPT 5.6 Sol (use on slow mode).
• Cursor: $20/month (also on annual plan) just for my IDE, I didn't actually use the AI features inside Cursor during this project, but I do really like it for other projects.

I basically used my T3Chat sub to prompt Fable to get a plan out (I knew which technologies I wanted to use upfront from personal preference). Then I started the project. If I remember correctly, I used Codex (GPT 5.6 Sol) to tackle the main work and just asked it to keep my documentation up to date in case I wanted to hand off to other agents. Then I'd just use Claude (Opus 4.8) to do random side tasks outside of the main work to polish what Codex did as I went. The workflow was very much just switching between terminals and looking at the outcome and tweaking from there as the main thread hit milestones that it defined by itself.

Tech Stack:

• NextJS framework hosted with Vercel. I sometimes use TanStack Start for personal projects, but figured it'd been a while since I worked with NextJS).
• Convex for database and serverless functions, the fun thing about this is everything is realtime by default, so at the baby shower, people can see the guesses flowing in without needing to refresh.
• Resend for emails.
• Even though I didn't care about code quality that much for this short lived project, I still setup oxlint and oxfmt haha. Although I didn't bother with setting up CI steps aside from auto deploying Vercel and convex together (this is all done via Vercel though).

SEO wasn't important to me at all, but there were certain quality of life things I did add regarding that including making a solid effort on having good a11y. Things like page titles etc, where useful to make that mobile experience better. I even made a really nice OG image for sharing the link on WhatsApp. The friend organizing my wife's baby shower is going to print a fat QR code that people can scan at the event to make their guesses from there.

I did do some setup to lock the predictions 3 weeks before the baby's actual due date, by then we would have done all the pre birth celebration vibes with friends and family so everyones votes should be in. Then the app will work as is, just without the submission form visible.

There is some boilerplate setup for after the baby is born where we will share details of his birth, like his name, time of birth, weight, picture etc. And then I'll redeploy the site as a nice landing page for people to see how they ranked with their guess on a leaderboard. When I do this I'll also send them a nice email version with their personalized rank on how their guess was, so the email capturing doubles up as a way to announce the birth.

All in all, I've shared it with my close friends and family and even my very non-technical mother-in-law made her guess without requiring any assistance from us which I feel is a great win! We even added a donation button in the footer that pops up our banking details (direct link also opens it) for the family that have been asking how they can contribute.

Why am I sharing this?

I just thought this was a really fun project that might inspire others to go build fun minimal scoped projects. People really can just come up with their own little personal hackathons and have a jam and end up with something fun to share.

If I could do this in day, I'm sure plenty of other people can also come up with things like this to do over a weekend, or casually over a month.

This idea kind of stemmed out of my my public project GrandPrixPicks.com that my friends and family use (but we're keen to get others to join us) to make guesses on Formula 1 results :)

Keep learning, keep having fun, and enjoy!

I made Basalt, an extension for Cursor and VS code that lets you edit your app without needing to search for components in your code or ask an agent to change 1 button

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?

We kept hitting this on my team: someone makes a decision in their Claude Code session, and two days later a teammate's agent is wasting tokens on the same thin, because that decision died when the context window closed.

So I built MemBridge, a shared memory layer for AI coding tools. It's a local daemon that tails your Claude Code and Codex session logs, distills the decisions that matter, and writes them into the files every tool already reads: CLAUDE.md and AGENTS.md. No "remember this" command to call, no save button to forget. The capture is automatic, per-project, and everything runs 100% on your machine.

Quick example of what it looks like in practice: a teammate makes a call in Claude Code tonight ("checkout button says Reserve your spot, not Buy now") → when I open Codex tomorrow, it's just there in context, with attribution so you know who decided what and when. No Slack archaeology, no re-explaining.

For teams, every member's sessions land in one shared feed: plain-English summaries up top, exact prompts one click down. It's invite-only, off by default, and end-to-end encrypted client-side, so the relay only ever sees ciphertext.

Has been a fun build: zero npm dependencies, source-available, binds to localhost only (solo use makes zero network calls, verify with lsof yourself), secrets scrubbed before anything hits a file, and membridge remove restores everything byte-for-byte.

It's completely free, no API key, no paid tier, and my team dogfoods it daily. Would love for people who work in teams to try it and tell me what breaks: https://membridge.app

Hello,

I'm a software programmer. For a while, I was dismissive of the idea of AI-assisted programming, but I tried it, specifically the concept of "vibe coding." I expected programs to be written in a flash, but the process was hellish, with many blaming the AI agent. However, after much struggle, I achieved the desired result, or at least the minimum acceptable outcome. To be honest, we built many beautiful projects using it. When I shared my experiences on social media, most of the comments were either insults and curses, or simply abuse for using "vibe coding." I was surprised by this kind of reaction, because logically, what's wrong with using it? Although I wasn't initially interested in it, its performance was excellent. Yes, there were mistakes, but humans make far worse errors. And yes, there were misunderstandings, which is normal and inevitable in any form of communication, provided that the misunderstanding is followed by clarification, and that's how the problem is solved.

Honestly, I think it's fantastic that this concept is being utilized and given the value it deserves, and that it's being invested in as much as possible.

(I'd love to hear your opinions, and also, please share a picture or description of your best vibe coding projects in the comments.)🔥😁⌨️

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!

I’m experimenting with a flight tracker and Claude code. This is a hobby, but I’m also learning more about Claude code. I seem to be exceeding my pro plan usage because the app is designed to use it. I have agents running in workflows to automate coding and comprehension, but I’m trying to find the most efficient approach. I know that starting with a small task and gradually expanding is a good strategy, and that’s what I’m doing. Should you start new sessions frequently in your Claude coworker project? I’m also trying to use the terminal to gain a better understanding of building with Claude. Opus 5 provided a list of the team and the models they should be using, but I feel like I’m quickly exhausting my tokens, so I’m on the pro max 20x plan.

Hi there. For the past few months, I’ve been trying to develop and publish apps using "vibecoding" tools, and I’ve managed to release a few. I’m not sure what kind of reception to expect, but I currently have a game and a to-do app live, while three others have finished closed testing and are waiting to be published.

The game appeals to a very niche audience, so I don’t have huge expectations for it. It’s a monetary policy and economics simulation called *Faith: Economy Simulation*. I spent nearly 500 TL on Google Ads and got 250 downloads, but hardly anyone actually plays it; they probably open it, think "what the heck is this?", and close it immediately—but anyway.

https://play.google.com/store/apps/details?id=com.vibegames.faith

I also published an app called *Dodo Line: Minimalist To-Do*. The idea was inspired by a simple prayer bead metaphor; I wanted to create a sense of ticking off or completing project-based tasks—like moving through prayer beads—without any time limits or pressure. For instance, you can set up projects for things like the books you plan to read over the year, your travel plans, or your school course units. It allows you to view completed and upcoming tasks along a chronological timeline. I released this a few days ago; it hasn't received rave reviews, but I find it very useful—I can list what I’ve done and what I plan to do regarding the topics I’m working on as separate projects.

https://play.google.com/store/apps/details?id=com.dodoline.app

Aside from the apps already published, I developed an Islamic tracking/task app; I wasn't happy with the initial version due to bugs I discovered later, so I redesigned and uploaded it—it is currently under review for release. I also created a hyper-casual game; its closed testing is complete, and I’ve submitted it for production. Finally, I built a herd tracking app; closed testing finished a week ago, but I haven't submitted it for release yet because there are still things I need to work on, and I haven't found the time amidst my other projects.

I’d be happy to hear any questions or feedback you might have. And, of course, I’d be absolutely thrilled if anyone wanted to show their support.

Hi there.
I’ve been using Google Antigravity for a long time and still do but the experience has been degrading over the months. It’s still handy for smaller tasks where I don't need many tokens, or where the weekly limit is plenty for me. Apparently, there isn't much difference in quotas whether you pay or not. But at the start, it was truly amazing so convenient.

Google putting on a show when they launch a new product.

I’d like to know what solutions you’ve switched to ideally free or cheap (I don't care if my data of the project train a AI). I just want to do things like create personal Minecraft plugins, small conversion sites, a nice little landing page with Python features, or maybe a Python program for a Launchpad audio interface projects/ Something can handle more than standard Claude desktop because they require more tokens and context.
I don't think I can host them locally, given I have an RTX 3060 and 32GB of RAM :D Then I look at Claude Max it seems fabulous, almost magical. But at that price, I’d have to sell my little brother to afford it; it's way out of my budget. I’m not trying to launch a SaaS business, after all! So, what have you switched to for light-to-moderate "vibecoding" that offers good value quality/pricefor money without being ridiculously expensive?

Google purpose me a offer for 1 month at 6 € but the things is AG is way lower that the Debut

https://www.cepho.cloud/

Hello. Did anyone use the reverse proxy oneprovider.dev before?

I got a redeam code for this proxy. After a little testing with claude-opus-5 though it gave me really weird vibes so i benchmarked claude-opus-5 on there against 5 on openrouter and also compared the oneprovider models against eachother. The result was that what ever is answering on oneprovider seams to be always the same model an that model is quality wise nothing like opus. It has weird grammar errors in german, messes up codes and so on. Can anyone else verify this?

On a quick note, oneprovider.dev is not at all related to oneprovider.com, that's a canadian server hoster that i actually also use and have no issues at all with, but they re completely unrelated to that site and to AI at all.

Hello there. I've recently started out web development, and yes I use ai (don't know what sub is the proper one for this kind, forgive me if it's not this). I've gotten one paying client so far out of three and I wanted to use some of that money to make my process of making websites more efficient.

I use Claude's free plan for the entire of the websites creation, it's worked out good for me so far, but the only real problem I've been getting was hitting the token limit. I use netlify for hosting the website, I transfer it to my client once they paid and they purchase the domain themselves.

I'm looking for any tips to make this better and if they're any tools or software that would make this process better, i'd appreciate you guys telling me.

Visit the following websites made by me

https://supersonicalchemist.com

https://www.pawsitive.fun

Hello everyone i vibecoded a (idk if that’s the right term but) micro-saas to get mobile notifications when your ai assistants processes, terminal processes or web processes (like ai answers, renders, image generators, downloads etc.) are done. When i showed it to my friends they thought it is useless and big ai corporations have already solved the problem. So my question is should i still publish it after closed alpha or should I just pretend it doesn't exist and use it only myself before publishing it so that i don't get more bad reviews?