I vibe-code with agents a lot and got tired of glancing back at the chat every time a long reply finished. So I made Aftertone: after each agent response, a local Supertonic ONNX voice reads a short line (what landed, blockers, next step) — not the whole wall of text.

What it is

• Runs on your machine (~/aftertone), MIT, no TTS subscription
• Cursor and Claude Code work today (Codex / OpenCode on the roadmap)
• Per-chat on/off (/aftertone-on in Cursor, /aftertone_on in Claude)
• Agents use a <spoken_summary> tag at the end of replies; if there is no tag, it stays quiet (tag-only mode by default)

Install (Linux/macOS):

curl -fsSL https://raw.githubusercontent.com/omarelkhal/aftertone/main/scripts/install.sh | bash -s -- --install-uv --start-daemon

Then in Cursor: Hooks on + trusted workspace. In Claude: /aftertone_on in the chats where you want audio.

Repo / docs: https://github.com/omarelkhal/aftertone

Happy to answer setup questions. If you try it, I would love to know whether the spoken summaries actually help your flow or feel like noise.

Hey everyone, I hope you are well.

I built a platform for builders who built vibecoded sites/businesses/apps/start ups etc, who just want to build and not worry about markets, competitor analysis, pitch decks, business plans etc. You pop your URLs, code, files, images, chatgpt, Claude, Gemini chats etc in and it generates it all for you. You pivot, change prices, markets, it changes it all for you as a living document and workspace and export it in any format you want.

This idea stemmed from my own frustrations of building a healthcare startup as a tool for myself but spiralled into something else.

It's early stages and looking for some potential testers if possible who will get free access to help me improve it and hopefully help you too.

https://ceoworkspace.lovable.app/

Cheers

Hey everyone,

One thing I kept noticing with iOS releases is that even solid apps often get delayed during App Store review for issues that aren’t really about the core product.

Things like missing metadata, incomplete privacy details, subscription setup inconsistencies, or small guideline oversights tend to cause repeated rejection cycles and slow down launches more than the actual code does.

So I built AppReviewer Preflight.

It’s a structured pre-submission checklist tool designed to help iOS developers catch common App Store review risks before submitting a build.

Instead of relying on memory, scattered notes, or last-minute checks, it centralizes everything into a clear workflow you can actually follow before release.

Key Features:

• Pre-submission checklist focused on common iOS review risks
• Filter checks by app type (subscriptions, IAP, ads, UGC, login-required apps, etc.)
• Severity labels for critical vs. major issues
• Mark items as resolved or unresolved during review
• Add internal notes for QA, handoff, or team tracking
• Fast search across rules and submission topics
• Save progress locally and continue anytime
• Export reports as PDF or JSON
• Quick access to official Apple guideline references
• Clean workflow designed for iPhone and iPad

Who it’s for:

• Indie developers preparing first launches
• Agencies shipping client apps
• Product and QA teams managing release cycles
• Developers trying to reduce avoidable App Store delays

What it helps you do:

• Catch privacy and compliance issues earlier
• Validate monetization and subscription setups
• Reduce preventable rejection cycles
• Track unresolved review items in one place
• Improve release confidence and consistency

The goal is to make App Store submission more predictable and less reactive.

You can try it here:
https://apps.apple.com/app/appreviewer-preflight/id6761920856

Over the past 18 months, I’ve switched from 15 years of “traditional” software engineering (manual memory management, strict type‑driven development, line‑by‑line debugging) to a vibe‑first workflow. I want to share a detailed, non‑pessimistic comparison – and then explain why I believe vibe coding will replace most traditional coding, leaving only one niche for the old guard.

This post is not AI‑generated. I’ve used LLMs (GPT‑4, Claude, Copilot) to refine my thinking and generate code, but every word here is my own. Let’s dive in.

1. Definitions (so we argue from the same map)

• Traditional coder – Prioritises exact syntax, manual control flow, test‑driven design, and deep understanding of every abstraction layer. Often writes code “from scratch” with minimal AI assistance beyond autocomplete.
• Vibe coder – Focuses on intent, flow, and outcomes. Uses LLMs to generate, refactor, explain, and test code. The vibe coder’s job is to guide the AI, review its output, and maintain the product vision – not to wrestle with brackets.

2. Where vibe coding excels (evidence from my own workflow)

I recently built a full‑stack document‑parsing pipeline (FastAPI + React + PostgreSQL) in 8 hours using a vibe‑coding approach. The same project would have taken me 3–4 days traditionally.

How I did it (educational part – tools & process):

Step	Tool	What I did (vibe style)
1. Requirements	GPT‑4	Described the desired user journey in plain English. AI returned a PRD + data model.
2. Backend boilerplate	Cursor + Copilot	Typed // create a FastAPI endpoint that accepts PDF, extracts tables, returns JSON. AI wrote 90% of the endpoint.
3. Database	Claude	Asked “given my models, write Alembic migration and SQLAlchemy relationships”. Fixed 2 minor foreign‑key issues.
4. Frontend component	v0.dev + manual tweaks	Generated a drag‑and‑drop upload component. Manually added error handling and loading states.
5. Integration & debugging	Cursor chat	Pasted error logs. AI suggested the exact fixes. I understood each fix before applying.

Key insight: I didn’t “blindly copy”. I read every line the AI wrote, questioned it, and sometimes rewrote 10‑20%. But I never typed boilerplate loops, DTO mappers, or CRUD endpoints manually. That’s the vibe coder’s advantage: speed without losing understanding.

3. Traditional coding’s remaining value (and its inevitable shrinking)

Traditional skills are not useless. But their highest leverage is now in exactly two places:

1. Building the AI agents themselves – LLM infrastructure, agent frameworks (LangGraph, AutoGen), tool‑use protocols, and evaluation systems. Those require deep systems knowledge.
2. Safety‑critical or mathematically verified systems – aerospace, medical devices, formal verification. But even there, AI‑assisted development is creeping in.

For everything else – web apps, internal tools, data pipelines, MVPs, automations – vibe coding is already faster, cheaper, and often more readable (because the AI enforces consistent patterns).

Conclusion of this section:
The traditional coder who refuses to adopt vibe workflows will become a specialist – the person who builds the LLM that vibe coders use. Everyone else will vibe code. That’s not pessimism; it’s observing the exponential curve of AI code generation.

4. Addressing the common anti‑vibe arguments (constructively)

>

Rebuttal: So do traditional coders who skip reviews. The difference: a vibe coder can ask the AI to “review this for SQL injection” and get an instant security analysis. Traditional security requires manual audit or expensive tooling. Vibe coding, done right, includes AI‑assisted review as part of the loop.

>

Counter: I’ve learned more by vibe coding – because I ask the AI to explain why it chose a certain pattern. I’ve deepened my knowledge of async Rust, complex SQL window functions, and React hooks exactly this way. Vibe coding is not “copy‑paste”; it’s dialogue‑driven learning.

>

Rule #1 of this sub: low‑effort posts are banned. Same for code. A vibe coder who just dumps AI output without understanding is a bad vibe coder. The professional vibe coder reviews, refactors, and tests – but at 10x speed.

5. My personal workflow rules for professional vibe coding

If you want to adopt vibe coding without becoming lazy, here is the system I use (and recommend):

1. Never commit AI code you don’t understand – read every line. If unclear, ask the AI to explain.
2. Use AI for generation, not for decision‑making – architecture, tech stack, trade‑offs are human.
3. Write tests first – then ask AI to implement until tests pass. That keeps you in control.
4. Keep a “vibe log” – document which prompts gave good results. That’s your reusable knowledge base.
5. Manually handle edge cases – AI often misses the weird inputs. That’s your job.

Following these, I’ve shipped 5 projects in 3 months. Zero major bugs in production. My traditional‑coder friends are shocked.

6. Final conclusion (the future, as I see it)

>

The future software engineer will be a product‑focused vibe coder – fluent in English, system design, and AI prompting. They will build what used to take teams of traditional coders.

The only traditional coders who remain will be the ones building the AI agents themselves – the LLM architects, agentic workflow engineers, and tool makers. Everyone else will vibe code.

That is not a threat. It is an upgrade.

Got tired of alt-tabbing between my editor, terminals, and browser. So I built a Figma like canvas to work on with all my terminals, browser windows, and so on. Have been building with this setup for two weeks now while still adding to it.

It's open source so you can just run and build it yourself or use the prebuilt Mac/Windows/Linux version. Just try it and give me feedback on what's missing. Happy about some feedback or new ideas. Would appreciate if you drop a star.

Download here: https://github.com/0-AI-UG/cate or https://cate.cero-ai.com

Hey everyone, I’m building a simple app called TechE for less techy people who just want plain-English answers to annoying tech problems.

Stuff like:

“Why is my internet slow?”
“Is my VPN making things worse?”
“Why does my PC take forever to load?”
“Why are my games lagging?”
“Is it my Wi-Fi, my ISP, or my actual computer?”

The goal is to make it feel like a friendly tech mate, not some scary enterprise dashboard full of jargon.

Currently running on Nextjs but happy to explore other options if anyone has any

I’m building it live here if anyone wants to follow along or roast the idea:
https://www.twitch.tv/turbulence_turtle

and you can have a look live at the site at www.teche.company

Here are some features I shipped for BiteTube this week:

• Added a dedicated “Why it’s worth watching” section so you don't have to watch videos just to end up closing them
• Built “Continue the Vibe” dynamic discovery which helps user stay on the same vibe of content
• Polished up the UI to improve user experience
• Integrated Sanity as the CMS to make managing content easier and efficient

Share what kind of features you shipped in the comments to let other users know about your project!

Hey r/saasbuild 👋

Every time I wanted to buy something online, I kept checking the same products over and over just to see if the price dropped.

So I built Price Pulse — a simple tool that tracks product prices and alerts you when prices change.

✅ Track products from links

✅ Get notified on price drops

✅ Clean dashboard to monitor everything in one place

✅ No spreadsheet chaos, no manual checking

Built this mainly for shoppers, deal hunters, and anyone waiting for the “right time” to buy.

Try it here: https://pricepulse-beryl.vercel.app/

Would love honest feedback:

Would you use something like this?

What feature would make this a must-have for you?

What pricing shall i put?

Thanks!

Pitch your product in 1–2 lines and drop a link below.

I help founders get their first 1000 users,

We handpick the best from the tools directory and give them free exposure to 55k+ subscribers (each week): https://tools.launchllama.co/