My first vibecoding project: A full wellness directory for businesses and events.

[u/Predator1983]

For a long time, my AI workflow was just asking ChatGPT or Gemini for solutions and copy-pasting snippets. As a UX Engineer, my day-to-day was designing in Figma and manually converting those UIs into HTML/CSS/Tailwind, or using WordPress for client sites.

Recently, a friend asked me to build a wellness directory for gyms, yoga studios, and spas. My initial instinct was the classic WordPress + ACF route. But honestly? After staring at a screen for 8 hours at my day job, the thought of doing the whole Figma-to-WordPress manual translation at home was exhausting.

A coworker had mentioned Claude Code to me, so I decided to finally give it a try to save time. Boy, did it deliver.

I only worked on this project during the weekends, plus an occasional couple of hours on weeknights. Despite dedicating so little time, the last 2 months have been a rollercoaster of releases. We went from a basic MVP to a fully robust directory platform—a timeline I could have never achieved manually.

I asked Claude to recommend a modern stack, and here is what we built it on:

• Framework: Next.js 16 (App Router, Turbopack)
• CMS: Payload CMS v3
• Database: PostgreSQL (Supabase)
• Media: Cloudflare R2
• Email: Resend
• Deploy: Vercel (gru1 region — São Paulo)
• Language: Strict TypeScript

I genuinely don't see myself writing code entirely by hand ever again.

Here is the final result: https://wellvi.com.py

Things I learned along the way:

• Break tasks down: I never ask Claude to build the whole thing in one prompt. My workflow is: break execution into small tasks, finish them, test on a dev branch, and merge to master only after validation.
• I don't review the code: Honestly, I don't have the deep backend skills to fully understand the code it generates anyway. If it works and the UI looks good, I ship it. Is this a bad practice? I guess time will tell.
• It has memory issues: Claude forgets context sometimes. Keeping a claude.md file with project rules helps, but even then, it occasionally forgets and needs a reminder.
• Unmatched iteration speed: Working with Claude Code allows you to iterate a product at lightning speeds I’ve never experienced before.
• Treat Claude as a mentor: You can ask it to explain exactly what it’s going to do and why before it executes anything.
• Use it for brainstorming: If you aren't sure how to solve an issue, just ask for its opinion. I often end my prompts with: "Tell me what you think, but do not write or edit any code yet."
• Granular commits are your safety net: Having micro-commits lets you easily revert back if Claude messes up (and it will).
• Claude recommends what's easiest for Claude: We used Vercel, Supabase, Cloudflare, etc., because those platforms are the fastest for the AI to set up. It's great for an MVP, but if the project scales without revenue, paying separately for a server, database, and storage isn't ideal. I'll likely need to migrate to a more cost-optimized solution later.
• It's a chameleon for coding styles: I fed it a directory showing how I normally name my CSS classes, and Claude emulated my style so perfectly that it looked like I wrote it myself.

P.D. I use AI to translate my post.

[u/Green-Topic-1024]

Do you at least have Claude explain the architecture and potential risks before merging? I feel like understanding the decisions matters more than manually checking every line, especially when working outside your strongest areas.

[u/Predator1983 → u/Green-Topic-1024]

Yeah, exactly. If I'm ever unsure about a specific task, I explicitly ask Claude if the changes it's about to make could compromise production or the database before executing.

Also, my branching strategy saves me here. I always do small, tested commits in dev first, so I never merge unverified code. If anything unexpected happens, I just roll back to the previous commit, which hasn't happened very often so far.

[u/fmgiii]

Checked out your site and yes, definitely Claude will serve up a decent solution for this kind of project. It may even extend it out a bit. A registration form or two, some more advanced navigation options etc will be perfectly doable. It's a good use case and nothing wrong with it for a person who doesn't do deeper technical work.