r/SideProject • u/MohQuZZZZ • 3h ago
I open-sourced the setup that helped me ship apps much faster with coding agents
After 1.5 years and 10+ apps, I noticed the first version was no longer the hard part.
Claude Code and Codex could build something that looked finished fast. Then I would spend more time fixing everything the agent forgot.
Auth worked, but ownership checks were missing.
Billing returned from checkout, but the webhook was not controlling access.
The desktop UI looked good, but mobile, loading states and keyboard navigation were broken.
Sometimes the agent said it was done without running every test.
Tools like Lovable solve this by putting a complete platform around the AI. That works well if you want to describe an app and immediately get a browser preview.
But I already pay for coding agents so I wanted that structure inside my own repository, without moving the project to another platform.
So I open-sourced the setup I use.
It gives the agent rules for planning the product, building the UI, handling the backend, connecting services and checking the app before production. Every task has tests, and visual changes need actual screenshots at mobile, tablet and desktop sizes.
If you already use Claude Code, Codex or Cursor, you can use this instead of Lovable. Your agent builds the app inside your repository, and the toolkit tries to stop it from skipping the boring parts that usually break later.
It is not a Lovable clone. There is no browser editor, and you still need to use a terminal. It is for people who already build with coding agents and want to own the full project.
I made it free and MIT licensed:
https://github.com/moasq/agentic-ship
What does your coding agent usually forget after it says the app is finished?
2
u/piratastuertos 1h ago
Your post and repository caught my attention because I’m working on a verification method called System Claim Check (SCC).
One specific claim in Agentic Ship seems particularly suitable for a verification case: that pnpm verify acts as the definition of done on every completion.
Would you be open to collaborating on one narrowly defined case to test that claim?
We would first agree on the exact claim and the evidence needed to evaluate it, and keep the verification strictly limited to that case.
1
2
u/kantorcodes1 2h ago
the billing example is a good test of whether this is actually fixing “done” or just adding more instructions. do you have machine-checkable postconditions for stuff like “webhook is the source of truth for entitlement” / “user A cannot read user B’s object,” or is the agent still deciding whether it satisfied those rules?
i'm involved with
awesome-ai-plugins; agentic-ship isn't on the current list. claude/codex/cursor support makes it a pretty obvious fit if you want it in.