Shubham Bhatt

Love seeing this repost from @marclou 🙌 I built FollowMRR after he opened the TrustMRR API. Follow startups and track their revenue growth: • MRR updates • 24h & 30d growth • revenue changes since you followed Fun little project built in a day. Try it ↓

@JCodesMore 🫡🫡

@BhattBuilds 🫡

Clone any website in one Prompt. This guy from Reddit literally made a Claude skill to clone any website in one prompt. Check this out here👇

@itsmarcosruiz Playbook

My agency has generated over $3 million and helped generate 1 million+ followers on LinkedIn. So I sat down and wrote a 34-page playbook that details A → Z how to launch, grow, and monetize your personal brand on LinkedIn. Like + Comment “Playbook” and I’ll DM it to you. Must be following / have your DMs open. 24 Hours only.

@romanbuildsaas Congrats, Roman. Happy for you. Wishing YC brings more success to you.

We just got accepted into YC and hit $1M ARR. Cold outreach is broken. So we built an AI that decides who to contact, when, and why. Want the exact playbook we used to reach 1,000 customers in 8 months? Comment “GO” + RT and I’ll send it.

Check out the original reddit post here: reddit.com/r/vibecoding/c…

Check out the skill here: github.com/JCodesMore/ai-…

6 design fixes that take your app from "obviously AI-built" to "wait, who made this?" 𝟭/ font > stop using whatever the UI library gave you. > pick one family, two weights max. > the font choice alone makes your app stop looking like a template. 𝟮/ spacing > stop eyeballing padding > use a 4px base unit: 4, 8, 12, 16, 24, 32, 48, 64. > never 13px. never 22px. > this is why your app feels off and you can't explain why. 𝟯/ colors > stop picking hex codes per component > define 8 semantic tokens once. > background, surface, border, text-primary, text-secondary, brand, brand-hover, destructive. CSS variables. > never hardcode a color again. 𝟰/ border radius > stop mixing rounded-lg, rounded-xl, and rounded-full in the same UI. > pick one radius. 8px or 12px. > apply it everywhere. cards, buttons, inputs, modals – all the same. 𝟱/ shadows > stop using shadows as decoration. > shadows mean elevation, nothing else. > one level for cards. one level for modals. that's it. 𝟲/ icons & inputs > stop mixing icon libraries. > stop having buttons at 36px next to inputs at 42px. > one icon set. one input height. > every element gets a hover state. none of this is taste. none of this is talent. it's 6 decisions made once, applied everywhere.

Got an idea sitting in your head? I'll ship it in 2 weeks. DM me or book a call: cal.com/bhattbuilds/qu…

you can spot a vibe coded app in 3 seconds. because it uses the same font, random spacing, and colors picked per component. 6 design decisions fix 90% of it under an hour👇

Got an idea sitting in your head? I'll ship it in 2 weeks. DM me or book a call: cal.com/bhattbuilds/qu…

Is this good enough to convert you? Be honest!👇

27 signs your vibe-coded app is a TICKING BOMB ! 1. API keys hardcoded “for now” 2. No /health endpoint, you just hit the homepage 3. Schema changes live in your head, not migrations 4. Every query is SELECT * and vibes 5. Error handling = console.log(e) and hope 6. No rate limit on auth or writes 7. UTC, local time, and “JS default” all mixed 8. README is empty or wrong 9. No staging env, just “dev” and “prod-ish” 10. One god component owns the whole screen 11. No analytics, just “feels like people use it” 12. You say “we’ll clean this up after launch” every week 13. Env vars live only on your laptop, nowhere else documented 14. Frontend talks directly to 5 different third-party APIs with no wrapper 15. No monitoring or alerts – you find out it’s down from a DM 16. Logs only exist in your local terminal history 17. DB backups are “automatic”… but you’ve never tested a restore 18. Feature flags = commenting code in and out 19. Deploys are done from your local machine with one random script 20. No input validation, you trust whatever the client sends 21. CORS is set to * because “it fixed the error” 22. CI is “I ran it once locally and it worked” 23. Same API token reused across staging, prod, and local 24. Only one person actually knows how to run or deploy the app 25. API keys / JWT secrets stored in client-side code or .env committed to git 26. Supabase/Firebase/Postgres exposed publicly with no RLS → full database readable via /rest/v1/ endpoint 27. Zero logging beyond console.log → good luck debugging

how much would you rate it out of 10?

Vibe coders🚨 Don’t overlook these essentials if you want your next build to be truly solid. > Use Clerk / Supabase for authentication. > Use shadcn/ui for UI. > Use Neon / Supabase for the database. > Use Vercel / Railway for deployment. > Use Stripe / Polar for payments. > Use UploadThing / Cloudinary for file uploads. > Use PostHog / Plausible for analytics. > Use Resend / SendGrid for emails. > Use Novu / Trigger for notifications and workflows. > Use Sentry for error monitoring. > Use Playwright for testing. > Use Upstash for caching and rate limits. > Use Cloudflare for security and CDN. > Use Pinecone / Vector DB for RAG. Bookmark it now!

@AdityaShips Most-built app on X right now. But you have a good distribution, really an edge for you. All the best, Aditya.

Announcing my next SaaS A MacOS screen recorder with auto zoom effects And this is the day 1 of me building my first ever mac app

shipping slop is a choice now. just feed these 6 design principles to you AI and ship a clean premium UI. Bookmark this before your next build.

@andrewxroas Will you still be called an indie hacker if you do so and build a successful app?

If you want to build a successful app AVOID indie hackers like the plague You might think it's just a group of people building software like you but they literally have the most anti-business mindset possible For starters: - They believe competition = bad - Their ultimate goal is 10k MRR (such low goal) - They think product > distribution - They avoid all forms of paid marketing - They all glaze the same X creators that made them think this "indie hacking" path is feasible You must unfollow all of these people and get them off your timeline otherwise you'll soon adopt their limiting beliefs

@marclou Because the future of SaaS is backends. - Marc Lou

QStash’s interface is so bad, I vibe coded my own UI to understand where the recent spike came from. I think in the future, most SaaS will expose an API, and the UI will be generated on the fly, custom-made for each user.

Genuine question: what’s the difference here?🤔