Skip to main content
vibeprompt

Built with
vibeprompt.

Six indie apps shipped end-to-end using the 10-step workflow. iOS, Android, web. Live URLs, real stacks, honest what-broke notes. Not aspirational — actually shipped.

Most “built with X” pages are marketing. This one is a postmortem. Every project below shipped to a real URL or store listing using vibeprompt’s workflow — and every one of them broke in some specific way that became a fix recipe on this site.

All six were built by the same solo dev (the maintainer of this site). The workflow didn’t come from a book — it came from the patterns that survived across these projects.

Excuse Caddie

🌐 Web🍎 iOS🤖 Android·Next.js + Vercel · SwiftUI · Jetpack Compose
Visit →

Random excuse generator for golf — three platforms, one weekend's worth of prompts each.

iOS live in App Store · Android in Play Store review · Web at excusecaddie.xyz

What worked
PRD-first kept the three platforms in sync. Same content model, three thin clients on top.
What broke
Closed testing on Google Play needs 12 testers for 14 consecutive days. Step 07 fix article got written *because* this broke.
Which steps
Used every step except 00. Step 02 PRD was the biggest single time-saver — wrote it once, the three clients fell out.

Commitment Issues

🌐 Web·Next.js · GitHub API · Vercel KV · Stripe
Visit →

Death certificates for abandoned GitHub repos. Open source, weirdly viral on dev Twitter.

Live · 12 awesome-list submissions, 2 merged so far

What worked
Step 08 (Launch) playbook for indie devs. Submitted to ~10 awesome-tool lists for backlinks — slow but steady traffic.
What broke
Stripe webhook silently stopped firing after a routing rename. Step 06 audit added 'verify webhook end-to-end after every deploy' to the personal checklist.
Which steps
Steps 01-09. Step 09 (Iterate) caught a 60-visitor-zero-conversion week that turned out to be a broken checkout button — only found via session replay.

Build2Race

🌐 Web·Next.js · OpenAI · Vercel
Visit →

Free triathlon training plan generator. PRD said 'free forever' which kept the build small.

Live · indexed for 'triathlon training plan' on Google

What worked
Tight PRD scope. 'Free forever, no signup' meant no auth, no payment, no DB. Shipped in two evenings.
What broke
Original prompt generated 30 weeks of generic 'easy run' workouts. Step 03 (Stack) revisit added a structured-output schema and the quality jumped.
Which steps
Stripped-down version of 02-07. Skipped Step 04 (Context) entirely — too small to need a memory-bank.

Indexia

🌐 Web·Next.js · Supabase · Resend
Visit →

AI-SEO and GEO (generative engine optimization) for Swedish businesses. Currently in customer outreach.

Live · 50+ cold-outreach emails sent, conversation in progress

What worked
Step 04 (Context) — AGENTS.md locked the Swedish-language constraints and tone. Every prompt came out in correct Swedish first try.
What broke
Step 08 outreach: first batch of 30 emails got 1 reply. Wrote the 'cold outreach for indie devs' fix recipe after this.
Which steps
01-09 with heavy emphasis on Step 08 (Launch). Outreach is the entire product strategy for this one.

Slothy

🍎 iOS🤖 Android·SwiftUI · Jetpack Compose · CloudKit · Firebase
Visit →

Productivity app for people who hate productivity apps. iOS + Android.

iOS live · Android live

What worked
Cross-platform PRD with separate platform-specific AGENTS.md files for iOS and Android. Step 02 split into 02a/02b.
What broke
First iOS submission rejected by App Review for 'minimal functionality'. Step 06 fix article 'app-review-rejected-vague' is the postmortem.
Which steps
Step 04 (Context) was critical — two AGENTS.md files (one per platform) prevented the AI from mixing SwiftUI and Compose patterns.

vibeprompt itself

🌐 Web·Next.js 16 · Tailwind v4 · Vercel · @vercel/kv
Visit →

The site you're on right now. Yes, it was built with its own workflow.

Live · MIT, free forever · 17 articles, 56 prompts, 46 fixes

What worked
Eating our own dogfood. The /workflow page literally describes how this site was built. Step 01 (Research) defined the wedge against competitors before any code.
What broke
First version had /list, /handbook, /cookbook, /templates all as separate pages — too much surface area. Step 09 (Iterate) collapsed them into articles + ⌘K.
Which steps
Every step, multiple times. The articles, prompts, and fixes are the artifacts of the workflow being applied to itself.

Shipped something with vibeprompt?

Add it to the list.

Open a PR to the repo with your project, what worked, what broke, and which workflow steps you actually used. No requirement that the project be successful — failed launches are useful data too.

See the workflow →

This site is
open source.

Every word, every prompt, every fix lives on GitHub. Fork it, edit it, ship your own version. MIT license, no strings.

View source →Try the workflow →