Samuel Rondot

Spec Coding by Capacity - Vibe Coding with a planning assistant to build with clarity

Most AI app builders jump straight into building. That feels fast until your app gets messy, inconsistent, and nothing like what you imagined. Today, we’re introducing Spec Coding in Capacity. Instead of building immediately, Capacity now lets you define your app first with the help of an AI co-founder that asks the right questions before any code is generated. More structure upfront. Far less refactoring later. Much better results.

Add a comment

Replies

Best
Samuel Rondot
Hey Product Hunt 👋 Samuel here, maker of Capacity. We love vibe coding it’s fun and incredibly fast. But after building a lot of real apps with AI, we kept running into the same problem: AI builds confidently, even when the idea isn’t clear. Humans ask questions. AI doesn’t, it guesses. So we built Spec Coding. Before any code is written, an AI co-founder helps you define: -what you’re building -who it’s for -what matters -and what doesn’t It slows down the first minute… and saves hours later. Would love your feedback especially if you’ve ever rebuilt the same AI app three times 😄 Happy to answer any questions!
Zolani Matebese

@samuel_rondot Hi Samuel, seems like you're on the right track with this. How do you deal with testing and code qual?

Samuel Rondot

Hey @zolani_matebese  !
Great question.
The main thing is we don’t let the AI guess.

Capacity starts with a spec (expected behavior, flows, data models), then generates code and tests from that spec.
That makes tests more reliable and code more predictable.

We also keep changes small, reviewable, and human-approved so you keep the speed of vibe coding without the usual quality drop.

Bob Gao

@zolani_matebese  @samuel_rondot thanks for sharing the insight! I wonder if you ever met corner cases that are not covered by the spec? How would those cases be handled?

Chris Messina

@samuel_rondot pretty cool!

Also, did you know that you video goes black from ~2:28-2:56?

Pavel Kucherbaev

Hey @samuel_rondot ,

I like the design of @Capacity . I like the name as well - brilliant.
Which tool / stack did you use to create @Capacity ?
What is your GTM?
I would like to meet with you and chat: https://timetuna.com/pavel

Samuel Rondot

@pavelk2 Hey Pavel !
Thank you so much !
We are using Nextjs, Nodejs. Our GTM strategy is simple : building an ai website builder that works. Currently most vibe coded app fail and we are fixing that with Spec coding.

Pavel Kucherbaev

@samuel_rondot Thanks! Good luck with the PH launch :)

Samuel Rondot

@pavelk2 Thank you !

Abdul Rehman

Slowing down at the start to save time later feels obvious now, but I never thought of it like this. Do you guide users on what “matters” vs “doesn’t matter”?

Baptiste Studer

Hey @abod_rehman 

On Capacity it all starts with a project brief you can co-write with an AI agent we developed. The document describes the problem you noticed and the solution you want to develop to kill this pain. The agent helps you refine your business idea, target market and MVP scope. Guiding the user on what matters and what doesn't as you mentioned is its purpose.

And it works the same for the design specs of your platform and the features to develop. Dedicated AI agents focused on these specific tasks do the heavy lifting to prepare the prompts that will be sent to the coding agent.

It starts slower but development is faster and app scales better

Ugo

Hey @samuel_rondot ,

Been following you from far on X, liked the Starter Story video too

Cool launch and very nice product you guys cooked here, congrats for top 3 :)

Baptiste Studer

@samuel_rondot  @ugo_builds we appreciate the support 🙏

Henry Adams

This looks great and really helps put the focus on the most important stage of the process. Do you have features to allow teams to work together on this? Good luck with the PH launch.

Baptiste Studer

@henry_adams5 we don't have a collaboration mode atm, it didn't came out as an important feature from our customers' feedback

Thanks! The PH battle is intense today

Bekjon Ibragimov

Nice Launch!
How much can you build on 100 credits ?

Baptiste Studer

@bekjon_ibragimov a complete web app. Here is a video of me implementing a fully working web app in only 50 credits:

. I still had 50 credits left in the end

Christian Pezzin

Thanks for sharing this @samuel_rondot ! Any free coupons for us PH users? 🤓

Baptiste Studer

@samuel_rondot  @pezzin  you can find it right here PH20OFF 🤫

Michaël Antoine

Really interesting approach with Spec Coding! As a full-stack dev building SaaS apps (DeadlineKeeper for college applications), I've been using BMAD Method (Breakthrough Method for Agile AI Driven Development) with Claude Code. The idea of defining structure upfront with an AI co-founder resonates with me - BMAD has 21 specialized AI agents that help architect before coding. Will definitely check out Capacity to see how your spec coding compares! 🚀

Baptiste Studer

@michael_antoine love it! BMAD is definitely one of our big inspirations 🔥

Michaël Antoine

Nice! Does Capacity follow a structured planning phase or is it more direct code generation? With BMAD I map out architecture upfront before Claude touches anything - wondering how you guys approach that. Already adopted BMAD for DeadlineKeeper. Good luck with the launch! Launching DeadlineKeeper soon myself

Praasshant Dubey

Great! How is this different from vibe coding tools? Like Lovable

Baptiste Studer

@praasshant_dubey we strongly committed on spec coding. The issue with vibecoding tools is they incitate you to build first, but this approach is not scalable. You end up with an application that lies on a growing technical depth.

With spec coding, you start with planning the features you want to implement with our specialized AI agents, and then you implement. AI output becomes more deterministic and you make your application scalable.

Spec coding tools are baked in Capacity.

Joyce Qiao

Would love to learn how Capacity is different from Lovable and Base44!

Baptiste Studer

@joyce_qiao1 we strongly committed on spec coding. The issue with vibecoding tools is they encourage to build first instead of planning, but this approach is not scalable. You end up with an application that lies on a growing technical debt.

With spec coding, you start with planning the features you want to implement with our specialized AI agents, and then you implement. AI output becomes more deterministic and you make your application scalable.

Spec coding tools are baked in Capacity.

Joyce Qiao

@baboo77777 That's so interesting! I would indeed have to plan out my code base before telling AI what to do because I noticed a lot of packages and dependencies AI chose for me is either out-of-date or non-scalable. Hope to see you guys change the game!!

12
Next
Last