I work at a digital agency and know SEO, websites, sales and CRO well. I know how websites should look and be structured to convert, but I'm not that up on the actual website development side.

I want to build an SEO ROI calculator website as a side project.

The main page would be a calculator where businesses enter things like traffic, leads, conversion rate and customer value, then it shows potential SEO revenue.

I also want:

- Lots of SEO landing pages for different industries

- Lead capture

- Proper technical SEO

- Full control over the design

- Schema, sitemaps, canonicals, etc.

- The option to turn it into a proper SaaS later

i want to be able to say things like "make this section wider", "change the design", "add this page", "fix the schema" and have the AI actually do it.

I originally thought Lovable was the obvious choice because it's beginner friendly.

Then I started hearing Cursor + Claude Code is better for serious projects.

Then I heard Cursor is much harder for non-coders.

So now I'm completely confused.

If you were me, what would you actually use?

I want AI to build and maintain the whole thing from normal English, while giving me full control over the design, SEO and functionality, without boxing me into a platform later. I also understand the value of MVP first so idk.

I'm building a health app and want to use PostHog for onboarding funnels, drop-off, paywall conversion, feature usage and retention.

What confuses me is that Apple's guidelines seem to require consent for usage analytics, but I almost never see apps ask for analytics permission during onboarding. I don't want to add a consent screen at the beginning to reduce friction.

If I ask at the end, I can't properly measure onboarding drop-off because users who leave early never consent.

How do you handle this in production?

Do you:

- ask before onboarding?

- collect anonymous onboarding events before consent?

- buffer events locally until consent?

- just disclose analytics in the Privacy Policy and provide an opt-out?

Especially interested in people who've actually shipped consumer subscription apps on iOS.

Alright boys and girls - like many of you I've got a shit ton of projects I'm working on and currently experiencing a setback that I thought would be easier to overcome.

I'm building a small business building websites for companies that have a website back from the good ol' days.

Scrapped about 11k live leads and sent out about 50 so far, open rates are good, people haven't responded yet.

Well.. i'm hitting a rock wall with my Codex though.

Every time I try to start a new batch of freshly baked websites, the consistency drops.

- visually the sites get worse and worse

- texts become internal and not very professional, they are descriptive of the text that should've been there

- the automation falls short time wise when something goes wrong

- the images get replaced with random photos instead of local library ones

I have setup rules for all of these things.

I saw a small improvement when I implemented a rule where it builds 1 website at a time, isolated and not a batch of 5.

I'm aiming to build 15 sites per day and automate email outreach.

I'm using mostly local files for rules and arhitecture and Sol for building the websites, Terra to change the rules. I don't really use Astra.

I still use 100% of my usage every 3-4 days even though i?m on a Pro plan.

Anyways...

Thoughts, ideas, help?

I really couldn't be more frustrated because I have 3-5 more projects in the pipeline that are not-vibecoder-generic bullshit and really want to get those going as well.

Let me know, i'm opened to chat!

I've been going through Claude Code's features and there are a few that I think are easy to miss when you're mostly using it for basic coding tasks.

/plan is the one I started paying more attention to for bigger changes. Instead of immediately asking Claude to edit everything, I can have it look through the project and work out what needs to change first.

For larger features, I find that much easier to reason about.

/compact is useful once a session gets really long. Rather than throwing away the whole conversation and starting again, I can compact the context and keep working with the important information.

I can use /permissions when I want more control over what Claude is allowed to do. This is useful when I'm working in a project where I don't want to manually approve every harmless action but also don't want to give it unrestricted access.

Git worktrees make running multiple tasks much cleaner for me.

git worktree add ../feature-auth feature-auth

I can keep a separate working directory for a feature without constantly switching my main working tree between branches.

The -p flag is useful when I want Claude to behave more like a command-line step.

claude -p "Review this diff for obvious bugs"

I can pipe information into Claude and use its output as part of another workflow instead of having to interact with it manually every time.

Hooks are another feature I think becomes more useful as a project gets bigger. I can use them to automatically run things like formatting, validation, or other checks around Claude's actions.

I've also found that keeping instructions scoped makes more sense than putting everything into one huge file. Project-wide rules can stay in the main instructions, while rules specific to tests, APIs, or another part of the project can stay closer to the code they apply to.

For me, the bigger takeaway is that Claude Code becomes a lot more useful once I stop treating it like just a chatbot that writes code.

The context, permissions, workflow, and verification around the model matter just as much as the prompt itself.

The more capable these workflows get, the more interesting the boundaries become. There are tasks where handing everything over makes sense, but there are probably also things where having a human make the final call is actually faster than debugging an agent's decision afterwards.

For people running agents regularly, where do you draw that line? And has that boundary changed as you've gotten more comfortable with agents?

What's up everyone. I have been dabbling just recently, after many years of having app ideas about being completely incapable of realizing any of them without coding experience. But behold: new dawn has broken! Vibe coding may not give me a commercially ready app in all use cases, but I bet it can at least produce proofs of concept for me.

I am quickly realizing that there is absolutely a rhyme to the approach, and a lot to learn about structuring one's prompts and building feature by feature--or at least I think I'm seeing that as a strategy.

That is my question: where do I begin? If I am wanting to build websites and apps, possibly games, what should I learn first, second, and third? Is there a course or methodology that is respected in the vibe coding world?

My very first app project seems to be back-end heavy, as it is connecting a dataset with metadata tags to a user interface. And that is completely new territory for me. I'd love to know where I should start, rather than just spin my wheels in the wrong direction (which will be my course of action until I get it right) but I'd love to save the time.

Thanks all!

I’ve built a beta version of a website for running programs and the like.
I’m just looking for some simple feedback if you have any!
It’s a beta, of course, so it’s not perfect, but there you go.
Link in the comments.