refactor(landing): rebrand to VibeBetter and update CTA routing

[sungmanch]

Summary

• Rebrand all landing page metadata, badges, and copyright from "NoMoreAISlop" to "VibeBetter"
• Refactor all CTA buttons from scroll-to-pricing (scrollIntoView) to direct dashboard navigation (router.push('/dashboard/analyze'))
• Update messaging copy, pricing section, social proof, trust items, and showcase sample data to align with new brand voice

Changes

• b013df8 refactor(landing): rebrand metadata and OG tags to VibeBetter
• afd9401 refactor(landing): update hero, showcase, and footer CTA routing and messaging
• 3b7dba7 refactor(landing): update pricing section copy and CTA routing
• 50cc9c9 refactor(landing): update social proof, trust, and showcase sample data

Test Plan

• Code compiles without errors (tsc --noEmit passes)
• Landing page renders correctly with new branding
• All CTA buttons navigate to /dashboard/analyze
• OG meta tags show "VibeBetter" in social previews

---

Generated with Claude Code using /ship-it

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
no-more-ai-slop	Ready	Preview, Comment	Feb 13, 2026 5:03am

[sungmanch]

Code Review: Landing Page Rebrand to VibeBetter

Overall Assessment

The PR accomplishes its stated goals cleanly: CTA routing is consistently migrated from scrollIntoView to router.push('/dashboard/analyze'), analytics event types are unified to get_started_free, and the landing page copy is refreshed. The code is well-structured and follows existing patterns.

However, this PR only covers the landing page surface of the rebrand. There are significant branding remnants elsewhere in the codebase that will create an inconsistent user experience if not addressed in a follow-up.

---

What Was Done Well

• CTA routing is consistent. All 4 landing components (HeroSection, AnalysisShowcase, DownloadSection, LandingFooter) now use the same router.push('/dashboard/analyze') pattern with useRouter from next/navigation.
• Analytics events are unified. All CTA clicks now track type: 'get_started_free', making funnel analysis clean.
• The "6-dimension" to "5-dimension" fix is correct. WORKER_DOMAIN_CONFIGS defines exactly 5 domains (thinkingQuality, communicationPatterns, learningBehavior, contextEfficiency, sessionOutcome). This was a factual bug in the old copy.
• Showcase data rewrite is appropriate. Security risk examples now describe AI session-level risks (secret handling in prompts, skipped auth checks in generation) rather than traditional code-level vulnerabilities. This better matches the product's actual analysis output.
• CLAUDE.md compliance: All code and copy is in English. No fallback patterns introduced. No schema changes.

---

Issues Found

Important (Should Fix)

1. TerminalCommand.tsx still references "NoMoreAISlop" in mobile share

src/components/landing/TerminalCommand.tsx line 46:

navigator.share({
  title: 'NoMoreAISlop - AI Coding Style Analysis',
  url: window.location.href,
});

This component is part of the landing page and will show the old brand name when users trigger the mobile share sheet. Since this PR aims to rebrand the landing page, this file should be included.

2. metadataBase still points to nomoreaislop.app

app/layout.tsx line 23:

metadataBase: new URL('https://www.nomoreaislop.app'),

The title and siteName were changed to VibeBetter, but the canonical URL still references the old domain. If a new domain exists (e.g., vibebetter.app), this should be updated. If the domain hasn't changed yet, this is acceptable but should be tracked.

3. Root OG image (app/opengraph-image.tsx) not updated

This file renders the social share image and contains:

• Line 5: alt = 'NoMoreAISlop - See Your Anti-Patterns. Stop Making AI Slop.'
• Line 91: Renders NoMoreAISlop as brand text in the image
• Line 133: Shows npx no-ai-slop as terminal command
• Line 172: Shows www.nomoreaislop.app URL

When someone shares the landing page on Twitter/LinkedIn, they'll see "NoMoreAISlop" branding in the preview card, contradicting the VibeBetter copy on the actual page. This is a user-facing inconsistency.

Suggestions (Nice to Have)

4. Broad codebase branding remnants (out of scope, but worth tracking)

A search for "NoMoreAISlop" across the codebase reveals 23+ files in src/ and 15+ files in app/ still using the old brand name. Notable user-facing locations:

• app/benchmarks/page.tsx / BenchmarksContent.tsx -- page title and logo text
• app/docs/page.tsx / src/views/DocsPage.tsx -- documentation pages
• app/dashboard/analyze/page.tsx -- the exact page CTAs now route to
• app/r/[resultId]/page.tsx -- shared report pages
• app/auth/desktop-callback/page.tsx and app/auth/device/page.tsx -- auth flows
• src/components/report/ReportFooter.tsx, ShareSection.tsx -- report UI
• src/components/dashboard/DashboardSidebar.tsx -- dashboard navigation

These are outside the PR's stated scope, but a user clicking "Get Started Free" on the VibeBetter landing page will immediately land on pages branded as "NoMoreAISlop". Consider creating a tracking issue for the full rebrand sweep.

5. SectionNav references sections that may not all exist

src/components/landing/SectionNav.tsx references section IDs ['problems', 'solution', 'preview', 'teams', 'pricing']. While not changed in this PR, it's worth confirming all these section IDs still exist in LandingPage.tsx. The scrollIntoView in SectionNav (line 58) is legitimate since it's for in-page section navigation, not a CTA pattern -- this is fine.

6. DownloadSection CTA uses variant="secondary" while all others use variant="primary"

The pricing section CTA at line 146-155 of DownloadSection.tsx uses variant="secondary" while Hero, Showcase, and Footer all use variant="primary". This appears intentional (secondary CTA at bottom of pricing, primary for hero/showcase/footer), but worth confirming it's a deliberate visual hierarchy choice.

---

Summary

Category	Count
Critical (must fix)	0
Important (should fix)	3
Suggestions	3

The landing page changes themselves are clean and consistent. The main concern is the incomplete rebrand perimeter -- the OG image and TerminalCommand.tsx are part of the landing experience and should match. The broader codebase rebrand is understandably a separate effort, but the user journey from landing page to dashboard will currently cross brand boundaries.

Recommend: fix items 1-3 in this PR (or a fast follow), and create a tracking issue for the full-codebase rebrand (item 4).