docs(www): rewrite hero description and record the vision in CLAUDE.md

CLAUDE.md

@@ -6,6 +6,8 @@ This is the dotUI repository — a design-system builder. Users compose a comple
 
 This is the goal, not the current state — check the code before assuming an axis exists.
 
+The vision: dotUI is the tool for creating a real, professional design system with your own taste — everything a startup needs as a foundation: technically strong, coherent, well built, and made to work well with AI. Create it once, then build on it everywhere — a web component library that matches your brand today; emails, native apps, and other platforms planned. Export widens the same way: the shadcn CLI and v0 today; vibe-coding tools like Bolt and Lovable, plus Figma and more, planned.
+
 The north star: the builder should be flexible enough to recreate almost any design system. If a user can't reproduce the look of a Material-, Geist-, or Linear-style system, an axis is missing. Coverage comes from a complete set of well-chosen axes, not infinite options: **every visual decision is a user-configurable axis of the builder**, never a hardcoded choice. Axes include (not exhaustive):
 
 - Color system: simple or advanced, selectable generation algorithm, semantic tokens, optionally context-aware tokens.
@@ -16,8 +18,6 @@ The north star: the builder should be flexible enough to recreate almost any des
 
 A second customization layer beyond visuals: `codeOptions` — the style of the exported code itself. Separator comments or not, arrow functions vs function declarations, tailwind-variants styles as commented arrays vs one line per slot/variant, etc. The exported design system should read like the user's codebase, not ours.
 
-Beyond that, export keeps widening: CLI + v0 today; Bolt, Lovable, Figma, Claude design, etc. planned.
-
 What this means when writing code today:
 
 - The test for hardcoded values: would two design systems disagree on it? The design system's look (color, radius, typography, shadows, density-affected spacing) goes through tokens/variants — `bg-primary`, not `bg-[#635bff]`. Component mechanics (internal layout, hairlines, hit areas) stay plain values — don't tokenize them. Look with no covering axis? Flag the missing axis; don't invent a token.

www/src/modules/marketing/home-page.tsx

@@ -47,8 +47,9 @@ export function HomePage() {
               </span>
             </h1>
             <p className="mt-5 max-w-2xl text-lg leading-relaxed text-balance text-fg-muted">
-              Every design decision is yours, previewed live on real components.
-              Install with the shadcn CLI, or export straight to v0.
+              Every design decision is yours — create, tweak, and ship code you
+              own.
+              {/* Once a non-web export ships: One foundation for all platforms. */}
             </p>
             <div className="mt-9 flex items-center gap-3">
               <LinkButton href="/studio" variant="primary" size="lg">