[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWQF3N3JSZKHAY5Y0RNHPW":3,"skill-same:01M6JWQF3N3JSZKHAY5Y0RNHPW":106},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6JWQF3N3JSZKHAY5Y0RNHPW","codiris-agentizer",null,"This skill should be used when the user asks to \"agentize a website\", \"transform a website\", \"create an agentfront\", \"build a WWA app\", \"make an agent-first website\", \"turn a website into an agent experience\", \"agentizer\", \"wwa transform\", or mentions \"agentfront\" in context of building one from a URL.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHumiris\u002Fwwa-transform\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"agentizer","codiris agentizer","build","when","agent-first","agentize","websearch","URL","make","transform","app","create","webfetch","user","context","edit","write","read","grep","Bash","first","website","2026-11-10 10:12:30",false,"---\nname: codiris-agentizer\ndescription: >-\n  This skill should be used when the user asks to \"agentize a website\",\n  \"transform a website\", \"create an agentfront\", \"build a WWA app\",\n  \"make an agent-first website\", \"turn a website into an agent experience\",\n  \"agentizer\", \"wwa transform\", or mentions \"agentfront\" in context of\n  building one from a URL.\nversion: 2.0.0\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Bash\n  - Glob\n  - Grep\n  - Agent\n  - WebFetch\n  - WebSearch\nargument-hint: \u003Cwebsite-url>\n---\n\n# Codiris Agentizer v2 — Intelligent Website-to-Agentfront\n\nTransform any website into a custom AI-powered agentfront. The skill deeply analyzes the company — its market, products, value proposition, customers — then builds a tailored experience. NOT a template copy-paste.\n\n## Core Principle\n\n**Understand the company first, build second.** Every company is different:\n- Stripe sells APIs to developers → show API products, code examples, pricing tiers\n- Nike sells shoes to consumers → show product catalog, categories, shopping\n- Visa sells payment cards → show card tiers, comparisons, benefits\n- Salesforce sells enterprise SaaS → show solutions by industry, case studies, demos\n\nThe agentfront must reflect what the company ACTUALLY is, not what Visa is.\n\n## Template Location\n`.\u002Ftemplate\u002F` relative to this SKILL.md — the skill directory (typically `~\u002F.claude\u002Fskills\u002Fagentizer\u002F` after install) contains the Next.js template. Content is generated custom per company. After `cp -R`, run the template's `npx next build` once to confirm nothing regressed in the template itself.\n\n## Reference Implementation\n**https:\u002F\u002Fwwa.visa.codiris.app** — live demo of a finished agentfront (payment card company). Source for the template is at https:\u002F\u002Fgithub.com\u002FHumiris\u002Fwwa-transform\u002Ftree\u002Fmain\u002Ftemplate.\n\nIf any template file looks incomplete or broken, inspect the live demo via WebFetch for visual reference, then apply the `visaCards → productItems` \u002F `VisaCard → ProductItem` \u002F `annualFee → price` renames — don't try to fix the template stub in place.\n\n---\n\n## PHASE 1: Deep Company Intelligence\n\n### Step 1.1: Crawl Multiple Pages\n\nUse `WebFetch` on at minimum:\n1. **Homepage** — hero, value prop, main CTAs, navigation\n2. **Products\u002FFeatures page** — what they actually sell\n3. **Pricing page** (if exists) — how they charge, what tiers\n4. **About page** — company story, mission, stats\n\nFor EACH page, ask WebFetch:\n```\nExtract everything: brand name, tagline, ALL image URLs (full absolute), \ncolors (hex from buttons\u002Fheaders\u002FCSS), navigation items, products\u002Ffeatures \nwith descriptions, pricing tiers, stats\u002Fnumbers, customer logos, \ntestimonials, CTAs, form fields. Be exhaustive.\n```\n\n### Step 1.2: AI Company Analysis\n\nAfter crawling, THINK deeply about the company. Answer these questions BEFORE writing any code:\n\n**Market Understanding:**\n- What industry is this company in? (Fintech, SaaS, E-commerce, Healthcare, etc.)\n- Who are their customers? (Developers, Enterprises, Consumers, SMBs)\n- What problem do they solve?\n- Who are their competitors?\n\n**Product Understanding:**\n- What do they sell? (APIs, Physical products, Subscriptions, Services, Cards)\n- How many products\u002Ftiers do they have?\n- How do they charge? (Per-transaction, Subscription, One-time, Usage-based, Free)\n- Do they have a free tier or trial?\n\n**Content Structure:**\n- What sections make sense for THIS company's homepage?\n- What navigation items should exist?\n- What categories should products be organized by?\n- Should there be a \"cards\" section? (Only if they sell cards\u002Fplans\u002Ftiers)\n- Should there be a pricing grid? A product catalog? Case studies?\n\n**Value Proposition:**\n- What's their main headline?\n- What stats are impressive? (Users, revenue, uptime, countries)\n- What social proof do they have? (Customer logos, testimonials)\n\n**Typography (CRITICAL — match brand aesthetic):**\n\nThe template uses Geist by default. You MUST change fonts to match the brand:\n\n| Brand Type | Fonts to Use | Implementation |\n|------------|--------------|----------------|\n| Luxury fashion (Dior, Hermès, Chanel) | Playfair Display + Inter | Serif headings, clean body |\n| Tech\u002FSaaS (Stripe, Notion, Linear) | Inter or Geist | Modern sans-serif |\n| Premium\u002FEditorial (Apple, Aesop) | SF Pro \u002F Helvetica Neue \u002F system fonts | Clean, minimal |\n| Fintech (Visa, Chase) | Geist \u002F Inter | Professional sans |\n| E-commerce (Amazon, Walmart) | Inter \u002F Roboto | Readable, utilitarian |\n\nUpdate `src\u002Fapp\u002Flayout.tsx`:\n```tsx\nimport { Playfair_Display, Inter } from \"next\u002Ffont\u002Fgoogle\";\n\nconst serif = Playfair_Display({ variable: \"--font-serif\", subsets: [\"latin\"] });\nconst sans = Inter({ variable: \"--font-sans\", subsets: [\"latin\"] });\n\n\u002F\u002F In body: className={`${serif.variable} ${sans.variable} font-sans`}\n```\n\nUpdate `src\u002Fapp\u002Fglobals.css`:\n```css\n:root {\n  --brand-primary: #000000;    \u002F* match brand color *\u002F\n  --brand-secondary: #C9A96E;\n  --font-serif-brand: var(--font-serif), \"Didot\", \"Bodoni MT\", \"Georgia\", serif;\n}\n\nh1, h2, .font-serif {\n  font-family: var(--font-serif-brand);\n  letter-spacing: -0.01em;\n}\n```\n\n**User Intent (CRITICAL — drives CTAs and modals):**\nAnalyze what users ACTUALLY do on this site. Map to correct CTA:\n\n| Company Type | Primary Intent | CTA Text | Modal Type |\n|--------------|---------------|----------|------------|\n| E-commerce (Dior, Nike, Apple) | Shop \u002F Buy products | \"Shop Now\" | Cart \u002F Product detail |\n| SaaS\u002FAPI (Stripe, Notion) | Try \u002F Book demo | \"Start Free\" or \"Book a Demo\" | Demo booking form |\n| Enterprise (Salesforce) | Contact sales | \"Contact Sales\" | Sales form |\n| Financial (Visa, banks) | Apply \u002F Get card | \"Apply Now\" | Application form |\n| Marketplace — Listings (Airbnb, Booking, Uber) | Search \u002F Book | \"Start Searching\" | Search UI |\n| Marketplace — C2C (Vinted, Depop, Etsy, eBay) | Sell AND Browse (dual intent) | \"Sell Now\" + \"Start Browsing\" | Seller signup modal (personal \u002F pro) |\n| Services (Consulting) | Contact \u002F Meeting | \"Book a Call\" | Calendar booking |\n| Content (Netflix, Spotify) | Subscribe \u002F Try | \"Start Free Trial\" | Signup form |\n\n**NEVER use \"Book a Demo\" for e-commerce.** E-commerce brands want you to SHOP, not schedule a meeting.\n\nUpdate these files based on intent:\n- `brand-config.ts` → `ctaPrimary` and `ctaSecondary`\n- `hero-section.tsx` → button text\n- `solution-detail-panel.tsx` → button text\n- `book-demo-modal.tsx` → rename, change fields to match intent (e-commerce = Contact Client Services, Cart, or remove entirely)\n- `actions.ts` system prompt → what the agent offers users\n\n### Step 1.3: Define the Page Architecture\n\nBased on your analysis, decide which sections the homepage should have. Choose from:\n\n| Section | Use When | Example |\n|---------|----------|---------|\n| Hero Carousel | Always | Rotating through top products\u002Ffeatures |\n| Stats Bar | Company has impressive numbers | \"$1.9T processed\", \"99.999% uptime\" |\n| Product Grid | 3+ distinct products | API products, SaaS modules |\n| Pricing Tiers | Clear pricing tiers exist | Free\u002FPro\u002FEnterprise |\n| Feature Showcase | Key differentiators | With images and descriptions |\n| Customer Logos | Has notable customers | \"Trusted by Amazon, Shopify...\" |\n| Solution Categories | Products grouped by use case | \"For Startups\", \"For Enterprise\" |\n| Code Example | Developer-focused company | Interactive code snippet |\n| Card Catalog | Sells cards\u002Fplans consumers browse | Credit cards, subscription plans |\n| CTA Banner | Always | \"Book a Demo\" \u002F \"Get Started\" \u002F \"Start Free\" |\n| World Map | Company has global presence story | Payment networks, logistics, international SaaS |\n\n**DO NOT include sections that don't apply:**\n- API company → NO credit card tiers, NO card comparison\n- E-commerce → NO API docs, NO code examples\n- SaaS without global story → NO world map (make `handleShowMap` a no-op in page.tsx)\n- Company without browsable products → leave `productItems` array empty, the browse section won't render\n\n---\n\n## PHASE 2: Download Assets\n\n### Step 2.1: Download ALL Images\n\n**MANDATORY.** The agentfront is useless without real images.\n\n> ❗ **The single biggest bug in past transforms** is shipping images from the wrong brand — a generic \"sneaker\" photo from Unsplash that happens to show a Nike Swoosh on an adidas site, or a \"handbag\" photo that's clearly Chanel on a Dior site. Mis-branded imagery destroys credibility instantly.\n>\n> **Rule**: Every image that represents a **specific named product or franchise** (e.g. \"Samba OG\", \"Air Max 90\", \"Lady Dior\") MUST come from a source that lets you verify it shows the correct brand. Generic-category Unsplash photos are banned for these slots. They are OK only for brand-agnostic shots (lifestyle hero, category tiles with no named product, abstract backgrounds).\n>\n> **And every image MUST pass visual verification (Step 2.3) before you write its path into `cards.ts` \u002F `solutions.ts`.**\n\n```bash\nmkdir -p ~\u002Fwwa.{domain}\u002Fpublic\u002Fimages\u002Fcards\n\n# Use browser headers to bypass CDN blocks\ncurl -L -o \"public\u002Fimages\u002F{name}.jpg\" \"{url}\" \\\n  -H \"User-Agent: Mozilla\u002F5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit\u002F537.36\" \\\n  -H \"Referer: https:\u002F\u002F{domain}\u002F\" \\\n  -H \"Accept: image\u002F*\"\n```\n\n**Download at minimum:**\n- Logo (SVG preferred, PNG fallback)\n- Hero\u002Fbanner image\n- 1 image per product\u002Fsolution (6-10 total)\n- 2-4 lifestyle\u002Ffeature images\n- Customer logos if available\n- Product screenshots\u002FUI images\n\n### Image Source Priority (USE IN THIS ORDER)\n\n**For e-commerce catalogs (fashion retailers, beauty retailers, online-only fashion), always try method 0 FIRST:**\n\n**0. Scrape the brand's SSR catalog JSON via Chrome MCP** — modern e-commerce sites (Zara, H&M, ASOS, Nordstrom, Sephora, etc.) ship the full product grid as a JSON blob inside a `\u003Cscript>` tag on every category page. Server-side curl gets WAF-blocked, but Chrome MCP with an organic-looking tab has no trouble reading the DOM.\n\nTwo flavors to look for:\n\n- **JSON-LD `\u003Cscript type=\"application\u002Fld+json\">`** (cleanest — H&M, many schemas). Has `@type: Product` entries with `name`, `image[]`, `offers.price` ready to `JSON.parse`.\n- **Raw hydration JSON** (Zara, ASOS — biggest `\u003Cscript>` that contains the brand's CDN hostname). Not always valid JSON; regex out the image URL pattern (e.g. `\u002Fstatic\\.zara\\.net\\\u002Fphotos\\\u002F[^\"'\\s]+\\.jpg\u002Fg` or `\u002Fproducts\\\u002F[a-z0-9-]+\\\u002F\\d+-\\d+[a-z0-9-]*\u002Fgi`) and dedupe by product id.\n\nPattern that works today (verified on Zara 259 · H&M 216 · ASOS 365 · Uniqlo 54 scrapes):\n\n```js\n\u002F\u002F In Chrome MCP, navigate to e.g. https:\u002F\u002Fwww.zara.com\u002Fuk\u002Fen\u002Fwoman-dresses-l1066.html, then:\n(() => {\n  const scripts = Array.from(document.querySelectorAll('script'));\n  \u002F\u002F JSON-LD path (H&M-style): cleanest\n  const ld = document.querySelector('script[type=\"application\u002Fld+json\"]');\n  if (ld && ld.textContent.includes('\"@type\":\"Product\"')) {\n    return JSON.parse(ld.textContent);\n  }\n  \u002F\u002F Raw-hydration path (Zara\u002FASOS): regex\n  const big = scripts.find(s => (s.textContent || '').includes('\u003Cbrand-cdn-hostname>'));\n  const text = big.textContent;\n  \u002F\u002F Adjust regex per brand URL shape\n  const urls = [...new Set((text.match(\u002Fhttps:\\\u002F\\\u002Fstatic\\.zara\\.net\\\u002F[^\"'\\s]+\\.jpg\u002Fg) || []))];\n  return urls;\n})();\n```\n\nThen get the result out of Chrome via a `Blob` download:\n\n```js\nconst blob = new Blob([JSON.stringify(catalog)], { type: 'application\u002Fjson' });\nconst a = Object.assign(document.createElement('a'), { href: URL.createObjectURL(blob), download: 'catalog.json' });\ndocument.body.appendChild(a); a.click();\n\u002F\u002F File lands in ~\u002FDownloads\u002Fcatalog.json — move to project, feed to cards.ts rewrite\n```\n\n**Hotlink don't download.** Once you have the URLs, put them directly in `cards.ts`'s `image` field — the browser will load them via `\u003Cimg src>` (no CORS issue on img tags). No local copy needed. Server-side curl typically fails with 403 \u002F 000 (WAF), but that doesn't matter because production serves from users' browsers.\n\n**For named products\u002Ffranchises** (Samba, Air Jordan 1, Stan Smith, Lady Dior, Birkin, etc.) where you need individual-product photos not a catalog:\n\n1. Brand's own CDN (works for most sportswear — Nike, adidas, Puma, Asics, New Balance)\n2. **Wikipedia \u002F Wikimedia Commons** — the category page `commons.wikimedia.org\u002Fwiki\u002FCategory:{Brand}_{Product}` has real, licensed product photos for every iconic sneaker, boot, bag, watch, perfume, etc.\n3. Industry publication CDN for the brand's segment (WWD for fashion, Fragrantica for perfume, SneakerNews\u002FHypebeast for sneakers)\n4. **DROP THE PRODUCT from `productItems`** if none of 1–3 yields a verified photo. A site with 6 real products is infinitely better than a site with 8 and two wrong-brand frauds.\n\n**Unsplash is BANNED for named-product slots.** It's OK only for: hero lifestyle shots (action\u002Fatmosphere, no named product), brand-agnostic category tiles, abstract backgrounds. If you use it, still run Step 2.3 verification — generic sneaker\u002Fbag photos on Unsplash very frequently show competitor logos.\n\nMost premium brand sites (Dior, Apple, Notion, Vercel, Hermès) AGGRESSIVELY BLOCK curl. Do NOT waste time trying to download from the brand's CDN. Skip directly to the fallback.\n\n**Sportswear CDNs are hit-or-miss** — Puma, Nike, Adidas, Asics, Under Armour, New Balance, Reebok sometimes serve real JPEGs on their public CDNs, but **you have to know the exact style code** and the match rate is worse than you'd expect. Observed on recent transforms:\n\n- **adidas** (`assets.adidas.com`) — returned 0 bytes on every style code tried (Apr 2026)\n- **Nike** (`static.nike.com`) — works for some products, requires inspecting a product page's `\u003Cimg srcset>` to get the right hash\n- **New Balance** (`nb.scene7.com`) — works with a Referer header, but style codes are hard to guess; ~50% hit rate even for the most popular models\n- **Puma** (`images.puma.com`) — most reliable of the sportswear CDNs\n\n**Rule of thumb**: try the brand CDN once with a single well-known SKU. If it returns real bytes (>20KB), map your remaining products; if it 0-bytes or errors, drop straight to Wikimedia Commons. Don't spend 10 minutes guessing style codes.\n\n| Brand | CDN pattern | How to get the `{styleId}` |\n|-------|-------------|----------------------------|\n| Puma | `https:\u002F\u002Fimages.puma.com\u002Fimage\u002Fupload\u002Ff_auto,q_auto,w_800,h_800\u002Fglobal\u002F{styleId}\u002F01\u002Fsv01\u002Ffnd\u002FPNA\u002Ffmt\u002Fpng\u002F{slug}` | The number after `\u002Fpd\u002Fslug\u002F` on a product page |\n| Nike | `https:\u002F\u002Fstatic.nike.com\u002Fa\u002Fimages\u002Ft_PDP_1280_v1\u002Ff_auto,q_auto:eco\u002F{hash}\u002F{slug}.jpg` | Inspect a product page's `\u003Cimg srcset>` |\n| Adidas | `https:\u002F\u002Fassets.adidas.com\u002Fimages\u002Fw_600,f_auto,q_auto\u002F{styleId}\u002F{slug}.jpg` | Often blocked — try once, fall back to Wikimedia |\n| New Balance | `https:\u002F\u002Fnb.scene7.com\u002Fis\u002Fimage\u002FNB\u002F{styleId}_nb_02_i?wid=1200&hei=1200` | Match the style id on the product page (e.g. `m1906rcd`) |\n\nAlways include `-H \"Referer: https:\u002F\u002F{brand-domain}\u002F\"` — the Cloudinary-style CDNs behind most sportswear brands accept the request with referrer, 404 it without.\n\n**Remember**: even when the CDN works, you still MUST run Step 2.3 visual verification on the downloaded bytes — CDNs occasionally return placeholder\u002Fblank images with a 200 status.\n\n**1. Brand's own CDN** (always try first for sportswear\u002Fathletic; ~30% of premium luxury sites; skip straight to #3 for most editorial\u002Fluxury brands)\n```bash\ncurl -sL -o public\u002Fimages\u002F{name}.jpg \"{url}\" \\\n  -H \"User-Agent: Mozilla\u002F5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit\u002F537.36\" \\\n  -H \"Referer: https:\u002F\u002F{domain}\u002F\"\n```\n\n**2. Wikipedia \u002F Wikimedia Commons** — works for famous brands, logos, iconic products\n```bash\ncurl -sL -o public\u002Fimages\u002Fbrand-logo.svg \\\n  \"https:\u002F\u002Fupload.wikimedia.org\u002Fwikipedia\u002Fcommons\u002F{path}\u002F{file}.svg\" \\\n  -H \"User-Agent: Mozilla\u002F5.0\"\n```\nUse WebSearch: \"{brand} logo SVG wikimedia commons\"\n\n**2.5. INDUSTRY PUBLICATIONS — USE THIS FOR FASHION BRANDS**\nFashion\u002Fluxury brands block their own CDN, but fashion PUBLICATIONS host real runway photos:\n\n```bash\n# WWD (Women's Wear Daily) — 2-3MB runway photos, works without auth\n# Pattern: https:\u002F\u002Fwwd.com\u002Fwp-content\u002Fuploads\u002F{YYYY}\u002F{MM}\u002F{brand}-{collection}-{location}-GG-{01-80}.jpg\n\ncurl -sL -o public\u002Fimages\u002Frunway.jpg \\\n  \"https:\u002F\u002Fwwd.com\u002Fwp-content\u002Fuploads\u002F2025\u002F05\u002Fdior-cruise-2026-rome-GG-01.jpg\" \\\n  -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Fragrantica CDN — real perfume bottle photos, works without auth\n# Pattern: https:\u002F\u002Ffimgs.net\u002Fmdimg\u002Fperfume\u002F375x500.{perfume_id}.jpg\n# Find IDs via WebSearch: \"{perfume name} fragrantica\"\n\ncurl -sL -o public\u002Fimages\u002Fjadore.jpg \\\n  \"https:\u002F\u002Ffimgs.net\u002Fmdimg\u002Fperfume\u002F375x500.210.jpg\" \\\n  -H \"User-Agent: Mozilla\u002F5.0\"\n```\n\nOther working fashion\u002Fbeauty publication CDNs:\n- **wwd.com\u002Fwp-content\u002Fuploads\u002F** — runway, backstage, beauty product shots\n- **fimgs.net\u002Fmdimg\u002Fperfume\u002F** — perfume bottles (Fragrantica)\n- **nowfashion.com\u002Fwp-content\u002Fuploads\u002F** — runway photos\n- **showstudio.com\u002F** — editorial fashion content\n- **vogue.com\u002Fphotos\u002F** — often requires auth\n- **fashionography.com\u002Fwp-content\u002Fuploads\u002F** — runway archives\n\n**IMPORTANT:** Sample a couple of images first (~2-3MB each). On macOS use `sips -Z 1200 input.jpg -o output.jpg` to resize before committing.\n\n### Brand Videos for Hero Backgrounds\n\nMany luxury brands have hero video loops that dramatically elevate the feel. Look for them:\n\n```bash\n# Brand-hosted videos often work with proper headers\ncurl -sL -o public\u002Fvideos\u002Fhero.webm \"{brand-video-url}\" \\\n  -H \"User-Agent: Mozilla\u002F5.0\" \\\n  -H \"Referer: https:\u002F\u002F{domain}\u002F\"\n```\n\n**Finding brand video URLs:**\n- Dior: `diorama.dam-broadcast.com\u002F...` — works publicly\n- Apple: `apple.com\u002Fassets-www\u002F...` — often public\n- Most fashion houses have `dam-broadcast` or `.cdn.` video CDNs\n- Inspect the brand's homepage for `\u003Cvideo>` or `\u003Csource>` tags with `.webm` \u002F `.mp4`\n- WebSearch: \"{brand} hero video webm\" or check Dam broadcast networks\n\n**Implementation in hero-section.tsx:**\n```tsx\n\u003Cvideo autoPlay loop muted playsInline className=\"absolute inset-0 w-full h-full object-cover\" poster=\"\u002Fimages\u002Fhero-image.jpg\">\n  \u003Csource src=\"\u002Fvideos\u002Fhero.webm\" type=\"video\u002Fwebm\" \u002F>\n\u003C\u002Fvideo>\n\u003Cdiv className=\"absolute inset-0 bg-gradient-to-b from-black\u002F10 via-transparent to-black\u002F70\" \u002F>\n```\n\nVideo hero is essential for luxury brands. Fall back to static image if video can't be obtained. Keep videos under 10MB (resize with ffmpeg if needed).\n\n**American heritage brands (Ralph Lauren, Levi's, L.L. Bean, J.Crew, Tommy Hilfiger) rarely expose public video CDNs.** Plan for a static full-bleed runway or editorial hero with a subtle 1.04 scale-on-mount or parallax effect instead — don't waste time hunting for a video that isn't there.\n\n**3. Unsplash (MANDATORY FALLBACK — always works, real product photos)**\n```bash\n# Search URL pattern: https:\u002F\u002Fimages.unsplash.com\u002Fphoto-{id}?w=800&q=80\n# DO NOT make up IDs — use these tested working IDs by category:\n\n# Luxury perfume \u002F fragrance bottle\ncurl -sL -o public\u002Fimages\u002Fperfume.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1541643600914-78b084683601?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Men's cologne \u002F dark bottle  \ncurl -sL -o public\u002Fimages\u002Fcologne.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1594035910387-fea47794261f?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Pink\u002Ffeminine perfume\ncurl -sL -o public\u002Fimages\u002Fmiss.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1592945403244-b3fbafd7f539?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Luxury handbag\ncurl -sL -o public\u002Fimages\u002Fbag.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1584917865442-de89df76afd3?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Canvas tote\ncurl -sL -o public\u002Fimages\u002Ftote.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1590874103328-eac38a683ce7?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Leather bag\ncurl -sL -o public\u002Fimages\u002Fleather-bag.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1548036328-c9fa89d128fa?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Red lipstick\ncurl -sL -o public\u002Fimages\u002Flipstick.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1586495777744-4413f21062fa?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Foundation \u002F makeup\ncurl -sL -o public\u002Fimages\u002Ffoundation.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1512496015851-a90fb38ba796?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Skincare cream\ncurl -sL -o public\u002Fimages\u002Fskincare.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1556228720-195a672e8a03?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Luxury skincare bottles\ncurl -sL -o public\u002Fimages\u002Fserum.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1608248543803-ba4f8c70ae0b?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Gold jewelry \u002F rings\ncurl -sL -o public\u002Fimages\u002Fjewelry.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1515562141207-7a88fb7ce338?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Fashion \u002F clothing\ncurl -sL -o public\u002Fimages\u002Ffashion.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1558769132-cb1aea458c5e?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Building \u002F atelier (hero\u002Fabout)\ncurl -sL -o public\u002Fimages\u002Fbuilding.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1519643225200-94e79e383724?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# SaaS \u002F tech product screenshot\ncurl -sL -o public\u002Fimages\u002Fsaas-ui.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1551288049-bebda4e38f71?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Abstract tech \u002F code\ncurl -sL -o public\u002Fimages\u002Ftech.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1518770660439-4636190af475?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# ═══════ ATHLETIC \u002F SPORTSWEAR (verified on Puma transform) ═══════\n\n# Running \u002F runner silhouette\ncurl -sL -o public\u002Fimages\u002Frunning.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1508685096489-7aacd43bd3b1?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Training \u002F gym \u002F lifting\ncurl -sL -o public\u002Fimages\u002Ftraining.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1517836357463-d25dfeac3438?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Football \u002F soccer\ncurl -sL -o public\u002Fimages\u002Ffootball.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1431324155629-1a6deb1dec8d?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Motorsport \u002F racing\ncurl -sL -o public\u002Fimages\u002Fmotorsport.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1504276048855-f3d60e69632f?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Kids athletic\ncurl -sL -o public\u002Fimages\u002Fkids.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1503944583220-79d8926ad5e2?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Athletic fashion \u002F streetwear runner\ncurl -sL -o public\u002Fimages\u002Fathleisure.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1558769132-cb1aea458c5e?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n```\n\n> **Unsplash ID format caveat:** stick to the timestamp-hex pattern (`photo-1508685096489-7aacd43bd3b1`). Modern Unsplash URLs use slug-style IDs (`hEIHXXic3yI`) that **do NOT work** with `https:\u002F\u002Fimages.unsplash.com\u002Fphoto-{slug}`. If an ID you find is 11 random characters instead of the classic timestamp-hex form, you need the old numeric pattern or the image will 404.\n\n**Verify downloads:** Check file size with `ls -la`. Files under 1KB are failures. Failed downloads return ~29 bytes (Unsplash not-found) or ~300 bytes (error page). Re-download with different ID if under 1KB.\n\n**4. Placehold.co** — LAST RESORT ONLY if Unsplash also fails\n```bash\ncurl -sL -o public\u002Fimages\u002F{name}.jpg \"https:\u002F\u002Fplacehold.co\u002F800x400\u002F{hex_no_hash}\u002Fwhite?text={Product}\"\n```\n\n### Required Downloads\n\nEvery project MUST have (minimum):\n- Logo (SVG from Wikipedia or brand CDN)\n- Hero image (brand or category-matched Unsplash)\n- 1 image per solution (category-matched Unsplash)\n- 1 image per product (category-matched Unsplash)\n- Favicon from `https:\u002F\u002Fwww.google.com\u002Fs2\u002Ffavicons?domain={domain}&sz=64`\n\n### Catalog size — minimum item count per brand type (REQUIRED)\n\nA thin catalog kills the demo. Every e-commerce, retail, or fashion brand transform MUST ship at least **100 real product items** spread across the brand's natural segments. The agent needs enough depth to recommend and compare realistically; an 8-item catalog makes every filter \u002F category \u002F chat prompt dead-end immediately.\n\n| Brand type | Minimum items | Split guidance |\n|------------|---------------|----------------|\n| Fashion mono-brand (Zara, H&M, Uniqlo, Ralph Lauren, Dior RTW) | **100+** | 40 Woman \u002F 30 Man \u002F 15 Kids \u002F 10 Accessories \u002F 5 Home — adjust to brand reality |\n| Fashion multi-brand retailer (Nordstrom, Net-A-Porter, Farfetch, Zalando) | **150+** | 50 Woman \u002F 40 Man \u002F 25 Kids \u002F 20 Shoes \u002F 15 Bags — plus 20+ brand catalogue entries |\n| Beauty multi-brand retailer (Sephora, Ulta, LookFantastic) | **120+** | 30 Skincare \u002F 30 Makeup \u002F 25 Fragrance \u002F 15 Hair \u002F 10 Body \u002F 10 Men — plus 20+ brands |\n| Beauty mono-brand (L'Oréal, Estée Lauder, MAC) | **80+** | 25 Skincare \u002F 25 Makeup \u002F 15 Fragrance \u002F 10 Hair \u002F 5 Men |\n| Outerwear \u002F Technical (Canada Goose, Arc'teryx, Patagonia) | **60+** | 25 Men \u002F 20 Women \u002F 10 Kids \u002F 5 Accessories — fewer items OK because parkas are expensive\u002Fcurated |\n| Luxury mono-brand (Hermès, Chanel — no RTW catalog online) | **50+** | Scale to what's published; bags + fragrance + leather small goods heavy |\n| Sportswear (Nike, Puma, Adidas, Under Armour) | **100+** | 30 Men \u002F 30 Women \u002F 20 Kids \u002F 15 Footwear \u002F 5 Accessories |\n| Marketplace listings (Airbnb, Booking) | **100+ stays × 40+ destinations** | destinations.ts covers the cities, cards.ts covers the stays |\n| Marketplace C2C (Vinted, Depop, Etsy) | **80+ feature tiles + category mock listings** | cards.ts holds features\u002Fflows, not individual listings |\n| Fintech \u002F SaaS | 6-12 products is fine | Few products is brand-accurate (Visa has ~8 tiers, Stripe has ~10 products) |\n\n**How to reach 100+ on an e-commerce transform:**\n1. Start by listing the brand's real product segments (Woman\u002FMan\u002FKids\u002FHome\u002FBeauty for Zara; Skincare\u002FMakeup\u002FFragrance for Sephora). Write the minimum count per segment before downloading images.\n2. Scrape representative products from the brand's own site when possible, even if names are paraphrased — the image + name + price + material gives the agent enough to recommend.\n3. When the brand CDN blocks (Zara, Dior, etc.), fall through to Unsplash with segment-matched searches. Each segment needs 30+ unique photos; guard against duplicates.\n4. Every product entry in `cards.ts` MUST be a real-looking record with: name + price + segment (gender\u002Fcategory) + material\u002Fsize + badge. Agent recommendations against a half-populated catalog feel hollow.\n\n**Per-section rendering rule (NEW, critical — addresses \"there's not a lot of items on Men's\" feedback):**\n\nThe catalog-size rule above covers `cards.ts` data depth. The **rendering cap** is a separate trap: template components often render `homes.slice(0, 12)` or similar, so even with 100+ items in data, the user sees a thin 8-tile grid.\n\n- **Homepage carousel rows**: 12-16 tiles OK (carousel UX, user scrolls horizontally).\n- **Category \u002F gender inner pages** (when user clicks \"Men's\" or \"Woman\" from nav or a tile): **MUST render the full filtered catalog, no slice cap.** If the brand has 30 Men's items, the Men's page shows 30, not 12. Minimum per-section display:\n  - Woman \u002F Man: 30+ tiles visible on the inner page\n  - Kids \u002F Baby: 15+ tiles\n  - Accessories \u002F Home \u002F Beauty: 10+ tiles\n- **Fix pattern**: in `inner-page.tsx` (or equivalent), the category grid must `productItems.filter(p => p.issuer === gender)` without a trailing `.slice()`. If the page feels too long, use pagination \u002F \"Load more\" — not a silent truncation.\n- Grep check before shipping: `grep -rnE '\\.slice\\(0,\\s*(6|8|12)' src\u002Fcomponents\u002Finner-page.tsx src\u002Fcomponents\u002Fhero-section.tsx src\u002Fapp\u002Fpage.tsx` — if caps are present on gender\u002Fcategory paths, they're bugs.\n\n**Quality gate (add to Phase 4 verification):**\n- `curl https:\u002F\u002Fwwa.{slug}.codiris.app\u002Fmcp -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Fcall\",\"params\":{\"name\":\"search_products\",\"arguments\":{}}}'` → `count: 100+` for any e-commerce brand type.\n- Curl the rendered HTML of the Men's \u002F Woman's category pages and count `\u003Cimg` tags for product tiles. Must be 30+ each (for mono-brand fashion) or 40+ (for multi-brand fashion). If below threshold, UI has a rendering cap that needs removal — the transform is incomplete.\n\n**Post-deploy smoke check (catches stale-alias bugs):** after `vercel alias set`, always re-verify that the alias points to the LATEST deploy. A common failure mode: you fix the code locally, run `npx vercel --prod`, but forget to re-alias — so `wwa.{slug}.codiris.app` continues pointing to the previous (broken) deploy. The Zara\u002FUniqlo\u002FH&M\u002FASOS retrofit pass uncovered 4 stale aliases where the uncap code was already correct in git but not reflected live. Always run:\n\n```bash\nnpx vercel --prod --yes 2>&1 | tee \u002Ftmp\u002Fdeploy.log\nDEPLOY_URL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.vercel\\.app' \u002Ftmp\u002Fdeploy.log | head -1)\nnpx vercel alias set \"$DEPLOY_URL\" wwa.{slug}.codiris.app\n# Then verify:\ncurl -s https:\u002F\u002Fwwa.{slug}.codiris.app\u002F | grep -c 'aspect-\\[3\u002F4\\]\\|aspect-\\[4\u002F5\\]\\|aspect-square'  # rough product-tile count\n```\n\n**MANDATORY: push API keys from a sibling project before declaring \"deployed\" (catches silent-AI-fallback bug):** every brand-new Vercel project starts with **zero env vars**. Without `GEMINI_API_KEY` \u002F `GOOGLE_GENERATIVE_AI_API_KEY` \u002F `OPENAI_API_KEY`, the AI panel silently falls back to canned `assistant-shared.tsx` strings (\"I can help you find...\"), and the user thinks the AI is dumb. Caught on the Joivy deploy after the user complained the AI was \"stupid\". The 200-response on `\u002Fapi\u002Fgemini-key` is the actual smoke check — until that endpoint returns a real key, the demo is broken even if every page renders correctly.\n\n```bash\n# Pull keys from any sibling project that already has them (wwa-vinted is reliable)\nmkdir -p \u002Ftmp\u002Fsibling-env && cd \u002Ftmp\u002Fsibling-env && mkdir -p .vercel\ncat > .vercel\u002Fproject.json \u003C\u003C 'EOF'\n{\"projectId\":\"prj_eoF8zwRk4i3blOS7Cy95N9Zn5I1s\",\"orgId\":\"team_CVjPPr2WoqlNcN6zmRDjk04Q\",\"projectName\":\"wwa-vinted\"}\nEOF\nnpx vercel env pull .env.production --environment=production --yes\n\n# Push to the new project via Vercel API\nTOKEN=$(python3 -c \"import json; print(json.load(open('\u002FUsers\u002Fjoel\u002FLibrary\u002FApplication Support\u002Fcom.vercel.cli\u002Fauth.json')).get('token',''))\")\nTEAM=\"team_CVjPPr2WoqlNcN6zmRDjk04Q\"\nPID=$(cat \u002Ftmp\u002Fwwa.{slug}\u002F.vercel\u002Fproject.json | python3 -c \"import sys,json; print(json.load(sys.stdin)['projectId'])\")\nfor k in GEMINI_API_KEY GOOGLE_GENERATIVE_AI_API_KEY OPENAI_API_KEY; do\n  v=$(grep \"^${k}=\" \u002Ftmp\u002Fsibling-env\u002F.env.production | head -1 | cut -d= -f2- | sed 's\u002F^\"\u002F\u002F;s\u002F\"$\u002F\u002F')\n  curl -s -X POST \"https:\u002F\u002Fapi.vercel.com\u002Fv10\u002Fprojects\u002F$PID\u002Fenv?teamId=$TEAM\" \\\n    -H \"Authorization: Bearer $TOKEN\" -H \"Content-Type: application\u002Fjson\" \\\n    -d \"$(python3 -c \"import json,sys; print(json.dumps({'key':'$k','value':'$v','type':'encrypted','target':['production','preview','development']}))\")\"\ndone\n\n# REDEPLOY + RE-ALIAS so the new envs take effect (env changes don't apply to existing builds)\ncd \u002Ftmp\u002Fwwa.{slug} && npx vercel --prod --yes\n# Then alias the new deploy.\n\n# Smoke check — this is the line that proves the AI works:\ncurl -s -X POST https:\u002F\u002Fwwa.{slug}.codiris.app\u002Fapi\u002Fgemini-key -H \"Content-Type: application\u002Fjson\" -w \"\\n%{http_code}\\n\"\n# Must return {\"key\":\"AIza...\"} and HTTP 200. Anything else = AI is silently degraded.\n```\n\n### Matching Unsplash Photos to Categories\n\n| Company Type | Use These Photos |\n|--------------|-----------------|\n| Luxury\u002FFashion (Dior, Hermès, LV) | Perfume + handbag + lipstick + jewelry + fashion |\n| Cosmetics (Sephora, Fenty) | Lipstick + foundation + makeup brushes |\n| Tech\u002FSaaS (Stripe, Notion) | SaaS UI screenshots + tech + abstract |\n| E-commerce (Amazon, Shopify) | Product shots + packaging + shopping |\n| Fintech (Visa, Chase) | Cards + phone + wallet |\n\n### Step 2.2: Download Favicon\n\n```bash\ncurl -L -o \"public\u002Ffavicon.ico\" \"https:\u002F\u002Fwww.google.com\u002Fs2\u002Ffavicons?domain={domain}&sz=64\"\n```\n\n### Step 2.3: Visual verification — MANDATORY before writing any image path into `cards.ts` \u002F `solutions.ts`\n\nYou are a multimodal model. You can see images. **Use the `Read` tool on every downloaded file** and visually inspect what it actually depicts. Do this BEFORE referencing the image from any data file.\n\n```\nRead file_path=\u002Fabsolute\u002Fpath\u002Fto\u002Fpublic\u002Fimages\u002Fsamba.jpg\n```\n\nFor each image, verify the following before approving it:\n\n1. **Brand match.** If the image represents a named product, does it show the correct brand's logo, wordmark, or trademark graphic?\n   - Nike → Swoosh visible and no other brand logos\n   - adidas → 3-Stripes and\u002For Trefoil visible, no Swoosh, no \"N\", no Brooks, no Puma cat\n   - Dior → \"Dior\" wordmark or CD monogram\n   - Hermès → \"H\" clasp or Kelly\u002FBirkin silhouette with Hermès marking\n   - Apple → Apple logo, no Samsung\u002FGoogle\u002Fother\n2. **Product match.** If the image is tied to a specific franchise in `solutions.ts` (e.g. \"Air Max\"), does the shoe in the photo actually look like an Air Max (visible Air unit) vs. a random sneaker?\n3. **No competitor logos.** If you can see **any** competitor's logo anywhere in the frame (even on a background wall, a bystander's shirt, the box the product is sitting on), reject the image.\n4. **No off-brand props.** A Nike shoebox in the corner of an adidas product shot → reject.\n\n**If verification fails**, in order:\n\n1. Retry with a different source from the priority list (Wikimedia Commons almost always has a clean product shot).\n2. If still no luck, **remove that product from `productItems` \u002F that franchise from `solutions`** rather than ship the bad image.\n3. NEVER \"just swap the filename\" and hope — the file on disk is what ships.\n\n**Checklist to run at the end of Phase 2:**\n\n```bash\n# List every image file with its size\nls -la public\u002Fimages\u002F*.jpg public\u002Fimages\u002F*.png public\u002Fimages\u002F*.svg 2>\u002Fdev\u002Fnull\n```\n\nThen, for EACH non-logo image, use `Read` on it and log either `VERIFIED: shows real \u003Cbrand> \u003Cproduct>` or `REJECTED: shows \u003Cwhat-it-actually-is>`. If any rejected image is still referenced from `cards.ts` \u002F `solutions.ts`, **you have failed this step** — fix it before proceeding to Phase 3.\n\n**For sizing**: if an image is ≥ 3MB, resize on macOS with `sips -Z 1200 input.jpg -o output.jpg` or `sips -Z 1200 --setProperty formatOptions 80 input.jpg -o output.jpg` to keep page weight reasonable.\n\n---\n\n## PHASE 3: Build the Project\n\n### Step 3.1: Copy Framework\n\n```bash\n# From inside the cloned skill (typically ~\u002F.claude\u002Fskills\u002Fagentizer):\nmkdir -p ~\u002Fwwa.{domain}\ncp -R .\u002Ftemplate\u002F. ~\u002Fwwa.{domain}\u002F\ncd ~\u002Fwwa.{domain} && npm install\n```\n\nDo NOT copy from absolute maintainer paths like `\u002FUsers\u002Fjoel\u002Fwwa-skill\u002Ftemplate\u002F` — that path only exists on the maintainer's machine. Always copy `.\u002Ftemplate\u002F.` relative to the skill directory that contains this SKILL.md.\n\n**Template naming:** The template uses `ProductItem`\u002F`productItems` (not VisaCard\u002FvisaCards) as generic names for browsable items. The navbar component is `brand-navbar.tsx`, the map is `world-map.tsx`. All imports in page.tsx already use these names.\n\n### Step 3.1b: Sweep Visa color tokens (MANDATORY, run once, before everything else)\n\nThe template ships with Visa's blue (`#1A1F71`), navy hover (`#141963`), and light blue (`#1434CB`) hardcoded in ~8 components — `solution-detail-panel.tsx`, `solution-slider.tsx`, `generated-view.tsx`, `agent-panel.tsx`, `account-panel.tsx`, `live-session-overlay.tsx`, and others. **Delegating component rewrites to parallel subagents always leaves some of these files unedited**, and the Step 3.6 audit catches it every time. Save yourself the re-roll — run this sweep FIRST, right after `cp -R .\u002Ftemplate\u002F.`:\n\n```bash\ncd ~\u002Fwwa.{domain}\n\n# Replace Visa blue (primary), navy (hover), and light blue (accent) with brand colors.\n# Pick hex codes that match your brand-config.ts primary\u002Fsecondary\u002Faccent.\nfind src -name \"*.tsx\" -o -name \"*.ts\" | xargs sed -i '' \\\n  -e 's\u002F#1A1F71\u002F{BRAND_PRIMARY}\u002Fg' \\\n  -e 's\u002F#141963\u002F{BRAND_PRIMARY_DARK}\u002Fg' \\\n  -e 's\u002F#1434CB\u002F{BRAND_ACCENT}\u002Fg'\n\n# Verify zero remaining\ngrep -rn \"#1A1F71\\|#141963\\|#1434CB\" src\u002F\n```\n\nExample for a black-primary brand: replace with `#000000`, `#000000`, `#CF0A2C`. For Dior (gold on black): `#0A0A0A`, `#000000`, `#C9A96E`.\n\nAfter the sweep, subagents can focus on rewriting content (copy, data) without worrying about color hunts. Re-run the grep at the end of Phase 3 to confirm nothing crept back in.\n\n### Step 3.2: Write Brand Config\n\nWrite `src\u002Flib\u002Fbrand-config.ts` with ALL company data from Phase 1. This drives the entire app.\n\n### Step 3.3: Write Solutions Data\n\nWrite `src\u002Flib\u002Fsolutions.ts` — these are the company's ACTUAL products\u002Fservices. Each must have:\n- Real name, real description from their website\n- Real features from their product pages\n- Image pointing to downloaded file\n- Appropriate category for THIS company (not Visa's categories)\n\n### Step 3.4: Write Products\u002FCards Data (ONLY IF APPLICABLE)\n\nWrite `src\u002Flib\u002Fcards.ts` — ONLY if the company sells browsable items (plans, cards, products with prices).\n\n**For API companies (Stripe, Twilio):** Use pricing tiers as \"cards\" — Free, Growth, Enterprise\n**For e-commerce (Nike, Apple):** Use actual products as cards\n**For SaaS (Salesforce, HubSpot):** Use subscription plans as cards\n**For companies with no browsable products:** Leave the array EMPTY and the browse section won't show\n\n### Step 3.5: Rewrite EVERY Content Component\n\n**CRITICAL: Do not sed-replace. REWRITE each file understanding the company.**\n\n**`src\u002Fcomponents\u002Fhero-section.tsx`** — Rewrite completely:\n- Stats must be THIS company's real stats\n- \"Card Tiers\" section: REMOVE if company doesn't have tiers. Replace with what makes sense (e.g., \"Choose your plan\", \"Explore by use case\", customer logos grid)\n- \"Why {Brand}\" section: Write real value props from their website, not Visa's\n- \"Find your card\" CTA: Change to whatever CTA makes sense (\"Start Building\", \"Get Started\", \"Shop Now\", \"Request Demo\")\n- Hero images should use downloaded images\n\n**`src\u002Fcomponents\u002Finner-page.tsx`** — Rewrite ALL pages:\n- Navigation pages must match THIS company's nav (from brand-config)\n- Each page content must be written from crawled data\n- Remove any pages that don't apply (Stripe doesn't need \"Travel\" or \"Personal\")\n- Add pages that DO apply (Stripe needs \"Developers\", \"Pricing\")\n\n**`src\u002Fcomponents\u002Fwwa-panel.tsx`** — Update:\n- SUGGESTIONS array: Write 6-8 suggestions relevant to THIS company\n- Card\u002Fsolution detection keywords: Based on THIS company's product names\n- Chat tab label: \"{Brand} Agent\"\n- Category labels in browse section\n\n**`src\u002Fcomponents\u002Fassistant-shared.tsx`** — Rewrite ALL fallback responses:\n- Every response must be about THIS company's products\n- Use real product names, real features, real pricing\n- Reference actual pages\u002Fdocs from their website\n\n**`src\u002Fapp\u002Factions.ts`** — **Always a full rewrite, regardless of peer clone.** Both the chat `SYSTEM_PROMPT` and the `CODE_GEN_PROMPT` bake brand knowledge in deep (named buildings, founding years, signature products, ambassadors, specific exhibition venues) that a simple `grep \"ralph\\|polo\"` misses. Example: a Ralph Lauren → Zara peer clone caught the obvious brand names but left phrases like \"Rhinelander Mansion\", \"1978 fragrance launches\", \"Jack Shainman Gallery\" in the system prompt — these shipped silently until end-to-end prompt re-read. Re-read this file line-by-line after any peer clone.\n- Identity: \"{Brand} Agent\" specialist in their actual domain\n- Product knowledge from crawled data\n- Stats from their actual numbers\n- Zero references to any prior brand's specific places, years, products, people, or institutions — these don't grep cleanly\n\n**`src\u002Fapp\u002Fpage.tsx`** — Update:\n- Category grid: Use THIS company's actual categories (not Travel\u002FCash Back\u002FBusiness)\n- Section titles and descriptions\n- Remove any sections that don't apply\n\n**`src\u002Fcomponents\u002Fbook-demo-modal.tsx`** — Update:\n- Product interests: THIS company's actual products\n- Company types relevant to their market\n- Form copy\n\nFor **luxury e-commerce \u002F heritage brands**, rewrite the whole modal as \"Request a Private Appointment\" with three fields — the B2B fields (company size, revenue range, country dropdown, SKU picker) are inappropriate. Keep it short:\n- Name + email\n- Preferred boutique (dropdown of real flagships from brand-config \u002F flagships.ts)\n- Occasion + interests (free text — \"wedding gift\", \"wardrobe refresh\", \"home\", etc.)\nSubmit CTA: \"Request Appointment\" — not \"Book a Demo\".\n\n**`src\u002Fcomponents\u002Flive-session-overlay.tsx`** — CRITICAL:\n- Replace the SVG logo paths (appears 2 times: header + animated center) with the brand's logo\n- Update the viewBox to match the brand's SVG\n- The voice call should show the BRAND logo, not any other brand\n\n**`src\u002Fcomponents\u002Fassistant-shared.tsx`** — CRITICAL:\n- The `EmptyState` component shows welcome screen with brand logo\n- The logo IS the call button — clicking it starts the voice call. NO separate \"Start Voice Call\" text button\n- Pattern: `\u003Cbutton onClick={onOpen}>\u003Cimg src=\"\u002Fimages\u002Fbrand-logo.svg\" \u002F>\u003C\u002Fbutton>`\n- Must use brand's logo image file (not inline SVG — renders badly)\n\n**`src\u002Fcomponents\u002Fagent-panel.tsx`** — CRITICAL (often forgotten):\n- Rename ALL skill names: \"visa-search\" → \"{brand}-search\", etc.\n- Rename CLI commands: \"visa-agent\" → \"{brand}-agent\"\n- Rename MCP package: \"visa-agent-mcp\" → \"{brand}-agent-mcp\"\n- Update AgentNet command: \"agentnet add {brand}-agent\"\n- Update skill descriptions to match brand's products\n- Update CLI example commands to be relevant to brand\n- MCP URL and Claude Code\u002FCodex install commands read from `BRAND.mcpUrl` + `BRAND.mcpServerName` automatically — no string edits needed here as long as brand-config is correct.\n\n**`src\u002Fapp\u002Fmcp\u002Froute.ts`** — REAL MCP ENDPOINT (ships with template):\n- The template serves a working MCP Streamable HTTP endpoint at `\u002Fmcp` on the same origin as the agentfront. JSON-RPC 2.0, stateless, CORS-enabled.\n- Default tools read from `productItems` (cards.ts) and `solutions` (solutions.ts): `search_products`, `compare_products`, `get_product`, `get_solutions`, `recommend_product`.\n- The `mcpTools` list shown in agent-panel.tsx is already synced with these 5 default tools.\n- To add brand-specific tools (e.g. `find_boutique` for luxury, `compare_tiers` for financial, `estimate_fees` for SaaS): append to the `TOOLS` array and add a `case` in `callTool`. Mirror the addition in agent-panel's `mcpTools` list.\n- **Brand-config keys to set:**\n  - `mcpUrl`: `\"https:\u002F\u002Fwwa.{brand}.codiris.app\u002Fmcp\"` (same origin as deployed agentfront)\n  - `mcpServerName`: `\"{brand}-agent\"` (CLI identifier for `claude mcp add`)\n- **Verify after deploy:** `curl -X POST https:\u002F\u002Fwwa.{brand}.codiris.app\u002Fmcp -H \"Content-Type: application\u002Fjson\" -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Flist\"}'` — must return the tool list with 200.\n- **Recommended brand-specific tools by type** (append to `TOOLS` in route.ts and to `mcpTools` in agent-panel.tsx):\n  - Heritage brand (Ralph Lauren, Rolex, Hermès, Patek Philippe): `get_heritage(yearFrom?, yearTo?)` from `src\u002Flib\u002Fheritage.ts`, `find_flagship(city?, country?)` from `src\u002Flib\u002Fflagships.ts`\n  - Multi-house luxury group (Dior, Chanel, Armani): `get_houses()`, `get_house(id)`\n  - Restaurant \u002F hospitality arm (Ralph Lauren Polo Bar, Bulgari hotels, Armani Caffè): `find_restaurant(city?)`\n  - SaaS with usage pricing (Stripe, Twilio): `estimate_cost(usage)`, `check_availability(region)`\n  - Fintech with tiered benefits (Visa, Mastercard, Amex): `compare_tiers(tiers[])`\n  - Luxury fragrance house: `get_fragrance_notes(productId)`, `find_boutique(city?)`\n  - Marketplace \u002F C2C (Vinted, Depop, Etsy, eBay): `list_markets(region?)`, `list_categories()`, `get_seller_flow(personal|pro)`, `estimate_fees(price, category)` — sellers and buyers want different info from the same API, and marketplaces have operational data (markets live, fee structure) that doesn't fit search\u002Fcompare\u002Frecommend alone.\n  - Marketplace \u002F Listings (Booking, Airbnb, VRBO, Expedia, Agoda): `search_stays(destination?, checkIn?, checkOut?, guests?, category?, priceMax?)` returning mocked stay results with price\u002Fcurrency\u002Frating\u002FreviewCount (no need to hit real inventory APIs), `list_destinations(region?, country?)` backed by `src\u002Flib\u002Fdestinations.ts`, and optionally `get_host_flow()` for the host-onboarding path.\n  - Marketplace \u002F Rentals — Residential (Joivy, Spotahome, HousingAnywhere, Uniplaces): `search_rentals(city?, duration_months?, room_type?, max_rent?, available_from?)` — different param shape from `search_stays` (months not nights, single move-in date not check-in\u002Fcheck-out range, room type not category). `find_co_living(city?, age_range?)` translation tool. `book_viewing(propertyId, date)` for tour scheduling — no \"reserve\" semantics. `get_lease_terms(propertyId)` — minimum lease, deposit, notice period, utilities included. `list_destinations(country?)` backed by `destinations.ts`. Skip `search_stays` \u002F `find_experience` \u002F `find_boutique` — wrong domain.\n  - Marketplace \u002F Rentals — Flex (Habyt Flex, Cove, Sonder, Outsite, Mindspace Living, Selina Co-Live): `search_stays(city?, checkIn?, checkOut?, guests?, unitType?, maxRent?, minNights?)` — uses **check-in\u002Fcheck-out range** like Booking, NOT residential-style `duration_months`. Listings carry both per-night AND per-month prices (`nightlyRent` + `monthlyRent` fields). `find_flex_living(preference)` translation tool. `book_stay(propertyId, checkIn, checkOut, guests)` supports days OR months in one tool — NOT `book_viewing`. `get_lease_terms(propertyId)` repurposed for stay terms (free-cancellation window, min nights). `get_living_spaces(propertyId)` for amenities\u002Fcommon-area inventory (rooftop, café, gym, coworking). Skip `search_rentals` \u002F `find_co_living` \u002F `book_viewing` — those are residential-only, wrong domain.\n  - Retail \u002F Multi-brand (Sephora, Nordstrom, Net-A-Porter, Farfetch): `list_brands(category?, featuredOnly?)` backed by `src\u002Flib\u002Fbrands.ts`, `find_shade_match(undertone?, coverage?, finish?)` for beauty, `get_routine(skinType?, concern?, budget?)` for skincare, `get_fragrance_notes(productId)` backed by `src\u002Flib\u002Ffragrances.ts`. Extend `search_products` with a `brand?` arg — customers ask \"foundations from Rare Beauty under €50\" and the default signature doesn't support that.\n  - Outerwear \u002F Technical (Canada Goose, Arc'teryx, Moncler, The North Face, Patagonia): `check_warmth(temperature_c, activity)` — a **translation tool** (conditions → product); `compare_parkas(ids[])` extended for fill-power\u002Fweight\u002FTEI spec axes; `get_heritage(yearFrom?, yearTo?)` from `heritage.ts`; `find_store(city?, country?)` for flagships with `note` field carrying experiential-retail differentiator (\"Cold Room\", \"Pinnacle Room\", \"Worn Wear repair\"); `get_sustainability(productId?)` returning sourcing + materials detail. Extend `search_products` with `gender?` and `tei?` args.\n  - Fashion editorial-minimalist (Zara, COS, ARKET, & Other Stories, Massimo Dutti): `list_collections()` — parallel capsule sub-lines from `src\u002Flib\u002Fcollections.ts`; `find_fit(bodyShape?, occasion?, season?)` translation tool (sibling to `check_warmth`); `get_size_guide(category, gender)` returning EU\u002FUK\u002FUS matrices — **new MCP tool pattern** for any mass-fashion brand with real size charts. Skip for luxury (bespoke) and beauty (shades instead). Extend `search_products` with `gender?`, `collection?`, `material?`.\n  - Fashion mass-market pop (H&M, Uniqlo, Gap, Mango, Primark, Forever 21): same core tool set as editorial-minimalist, PLUS extend `search_products` with a **`tech?` arg** for proprietary material technologies (HEATTECH \u002F AIRism \u002F Supima \u002F Ultra Light Down \u002F BlockTech for Uniqlo; CONSCIOUS \u002F Recycled \u002F Organic Cotton for H&M). Critical because customers ask \"HEATTECH base layer for -10°C\" and the natural query needs the tech axis to resolve — don't overload `material` with it.\n  - Fashion marketplace online (ASOS, Shein, Nasty Gal, Boohoo): `list_brands(category?, featuredOnly?)` backed by `src\u002Flib\u002Fbrands.ts`; `list_collections()` for own-label sub-lines; `find_fit(bodyShape?, occasion?, season?, sizeRange?)` — extend with sizeRange for size-inclusive brands; `get_size_guide(category, gender, sizeRange?)` — per-range cut measurements (curve cut ≠ petite cut, not just number); **`check_delivery(postcode?, country?)`** — NEW translation tool for Premier\u002FPrime\u002FSaver eligibility (service-eligibility translator, sibling to `check_warmth`). Extend `search_products` with `brand?`, `gender?`, **`sizeRange?`** (`\"curve\" | \"petite\" | \"tall\" | \"maternity\" | \"standard\"`).\n  - **NEW TOOL CATEGORY — \"translation tools\"** (conditions → product): `check_warmth(temp, activity)` is the first. Other candidates across brand types: footwear `check_fit(usSize, width, foot-shape)`; skincare `check_compatibility(drug, pregnancy)`; luggage `check_airline_allowance(airline, class)`. These are neither `search` nor `recommend` nor `compare` — they translate external conditions into product filters. Document as a sibling to the three classic MCP verbs.\n\n**`src\u002Flib\u002Fbrand-config.ts`** — Logo:\n- Download logo via WebSearch: \"{brand} logo SVG wikipedia\" or \"{brand} press kit\"\n- Set `logoSvg: \"\"` and `logoImage: \"\u002Fimages\u002Fbrand-logo.svg\"`\n- ALWAYS prefer logo image file over inline SVG to avoid rendering issues\n\n**`src\u002Fcomponents\u002Fworld-map.tsx`** — Update stats or remove if not relevant\n\n**`src\u002Fcomponents\u002Fcard-3d.tsx`** — ONLY for credit card companies (Visa, Mastercard). \n- For ALL other companies: the template already uses product image cards instead of Card3D\n- The `cards-browse-panel.tsx` and `wwa-panel.tsx` CardCarousel show product images with name\u002Fprice overlay\n- Do NOT use Card3D for fashion, SaaS, e-commerce, or any non-card company — it renders a credit card with chip and magnetic stripe\n- The file contains hardcoded Visa SVG paths and a `1-800-VISA` customer-service phone. Even if the component is never rendered, the audit grep will still flag those strings. For non-card brands, either **delete `card-3d.tsx` entirely** or scrub the hardcoded Visa strings before running the audit.\n- **Specific residue check** — `template\u002Fsrc\u002Fcomponents\u002Fwwa-panel.tsx` line ~68 still renders `\u003CCard3D card={card} size=\"sm\" onClick={...} \u002F>` inside the `CardCarousel` component. Every non-card transform MUST replace that line with a photo tile (e.g. `\u003Cimg src={card.image} ...\u002F>` wrapped in a button). Confirmed on Airbnb sim — the template ships with this leak and it has to be edited in-place.\n\n**`src\u002Fcomponents\u002Fcards-browse-panel.tsx`** — PRODUCT DETAIL VIEW (non-credit-card companies):\n\nThe template has credit-card-specific labels throughout the detail view. You MUST rewrite ALL of these for non-card brands:\n\n| Credit-card term | E-commerce\u002FSaaS replacement |\n|------------------|----------------------------|\n| \"Back to Cards\" | \"Back to Products\" \u002F \"Back to Collection\" |\n| \"Issued by\" | \"From\" \u002F remove for brand-native products |\n| \"Annual fee:\" | \"Price:\" |\n| \"Card Tier\" | \"Collection\" \u002F \"Tier\" \u002F \"Plan\" |\n| \"Card Highlights\" | \"Product Highlights\" \u002F \"Features\" |\n| \"Card Details\" | \"Details\" \u002F \"Specifications\" |\n| \"REWARDS \u002F WELCOME BONUS \u002F APR\" | Remove entirely — not applicable |\n| \"Ready to apply?\" | \"Ready to shop?\" \u002F \"Ready to get started?\" |\n| \"Apply Now\" | \"Add to Bag\" \u002F \"Buy Now\" \u002F \"Subscribe\" |\n| \"Compare Other Cards\" | \"Explore Collection\" \u002F \"Continue Shopping\" |\n| \"Application Submitted!\" | \"Order Confirmed!\" \u002F \"Welcome!\" |\n| \"Quick application with instant decision\" | \"Complete your purchase\" \u002F \"Get started in seconds\" |\n| \"Browse More Cards\" | \"Continue Shopping\" \u002F \"Explore More\" |\n| \"Annual Income *\" | \"Shipping Notes\" \u002F remove |\n| \"credit history\" | Remove the credit check reference entirely |\n| `{annualFee}\u002Fyr` | `{price}` |\n| \"Secure Application\" | \"Secure Checkout\" |\n\nAlso: the detail view renders the product with a dark gradient background and centered 3D card — change to a white background with image on left + details on right for product-style layout.\n\n**`src\u002Fcomponents\u002Fhero-section.tsx`** — VISUAL STYLE BY BRAND TYPE:\n\nThe default template uses a SaaS\u002Ftech aesthetic (split layout, colored gradient tiles, tech-y feature grid). This is WRONG for luxury\u002Feditorial brands. Adapt per brand:\n\n**LUXURY \u002F EDITORIAL — FRENCH \u002F EUROPEAN (Dior, Hermès, Chanel, Gucci, Aesop):**\n- **Hero**: Full-bleed image or video, black\u002Fwhite overlay, centered text, serif heading, no split\n- **CTAs**: Square buttons (no rounded-full), white-on-image, \"Discover\" \u002F \"Shop the Collection\"\n- **Stats**: Minimal, no gradient background, serif numbers, uppercase labels with wide tracking\n- **Collections**: Large 2-col tiles with full product imagery, gradient overlay, serif headings\n- **Category grid**: Aspect 4:5 tiles with real product images as backgrounds (NOT colored gradients)\n- **Fonts**: Playfair Display \u002F Didot-style serif for all headings\n- **Typography**: `tracking-[0.3em]` on uppercase labels, `font-normal` (not bold) on headings\n- **Colors**: Black, white, cream, gold — no blue\u002Fpurple accents\n- **Motion**: Slow, gentle (1-2s transitions), long fade-ins\n\n**FASHION — EDITORIAL MINIMALIST (Zara, COS, ARKET, & Other Stories, Massimo Dutti):**\n\nMono-brand mono-color fashion with rapid-turn seasonal drops, no heritage narrative, maximal typography contrast. The pure-B&W editorial-gallery aesthetic. Distinct from its mass-market cousin (H&M \u002F Uniqlo \u002F Gap \u002F Mango) which uses color-friendly pop aesthetics.\n\n- **Palette**: **pure black + pure white, NO accent color**. This is the signature — monochrome is the brand. Don't use the Visa-navy \u002F Sephora-red \u002F any-color pattern; resist the instinct to add an accent. Zara's brand voice IS the restraint.\n- **Typography**: **condensed elongated display serif** for headlines (free equivalents: `Big Shoulders Display`, `Oswald`, `Abril Fatface` — pick the one that matches the brand's wordmark shape). Inter or Helvetica for body. The *contrast* between massive display headlines and tiny body copy is the brand signature — don't temper it.\n- **Hero**: oversized display text (4-8 rem+) over a **single** full-bleed editorial photo. NOT a carousel (RL\u002FDior pattern), NOT a search form (marketplace), NOT a split (SaaS). One big photo, scroll for the next editorial block. Massive negative space between sections.\n- **Buttons**: sharp-cornered (border-radius 0), uppercase wide-tracking tiny text, black-on-white or white-on-black only. The button text reads `ADD` or `SHOP NOW →` — never more.\n- **Navigation**: pure text, tiny size, pure black. The navbar is lean — Woman \u002F Man \u002F Kids \u002F Home \u002F Beauty \u002F Join Life or similar brand-specific top facets. No icons, no dropdowns.\n- **Product grid**: large rectangular tiles, no pills, no \"guest favorite\" badges, no discount flags during a normal season. Just photo + product name + price.\n- **Product detail view** — DISTINCT from all other sub-types:\n  - Huge display-serif product name (not bold sans, not Didot — the condensed elongated serif)\n  - Price: small but bold, under the name. No strikethrough unless genuinely on sale.\n  - **Size picker = single `\u003Cselect>` dropdown**, not a grid (Zara does this deliberately — minimalism)\n  - Color chips: small circles, inline\n  - **Single \"ADD\" button**, no \"Wishlist\", no \"Request consultation\" — just ADD\n  - Body-copy paragraph (not an accordion) with material + care text\n  - \"YOU MAY ALSO LIKE\" row at bottom\n  - No trust badges, no reviews, no \"Recommended for you\" personalization chrome\n- **Animations**: restrained — quick fades only. NO scale-on-hover, NO slide-ins. The minimalism applies to motion too.\n- **Collection sub-lines**: most editorial-fast-fashion brands run 4-8 parallel sub-capsules (Zara's Main\u002FStudio\u002FSRPLS\u002FOrigins\u002FTRF\u002FLimited Edition\u002FAthleticz\u002FJoin Life; Uniqlo's Main\u002FU\u002FC\u002FJ; H&M's Main\u002FStudio\u002FHome\u002FConscious). Add `src\u002Flib\u002Fcollections.ts` + a `list_collections()` MCP tool — these don't map onto gender\u002Fcategory axes.\n- **MCP tools** specific to editorial-minimalist fashion:\n  - `list_collections()` — parallel capsule sub-lines from `collections.ts`\n  - `find_fit(bodyShape?, occasion?, season?)` — translation tool (sibling to Canada Goose's `check_warmth`; conditions → curated picks)\n  - `get_size_guide(category, gender)` — EU\u002FUK\u002FUS size matrix with measurements. This is a **new MCP tool pattern** for any mass-fashion brand with real size charts (Zara, Uniqlo, H&M, Gap, ASOS). Luxury brands skip it (bespoke); beauty retailers skip it (shades instead).\n  - `find_store(city?, country?)` — flagship physical presence\n\n**FASHION — MASS-MARKET POP (H&M, Uniqlo, Gap, Mango, Primark, Forever 21):**\n\nCousin to editorial-minimalist but color-friendly and accessible. Distinguished from Zara\u002FCOS\u002FARKET by: bold brand accent color (H&M red, Uniqlo red, Gap navy), pop-magazine aesthetic (pink\u002Folive\u002Fcream seasonal backgrounds, NOT pure B&W), entry-level pricing (£4.99–£14.99 basics vs Zara's £19.95 floor), youth-dedicated sub-line (H&M's Divided, Gap's Teen), and first-class Baby + Home categories.\n\n- **Palette**: brand-color primary + accessible pastels. H&M red `#E50010`, Uniqlo red `#E30A18`, Gap navy `#00256C`, Mango camel. Seasonal backgrounds use soft pink \u002F olive \u002F cream \u002F camel — a color accent is expected and welcome (opposite of the Zara rule).\n- **Typography**: **bold chunky sans** (Inter Bold Extended, Helvetica Bold, Noto Sans) — NOT condensed elongated serif. The mass-market signal is confidence and clarity, not editorial drama.\n- **Hero**: color-block rotating panels (2-3 panels, each a different hero offer) OR a \"shop-by-trend\" tile row (Y2K \u002F Boho \u002F Workwear \u002F Festival \u002F Preppy). Multiple narratives surfaced, not a single editorial moment.\n- **Navigation** includes: Ladies\u002FWoman, Men, Youth sub-line (Divided\u002FTeen), **Kids, Baby, Home** — Baby and Home are first-class top-nav entries, not nested under Kids\u002FLifestyle. Uniqlo Baby sizing goes 50-100cm.\n- **Product detail view** — like editorial-minimalist but with:\n  - Color swatches as prominent circles (not discrete)\n  - Size grid XS–XXXL PLUS numerical EU 34-46 both shown\n  - **Members price** strikethrough shown (\"£29.99 \u002F H&M Member £24.99\")\n  - Tech-feature badges where applicable (HEATTECH \u002F AIRism \u002F Supima \u002F Ultra Light Down for Uniqlo; CONSCIOUS \u002F RECYCLED \u002F ORGANIC for H&M)\n  - Accessible price ladder on every tile (entry + aspirational side-by-side)\n- **Product grid** is denser than editorial-minimalist, merch-oriented, with badge flags (NEW \u002F SAVE \u002F BESTSELLER \u002F CONSCIOUS) that would be too loud for Zara but are on-brand here.\n- **Loyalty programme** is first-class chrome: H&M Members, Uniqlo IQ, Gap Good Rewards. Surface in the navbar, the PDP price block, and the book-demo-modal (rewrite as loyalty signup per SKILL.md residues).\n- **Technical-functional tech features** are product-level filters: Uniqlo's HEATTECH\u002FAIRism\u002FSupima\u002FUltra Light Down\u002FBlockTech\u002FPUFFTECH. Extend `search_products` with a `tech?` arg so customers can filter by proprietary material tech (\"HEATTECH base layer for -10°C\"). Don't overload `material` with it.\n- **MCP tools** — same as editorial-minimalist plus:\n  - `search_products` extended with `tech?` arg (HEATTECH \u002F Supima \u002F CONSCIOUS \u002F Organic Cotton \u002F Recycled)\n  - `list_collections()` — Uniqlo's Main\u002FU\u002FC\u002FJ\u002F+J\u002FJW Anderson\u002FMarimekko; H&M's Main\u002FStudio\u002FDivided\u002FConscious Exclusive + designer collabs\n\n**FASHION MARKETPLACE — ONLINE (ASOS, Shein, Nasty Gal, Boohoo, Zalando):**\n\nPure-play online retailers with substantial own-label catalogues + stocked external brands. Distinct from `RETAIL — MULTI-BRAND` (Sephora \u002F Nordstrom \u002F Net-A-Porter) which are primarily curated external-brand retailers. Distinct from `marketplace-listings` (Booking \u002F Airbnb) which is host-traveler dynamics.\n\n- **Palette**: dark-minimalist with an electric accent. ASOS true black + neon yellow; Shein black + pink; Zalando white + orange. The neon\u002Felectric accent is the \"online-only youth\" signal.\n- **Typography**: bold chunky sans with confident presence. Inter Bold Extended or Helvetica Bold Extended.\n- **Signature nav pattern** — **size-inclusive top-level entries**: Curve & Plus \u002F Petite \u002F Tall \u002F Maternity as first-class nav categories alongside Women \u002F Men \u002F Kids. This is unique to online-only fashion marketplaces (ASOS pioneered it; Boohoo \u002F Nasty Gal followed). SKIP this for Zalando\u002FNordstrom\u002FNet-A-Porter which keep size ranges as filter chips instead.\n- **Hero**: weekly editorial cover (\"Trending now\", \"Fit of the week\", \"We're obsessed with…\") + a \"shop-by-size-range\" tile row. Model-led street-style photography, NOT studio white-background.\n- **Product detail view**:\n  - Prominent brand badge above product name (\"NIKE · Air Max 90\")\n  - Size + fit info block (\"Model wears UK 8 \u002F size S, 5'10\"\") — ASOS-signature\n  - Stock indicator (\"Only 3 left in size M\")\n  - Star rating + review count from the brand's own reviews\n  - Premier \u002F Prime \u002F Saver delivery eligibility teaser\n- **Required `src\u002Flib\u002Fbrands.ts`** + `list_brands(category?, featuredOnly?)` MCP tool (same convention as multi-brand beauty retail — ASOS stocks 850+ brands).\n- **Required `src\u002Flib\u002Fcollections.ts`** for own-label sub-lines (ASOS Design \u002F Edition \u002F 4505 \u002F Weekend Collective \u002F Made In \u002F Topshop \u002F Topman).\n- **MCP tools** — substantial extension:\n  - `search_products` extended with `brand?`, `sizeRange?` (`\"curve\" | \"petite\" | \"tall\" | \"maternity\" | \"standard\"`), `gender?`\n  - `list_brands(category?, featuredOnly?)`\n  - `list_collections()`\n  - `find_fit(bodyShape?, occasion?, season?, sizeRange?)` — extended with sizeRange\n  - `get_size_guide(category, gender, sizeRange?)` — UK\u002FEU\u002FUS PLUS per-range cut measurements (curve cut differs from petite cut, not just the number)\n  - `check_delivery(postcode?, country?)` — NEW translation tool (conditions → Premier \u002F Saver \u002F Standard eligibility). Sibling to Canada Goose's `check_warmth`. General pattern: a translation tool for service eligibility is a third category beside product-search and product-recommend.\n\n**LUXURY — AMERICAN HERITAGE \u002F PREP (Ralph Lauren, Tommy Hilfiger, J.Crew, L.L. Bean, Brooks Brothers):**\n- **Hero**: Full-bleed runway OR editorial lifestyle photograph (equestrian, sailing, library, cabin interior — NOT Paris-minimalist void). Static image with 1.04 scale-on-mount is fine — most of these brands have no public video CDN.\n- **CTAs**: Square buttons, uppercase-wide tracking, \"Shop the Collection\" \u002F \"Request an Appointment\" \u002F \"Visit the Flagship\"\n- **Stats**: Minimal, serif numbers, uppercase labels — same as French luxury\n- **Collections**: 2- or 3-col grid of portrait 3:4 or 4:5 images with serif captions\n- **Fonts**: Caslon \u002F Garamond \u002F Playfair Display — NOT Didot (that reads as French and wrong)\n- **Typography**: Wide-tracked uppercase labels in burgundy or navy, italic body for pullquotes, never all-caps long-form\n- **Colors**: Navy primary, burgundy accent, cream surface, racing green or tartan secondary, antique gold highlight — avoid stark black\u002Fwhite\u002Fgold (that's French)\n- **Motion**: Slower than French luxury (1200–1600ms), no scale transforms beyond 1.04\n\n**TECH \u002F SAAS (Stripe, Notion, Linear):**\n- Split hero with copy left + product screenshot right\n- Colored CTAs (rounded-full), \"Start Building\" \u002F \"Book a Demo\"\n- Stats on dark background with bold numbers\n- Feature grid with icons (not images)\n- Code snippets as visual elements\n\n**CONSUMER (Apple, Nike, Spotify):**\n- Full-bleed hero with big bold text, keep sans-serif\n- Single prominent CTA, bold colors\n- Product-focused imagery, minimal copy\n\n**FINTECH \u002F FINANCIAL (Visa, Chase, Robinhood):**\n- Keep current template style (split, colored tiers, card visuals)\n- Blue\u002Fnavy color palette\n- Stats-heavy design, trust signals\n\n**MARKETPLACE \u002F C2C (Vinted, Depop, Etsy, eBay, Poshmark):**\n- **Hero**: carousel of category solutions with lifestyle photography (real people + items — NOT isolated product shots). Hero copy is short and action-oriented (\"Dresses, tops, denim, and outerwear — secondhand\").\n- **CTAs**: dual-intent, always two buttons — primary \"Sell Now\" (solid brand color) + secondary \"Start Browsing\" (outline or darker brand color). Never \"Shop Now\" alone; a marketplace's sellers are half the audience.\n- **Stats bar**: members \u002F markets \u002F lifetime GMV \u002F seller-fees. Example from Vinted: \"80M+ Members · 26 Markets · €10.8B Annual GMV · 0% Selling fees\". The zero-fees or low-fees stat is often the single most persuasive number — lead with it if true.\n- **Navigation**: the brand's real category tree (Women \u002F Men \u002F Designer \u002F Kids \u002F Home), plus a \"Sell\" item that routes to the seller flow.\n- **Feature tiles** (instead of product grid): Buyer Protection, Ship Fast, Designer Authentication, Bundle Discounts, Zero Fees, Wallet — these are *trust & flow* features, not products.\n- **Fonts**: utility sans-serif (Inter, Geist). Marketplaces are utility-first; serif reads luxury and is wrong.\n- **Colors**: most marketplaces use a single bold color (Vinted teal `#09B1BA`, Depop red, Etsy orange, Poshmark pink). Use the brand color boldly — stats band, hero CTAs, feature icons.\n- **No `book-demo-modal` in the classic B2B shape** — see the marketplace variant in the `book-demo-modal.tsx` guidance below.\n\n**MARKETPLACE \u002F LISTINGS (Booking, Airbnb, VRBO, Trivago, Expedia, Hotels.com, Agoda):**\n\nSimilar to C2C marketplaces but asymmetric — travellers\u002Fbuyers are the primary audience, hosts\u002Fsellers are the B-side. Different hero + CTA pattern:\n\n- **Hero**: large photographic hero (city skyline \u002F destination \u002F accommodation) with a **search form overlay** — not a static CTA button. The search form IS the primary interaction. Standard fields: destination, check-in, check-out, guests.\n- **CTAs — asymmetric, NOT dual-intent**:\n  - Primary: \"Search Stays\" \u002F \"Find a Hotel\" \u002F \"Search Flights\" — large, solid brand color, near the search form\n  - Secondary: \"List Your Property\" \u002F \"Become a Host\" — small outline button in nav or footer, routes to a host-onboarding modal\n  - Do NOT paste dual CTAs side-by-side like C2C. The search form is a primary-heavy pattern.\n- **Two signature grids** — SHIP BOTH on the homepage:\n  1. **Trending inventory grid** — 18-26 tiles of individual stays\u002Fcities\u002Froutes with real photography (Paris boutique, Tokyo capsule, Santorini cave, Maldives villa). Each tile shows image + name + price indicator (\"from €180\u002Fnight\") + city label.\n  2. **Destinations \u002F categories grid** — 24-36 tiles of countries\u002Fcities\u002Fregions with iconic destination photos (Eiffel, skyline, monument). Each tile shows image + destination name + property count (\"12,450 stays\").\n  - Both grids are what travellers actually scroll through. Skipping either breaks the marketplace feel.\n- **Stats bar**: properties \u002F countries \u002F languages \u002F support. Example from Booking: \"3M+ Properties · 220+ Countries · 40+ Languages · 24\u002F7 Support\".\n- **Navigation**: Hotels · Apartments · Villas · Hostels · B&Bs · Holiday homes · Resorts · plus \"List your property\" as the host entry.\n- **`src\u002Flib\u002Fcards.ts` repurposing**: the 9-15 `productItems` represent stay categories (Hotels\u002FApartments\u002FVillas\u002Fetc.), NOT individual properties — the same repurposing convention as C2C features but with category shape.\n- **Optional `src\u002Flib\u002Fdestinations.ts`**: listings marketplaces almost always have a destinations catalog. Create this file with `{ id, city, country, region, heroImage, propertyCount }[]` and wire a `list_destinations(region?)` MCP tool to it. Vinted uses `list_markets(region?)` for country markets; Booking uses `list_destinations(region?)` for cities; Uber would use `list_cities(country?)`. Same shape, different primary axis.\n- **Optional `src\u002Flib\u002Fexperiences.ts`** (for brands that sell **activities** alongside stays — Airbnb Experiences, Klook, Viator, GetYourGuide, Hotels.com Spots): `{ id, city, title, type, price, duration, image }[]`. Experiences aren't stays (no overnight axis) and aren't destinations (they're bookable events) — they need their own dataset. Wire a `find_experience(city?, type?)` MCP tool. Skip this file if the brand only sells stays.\n- **Premium tier within the marketplace** — Airbnb Luxe, Booking Genius, VRBO Premier Partner, Expedia One Key. These are *tiers-within-the-marketplace* that carry extra service slots (trip designer, pre-stocked pantry, airport transfer, priority support). The flat `productItems[].tier` field in the template captures the label but not the extras. If the premium tier matters to the brand story, create a `premium-tier.ts` with `{ features: string[], amenities: string[], support: string }` and add a fifth MCP tool `get_premium_tier()`. Otherwise just flag the tier with a single card in `productItems` and accept the simplification.\n- **Fonts**: utility sans-serif (Inter, Geist). Same as C2C.\n- **Colors**: a confident primary color (Booking blue `#003580`, Airbnb red `#FF5A5F`, Expedia yellow `#FFC72C`) — the primary drives the search form, stats bar, and trending grid chrome.\n\nWhen transforming, EXPLICITLY adapt the hero and category grid to match the brand's visual DNA. Don't just update text — change the layout pattern.\n\n**MARKETPLACE \u002F RENTALS — RESIDENTIAL (Joivy, Spotahome, HousingAnywhere, Uniplaces, The Student Hotel, Kabute, Casavo):**\n\n**Distinct from listings-marketplace (Booking\u002FAirbnb)** — long-term residential rentals (1–24 months), not nightly stays. The vocabulary, pricing model, transaction flow, and visual surfaces are different enough that listings-marketplace guidance leads you wrong. Verified across the Joivy transform.\n\n- **Vocabulary swap (CRITICAL — do a sweep)**:\n  - \"Stay\" → \"Rental\" or \"Tenancy\"\n  - \"Night\" \u002F \"Nights\" → \"Month\" \u002F \"Months\"\n  - \"Check-in \u002F check-out\" → \"Move-in date \u002F Move-out date\"\n  - \"Guests\" → \"Tenants\" \u002F \"Residents\" (or \"Roommates\" for co-living)\n  - \"Reserve\" \u002F \"Book this stay\" → **\"Schedule a viewing\"** or \"Apply\" or \"Request a tour\"\n  - \"Free cancellation\" → \"Lease flexibility\" \u002F \"Notice period\" (typically 30-60 days)\n  - \"Trip\" \u002F \"Vacation\" → just remove\n  - \"Hotel\" \u002F \"Resort\" → \"Building\" \u002F \"Residence\" \u002F \"Apartment block\"\n- **Hero \u002F search form fields** (different from Booking's destination\u002Fcheck-in\u002Fcheck-out\u002Fguests):\n  - **City** (dropdown of live markets)\n  - **Move-in date** (single date picker, not a range — open-ended duration)\n  - **Duration** — radio or pills: 1-3 mo \u002F 3-6 mo \u002F 6-12 mo \u002F 12+ mo\n  - **Room type** — Entire studio \u002F 1-bed \u002F Co-living room \u002F Shared apartment \u002F Family suite\n  - **Monthly budget** (single slider — €400-€2,500 typical range)\n  - Primary CTA: \"Find a home\" or \"Search rentals\" — not \"Search stays\"\n- **Stats bar** (different metrics): markets · cities · operating since · average move-in time. Example for Joivy: \"8 countries · 50+ cities · since 2007 (DoveVivo) · 24h average viewing booking\".\n- **`src\u002Flib\u002Fcards.ts` repurposing — DIFFERENT FROM LISTINGS**: `productItems` represent **rental categories** (Studio · Co-living room · 1-bed apartment · 2-bed apartment · Student studio · Shared apartment · Family suite · Pro suite), NOT stay categories (Hotels\u002FVillas). Field mapping:\n  - `issuer` → city\u002Fcountry (not gender, not house — for residential the city is the primary filter)\n  - `tier` → lease duration (\"Short-term 1-3 mo\" \u002F \"Medium 3-6 mo\" \u002F \"Long-term 6-12 mo\" \u002F \"Annual 12+ mo\")\n  - `annualFee` → monthly rent (\"€650 \u002F month\")\n  - `apr` → utilities + furnishing (\"Utilities included · Furnished\" \u002F \"Bills excluded · Unfurnished\")\n  - `rewardRate` → minimum lease (\"3 month minimum\")\n  - `signUpBonus` → onboarding offer (\"First month -50%\" \u002F \"No deposit\" \u002F \"Free Wi-Fi\" \u002F \"Move in same week\")\n  - `applyUrl` → property URL on the brand's site\n- **Property detail view** — **NOT the Airbnb gallery + booking card**. Use:\n  - Photo gallery (room + common spaces + building exterior + neighborhood)\n  - Header: building name + address + city + monthly rent + utilities-included badge\n  - **Lease terms block** (essential — lease duration, deposit amount, notice period, what's included, available-from date)\n  - **Building amenities** (Wi-Fi, kitchen, gym, common lounge, washing machine, bike storage)\n  - **Nearby** (universities, transit, supermarkets — text list, not just a map pin)\n  - **\"Schedule a viewing\"** primary CTA + \"Apply now\" secondary\n  - No \"Reserve\" button. No nightly price calculator. No \"guests\" picker.\n- **`src\u002Flib\u002Fdestinations.ts`** stays useful — same shape as listings-marketplace, just `propertyCount` is larger (Joivy has ~5,000 rooms in Milan).\n- **MCP tools** specific to residential rentals:\n  - `search_rentals(city?, duration_months?, room_type?, max_rent?, available_from?)` — instead of `search_stays`. Different param shape.\n  - `find_co_living(city?, age_range?)` — translation tool (sibling to `check_warmth`, `find_fit`, `check_delivery`). Conditions → property pick.\n  - `book_viewing(propertyId, date)` — schedule a tour, NOT a stay reservation.\n  - `get_lease_terms(propertyId)` — minimum lease, deposit, notice period, included utilities. Documenting the contract is the equivalent of Booking's \"free cancellation\" trust signal.\n  - `get_property(propertyId)`, `compare_properties(ids[])` — same as listings.\n  - **Skip**: `search_stays`, `find_experience`, `find_boutique` — wrong domain.\n- **Fonts**: clean sans-serif (Inter, Söhne). Joivy uses ABC Diatype-adjacent.\n- **Colors**: residential brands lean toward **trust-warm palettes** — deep teal (Joivy `#015962`), forest green, terracotta, navy. NOT bright vacation-marketing colors (Booking blue, Airbnb red, Expedia yellow). The vibe is \"your home\", not \"your getaway\".\n\n**MARKETPLACE \u002F RENTALS — FLEX (Habyt Flex, Cove, Sonder, Mindspace Living, Outsite, Selina Co-Live):**\n\n**Distinct from residential rentals (Joivy)** — flex-living = stays for **days OR months**, not 1+ month minimum. Habyt's pitch is \"a stay that moves with you\" — book 3 nights or 8 months in the same building, with free cancellation. Verified across the Habyt transform.\n\n- **Vocabulary swap (different from residential)**: keep \"stay\" and \"guests\" (NOT \"rental\" \u002F \"tenants\"). \"Book\" or \"Book now\" (NOT \"Schedule a viewing\"). \"Free cancellation\" is the headline trust signal, not \"lease flexibility\". The whole grammar is closer to extended-stay-hotel than to residential lease.\n- **Hero \u002F search form fields** (closer to Booking's stay form than Joivy's rental form):\n  - **City** (dropdown of live properties, NOT live cities — flex brands often have just 1-3 active buildings)\n  - **Check-in date + Check-out date** (range picker, like Booking) — NOT a single move-in date\n  - **Guests** (1-4 typical)\n  - **Unit type** — Studio \u002F 1-Bed \u002F 2-Bed \u002F Suite (per-property)\n  - Primary CTA: **\"Book now\"** or **\"Search\"** — NOT \"Find a home\" (that's residential).\n- **Pricing model — DUAL TIER**: every listing carries BOTH a per-night price (`€95\u002Fnight`) AND a per-month price (`€1,450\u002Fmo`). The PDP and the booking card need to surface both. Discount messaging: \"Stay 7+ nights for X% off\", \"Stay 30+ nights for X% off\". `cards.ts` should have `monthlyRent` AND `nightlyRent` fields (or a single `priceTiers` object).\n- **Tier mapping** (different from residential): `tier` field becomes the stay-length tier — `\"Flex 1-3 nights\"` \u002F `\"Short stay 7+ nights\"` \u002F `\"Monthly stay\"` \u002F `\"Long stay 6+ months\"` — instead of lease duration.\n- **Property catalog tends to be SMALL**: Habyt Flex has 2 active properties globally (Berlin Waterfront, Truliving Vallecas Madrid). Don't fake a 50-property catalog. Generate 5-10 unit-type variants per real property (different floors, views, slight price spread) for a 20-30 card catalog. Then list \"coming soon\" cities with `comingSoon: true` flags + a coming-soon UI badge.\n- **`destinations.ts` shape**: add `comingSoon: boolean` and `propertyCount: 0` for non-active cities. The world-map and city grid then render those with a muted \"Coming soon\" treatment instead of a fake property count.\n- **MCP tools** specific to flex-living (different signatures from residential):\n  - `search_stays(city?, checkIn?, checkOut?, guests?, unitType?, maxRent?, minNights?)` — uses **check-in\u002Fcheck-out range** like Booking, NOT `duration_months` like Joivy. Both nightly + monthly results in one response.\n  - `find_flex_living(preference)` — translation tool (sibling to `find_co_living`). Natural-language → property + unit pick. Includes nights vs. months parsing.\n  - `book_stay(propertyId, checkIn, checkOut, guests)` — supports days OR months in one tool. NOT `book_viewing`.\n  - `get_lease_terms(propertyId)` — repurposed for \"stay terms\" — free cancellation window (typically 24-48h before), minimum nights, deposit, what's included.\n  - `get_living_spaces(propertyId)` — list amenities + common spaces (rooftop pool, café, cinema room, gym, coworking — Habyt Vallecas style).\n  - `get_property(propertyId)`, `compare_properties(ids[])`, `list_destinations(country?)` — same as residential.\n  - **Skip**: `search_rentals`, `find_co_living`, `book_viewing`, `find_experience` — wrong domain (residential or hotel).\n- **No 3D Matterport tours** typically — flex brands lean on photography + video walkthrough instead. The tours.json should be `{}` and `hasTour()` returns false; the PDP's 3D-tour pill must be conditional (`{tourAvailable && \u003Cpill\u002F>}`) so it silently disappears, not breaks.\n- **Hero subhead**: \"A stay that moves with you\" \u002F \"Flexible living, anywhere you go\" \u002F \"Book for days or months\" — emphasize flexibility, NOT permanence.\n- **Trust badges** (real Habyt order): `Free cancellation · Flexible stay · Best price` — these go above the price on the PDP booking card AND on listing tiles.\n- **Colors**: flex-living brands lean **darker, more luxurious** than residential — Habyt is forest green `#00271A` + terracotta `#572411` + cream `#FFFBF1`. NOT trust-warm teal (that's residential). The vibe is \"boutique extended-stay hotel\", not \"your home\" or \"your getaway\".\n- **Fonts**: same clean modern sans (Inter, Söhne) but allow a serif accent for headings on luxury-skewed flex brands (Habyt uses a humanist sans throughout).\n\n**RETAIL — MULTI-BRAND (Sephora, Nordstrom, Net-A-Porter, Farfetch, Selfridges, MatchesFashion):**\n\nDifferent from mono-brand luxury (Dior\u002FHermès) because they stock hundreds of external brands and have to surface those brands as first-class entities. Different from marketplace (Vinted\u002FAirbnb) because they carry real inventory, not user listings.\n\n- **Hero**: large campaign carousel (3-4 slides) with brand collaborations or seasonal themes — less minimalist than luxury, more editorial\u002Fcommercial.\n- **Navigation**: by category (Makeup, Skincare, Fragrance, Hair, Men, Gifts) AND by brand (dedicated \"Brands\" entry in the nav).\n- **Signature sections** on homepage:\n  1. Nouveautés \u002F New in — 16+ products\n  2. Bestsellers — 16+ products\n  3. Shop by category — 6-8 large tiles\n  4. Featured brands — horizontal row of 20+ brand cards (logos + \"shop the brand\")\n  5. Curated routine \u002F look builder — 3-4 step walkthrough (Nettoyer → Tonifier → Traiter → Hydrater for beauty)\n- **`src\u002Flib\u002Fbrands.ts`** — REQUIRED for multi-brand retail. `{ id, name, logo, origin, categories[], featured }[]` + `list_brands(category?, featuredOnly?)` MCP tool. Sephora stocks 340+ brands and without this the agent can't answer \"what brands do you stock from Korea\".\n- **Product detail view** — e-commerce shape (NOT Airbnb listing card, NOT credit-card detail):\n  - Gallery strip (hero + 3 thumbs; thumbs can repeat with product variants)\n  - Brand name (prominent, above title) + product title + star rating + review count + trust badges (\"Clean at Sephora\", \"Cruelty-free\", \"Vegan\")\n  - Price row (with strikethrough if discounted)\n  - **Shade \u002F swatch picker** — 8-12 color chips with hover labels (required for makeup; skincare skips this)\n  - Quantity selector + \"Add to bag\" \u002F \"Ajouter au panier\" button in the brand accent color\n  - Accordion sections: Ingredients, How to use, Benefits, Reviews\n  - \"Recommandés pour vous\" \u002F \"You might also like\" — 4-card row filtered to same category\n  - No booking card, no application form — pure e-commerce\n- **Fonts**: utility sans-serif (Inter \u002F Helvetica Neue). Matches beauty\u002Fretail flat-minimalism.\n- **Colors**: most beauty retailers use a stark black\u002Fwhite palette (Sephora, Net-A-Porter) with a single accent (Sephora red `#DE1F29`). Tom Ford \u002F Charlotte Tilbury do black + gold. Farfetch does black + editorial color blocks.\n- **MCP tools** specific to beauty retail:\n  - `list_brands(category?, featuredOnly?)` — filter 340+ brands by category\n  - `find_shade_match(undertone?, coverage?, finish?, skinTone?)` — foundation\u002Flipstick recommendation\n  - `get_routine(skinType?, concern?, budget?)` — 3-4 step skincare routine\n  - `get_fragrance_notes(productId)` — top\u002Fheart\u002Fbase notes per fragrance\n  - `search_products` extended with `brand?` and `skinType?` args\n\n**OUTERWEAR \u002F TECHNICAL (Canada Goose, Arc'teryx, Moncler, The North Face, Patagonia, Mammut):**\n\nMono-brand, premium\u002Fluxury, with technical-spec-forward product detail. Sits at the intersection of American heritage (narrative-heavy, made-in-X provenance) and sportswear (gender\u002Ffit\u002Factivity filter axes). Neither the Dior shape nor the Sephora shape nor the Ralph Lauren shape fits cleanly — it's its own pattern.\n\n- **Hero**: photographic — cold\u002Farctic\u002Fmountain landscape with a single figure in the brand's flagship product. Headline anchored in conditions (\"Built for the coldest place on earth\", \"Made for the alpine\", \"Tested at -40°C\"). Primary CTA = \"Shop [Flagship Product]\"; secondary = \"Discover the Heritage\".\n- **Stats bar**: founding year · Made-in-[country] · Lifetime Warranty · sustainability badge (HUMANE DOWN \u002F RECYCLED \u002F BLUESIGN).\n- **Signature sections on homepage**: 1) Shop the flagship product line (16+ tiles with warmth\u002Fweight indicator per tile); 2) Explore by collection (Expedition, Black Label, Eco-line, Lightweight); 3) Heritage timeline (wire to `heritage.ts`); 4) \"Built for explorers\" — 4 story cards featuring real-world users (scientist, mountaineer, ranger, conservationist).\n- **Product detail view — NEITHER the Airbnb booking card NOR the Sephora shade picker NOR the credit-card detail**. New shape:\n  - Gallery strip (hero + 3-4 thumbs)\n  - Breadcrumb: Home > [Gender] > [Category] > [Collection] > [Style]\n  - Style name + collection line (\"Expedition Parka\") + price\n  - **Color swatches** (circles, 6-8 colorways) — not shade chips, smaller\n  - **Size selector grid** (XS–XXL, with sold-out strikethrough on unavailable)\n  - **Warmth \u002F technical rating bar** — horizontal 1-5 scale (Canada Goose TEI, Arc'teryx has similar tier naming, North Face has similar). Label where this product sits.\n  - **Trust badge row** — 3 pills like HUMANE DOWN · MADE IN CANADA · LIFETIME WARRANTY\n  - Single \"Add to Bag\" button in brand color\n  - Accordions: Details (fill power, shell fabric, weight in g\u002Fkg), Sizing, Care, Sustainability\n  - \"Fit\" editorial block (how it's cut)\n  - \"You might also like\" — 4 cards\n- **Fonts**: utility sans-serif, often condensed (Helvetica Neue, Inter, Neue Haas).\n- **Colors**: the brand's dominant hero color (Canada Goose black, Moncler navy, Patagonia earth-tone) + a single flag-adjacent accent (Canada red, French blue, etc.).\n- **MCP tools** specific to outerwear \u002F technical:\n  - `check_warmth(temperature_c, activity)` — a **translation tool** (conditions → product suggestion) that's neither search nor recommend nor compare. Pattern: customer asks \"what works at -25°C hiking\", tool returns TEI band + matching products. **This shape is new** — document it as a category, other brand types will need translation tools too (e.g. shoes \"what fits size 10 UK narrow\"; skincare \"what's safe during pregnancy\").\n  - `compare_parkas(ids[])` — extended comparison exposing the technical-spec axes (fill power, weight, TEI, shell fabric).\n  - `get_heritage(yearFrom?, yearTo?)` — from `heritage.ts`.\n  - `find_store(city?, country?)` — flagship + experiential retail; use `flagships.ts`'s `note` field for retail-differentiator metadata (\"Cold Room try-on\", \"Arc'teryx Pinnacle Room\", \"Patagonia Worn Wear repair\").\n  - `get_sustainability(productId?)` — sourcing + materials detail; customers ask this more than the other verticals.\n\n**`src\u002Fcomponents\u002Fwwa-panel.tsx`** — ACCOUNT CREATION FLOW:\n\nThe template's account creation asks for \"annual income\" (makes sense for credit card applications, wrong for everything else). For non-financial brands, replace the income question with something contextually relevant:\n\n| Brand Type | Replace \"annual income\" with |\n|------------|------------------------------|\n| Luxury\u002FFashion | \"What categories interest you most? (Fragrance, Bags, Fashion, Jewelry)\" |\n| E-commerce | \"What styles do you prefer?\" |\n| SaaS | \"What's your role\u002Fteam size?\" |\n| Enterprise | \"What's your company size?\" |\n| Content\u002FMedia | \"What genres do you like?\" |\n| Financial | Keep \"annual income\" — it's relevant |\n| Marketplace \u002F C2C | \"Are you mostly buying or selling?\" + follow-up category interest. Ask BOTH because the primary flow branches on this. |\n\nAlso update:\n- `lastAssistantMsg.includes(\"annual income\")` → check for the new question\n- Welcome message: \"Apply for any card\" → \"Shop\" \u002F \"Start using\" \u002F appropriate verb\n- Summary line: \"? $income\" → \"✨ Interests: preferences\"\n- Avatar background color: `1A1F71` (Visa blue) → brand primary color\n\n**`src\u002Fcomponents\u002Fwwa-panel.tsx`** — BUY\u002FCHECKOUT MESSAGES:\n\nReplace credit-card phrasing in the buy intent responses:\n- \"apply for\" → \"order\" \u002F \"shop\" \u002F \"checkout\"\n- \"card\" → \"product\" \u002F \"item\"\n- \"annual fee\" → \"price\"\n- \"Quick apply\" → \"Quick checkout\" \u002F \"Fast order\"\n- \"I'll fill the form for you\" → \"I'll place the order for you\"\n\n**`src\u002Fcomponents\u002Fworld-map.tsx`** — REGIONAL STATS:\n\nThe template has credit-card network stats (`merchants: \"12M+\"`, `banks: \"5,000+\"`, `cards: \"800M+\"`). Replace with brand-appropriate stats:\n\n| Brand Type | Regional Stats |\n|------------|----------------|\n| Luxury\u002FFashion | Boutiques per region, artisans, flagship locations |\n| SaaS | Data centers, enterprise customers, API regions |\n| Retail | Stores, distribution centers, warehouses |\n| Finance | Banks, merchants, cards (keep default) |\n\nAlso update GLOBAL_STATS: `\"4B+ Cards worldwide\"` must match the brand's reality.\n\n**`src\u002Fcomponents\u002Fcard-comparison.tsx`** — TIER BENEFITS:\n\nThe template has 20+ Visa-specific credit card benefits (Zero Liability, Auto Rental CDW, Trip Delay, Global Entry Credit, etc). REMOVE all of these and write tier benefits that apply to the brand:\n\n| Brand Type | Tier Benefit Examples |\n|------------|----------------------|\n| Luxury\u002FFashion | Free shipping, gift wrap, personalization, private shopping, birthday gift, archive access |\n| SaaS | API calls\u002Fmo, support SLA, seats, priority features, dedicated account manager |\n| Retail | Free shipping threshold, returns window, early access, member pricing |\n| Subscription | Streaming quality, devices, downloads, family sharing, ad-free |\n\nTier names `Traditional \u002F Signature \u002F Infinite` are Visa-specific — rename to match the brand's tier system (e.g., Free\u002FPro\u002FEnterprise for SaaS, Essentials\u002FSignature\u002FÉlite for luxury).\n\n### Step 3.6: Verify Zero Original References\n\nThree comprehensive checks. ALL must pass before deploying:\n\n```bash\n# 0. RE-RUN Step 2.3 visual verification for every image referenced from cards.ts \u002F solutions.ts.\n#    Open each file in Read and confirm it still shows the correct brand. Do not trust\n#    earlier verification — if an agent rewrote data files during Phase 3, image paths may\n#    have been shuffled. This check is fast (8-12 Read calls) and catches the #1 UX bug.\ngrep -oE '\"\u002Fimages\u002F[^\"]+\"' src\u002Flib\u002Fcards.ts src\u002Flib\u002Fsolutions.ts | sort -u\n# For each path listed, Read it and confirm brand match.\n\n# 1. Check for any Visa-brand text leaks\ngrep -rn \"Visa\\|visa\\.\\|#1A1F71\\|#141963\\|#1434CB\" src\u002F --include=\"*.tsx\" --include=\"*.ts\" | grep -v visaCards | grep -v VisaCard\n\n# 2. Check for credit-card terminology that doesn't fit non-card brands\ngrep -rn \"annual fee\\|annual income\\|card tier\\|Apply Now\\|cardholder\\|APR\\|Reward Rate\\|Sign-Up Bonus\\|issued by\\|Zero Liability\\|credit check\\|credit history\\|Traditional, Signature, and Infinite\\|Issuer opt\\.\" src\u002F --include=\"*.tsx\" --include=\"*.ts\" -i | grep -v node_modules\n```\n\nFix every remaining line before deployment. The `card-3d.tsx` component is allowed to keep credit-card text because it's only rendered for actual credit card brands (Visa\u002FMastercard).\n\n### Known template residues — scrub before deploy\n\nThese files ship in the template with Visa-shaped placeholders that the ordinary Phase 3 rewrites don't always catch. Verify each one explicitly before deploying:\n\n| File | What to scrub |\n|------|---------------|\n| `src\u002Fcomponents\u002Fbook-demo-modal.tsx` | Ships with B2B fields (CompanySize, AnnualRevenue, Country dropdown, SKU picker) AND an inline Visa wordmark SVG in the header. For luxury \u002F e-commerce brands, rewrite as \"Request a Private Appointment\" per the luxury pattern above. For SaaS keep B2B but relabel products. For consumer, replace entirely with a newsletter\u002Fcontact form. **For marketplace \u002F C2C brands**, rewrite as \"Open your seller account\" — fields: name + email + username + preferred market (dropdown of the brand's live markets only, NOT all countries) + account type (Personal vs Pro) + main category + expected item volume. Drop B2B revenue\u002Fsize fields entirely. **For marketplace \u002F Listings brands** (Booking, Airbnb, VRBO, Expedia), rewrite instead as \"List your property\" — fields: contact name + email + phone + property type (Hotel \u002F Apartment \u002F Villa \u002F B&B \u002F Holiday home \u002F Cabin) + number of rooms + destination (city\u002Fcountry) + property name + short description + partner-terms opt-in. Primary audience of this modal is hosts, not buyers — the buyer surface is the search form in the hero. Drop B2B revenue\u002Fsize fields. **For retail \u002F multi-brand brands** (Sephora, Nordstrom, Net-A-Porter, Farfetch), rewrite as a loyalty signup — fields: name + email + birthday (short format MM-DD for anniversary gifts) + preferred categories (multi-select chips: Makeup \u002F Skincare \u002F Fragrance \u002F Hair \u002F Men \u002F Gifts) + occasion dropdown (\"For myself\" \u002F \"As a gift\" \u002F \"Wedding\" \u002F \"Event\") + GDPR\u002Fmarketing consent checkbox. The loyalty programme name and tiers go in the header copy (e.g. Sephora's Blanche\u002FOr\u002FNoire, Nordstrom's Nordy Club). Drop B2B revenue\u002Fsize fields. In all cases, replace the header SVG with `\u003Cimg src={BRAND.logoImage} className=\"brightness-0 invert\" \u002F>`. The hero's main CTA opens this modal — an untouched modal ships the wrong form and the wrong logo on the most-clicked button. |\n| `src\u002Flib\u002Fcards.ts` field repurposing per brand type | The `ProductItem` interface is finance-shaped (`issuer`\u002F`tier`\u002F`annualFee`\u002F`apr`\u002F`rewardRate`\u002F`signUpBonus`\u002F`applyUrl`) but the field names are stable — semantics repurpose per brand. Keep a comment block at top of `cards.ts` documenting the mapping so the next maintainer doesn't report them as Visa leaks. **Per brand type:** marketplace C2C → `annualFee: \"Free\" \u002F \"€5 shipping\"`, `apr: \"All markets\"`, `rewardRate: headline benefit`, `signUpBonus: incentive`. Marketplace Listings → `annualFee: \"from €180\u002Fnight\"`, `apr: \"Entire place\"`, `rewardRate: \"★ 4.9\"`, `signUpBonus: \"Free cancellation\"`. Retail Multi-brand Beauty → `issuer: brand name` (e.g. \"Fenty Beauty\"), `tier: collection\u002Fline`, `annualFee: price (€)`, `apr: shade \u002F finish` (\"50 shades · Matte finish\"), `rewardRate: \"★ 4.6 (1.2K reviews)\"`, `signUpBonus: badge` (\"Clean at Sephora\" \u002F \"Award winner\"), `applyUrl: product URL`. Luxury mono-brand → `issuer: House name`, `tier: line` (Lady Dior \u002F Book Tote), `annualFee: price`, `apr: material\u002Fsize`, `signUpBonus: included` (engraving \u002F monogram). **Outerwear \u002F Technical** → `issuer: **gender line**` (\"Men's\" \u002F \"Women's\" \u002F \"Kids'\" \u002F \"Unisex\") — NOTE this is the inverse of beauty where `issuer` holds the brand name. For technical apparel the gender axis is the primary filter, so `issuer` carries it; the brand is implicit (mono-brand). `tier: collection` (\"Expedition\" \u002F \"Black Label\" \u002F \"Lightweight\"), `annualFee: price`, `apr: warmth rating \u002F weight` (\"TEI 4 · 2.05 kg\"), `rewardRate: fill-power` (\"625 fill\"), `signUpBonus: sustainability badge` (\"HUMANE DOWN\" \u002F \"RECYCLED\" \u002F \"MADE IN CANADA\"). **Fashion editorial-minimalist \u002F fast-fashion** → `issuer: gender line` (\"Woman\" \u002F \"Man\" \u002F \"Kids\" — same inversion as outerwear; mono-brand fashion uses issuer for gender, not brand). `tier: collection sub-line` (\"Main\" \u002F \"Studio\" \u002F \"SRPLS\" \u002F \"Origins\" \u002F \"TRF\" \u002F \"Limited Edition\" \u002F \"Join Life\"), `annualFee: price`, `apr: material\u002Fcomposition` (\"100% linen\" \u002F \"Wool blend\"), `rewardRate: size range` (\"XS – XXL\"), `signUpBonus: badge` (\"NEW\" \u002F \"JOIN LIFE\" \u002F \"LIMITED\" \u002F \"BESTSELLER\"). Also add `src\u002Flib\u002Fcollections.ts` for the parallel capsule sub-lines. Don't rename the interface properties unless you're willing to update ~12 component references. For listings marketplaces also create `src\u002Flib\u002Fdestinations.ts`; for multi-brand retail also create `src\u002Flib\u002Fbrands.ts` (brand catalogue) and optionally `src\u002Flib\u002Ffragrances.ts` (notes + perfumer); for heritage + outerwear reuse the template's `src\u002Flib\u002Fheritage.ts` + `src\u002Flib\u002Fflagships.ts` stubs. |\n| `src\u002Fcomponents\u002Fassistant-shared.tsx` EmptyState | The welcome-screen logo is **the call button** (clicking it starts the voice call). Ships with an inline Visa wordmark SVG — which means the FIRST FRAME a customer sees before any interaction shows a Visa logo. Replace the `\u003Csvg>\u003Cpath d=\"...\" \u002F>\u003C\u002Fsvg>` inside the EmptyState button with `\u003Cimg src={BRAND.logoImage} alt={BRAND.name} \u002F>`. Without this fix, every brand transform launches on a Visa logo. |\n| `src\u002Fcomponents\u002Flive-session-overlay.tsx` | Two inline SVG references render the Visa wordmark in the voice-call overlay (header + animated center). Replace with `\u003Cimg src={BRAND.logoImage} alt={BRAND.name} \u002F>` or swap the SVG path — otherwise the voice call shows Visa. Also rewrite the system-prompt text (role, CTAs, \"local banks in 200+ countries\") per brand, BUT keep the \"TOOL USE IS MANDATORY\" block verbatim — it's what makes Gemini Live actually drive the left panel. |\n| `src\u002Flib\u002Fgemini-live-client.ts` | The `show_card` \u002F `show_solution` tool descriptions include example IDs (`'chase-sapphire-preferred'`, `'tap-to-pay'`). Gemini Live reads these as strong hints about what valid IDs look like. If you leave them unchanged on a non-Visa brand, the voice call will refuse to invoke the tools or will call them with made-up IDs — and the left panel stays empty during the call. Replace both example IDs with real ids from your brand's `cards.ts` \u002F `solutions.ts` (e.g. `'jadore-edp'`, `'cruise-2026'`). This is the single most common reason voice calls \"just talk\" without updating the visible panel. |\n| `src\u002Fcomponents\u002Fagent-panel.tsx` | The mock API key uses the prefix `vsk_live_` (Visa-derived). Change to a brand-neutral `api_live_` or a brand-specific prefix (`hsk_`, `drk_`, etc). Runs through `Math.random().toString(36)` — easy to miss. |\n| `src\u002Flib\u002Fcards.ts` | The `ProductItem` interface fields (`annualFee`, `apr`, `rewardRate`, `signUpBonus`, `issuer`, `applyUrl`) all bias toward credit cards. For non-card brands, either repurpose them (document with a comment block at the top of cards.ts — e.g. `annualFee` → price, `apr` → material, `rewardRate` → craftsmanship) or rename the interface properly (updates ~12 components). The audit grep cannot tell a repurposed field from a leak. |\n| `src\u002Fcomponents\u002Fhero-section.tsx` | Often still contains hardcoded `STATS` \u002F `CARD_TIERS` arrays instead of reading from `BRAND.stats`. Replace with `BRAND.stats.map(...)` so stats come from brand-config. |\n| `src\u002Fcomponents\u002Finner-page.tsx` | Contains `PersonalPage`, `BusinessPage`, `TravelPage` route shapes that assume a payments-brand nav. Rename \u002F re-shape to match `BRAND.navItems` or delete and let `page.tsx` route dynamically. |\n\n---\n\n## PHASE 4: Build, Deploy, Verify\n\n### Step 4.0: Generate a unique, safe slug (REQUIRED)\n\n**Every transform MUST deploy under a `project-*` slug, not the raw brand name.** Two reasons:\n\n1. **Safe Browsing safety** — Chrome's brand-phishing classifier flags any subdomain that looks like a well-known brand (`booking.codiris.app`, `apple.codiris.app`, `nike.codiris.app`). Using `project-\u003Cbrand>-\u003Cunique>` breaks that exact-match heuristic. This is a hard requirement for new transforms since the Booking incident (2026-04-21).\n2. **Collision avoidance** — multiple customers transforming the same brand would race for one subdomain. A unique suffix guarantees every customer's deploy has its own URL.\n\n**The required slug shape:**\n\n```\nproject-\u003Cshort-brand>-\u003C4char-hex>\n```\n\n- `\u003Cshort-brand>` — 3-8 letters, lowercase, pointing at the brand but not the full domain. Drop the word most associated with the real brand if the full name is too recognizable. Examples:\n  - `booking.com` → `book24` (NOT `booking`)\n  - `airbnb.com` → `abnb`\n  - `dior.com` → `dior` is fine (not a phishing target yet)\n  - `nike.com` → `nk` or `nike` (borderline — prefer `nk`)\n  - `chase.com` → `chs` (fintech = high-risk — always obfuscate)\n- `\u003C4char-hex>` — generated from `openssl rand -hex 2` (4 hex chars = 65,536 combinations). Never reuse.\n\n**Generate at the start of Phase 4:**\n\n```bash\nSHORT_BRAND=\"book24\"     # replace per brand\nRANDOM_ID=$(openssl rand -hex 2)\nSLUG=\"project-${SHORT_BRAND}-${RANDOM_ID}\"\necho \"Your slug: $SLUG\"\n# e.g. project-book24-a4f2\n```\n\nSave this value — you'll use it in `brand-config.ts`, as the Vercel project name, as the Cloudflare CNAME, and as the alias.\n\n**Collision check against the registry:**\n\n```bash\ncurl -s -o \u002Ftmp\u002Fclaim.json -w \"%{http_code}\\n\" \"https:\u002F\u002Fcodiris.app\u002Fapi\u002Fwwa\u002Fregistry\u002F$SLUG\"\n```\n\n- **HTTP 404** — slug is free (expected when using the 4-char random suffix). Continue.\n- **HTTP 200** — astronomically unlikely collision. Regenerate `RANDOM_ID` and try again.\n\n**Update brand-config.ts** so every runtime reference to the deploy URL is correct:\n\n```ts\nexport const BRAND: BrandConfig = {\n  \u002F\u002F ...\n  mcpUrl: `https:\u002F\u002Fwwa.${SLUG}.codiris.app\u002Fmcp`,   \u002F\u002F replace ${SLUG} with your generated value\n  mcpServerName: `${SLUG}-agent`,                   \u002F\u002F used in MCP server name + CLI install command\n};\n```\n\n**Exceptions (grandfathered):** the original 7 brands on `codiris.app\u002Fskills` (visa, stripe, dior, ralphlauren, hermes, puma, vinted) still live at `wwa.\u003Cbrand>.codiris.app` — they pre-date this policy. Do NOT add new transforms at raw-brand subdomains; every new one gets a `project-*` slug.\n\n**After a successful deploy,** open a PR to `public\u002Fwwa-registry.json` in `wwwtowwa` adding your entry:\n\n```json\n{\n  \"slug\": \"{short-brand}\",\n  \"domain\": \"{brand}.com\",\n  \"deployed_url\": \"https:\u002F\u002Fwwa.{slug-with-random}.codiris.app\",\n  \"mcp_url\": \"https:\u002F\u002Fwwa.{slug-with-random}.codiris.app\u002Fmcp\",\n  \"type\": \"{luxury-french|luxury-heritage|fintech|saas|marketplace|marketplace-listings|sportswear|consumer}\",\n  \"color\": \"{brand primary hex}\",\n  \"first_claimed_at\": \"YYYY-MM-DD\",\n  \"owner\": \"{your-handle-or-email}\"\n}\n```\n\nNote: the registry `slug` field is the **short brand** (e.g. `booking`) so the showcase lookup groups all deploys of that brand together, while `deployed_url` carries the full `project-\u003Cbrand>-\u003Chex>` subdomain that's unique per transform.\n\n### Step 4.1: Build\n```bash\nnpm run build\n```\nFix ALL errors. Common: unterminated strings, missing images, type mismatches.\n\n### Step 4.2: Deploy\n\nCreate `.env.local` in your new project with the keys below. A stub `.env.example` ships in the template — `cp .env.example .env.local` and fill in your own values.\n\n```\nOPENAI_API_KEY=sk-…          # from https:\u002F\u002Fplatform.openai.com (fallback chat model)\nGEMINI_API_KEY=AIza…         # from https:\u002F\u002Faistudio.google.com\u002Fapikey (primary)\nGOOGLE_GENERATIVE_AI_API_KEY=AIza…  # same value as GEMINI_API_KEY (the voice client reads this name)\n```\n\nThe MCP endpoint renders without these keys — only the AI chat + voice call need them.\n\n```bash\nnpx vercel --prod --yes\n\n# Push env vars to Vercel\nsource .env.local\necho \"$OPENAI_API_KEY\"               | npx vercel env add OPENAI_API_KEY               production --force\necho \"$GEMINI_API_KEY\"               | npx vercel env add GEMINI_API_KEY               production --force\necho \"$GOOGLE_GENERATIVE_AI_API_KEY\" | npx vercel env add GOOGLE_GENERATIVE_AI_API_KEY production --force\n\nnpx vercel --prod --yes\n```\n\n### Step 4.2b: Disable Vercel Deployment Protection (if the deploy returns 401)\n\nNew Vercel projects under some team accounts default to **Standard Protection** (SSO-required). Symptom: `curl https:\u002F\u002Fwwa{brand}.vercel.app` returns **HTTP 401** with a Vercel SSO login page. Happens silently — no warning from the CLI.\n\nCheck with `curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\\n\" https:\u002F\u002F{your-vercel-url}`. If you see 401, disable protection via the Vercel API:\n\n```bash\n# Read the Vercel CLI's auth token (macOS path)\nTOKEN=$(cat \"$HOME\u002FLibrary\u002FApplication Support\u002Fcom.vercel.cli\u002Fauth.json\" | python3 -c 'import sys,json; print(json.load(sys.stdin).get(\"token\",\"\"))')\nPROJECT_ID=$(python3 -c \"import json; print(json.load(open('.vercel\u002Fproject.json'))['projectId'])\")\nTEAM_ID=$(python3 -c \"import json; print(json.load(open('.vercel\u002Fproject.json'))['orgId'])\")\n\ncurl -s -X PATCH \"https:\u002F\u002Fapi.vercel.com\u002Fv9\u002Fprojects\u002F$PROJECT_ID?teamId=$TEAM_ID\" \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"ssoProtection\":null,\"passwordProtection\":null}' \\\n  | python3 -c \"import sys,json; r=json.load(sys.stdin); print('sso:', r.get('ssoProtection'), '| pw:', r.get('passwordProtection'))\"\n```\n\nExpected output: `sso: None | pw: None`. The change takes effect within seconds — no redeploy needed.\n\nLinux path: `$HOME\u002F.local\u002Fshare\u002Fcom.vercel.cli\u002Fauth.json`. Windows path: `%APPDATA%\\com.vercel.cli\\auth.json`.\n\n### Step 4.3: Custom subdomain (OPTIONAL — requires Cloudflare token)\n\nThe `wwa.{brand}.codiris.app` alias requires a Cloudflare API token scoped to the `codiris.app` zone. **This token is not shipped with the skill** — it's private infrastructure. Two paths:\n\n**A. You have the token** (maintainer, or coordinated with Iris Lab):\n```bash\nexport CLOUDFLARE_API_TOKEN=…  # scoped to codiris.app zone, DNS edit permission\n\nZONE_ID=$(curl -s \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones?name=codiris.app\" \\\n  -H \"Authorization: Bearer $CLOUDFLARE_API_TOKEN\" \\\n  | python3 -c \"import sys,json; print(json.load(sys.stdin)['result'][0]['id'])\")\ncurl -s -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Fdns_records\" \\\n  -H \"Authorization: Bearer $CLOUDFLARE_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"type\":\"CNAME\",\"name\":\"wwa.{domain}\",\"content\":\"cname.vercel-dns.com\",\"proxied\":false,\"ttl\":1}'\nnpx vercel domains add wwa.{domain}.codiris.app\nnpx vercel --prod --yes\n```\n\n**B. You don't have the token** (most customers):\nSkip this step. Your Vercel default URL (`https:\u002F\u002F\u003Cproject>.vercel.app`) is a fully working agentfront — the MCP endpoint, chat, and all pages work there. Update `brand-config.ts` `mcpUrl` to the Vercel URL so the displayed install command matches. Ask the registry owner (open an issue at github.com\u002FHumiris\u002Fwwa-transform) to provision the `wwa.{brand}.codiris.app` alias when you're ready to ship under the shared subdomain.\n\n### Step 4.4: Verify\n1. Check HTTP 200: `curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fwwa.{domain}.codiris.app`\n2. Use WebFetch to read the deployed page — check NO wrong-company content\n3. Check images load\n4. **MCP round-trip**: `curl -s -m 20 -X POST https:\u002F\u002Fwwa.{domain}.codiris.app\u002Fmcp -H \"Content-Type: application\u002Fjson\" -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Flist\"}'` — must return the tool list with 200\n5. Report URL to user\n\n**Preview-tool caveat:** the `preview_start` MCP tool detects `package.json` from your **session cwd**, not from `.claude\u002Flaunch.json` in the target project. If your session cwd is not the target project (e.g. you're working on `wwa.ralphlauren` from a session rooted at `wwa.visa`), `preview_start` will start the wrong dev server. Verify via `curl` against the deployed URL instead of local screenshots when working cross-project.\n\n---\n\n## QUALITY CHECKLIST\n\nBefore saying \"done\", verify:\n- [ ] Hero shows THIS company's real value prop and images\n- [ ] Stats are THIS company's real numbers\n- [ ] Products\u002Fsolutions are from THIS company's website\n- [ ] Categories make sense for THIS company (no \"Travel Cards\" for Stripe)\n- [ ] Navigation matches THIS company's actual sections\n- [ ] Inner pages have real content from THIS company\n- [ ] Chat suggestions are relevant to THIS company\n- [ ] Fallback responses reference THIS company's real products\n- [ ] All images are downloaded and loading\n- [ ] Zero references to any other company (Visa, etc.)\n- [ ] The page structure makes sense for THIS type of company\n- [ ] CTAs match what the company actually wants users to do\n- [ ] **Catalog depth meets the minimum for this brand type** (see Phase 2 \"Catalog size\" table). For e-commerce: 100+ product entries in `cards.ts`, spread across the brand's real segments (Woman\u002FMan\u002FKids\u002Fetc). Verify with `search_products` returning `count ≥ 100` via MCP.\n","# Codiris Agentizer v2 — Intelligent Website-to-Agentfront\n\nTransform any website into a custom AI-powered agentfront. The skill deeply analyzes the company — its market, products, value proposition, customers — then builds a tailored experience. NOT a template copy-paste.\n\n## Core Principle\n\n**Understand the company first, build second.** Every company is different:\n- Stripe sells APIs to developers → show API products, code examples, pricing tiers\n- Nike sells shoes to consumers → show product catalog, categories, shopping\n- Visa sells payment cards → show card tiers, comparisons, benefits\n- Salesforce sells enterprise SaaS → show solutions by industry, case studies, demos\n\nThe agentfront must reflect what the company ACTUALLY is, not what Visa is.\n\n## Template Location\n`.\u002Ftemplate\u002F` relative to this SKILL.md — the skill directory (typically `~\u002F.claude\u002Fskills\u002Fagentizer\u002F` after install) contains the Next.js template. Content is generated custom per company. After `cp -R`, run the template's `npx next build` once to confirm nothing regressed in the template itself.\n\n## Reference Implementation\n**https:\u002F\u002Fwwa.visa.codiris.app** — live demo of a finished agentfront (payment card company). Source for the template is at https:\u002F\u002Fgithub.com\u002FHumiris\u002Fwwa-transform\u002Ftree\u002Fmain\u002Ftemplate.\n\nIf any template file looks incomplete or broken, inspect the live demo via WebFetch for visual reference, then apply the `visaCards → productItems` \u002F `VisaCard → ProductItem` \u002F `annualFee → price` renames — don't try to fix the template stub in place.\n\n---\n\n## PHASE 1: Deep Company Intelligence\n\n### Step 1.1: Crawl Multiple Pages\n\nUse `WebFetch` on at minimum:\n1. **Homepage** — hero, value prop, main CTAs, navigation\n2. **Products\u002FFeatures page** — what they actually sell\n3. **Pricing page** (if exists) — how they charge, what tiers\n4. **About page** — company story, mission, stats\n\nFor EACH page, ask WebFetch:\n```\nExtract everything: brand name, tagline, ALL image URLs (full absolute), \ncolors (hex from buttons\u002Fheaders\u002FCSS), navigation items, products\u002Ffeatures \nwith descriptions, pricing tiers, stats\u002Fnumbers, customer logos, \ntestimonials, CTAs, form fields. Be exhaustive.\n```\n\n### Step 1.2: AI Company Analysis\n\nAfter crawling, THINK deeply about the company. Answer these questions BEFORE writing any code:\n\n**Market Understanding:**\n- What industry is this company in? (Fintech, SaaS, E-commerce, Healthcare, etc.)\n- Who are their customers? (Developers, Enterprises, Consumers, SMBs)\n- What problem do they solve?\n- Who are their competitors?\n\n**Product Understanding:**\n- What do they sell? (APIs, Physical products, Subscriptions, Services, Cards)\n- How many products\u002Ftiers do they have?\n- How do they charge? (Per-transaction, Subscription, One-time, Usage-based, Free)\n- Do they have a free tier or trial?\n\n**Content Structure:**\n- What sections make sense for THIS company's homepage?\n- What navigation items should exist?\n- What categories should products be organized by?\n- Should there be a \"cards\" section? (Only if they sell cards\u002Fplans\u002Ftiers)\n- Should there be a pricing grid? A product catalog? Case studies?\n\n**Value Proposition:**\n- What's their main headline?\n- What stats are impressive? (Users, revenue, uptime, countries)\n- What social proof do they have? (Customer logos, testimonials)\n\n**Typography (CRITICAL — match brand aesthetic):**\n\nThe template uses Geist by default. You MUST change fonts to match the brand:\n\n| Brand Type | Fonts to Use | Implementation |\n|------------|--------------|----------------|\n| Luxury fashion (Dior, Hermès, Chanel) | Playfair Display + Inter | Serif headings, clean body |\n| Tech\u002FSaaS (Stripe, Notion, Linear) | Inter or Geist | Modern sans-serif |\n| Premium\u002FEditorial (Apple, Aesop) | SF Pro \u002F Helvetica Neue \u002F system fonts | Clean, minimal |\n| Fintech (Visa, Chase) | Geist \u002F Inter | Professional sans |\n| E-commerce (Amazon, Walmart) | Inter \u002F Roboto | Readable, utilitarian |\n\nUpdate `src\u002Fapp\u002Flayout.tsx`:\n```tsx\nimport { Playfair_Display, Inter } from \"next\u002Ffont\u002Fgoogle\";\n\nconst serif = Playfair_Display({ variable: \"--font-serif\", subsets: [\"latin\"] });\nconst sans = Inter({ variable: \"--font-sans\", subsets: [\"latin\"] });\n\n\u002F\u002F In body: className={`${serif.variable} ${sans.variable} font-sans`}\n```\n\nUpdate `src\u002Fapp\u002Fglobals.css`:\n```css\n:root {\n  --brand-primary: #000000;    \u002F* match brand color *\u002F\n  --brand-secondary: #C9A96E;\n  --font-serif-brand: var(--font-serif), \"Didot\", \"Bodoni MT\", \"Georgia\", serif;\n}\n\nh1, h2, .font-serif {\n  font-family: var(--font-serif-brand);\n  letter-spacing: -0.01em;\n}\n```\n\n**User Intent (CRITICAL — drives CTAs and modals):**\nAnalyze what users ACTUALLY do on this site. Map to correct CTA:\n\n| Company Type | Primary Intent | CTA Text | Modal Type |\n|--------------|---------------|----------|------------|\n| E-commerce (Dior, Nike, Apple) | Shop \u002F Buy products | \"Shop Now\" | Cart \u002F Product detail |\n| SaaS\u002FAPI (Stripe, Notion) | Try \u002F Book demo | \"Start Free\" or \"Book a Demo\" | Demo booking form |\n| Enterprise (Salesforce) | Contact sales | \"Contact Sales\" | Sales form |\n| Financial (Visa, banks) | Apply \u002F Get card | \"Apply Now\" | Application form |\n| Marketplace — Listings (Airbnb, Booking, Uber) | Search \u002F Book | \"Start Searching\" | Search UI |\n| Marketplace — C2C (Vinted, Depop, Etsy, eBay) | Sell AND Browse (dual intent) | \"Sell Now\" + \"Start Browsing\" | Seller signup modal (personal \u002F pro) |\n| Services (Consulting) | Contact \u002F Meeting | \"Book a Call\" | Calendar booking |\n| Content (Netflix, Spotify) | Subscribe \u002F Try | \"Start Free Trial\" | Signup form |\n\n**NEVER use \"Book a Demo\" for e-commerce.** E-commerce brands want you to SHOP, not schedule a meeting.\n\nUpdate these files based on intent:\n- `brand-config.ts` → `ctaPrimary` and `ctaSecondary`\n- `hero-section.tsx` → button text\n- `solution-detail-panel.tsx` → button text\n- `book-demo-modal.tsx` → rename, change fields to match intent (e-commerce = Contact Client Services, Cart, or remove entirely)\n- `actions.ts` system prompt → what the agent offers users\n\n### Step 1.3: Define the Page Architecture\n\nBased on your analysis, decide which sections the homepage should have. Choose from:\n\n| Section | Use When | Example |\n|---------|----------|---------|\n| Hero Carousel | Always | Rotating through top products\u002Ffeatures |\n| Stats Bar | Company has impressive numbers | \"$1.9T processed\", \"99.999% uptime\" |\n| Product Grid | 3+ distinct products | API products, SaaS modules |\n| Pricing Tiers | Clear pricing tiers exist | Free\u002FPro\u002FEnterprise |\n| Feature Showcase | Key differentiators | With images and descriptions |\n| Customer Logos | Has notable customers | \"Trusted by Amazon, Shopify...\" |\n| Solution Categories | Products grouped by use case | \"For Startups\", \"For Enterprise\" |\n| Code Example | Developer-focused company | Interactive code snippet |\n| Card Catalog | Sells cards\u002Fplans consumers browse | Credit cards, subscription plans |\n| CTA Banner | Always | \"Book a Demo\" \u002F \"Get Started\" \u002F \"Start Free\" |\n| World Map | Company has global presence story | Payment networks, logistics, international SaaS |\n\n**DO NOT include sections that don't apply:**\n- API company → NO credit card tiers, NO card comparison\n- E-commerce → NO API docs, NO code examples\n- SaaS without global story → NO world map (make `handleShowMap` a no-op in page.tsx)\n- Company without browsable products → leave `productItems` array empty, the browse section won't render\n\n---\n\n## PHASE 2: Download Assets\n\n### Step 2.1: Download ALL Images\n\n**MANDATORY.** The agentfront is useless without real images.\n\n> ❗ **The single biggest bug in past transforms** is shipping images from the wrong brand — a generic \"sneaker\" photo from Unsplash that happens to show a Nike Swoosh on an adidas site, or a \"handbag\" photo that's clearly Chanel on a Dior site. Mis-branded imagery destroys credibility instantly.\n>\n> **Rule**: Every image that represents a **specific named product or franchise** (e.g. \"Samba OG\", \"Air Max 90\", \"Lady Dior\") MUST come from a source that lets you verify it shows the correct brand. Generic-category Unsplash photos are banned for these slots. They are OK only for brand-agnostic shots (lifestyle hero, category tiles with no named product, abstract backgrounds).\n>\n> **And every image MUST pass visual verification (Step 2.3) before you write its path into `cards.ts` \u002F `solutions.ts`.**\n\n```bash\nmkdir -p ~\u002Fwwa.{domain}\u002Fpublic\u002Fimages\u002Fcards\n\n# Use browser headers to bypass CDN blocks\ncurl -L -o \"public\u002Fimages\u002F{name}.jpg\" \"{url}\" \\\n  -H \"User-Agent: Mozilla\u002F5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit\u002F537.36\" \\\n  -H \"Referer: https:\u002F\u002F{domain}\u002F\" \\\n  -H \"Accept: image\u002F*\"\n```\n\n**Download at minimum:**\n- Logo (SVG preferred, PNG fallback)\n- Hero\u002Fbanner image\n- 1 image per product\u002Fsolution (6-10 total)\n- 2-4 lifestyle\u002Ffeature images\n- Customer logos if available\n- Product screenshots\u002FUI images\n\n### Image Source Priority (USE IN THIS ORDER)\n\n**For e-commerce catalogs (fashion retailers, beauty retailers, online-only fashion), always try method 0 FIRST:**\n\n**0. Scrape the brand's SSR catalog JSON via Chrome MCP** — modern e-commerce sites (Zara, H&M, ASOS, Nordstrom, Sephora, etc.) ship the full product grid as a JSON blob inside a `\u003Cscript>` tag on every category page. Server-side curl gets WAF-blocked, but Chrome MCP with an organic-looking tab has no trouble reading the DOM.\n\nTwo flavors to look for:\n\n- **JSON-LD `\u003Cscript type=\"application\u002Fld+json\">`** (cleanest — H&M, many schemas). Has `@type: Product` entries with `name`, `image[]`, `offers.price` ready to `JSON.parse`.\n- **Raw hydration JSON** (Zara, ASOS — biggest `\u003Cscript>` that contains the brand's CDN hostname). Not always valid JSON; regex out the image URL pattern (e.g. `\u002Fstatic\\.zara\\.net\\\u002Fphotos\\\u002F[^\"'\\s]+\\.jpg\u002Fg` or `\u002Fproducts\\\u002F[a-z0-9-]+\\\u002F\\d+-\\d+[a-z0-9-]*\u002Fgi`) and dedupe by product id.\n\nPattern that works today (verified on Zara 259 · H&M 216 · ASOS 365 · Uniqlo 54 scrapes):\n\n```js\n\u002F\u002F In Chrome MCP, navigate to e.g. https:\u002F\u002Fwww.zara.com\u002Fuk\u002Fen\u002Fwoman-dresses-l1066.html, then:\n(() => {\n  const scripts = Array.from(document.querySelectorAll('script'));\n  \u002F\u002F JSON-LD path (H&M-style): cleanest\n  const ld = document.querySelector('script[type=\"application\u002Fld+json\"]');\n  if (ld && ld.textContent.includes('\"@type\":\"Product\"')) {\n    return JSON.parse(ld.textContent);\n  }\n  \u002F\u002F Raw-hydration path (Zara\u002FASOS): regex\n  const big = scripts.find(s => (s.textContent || '').includes('\u003Cbrand-cdn-hostname>'));\n  const text = big.textContent;\n  \u002F\u002F Adjust regex per brand URL shape\n  const urls = [...new Set((text.match(\u002Fhttps:\\\u002F\\\u002Fstatic\\.zara\\.net\\\u002F[^\"'\\s]+\\.jpg\u002Fg) || []))];\n  return urls;\n})();\n```\n\nThen get the result out of Chrome via a `Blob` download:\n\n```js\nconst blob = new Blob([JSON.stringify(catalog)], { type: 'application\u002Fjson' });\nconst a = Object.assign(document.createElement('a'), { href: URL.createObjectURL(blob), download: 'catalog.json' });\ndocument.body.appendChild(a); a.click();\n\u002F\u002F File lands in ~\u002FDownloads\u002Fcatalog.json — move to project, feed to cards.ts rewrite\n```\n\n**Hotlink don't download.** Once you have the URLs, put them directly in `cards.ts`'s `image` field — the browser will load them via `\u003Cimg src>` (no CORS issue on img tags). No local copy needed. Server-side curl typically fails with 403 \u002F 000 (WAF), but that doesn't matter because production serves from users' browsers.\n\n**For named products\u002Ffranchises** (Samba, Air Jordan 1, Stan Smith, Lady Dior, Birkin, etc.) where you need individual-product photos not a catalog:\n\n1. Brand's own CDN (works for most sportswear — Nike, adidas, Puma, Asics, New Balance)\n2. **Wikipedia \u002F Wikimedia Commons** — the category page `commons.wikimedia.org\u002Fwiki\u002FCategory:{Brand}_{Product}` has real, licensed product photos for every iconic sneaker, boot, bag, watch, perfume, etc.\n3. Industry publication CDN for the brand's segment (WWD for fashion, Fragrantica for perfume, SneakerNews\u002FHypebeast for sneakers)\n4. **DROP THE PRODUCT from `productItems`** if none of 1–3 yields a verified photo. A site with 6 real products is infinitely better than a site with 8 and two wrong-brand frauds.\n\n**Unsplash is BANNED for named-product slots.** It's OK only for: hero lifestyle shots (action\u002Fatmosphere, no named product), brand-agnostic category tiles, abstract backgrounds. If you use it, still run Step 2.3 verification — generic sneaker\u002Fbag photos on Unsplash very frequently show competitor logos.\n\nMost premium brand sites (Dior, Apple, Notion, Vercel, Hermès) AGGRESSIVELY BLOCK curl. Do NOT waste time trying to download from the brand's CDN. Skip directly to the fallback.\n\n**Sportswear CDNs are hit-or-miss** — Puma, Nike, Adidas, Asics, Under Armour, New Balance, Reebok sometimes serve real JPEGs on their public CDNs, but **you have to know the exact style code** and the match rate is worse than you'd expect. Observed on recent transforms:\n\n- **adidas** (`assets.adidas.com`) — returned 0 bytes on every style code tried (Apr 2026)\n- **Nike** (`static.nike.com`) — works for some products, requires inspecting a product page's `\u003Cimg srcset>` to get the right hash\n- **New Balance** (`nb.scene7.com`) — works with a Referer header, but style codes are hard to guess; ~50% hit rate even for the most popular models\n- **Puma** (`images.puma.com`) — most reliable of the sportswear CDNs\n\n**Rule of thumb**: try the brand CDN once with a single well-known SKU. If it returns real bytes (>20KB), map your remaining products; if it 0-bytes or errors, drop straight to Wikimedia Commons. Don't spend 10 minutes guessing style codes.\n\n| Brand | CDN pattern | How to get the `{styleId}` |\n|-------|-------------|----------------------------|\n| Puma | `https:\u002F\u002Fimages.puma.com\u002Fimage\u002Fupload\u002Ff_auto,q_auto,w_800,h_800\u002Fglobal\u002F{styleId}\u002F01\u002Fsv01\u002Ffnd\u002FPNA\u002Ffmt\u002Fpng\u002F{slug}` | The number after `\u002Fpd\u002Fslug\u002F` on a product page |\n| Nike | `https:\u002F\u002Fstatic.nike.com\u002Fa\u002Fimages\u002Ft_PDP_1280_v1\u002Ff_auto,q_auto:eco\u002F{hash}\u002F{slug}.jpg` | Inspect a product page's `\u003Cimg srcset>` |\n| Adidas | `https:\u002F\u002Fassets.adidas.com\u002Fimages\u002Fw_600,f_auto,q_auto\u002F{styleId}\u002F{slug}.jpg` | Often blocked — try once, fall back to Wikimedia |\n| New Balance | `https:\u002F\u002Fnb.scene7.com\u002Fis\u002Fimage\u002FNB\u002F{styleId}_nb_02_i?wid=1200&hei=1200` | Match the style id on the product page (e.g. `m1906rcd`) |\n\nAlways include `-H \"Referer: https:\u002F\u002F{brand-domain}\u002F\"` — the Cloudinary-style CDNs behind most sportswear brands accept the request with referrer, 404 it without.\n\n**Remember**: even when the CDN works, you still MUST run Step 2.3 visual verification on the downloaded bytes — CDNs occasionally return placeholder\u002Fblank images with a 200 status.\n\n**1. Brand's own CDN** (always try first for sportswear\u002Fathletic; ~30% of premium luxury sites; skip straight to #3 for most editorial\u002Fluxury brands)\n```bash\ncurl -sL -o public\u002Fimages\u002F{name}.jpg \"{url}\" \\\n  -H \"User-Agent: Mozilla\u002F5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit\u002F537.36\" \\\n  -H \"Referer: https:\u002F\u002F{domain}\u002F\"\n```\n\n**2. Wikipedia \u002F Wikimedia Commons** — works for famous brands, logos, iconic products\n```bash\ncurl -sL -o public\u002Fimages\u002Fbrand-logo.svg \\\n  \"https:\u002F\u002Fupload.wikimedia.org\u002Fwikipedia\u002Fcommons\u002F{path}\u002F{file}.svg\" \\\n  -H \"User-Agent: Mozilla\u002F5.0\"\n```\nUse WebSearch: \"{brand} logo SVG wikimedia commons\"\n\n**2.5. INDUSTRY PUBLICATIONS — USE THIS FOR FASHION BRANDS**\nFashion\u002Fluxury brands block their own CDN, but fashion PUBLICATIONS host real runway photos:\n\n```bash\n# WWD (Women's Wear Daily) — 2-3MB runway photos, works without auth\n# Pattern: https:\u002F\u002Fwwd.com\u002Fwp-content\u002Fuploads\u002F{YYYY}\u002F{MM}\u002F{brand}-{collection}-{location}-GG-{01-80}.jpg\n\ncurl -sL -o public\u002Fimages\u002Frunway.jpg \\\n  \"https:\u002F\u002Fwwd.com\u002Fwp-content\u002Fuploads\u002F2025\u002F05\u002Fdior-cruise-2026-rome-GG-01.jpg\" \\\n  -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Fragrantica CDN — real perfume bottle photos, works without auth\n# Pattern: https:\u002F\u002Ffimgs.net\u002Fmdimg\u002Fperfume\u002F375x500.{perfume_id}.jpg\n# Find IDs via WebSearch: \"{perfume name} fragrantica\"\n\ncurl -sL -o public\u002Fimages\u002Fjadore.jpg \\\n  \"https:\u002F\u002Ffimgs.net\u002Fmdimg\u002Fperfume\u002F375x500.210.jpg\" \\\n  -H \"User-Agent: Mozilla\u002F5.0\"\n```\n\nOther working fashion\u002Fbeauty publication CDNs:\n- **wwd.com\u002Fwp-content\u002Fuploads\u002F** — runway, backstage, beauty product shots\n- **fimgs.net\u002Fmdimg\u002Fperfume\u002F** — perfume bottles (Fragrantica)\n- **nowfashion.com\u002Fwp-content\u002Fuploads\u002F** — runway photos\n- **showstudio.com\u002F** — editorial fashion content\n- **vogue.com\u002Fphotos\u002F** — often requires auth\n- **fashionography.com\u002Fwp-content\u002Fuploads\u002F** — runway archives\n\n**IMPORTANT:** Sample a couple of images first (~2-3MB each). On macOS use `sips -Z 1200 input.jpg -o output.jpg` to resize before committing.\n\n### Brand Videos for Hero Backgrounds\n\nMany luxury brands have hero video loops that dramatically elevate the feel. Look for them:\n\n```bash\n# Brand-hosted videos often work with proper headers\ncurl -sL -o public\u002Fvideos\u002Fhero.webm \"{brand-video-url}\" \\\n  -H \"User-Agent: Mozilla\u002F5.0\" \\\n  -H \"Referer: https:\u002F\u002F{domain}\u002F\"\n```\n\n**Finding brand video URLs:**\n- Dior: `diorama.dam-broadcast.com\u002F...` — works publicly\n- Apple: `apple.com\u002Fassets-www\u002F...` — often public\n- Most fashion houses have `dam-broadcast` or `.cdn.` video CDNs\n- Inspect the brand's homepage for `\u003Cvideo>` or `\u003Csource>` tags with `.webm` \u002F `.mp4`\n- WebSearch: \"{brand} hero video webm\" or check Dam broadcast networks\n\n**Implementation in hero-section.tsx:**\n```tsx\n\u003Cvideo autoPlay loop muted playsInline className=\"absolute inset-0 w-full h-full object-cover\" poster=\"\u002Fimages\u002Fhero-image.jpg\">\n  \u003Csource src=\"\u002Fvideos\u002Fhero.webm\" type=\"video\u002Fwebm\" \u002F>\n\u003C\u002Fvideo>\n\u003Cdiv className=\"absolute inset-0 bg-gradient-to-b from-black\u002F10 via-transparent to-black\u002F70\" \u002F>\n```\n\nVideo hero is essential for luxury brands. Fall back to static image if video can't be obtained. Keep videos under 10MB (resize with ffmpeg if needed).\n\n**American heritage brands (Ralph Lauren, Levi's, L.L. Bean, J.Crew, Tommy Hilfiger) rarely expose public video CDNs.** Plan for a static full-bleed runway or editorial hero with a subtle 1.04 scale-on-mount or parallax effect instead — don't waste time hunting for a video that isn't there.\n\n**3. Unsplash (MANDATORY FALLBACK — always works, real product photos)**\n```bash\n# Search URL pattern: https:\u002F\u002Fimages.unsplash.com\u002Fphoto-{id}?w=800&q=80\n# DO NOT make up IDs — use these tested working IDs by category:\n\n# Luxury perfume \u002F fragrance bottle\ncurl -sL -o public\u002Fimages\u002Fperfume.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1541643600914-78b084683601?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Men's cologne \u002F dark bottle  \ncurl -sL -o public\u002Fimages\u002Fcologne.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1594035910387-fea47794261f?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Pink\u002Ffeminine perfume\ncurl -sL -o public\u002Fimages\u002Fmiss.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1592945403244-b3fbafd7f539?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Luxury handbag\ncurl -sL -o public\u002Fimages\u002Fbag.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1584917865442-de89df76afd3?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Canvas tote\ncurl -sL -o public\u002Fimages\u002Ftote.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1590874103328-eac38a683ce7?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Leather bag\ncurl -sL -o public\u002Fimages\u002Fleather-bag.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1548036328-c9fa89d128fa?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Red lipstick\ncurl -sL -o public\u002Fimages\u002Flipstick.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1586495777744-4413f21062fa?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Foundation \u002F makeup\ncurl -sL -o public\u002Fimages\u002Ffoundation.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1512496015851-a90fb38ba796?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Skincare cream\ncurl -sL -o public\u002Fimages\u002Fskincare.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1556228720-195a672e8a03?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Luxury skincare bottles\ncurl -sL -o public\u002Fimages\u002Fserum.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1608248543803-ba4f8c70ae0b?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Gold jewelry \u002F rings\ncurl -sL -o public\u002Fimages\u002Fjewelry.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1515562141207-7a88fb7ce338?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Fashion \u002F clothing\ncurl -sL -o public\u002Fimages\u002Ffashion.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1558769132-cb1aea458c5e?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Building \u002F atelier (hero\u002Fabout)\ncurl -sL -o public\u002Fimages\u002Fbuilding.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1519643225200-94e79e383724?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# SaaS \u002F tech product screenshot\ncurl -sL -o public\u002Fimages\u002Fsaas-ui.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1551288049-bebda4e38f71?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Abstract tech \u002F code\ncurl -sL -o public\u002Fimages\u002Ftech.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1518770660439-4636190af475?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# ═══════ ATHLETIC \u002F SPORTSWEAR (verified on Puma transform) ═══════\n\n# Running \u002F runner silhouette\ncurl -sL -o public\u002Fimages\u002Frunning.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1508685096489-7aacd43bd3b1?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Training \u002F gym \u002F lifting\ncurl -sL -o public\u002Fimages\u002Ftraining.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1517836357463-d25dfeac3438?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Football \u002F soccer\ncurl -sL -o public\u002Fimages\u002Ffootball.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1431324155629-1a6deb1dec8d?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Motorsport \u002F racing\ncurl -sL -o public\u002Fimages\u002Fmotorsport.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1504276048855-f3d60e69632f?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Kids athletic\ncurl -sL -o public\u002Fimages\u002Fkids.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1503944583220-79d8926ad5e2?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n\n# Athletic fashion \u002F streetwear runner\ncurl -sL -o public\u002Fimages\u002Fathleisure.jpg \"https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1558769132-cb1aea458c5e?w=800&q=80\" -H \"User-Agent: Mozilla\u002F5.0\"\n```\n\n> **Unsplash ID format caveat:** stick to the timestamp-hex pattern (`photo-1508685096489-7aacd43bd3b1`). Modern Unsplash URLs use slug-style IDs (`hEIHXXic3yI`) that **do NOT work** with `https:\u002F\u002Fimages.unsplash.com\u002Fphoto-{slug}`. If an ID you find is 11 random characters instead of the classic timestamp-hex form, you need the old numeric pattern or the image will 404.\n\n**Verify downloads:** Check file size with `ls -la`. Files under 1KB are failures. Failed downloads return ~29 bytes (Unsplash not-found) or ~300 bytes (error page). Re-download with different ID if under 1KB.\n\n**4. Placehold.co** — LAST RESORT ONLY if Unsplash also fails\n```bash\ncurl -sL -o public\u002Fimages\u002F{name}.jpg \"https:\u002F\u002Fplacehold.co\u002F800x400\u002F{hex_no_hash}\u002Fwhite?text={Product}\"\n```\n\n### Required Downloads\n\nEvery project MUST have (minimum):\n- Logo (SVG from Wikipedia or brand CDN)\n- Hero image (brand or category-matched Unsplash)\n- 1 image per solution (category-matched Unsplash)\n- 1 image per product (category-matched Unsplash)\n- Favicon from `https:\u002F\u002Fwww.google.com\u002Fs2\u002Ffavicons?domain={domain}&sz=64`\n\n### Catalog size — minimum item count per brand type (REQUIRED)\n\nA thin catalog kills the demo. Every e-commerce, retail, or fashion brand transform MUST ship at least **100 real product items** spread across the brand's natural segments. The agent needs enough depth to recommend and compare realistically; an 8-item catalog makes every filter \u002F category \u002F chat prompt dead-end immediately.\n\n| Brand type | Minimum items | Split guidance |\n|------------|---------------|----------------|\n| Fashion mono-brand (Zara, H&M, Uniqlo, Ralph Lauren, Dior RTW) | **100+** | 40 Woman \u002F 30 Man \u002F 15 Kids \u002F 10 Accessories \u002F 5 Home — adjust to brand reality |\n| Fashion multi-brand retailer (Nordstrom, Net-A-Porter, Farfetch, Zalando) | **150+** | 50 Woman \u002F 40 Man \u002F 25 Kids \u002F 20 Shoes \u002F 15 Bags — plus 20+ brand catalogue entries |\n| Beauty multi-brand retailer (Sephora, Ulta, LookFantastic) | **120+** | 30 Skincare \u002F 30 Makeup \u002F 25 Fragrance \u002F 15 Hair \u002F 10 Body \u002F 10 Men — plus 20+ brands |\n| Beauty mono-brand (L'Oréal, Estée Lauder, MAC) | **80+** | 25 Skincare \u002F 25 Makeup \u002F 15 Fragrance \u002F 10 Hair \u002F 5 Men |\n| Outerwear \u002F Technical (Canada Goose, Arc'teryx, Patagonia) | **60+** | 25 Men \u002F 20 Women \u002F 10 Kids \u002F 5 Accessories — fewer items OK because parkas are expensive\u002Fcurated |\n| Luxury mono-brand (Hermès, Chanel — no RTW catalog online) | **50+** | Scale to what's published; bags + fragrance + leather small goods heavy |\n| Sportswear (Nike, Puma, Adidas, Under Armour) | **100+** | 30 Men \u002F 30 Women \u002F 20 Kids \u002F 15 Footwear \u002F 5 Accessories |\n| Marketplace listings (Airbnb, Booking) | **100+ stays × 40+ destinations** | destinations.ts covers the cities, cards.ts covers the stays |\n| Marketplace C2C (Vinted, Depop, Etsy) | **80+ feature tiles + category mock listings** | cards.ts holds features\u002Fflows, not individual listings |\n| Fintech \u002F SaaS | 6-12 products is fine | Few products is brand-accurate (Visa has ~8 tiers, Stripe has ~10 products) |\n\n**How to reach 100+ on an e-commerce transform:**\n1. Start by listing the brand's real product segments (Woman\u002FMan\u002FKids\u002FHome\u002FBeauty for Zara; Skincare\u002FMakeup\u002FFragrance for Sephora). Write the minimum count per segment before downloading images.\n2. Scrape representative products from the brand's own site when possible, even if names are paraphrased — the image + name + price + material gives the agent enough to recommend.\n3. When the brand CDN blocks (Zara, Dior, etc.), fall through to Unsplash with segment-matched searches. Each segment needs 30+ unique photos; guard against duplicates.\n4. Every product entry in `cards.ts` MUST be a real-looking record with: name + price + segment (gender\u002Fcategory) + material\u002Fsize + badge. Agent recommendations against a half-populated catalog feel hollow.\n\n**Per-section rendering rule (NEW, critical — addresses \"there's not a lot of items on Men's\" feedback):**\n\nThe catalog-size rule above covers `cards.ts` data depth. The **rendering cap** is a separate trap: template components often render `homes.slice(0, 12)` or similar, so even with 100+ items in data, the user sees a thin 8-tile grid.\n\n- **Homepage carousel rows**: 12-16 tiles OK (carousel UX, user scrolls horizontally).\n- **Category \u002F gender inner pages** (when user clicks \"Men's\" or \"Woman\" from nav or a tile): **MUST render the full filtered catalog, no slice cap.** If the brand has 30 Men's items, the Men's page shows 30, not 12. Minimum per-section display:\n  - Woman \u002F Man: 30+ tiles visible on the inner page\n  - Kids \u002F Baby: 15+ tiles\n  - Accessories \u002F Home \u002F Beauty: 10+ tiles\n- **Fix pattern**: in `inner-page.tsx` (or equivalent), the category grid must `productItems.filter(p => p.issuer === gender)` without a trailing `.slice()`. If the page feels too long, use pagination \u002F \"Load more\" — not a silent truncation.\n- Grep check before shipping: `grep -rnE '\\.slice\\(0,\\s*(6|8|12)' src\u002Fcomponents\u002Finner-page.tsx src\u002Fcomponents\u002Fhero-section.tsx src\u002Fapp\u002Fpage.tsx` — if caps are present on gender\u002Fcategory paths, they're bugs.\n\n**Quality gate (add to Phase 4 verification):**\n- `curl https:\u002F\u002Fwwa.{slug}.codiris.app\u002Fmcp -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Fcall\",\"params\":{\"name\":\"search_products\",\"arguments\":{}}}'` → `count: 100+` for any e-commerce brand type.\n- Curl the rendered HTML of the Men's \u002F Woman's category pages and count `\u003Cimg` tags for product tiles. Must be 30+ each (for mono-brand fashion) or 40+ (for multi-brand fashion). If below threshold, UI has a rendering cap that needs removal — the transform is incomplete.\n\n**Post-deploy smoke check (catches stale-alias bugs):** after `vercel alias set`, always re-verify that the alias points to the LATEST deploy. A common failure mode: you fix the code locally, run `npx vercel --prod`, but forget to re-alias — so `wwa.{slug}.codiris.app` continues pointing to the previous (broken) deploy. The Zara\u002FUniqlo\u002FH&M\u002FASOS retrofit pass uncovered 4 stale aliases where the uncap code was already correct in git but not reflected live. Always run:\n\n```bash\nnpx vercel --prod --yes 2>&1 | tee \u002Ftmp\u002Fdeploy.log\nDEPLOY_URL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.vercel\\.app' \u002Ftmp\u002Fdeploy.log | head -1)\nnpx vercel alias set \"$DEPLOY_URL\" wwa.{slug}.codiris.app\n# Then verify:\ncurl -s https:\u002F\u002Fwwa.{slug}.codiris.app\u002F | grep -c 'aspect-\\[3\u002F4\\]\\|aspect-\\[4\u002F5\\]\\|aspect-square'  # rough product-tile count\n```\n\n**MANDATORY: push API keys from a sibling project before declaring \"deployed\" (catches silent-AI-fallback bug):** every brand-new Vercel project starts with **zero env vars**. Without `GEMINI_API_KEY` \u002F `GOOGLE_GENERATIVE_AI_API_KEY` \u002F `OPENAI_API_KEY`, the AI panel silently falls back to canned `assistant-shared.tsx` strings (\"I can help you find...\"), and the user thinks the AI is dumb. Caught on the Joivy deploy after the user complained the AI was \"stupid\". The 200-response on `\u002Fapi\u002Fgemini-key` is the actual smoke check — until that endpoint returns a real key, the demo is broken even if every page renders correctly.\n\n```bash\n# Pull keys from any sibling project that already has them (wwa-vinted is reliable)\nmkdir -p \u002Ftmp\u002Fsibling-env && cd \u002Ftmp\u002Fsibling-env && mkdir -p .vercel\ncat > .vercel\u002Fproject.json \u003C\u003C 'EOF'\n{\"projectId\":\"prj_eoF8zwRk4i3blOS7Cy95N9Zn5I1s\",\"orgId\":\"team_CVjPPr2WoqlNcN6zmRDjk04Q\",\"projectName\":\"wwa-vinted\"}\nEOF\nnpx vercel env pull .env.production --environment=production --yes\n\n# Push to the new project via Vercel API\nTOKEN=$(python3 -c \"import json; print(json.load(open('\u002FUsers\u002Fjoel\u002FLibrary\u002FApplication Support\u002Fcom.vercel.cli\u002Fauth.json')).get('token',''))\")\nTEAM=\"team_CVjPPr2WoqlNcN6zmRDjk04Q\"\nPID=$(cat \u002Ftmp\u002Fwwa.{slug}\u002F.vercel\u002Fproject.json | python3 -c \"import sys,json; print(json.load(sys.stdin)['projectId'])\")\nfor k in GEMINI_API_KEY GOOGLE_GENERATIVE_AI_API_KEY OPENAI_API_KEY; do\n  v=$(grep \"^${k}=\" \u002Ftmp\u002Fsibling-env\u002F.env.production | head -1 | cut -d= -f2- | sed 's\u002F^\"\u002F\u002F;s\u002F\"$\u002F\u002F')\n  curl -s -X POST \"https:\u002F\u002Fapi.vercel.com\u002Fv10\u002Fprojects\u002F$PID\u002Fenv?teamId=$TEAM\" \\\n    -H \"Authorization: Bearer $TOKEN\" -H \"Content-Type: application\u002Fjson\" \\\n    -d \"$(python3 -c \"import json,sys; print(json.dumps({'key':'$k','value':'$v','type':'encrypted','target':['production','preview','development']}))\")\"\ndone\n\n# REDEPLOY + RE-ALIAS so the new envs take effect (env changes don't apply to existing builds)\ncd \u002Ftmp\u002Fwwa.{slug} && npx vercel --prod --yes\n# Then alias the new deploy.\n\n# Smoke check — this is the line that proves the AI works:\ncurl -s -X POST https:\u002F\u002Fwwa.{slug}.codiris.app\u002Fapi\u002Fgemini-key -H \"Content-Type: application\u002Fjson\" -w \"\\n%{http_code}\\n\"\n# Must return {\"key\":\"AIza...\"} and HTTP 200. Anything else = AI is silently degraded.\n```\n\n### Matching Unsplash Photos to Categories\n\n| Company Type | Use These Photos |\n|--------------|-----------------|\n| Luxury\u002FFashion (Dior, Hermès, LV) | Perfume + handbag + lipstick + jewelry + fashion |\n| Cosmetics (Sephora, Fenty) | Lipstick + foundation + makeup brushes |\n| Tech\u002FSaaS (Stripe, Notion) | SaaS UI screenshots + tech + abstract |\n| E-commerce (Amazon, Shopify) | Product shots + packaging + shopping |\n| Fintech (Visa, Chase) | Cards + phone + wallet |\n\n### Step 2.2: Download Favicon\n\n```bash\ncurl -L -o \"public\u002Ffavicon.ico\" \"https:\u002F\u002Fwww.google.com\u002Fs2\u002Ffavicons?domain={domain}&sz=64\"\n```\n\n### Step 2.3: Visual verification — MANDATORY before writing any image path into `cards.ts` \u002F `solutions.ts`\n\nYou are a multimodal model. You can see images. **Use the `Read` tool on every downloaded file** and visually inspect what it actually depicts. Do this BEFORE referencing the image from any data file.\n\n```\nRead file_path=\u002Fabsolute\u002Fpath\u002Fto\u002Fpublic\u002Fimages\u002Fsamba.jpg\n```\n\nFor each image, verify the following before approving it:\n\n1. **Brand match.** If the image represents a named product, does it show the correct brand's logo, wordmark, or trademark graphic?\n   - Nike → Swoosh visible and no other brand logos\n   - adidas → 3-Stripes and\u002For Trefoil visible, no Swoosh, no \"N\", no Brooks, no Puma cat\n   - Dior → \"Dior\" wordmark or CD monogram\n   - Hermès → \"H\" clasp or Kelly\u002FBirkin silhouette with Hermès marking\n   - Apple → Apple logo, no Samsung\u002FGoogle\u002Fother\n2. **Product match.** If the image is tied to a specific franchise in `solutions.ts` (e.g. \"Air Max\"), does the shoe in the photo actually look like an Air Max (visible Air unit) vs. a random sneaker?\n3. **No competitor logos.** If you can see **any** competitor's logo anywhere in the frame (even on a background wall, a bystander's shirt, the box the product is sitting on), reject the image.\n4. **No off-brand props.** A Nike shoebox in the corner of an adidas product shot → reject.\n\n**If verification fails**, in order:\n\n1. Retry with a different source from the priority list (Wikimedia Commons almost always has a clean product shot).\n2. If still no luck, **remove that product from `productItems` \u002F that franchise from `solutions`** rather than ship the bad image.\n3. NEVER \"just swap the filename\" and hope — the file on disk is what ships.\n\n**Checklist to run at the end of Phase 2:**\n\n```bash\n# List every image file with its size\nls -la public\u002Fimages\u002F*.jpg public\u002Fimages\u002F*.png public\u002Fimages\u002F*.svg 2>\u002Fdev\u002Fnull\n```\n\nThen, for EACH non-logo image, use `Read` on it and log either `VERIFIED: shows real \u003Cbrand> \u003Cproduct>` or `REJECTED: shows \u003Cwhat-it-actually-is>`. If any rejected image is still referenced from `cards.ts` \u002F `solutions.ts`, **you have failed this step** — fix it before proceeding to Phase 3.\n\n**For sizing**: if an image is ≥ 3MB, resize on macOS with `sips -Z 1200 input.jpg -o output.jpg` or `sips -Z 1200 --setProperty formatOptions 80 input.jpg -o output.jpg` to keep page weight reasonable.\n\n---\n\n## PHASE 3: Build the Project\n\n### Step 3.1: Copy Framework\n\n```bash\n# From inside the cloned skill (typically ~\u002F.claude\u002Fskills\u002Fagentizer):\nmkdir -p ~\u002Fwwa.{domain}\ncp -R .\u002Ftemplate\u002F. ~\u002Fwwa.{domain}\u002F\ncd ~\u002Fwwa.{domain} && npm install\n```\n\nDo NOT copy from absolute maintainer paths like `\u002FUsers\u002Fjoel\u002Fwwa-skill\u002Ftemplate\u002F` — that path only exists on the maintainer's machine. Always copy `.\u002Ftemplate\u002F.` relative to the skill directory that contains this SKILL.md.\n\n**Template naming:** The template uses `ProductItem`\u002F`productItems` (not VisaCard\u002FvisaCards) as generic names for browsable items. The navbar component is `brand-navbar.tsx`, the map is `world-map.tsx`. All imports in page.tsx already use these names.\n\n### Step 3.1b: Sweep Visa color tokens (MANDATORY, run once, before everything else)\n\nThe template ships with Visa's blue (`#1A1F71`), navy hover (`#141963`), and light blue (`#1434CB`) hardcoded in ~8 components — `solution-detail-panel.tsx`, `solution-slider.tsx`, `generated-view.tsx`, `agent-panel.tsx`, `account-panel.tsx`, `live-session-overlay.tsx`, and others. **Delegating component rewrites to parallel subagents always leaves some of these files unedited**, and the Step 3.6 audit catches it every time. Save yourself the re-roll — run this sweep FIRST, right after `cp -R .\u002Ftemplate\u002F.`:\n\n```bash\ncd ~\u002Fwwa.{domain}\n\n# Replace Visa blue (primary), navy (hover), and light blue (accent) with brand colors.\n# Pick hex codes that match your brand-config.ts primary\u002Fsecondary\u002Faccent.\nfind src -name \"*.tsx\" -o -name \"*.ts\" | xargs sed -i '' \\\n  -e 's\u002F#1A1F71\u002F{BRAND_PRIMARY}\u002Fg' \\\n  -e 's\u002F#141963\u002F{BRAND_PRIMARY_DARK}\u002Fg' \\\n  -e 's\u002F#1434CB\u002F{BRAND_ACCENT}\u002Fg'\n\n# Verify zero remaining\ngrep -rn \"#1A1F71\\|#141963\\|#1434CB\" src\u002F\n```\n\nExample for a black-primary brand: replace with `#000000`, `#000000`, `#CF0A2C`. For Dior (gold on black): `#0A0A0A`, `#000000`, `#C9A96E`.\n\nAfter the sweep, subagents can focus on rewriting content (copy, data) without worrying about color hunts. Re-run the grep at the end of Phase 3 to confirm nothing crept back in.\n\n### Step 3.2: Write Brand Config\n\nWrite `src\u002Flib\u002Fbrand-config.ts` with ALL company data from Phase 1. This drives the entire app.\n\n### Step 3.3: Write Solutions Data\n\nWrite `src\u002Flib\u002Fsolutions.ts` — these are the company's ACTUAL products\u002Fservices. Each must have:\n- Real name, real description from their website\n- Real features from their product pages\n- Image pointing to downloaded file\n- Appropriate category for THIS company (not Visa's categories)\n\n### Step 3.4: Write Products\u002FCards Data (ONLY IF APPLICABLE)\n\nWrite `src\u002Flib\u002Fcards.ts` — ONLY if the company sells browsable items (plans, cards, products with prices).\n\n**For API companies (Stripe, Twilio):** Use pricing tiers as \"cards\" — Free, Growth, Enterprise\n**For e-commerce (Nike, Apple):** Use actual products as cards\n**For SaaS (Salesforce, HubSpot):** Use subscription plans as cards\n**For companies with no browsable products:** Leave the array EMPTY and the browse section won't show\n\n### Step 3.5: Rewrite EVERY Content Component\n\n**CRITICAL: Do not sed-replace. REWRITE each file understanding the company.**\n\n**`src\u002Fcomponents\u002Fhero-section.tsx`** — Rewrite completely:\n- Stats must be THIS company's real stats\n- \"Card Tiers\" section: REMOVE if company doesn't have tiers. Replace with what makes sense (e.g., \"Choose your plan\", \"Explore by use case\", customer logos grid)\n- \"Why {Brand}\" section: Write real value props from their website, not Visa's\n- \"Find your card\" CTA: Change to whatever CTA makes sense (\"Start Building\", \"Get Started\", \"Shop Now\", \"Request Demo\")\n- Hero images should use downloaded images\n\n**`src\u002Fcomponents\u002Finner-page.tsx`** — Rewrite ALL pages:\n- Navigation pages must match THIS company's nav (from brand-config)\n- Each page content must be written from crawled data\n- Remove any pages that don't apply (Stripe doesn't need \"Travel\" or \"Personal\")\n- Add pages that DO apply (Stripe needs \"Developers\", \"Pricing\")\n\n**`src\u002Fcomponents\u002Fwwa-panel.tsx`** — Update:\n- SUGGESTIONS array: Write 6-8 suggestions relevant to THIS company\n- Card\u002Fsolution detection keywords: Based on THIS company's product names\n- Chat tab label: \"{Brand} Agent\"\n- Category labels in browse section\n\n**`src\u002Fcomponents\u002Fassistant-shared.tsx`** — Rewrite ALL fallback responses:\n- Every response must be about THIS company's products\n- Use real product names, real features, real pricing\n- Reference actual pages\u002Fdocs from their website\n\n**`src\u002Fapp\u002Factions.ts`** — **Always a full rewrite, regardless of peer clone.** Both the chat `SYSTEM_PROMPT` and the `CODE_GEN_PROMPT` bake brand knowledge in deep (named buildings, founding years, signature products, ambassadors, specific exhibition venues) that a simple `grep \"ralph\\|polo\"` misses. Example: a Ralph Lauren → Zara peer clone caught the obvious brand names but left phrases like \"Rhinelander Mansion\", \"1978 fragrance launches\", \"Jack Shainman Gallery\" in the system prompt — these shipped silently until end-to-end prompt re-read. Re-read this file line-by-line after any peer clone.\n- Identity: \"{Brand} Agent\" specialist in their actual domain\n- Product knowledge from crawled data\n- Stats from their actual numbers\n- Zero references to any prior brand's specific places, years, products, people, or institutions — these don't grep cleanly\n\n**`src\u002Fapp\u002Fpage.tsx`** — Update:\n- Category grid: Use THIS company's actual categories (not Travel\u002FCash Back\u002FBusiness)\n- Section titles and descriptions\n- Remove any sections that don't apply\n\n**`src\u002Fcomponents\u002Fbook-demo-modal.tsx`** — Update:\n- Product interests: THIS company's actual products\n- Company types relevant to their market\n- Form copy\n\nFor **luxury e-commerce \u002F heritage brands**, rewrite the whole modal as \"Request a Private Appointment\" with three fields — the B2B fields (company size, revenue range, country dropdown, SKU picker) are inappropriate. Keep it short:\n- Name + email\n- Preferred boutique (dropdown of real flagships from brand-config \u002F flagships.ts)\n- Occasion + interests (free text — \"wedding gift\", \"wardrobe refresh\", \"home\", etc.)\nSubmit CTA: \"Request Appointment\" — not \"Book a Demo\".\n\n**`src\u002Fcomponents\u002Flive-session-overlay.tsx`** — CRITICAL:\n- Replace the SVG logo paths (appears 2 times: header + animated center) with the brand's logo\n- Update the viewBox to match the brand's SVG\n- The voice call should show the BRAND logo, not any other brand\n\n**`src\u002Fcomponents\u002Fassistant-shared.tsx`** — CRITICAL:\n- The `EmptyState` component shows welcome screen with brand logo\n- The logo IS the call button — clicking it starts the voice call. NO separate \"Start Voice Call\" text button\n- Pattern: `\u003Cbutton onClick={onOpen}>\u003Cimg src=\"\u002Fimages\u002Fbrand-logo.svg\" \u002F>\u003C\u002Fbutton>`\n- Must use brand's logo image file (not inline SVG — renders badly)\n\n**`src\u002Fcomponents\u002Fagent-panel.tsx`** — CRITICAL (often forgotten):\n- Rename ALL skill names: \"visa-search\" → \"{brand}-search\", etc.\n- Rename CLI commands: \"visa-agent\" → \"{brand}-agent\"\n- Rename MCP package: \"visa-agent-mcp\" → \"{brand}-agent-mcp\"\n- Update AgentNet command: \"agentnet add {brand}-agent\"\n- Update skill descriptions to match brand's products\n- Update CLI example commands to be relevant to brand\n- MCP URL and Claude Code\u002FCodex install commands read from `BRAND.mcpUrl` + `BRAND.mcpServerName` automatically — no string edits needed here as long as brand-config is correct.\n\n**`src\u002Fapp\u002Fmcp\u002Froute.ts`** — REAL MCP ENDPOINT (ships with template):\n- The template serves a working MCP Streamable HTTP endpoint at `\u002Fmcp` on the same origin as the agentfront. JSON-RPC 2.0, stateless, CORS-enabled.\n- Default tools read from `productItems` (cards.ts) and `solutions` (solutions.ts): `search_products`, `compare_products`, `get_product`, `get_solutions`, `recommend_product`.\n- The `mcpTools` list shown in agent-panel.tsx is already synced with these 5 default tools.\n- To add brand-specific tools (e.g. `find_boutique` for luxury, `compare_tiers` for financial, `estimate_fees` for SaaS): append to the `TOOLS` array and add a `case` in `callTool`. Mirror the addition in agent-panel's `mcpTools` list.\n- **Brand-config keys to set:**\n  - `mcpUrl`: `\"https:\u002F\u002Fwwa.{brand}.codiris.app\u002Fmcp\"` (same origin as deployed agentfront)\n  - `mcpServerName`: `\"{brand}-agent\"` (CLI identifier for `claude mcp add`)\n- **Verify after deploy:** `curl -X POST https:\u002F\u002Fwwa.{brand}.codiris.app\u002Fmcp -H \"Content-Type: application\u002Fjson\" -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Flist\"}'` — must return the tool list with 200.\n- **Recommended brand-specific tools by type** (append to `TOOLS` in route.ts and to `mcpTools` in agent-panel.tsx):\n  - Heritage brand (Ralph Lauren, Rolex, Hermès, Patek Philippe): `get_heritage(yearFrom?, yearTo?)` from `src\u002Flib\u002Fheritage.ts`, `find_flagship(city?, country?)` from `src\u002Flib\u002Fflagships.ts`\n  - Multi-house luxury group (Dior, Chanel, Armani): `get_houses()`, `get_house(id)`\n  - Restaurant \u002F hospitality arm (Ralph Lauren Polo Bar, Bulgari hotels, Armani Caffè): `find_restaurant(city?)`\n  - SaaS with usage pricing (Stripe, Twilio): `estimate_cost(usage)`, `check_availability(region)`\n  - Fintech with tiered benefits (Visa, Mastercard, Amex): `compare_tiers(tiers[])`\n  - Luxury fragrance house: `get_fragrance_notes(productId)`, `find_boutique(city?)`\n  - Marketplace \u002F C2C (Vinted, Depop, Etsy, eBay): `list_markets(region?)`, `list_categories()`, `get_seller_flow(personal|pro)`, `estimate_fees(price, category)` — sellers and buyers want different info from the same API, and marketplaces have operational data (markets live, fee structure) that doesn't fit search\u002Fcompare\u002Frecommend alone.\n  - Marketplace \u002F Listings (Booking, Airbnb, VRBO, Expedia, Agoda): `search_stays(destination?, checkIn?, checkOut?, guests?, category?, priceMax?)` returning mocked stay results with price\u002Fcurrency\u002Frating\u002FreviewCount (no need to hit real inventory APIs), `list_destinations(region?, country?)` backed by `src\u002Flib\u002Fdestinations.ts`, and optionally `get_host_flow()` for the host-onboarding path.\n  - Marketplace \u002F Rentals — Residential (Joivy, Spotahome, HousingAnywhere, Uniplaces): `search_rentals(city?, duration_months?, room_type?, max_rent?, available_from?)` — different param shape from `search_stays` (months not nights, single move-in date not check-in\u002Fcheck-out range, room type not category). `find_co_living(city?, age_range?)` translation tool. `book_viewing(propertyId, date)` for tour scheduling — no \"reserve\" semantics. `get_lease_terms(propertyId)` — minimum lease, deposit, notice period, utilities included. `list_destinations(country?)` backed by `destinations.ts`. Skip `search_stays` \u002F `find_experience` \u002F `find_boutique` — wrong domain.\n  - Marketplace \u002F Rentals — Flex (Habyt Flex, Cove, Sonder, Outsite, Mindspace Living, Selina Co-Live): `search_stays(city?, checkIn?, checkOut?, guests?, unitType?, maxRent?, minNights?)` — uses **check-in\u002Fcheck-out range** like Booking, NOT residential-style `duration_months`. Listings carry both per-night AND per-month prices (`nightlyRent` + `monthlyRent` fields). `find_flex_living(preference)` translation tool. `book_stay(propertyId, checkIn, checkOut, guests)` supports days OR months in one tool — NOT `book_viewing`. `get_lease_terms(propertyId)` repurposed for stay terms (free-cancellation window, min nights). `get_living_spaces(propertyId)` for amenities\u002Fcommon-area inventory (rooftop, café, gym, coworking). Skip `search_rentals` \u002F `find_co_living` \u002F `book_viewing` — those are residential-only, wrong domain.\n  - Retail \u002F Multi-brand (Sephora, Nordstrom, Net-A-Porter, Farfetch): `list_brands(category?, featuredOnly?)` backed by `src\u002Flib\u002Fbrands.ts`, `find_shade_match(undertone?, coverage?, finish?)` for beauty, `get_routine(skinType?, concern?, budget?)` for skincare, `get_fragrance_notes(productId)` backed by `src\u002Flib\u002Ffragrances.ts`. Extend `search_products` with a `brand?` arg — customers ask \"foundations from Rare Beauty under €50\" and the default signature doesn't support that.\n  - Outerwear \u002F Technical (Canada Goose, Arc'teryx, Moncler, The North Face, Patagonia): `check_warmth(temperature_c, activity)` — a **translation tool** (conditions → product); `compare_parkas(ids[])` extended for fill-power\u002Fweight\u002FTEI spec axes; `get_heritage(yearFrom?, yearTo?)` from `heritage.ts`; `find_store(city?, country?)` for flagships with `note` field carrying experiential-retail differentiator (\"Cold Room\", \"Pinnacle Room\", \"Worn Wear repair\"); `get_sustainability(productId?)` returning sourcing + materials detail. Extend `search_products` with `gender?` and `tei?` args.\n  - Fashion editorial-minimalist (Zara, COS, ARKET, & Other Stories, Massimo Dutti): `list_collections()` — parallel capsule sub-lines from `src\u002Flib\u002Fcollections.ts`; `find_fit(bodyShape?, occasion?, season?)` translation tool (sibling to `check_warmth`); `get_size_guide(category, gender)` returning EU\u002FUK\u002FUS matrices — **new MCP tool pattern** for any mass-fashion brand with real size charts. Skip for luxury (bespoke) and beauty (shades instead). Extend `search_products` with `gender?`, `collection?`, `material?`.\n  - Fashion mass-market pop (H&M, Uniqlo, Gap, Mango, Primark, Forever 21): same core tool set as editorial-minimalist, PLUS extend `search_products` with a **`tech?` arg** for proprietary material technologies (HEATTECH \u002F AIRism \u002F Supima \u002F Ultra Light Down \u002F BlockTech for Uniqlo; CONSCIOUS \u002F Recycled \u002F Organic Cotton for H&M). Critical because customers ask \"HEATTECH base layer for -10°C\" and the natural query needs the tech axis to resolve — don't overload `material` with it.\n  - Fashion marketplace online (ASOS, Shein, Nasty Gal, Boohoo): `list_brands(category?, featuredOnly?)` backed by `src\u002Flib\u002Fbrands.ts`; `list_collections()` for own-label sub-lines; `find_fit(bodyShape?, occasion?, season?, sizeRange?)` — extend with sizeRange for size-inclusive brands; `get_size_guide(category, gender, sizeRange?)` — per-range cut measurements (curve cut ≠ petite cut, not just number); **`check_delivery(postcode?, country?)`** — NEW translation tool for Premier\u002FPrime\u002FSaver eligibility (service-eligibility translator, sibling to `check_warmth`). Extend `search_products` with `brand?`, `gender?`, **`sizeRange?`** (`\"curve\" | \"petite\" | \"tall\" | \"maternity\" | \"standard\"`).\n  - **NEW TOOL CATEGORY — \"translation tools\"** (conditions → product): `check_warmth(temp, activity)` is the first. Other candidates across brand types: footwear `check_fit(usSize, width, foot-shape)`; skincare `check_compatibility(drug, pregnancy)`; luggage `check_airline_allowance(airline, class)`. These are neither `search` nor `recommend` nor `compare` — they translate external conditions into product filters. Document as a sibling to the three classic MCP verbs.\n\n**`src\u002Flib\u002Fbrand-config.ts`** — Logo:\n- Download logo via WebSearch: \"{brand} logo SVG wikipedia\" or \"{brand} press kit\"\n- Set `logoSvg: \"\"` and `logoImage: \"\u002Fimages\u002Fbrand-logo.svg\"`\n- ALWAYS prefer logo image file over inline SVG to avoid rendering issues\n\n**`src\u002Fcomponents\u002Fworld-map.tsx`** — Update stats or remove if not relevant\n\n**`src\u002Fcomponents\u002Fcard-3d.tsx`** — ONLY for credit card companies (Visa, Mastercard). \n- For ALL other companies: the template already uses product image cards instead of Card3D\n- The `cards-browse-panel.tsx` and `wwa-panel.tsx` CardCarousel show product images with name\u002Fprice overlay\n- Do NOT use Card3D for fashion, SaaS, e-commerce, or any non-card company — it renders a credit card with chip and magnetic stripe\n- The file contains hardcoded Visa SVG paths and a `1-800-VISA` customer-service phone. Even if the component is never rendered, the audit grep will still flag those strings. For non-card brands, either **delete `card-3d.tsx` entirely** or scrub the hardcoded Visa strings before running the audit.\n- **Specific residue check** — `template\u002Fsrc\u002Fcomponents\u002Fwwa-panel.tsx` line ~68 still renders `\u003CCard3D card={card} size=\"sm\" onClick={...} \u002F>` inside the `CardCarousel` component. Every non-card transform MUST replace that line with a photo tile (e.g. `\u003Cimg src={card.image} ...\u002F>` wrapped in a button). Confirmed on Airbnb sim — the template ships with this leak and it has to be edited in-place.\n\n**`src\u002Fcomponents\u002Fcards-browse-panel.tsx`** — PRODUCT DETAIL VIEW (non-credit-card companies):\n\nThe template has credit-card-specific labels throughout the detail view. You MUST rewrite ALL of these for non-card brands:\n\n| Credit-card term | E-commerce\u002FSaaS replacement |\n|------------------|----------------------------|\n| \"Back to Cards\" | \"Back to Products\" \u002F \"Back to Collection\" |\n| \"Issued by\" | \"From\" \u002F remove for brand-native products |\n| \"Annual fee:\" | \"Price:\" |\n| \"Card Tier\" | \"Collection\" \u002F \"Tier\" \u002F \"Plan\" |\n| \"Card Highlights\" | \"Product Highlights\" \u002F \"Features\" |\n| \"Card Details\" | \"Details\" \u002F \"Specifications\" |\n| \"REWARDS \u002F WELCOME BONUS \u002F APR\" | Remove entirely — not applicable |\n| \"Ready to apply?\" | \"Ready to shop?\" \u002F \"Ready to get started?\" |\n| \"Apply Now\" | \"Add to Bag\" \u002F \"Buy Now\" \u002F \"Subscribe\" |\n| \"Compare Other Cards\" | \"Explore Collection\" \u002F \"Continue Shopping\" |\n| \"Application Submitted!\" | \"Order Confirmed!\" \u002F \"Welcome!\" |\n| \"Quick application with instant decision\" | \"Complete your purchase\" \u002F \"Get started in seconds\" |\n| \"Browse More Cards\" | \"Continue Shopping\" \u002F \"Explore More\" |\n| \"Annual Income *\" | \"Shipping Notes\" \u002F remove |\n| \"credit history\" | Remove the credit check reference entirely |\n| `{annualFee}\u002Fyr` | `{price}` |\n| \"Secure Application\" | \"Secure Checkout\" |\n\nAlso: the detail view renders the product with a dark gradient background and centered 3D card — change to a white background with image on left + details on right for product-style layout.\n\n**`src\u002Fcomponents\u002Fhero-section.tsx`** — VISUAL STYLE BY BRAND TYPE:\n\nThe default template uses a SaaS\u002Ftech aesthetic (split layout, colored gradient tiles, tech-y feature grid). This is WRONG for luxury\u002Feditorial brands. Adapt per brand:\n\n**LUXURY \u002F EDITORIAL — FRENCH \u002F EUROPEAN (Dior, Hermès, Chanel, Gucci, Aesop):**\n- **Hero**: Full-bleed image or video, black\u002Fwhite overlay, centered text, serif heading, no split\n- **CTAs**: Square buttons (no rounded-full), white-on-image, \"Discover\" \u002F \"Shop the Collection\"\n- **Stats**: Minimal, no gradient background, serif numbers, uppercase labels with wide tracking\n- **Collections**: Large 2-col tiles with full product imagery, gradient overlay, serif headings\n- **Category grid**: Aspect 4:5 tiles with real product images as backgrounds (NOT colored gradients)\n- **Fonts**: Playfair Display \u002F Didot-style serif for all headings\n- **Typography**: `tracking-[0.3em]` on uppercase labels, `font-normal` (not bold) on headings\n- **Colors**: Black, white, cream, gold — no blue\u002Fpurple accents\n- **Motion**: Slow, gentle (1-2s transitions), long fade-ins\n\n**FASHION — EDITORIAL MINIMALIST (Zara, COS, ARKET, & Other Stories, Massimo Dutti):**\n\nMono-brand mono-color fashion with rapid-turn seasonal drops, no heritage narrative, maximal typography contrast. The pure-B&W editorial-gallery aesthetic. Distinct from its mass-market cousin (H&M \u002F Uniqlo \u002F Gap \u002F Mango) which uses color-friendly pop aesthetics.\n\n- **Palette**: **pure black + pure white, NO accent color**. This is the signature — monochrome is the brand. Don't use the Visa-navy \u002F Sephora-red \u002F any-color pattern; resist the instinct to add an accent. Zara's brand voice IS the restraint.\n- **Typography**: **condensed elongated display serif** for headlines (free equivalents: `Big Shoulders Display`, `Oswald`, `Abril Fatface` — pick the one that matches the brand's wordmark shape). Inter or Helvetica for body. The *contrast* between massive display headlines and tiny body copy is the brand signature — don't temper it.\n- **Hero**: oversized display text (4-8 rem+) over a **single** full-bleed editorial photo. NOT a carousel (RL\u002FDior pattern), NOT a search form (marketplace), NOT a split (SaaS). One big photo, scroll for the next editorial block. Massive negative space between sections.\n- **Buttons**: sharp-cornered (border-radius 0), uppercase wide-tracking tiny text, black-on-white or white-on-black only. The button text reads `ADD` or `SHOP NOW →` — never more.\n- **Navigation**: pure text, tiny size, pure black. The navbar is lean — Woman \u002F Man \u002F Kids \u002F Home \u002F Beauty \u002F Join Life or similar brand-specific top facets. No icons, no dropdowns.\n- **Product grid**: large rectangular tiles, no pills, no \"guest favorite\" badges, no discount flags during a normal season. Just photo + product name + price.\n- **Product detail view** — DISTINCT from all other sub-types:\n  - Huge display-serif product name (not bold sans, not Didot — the condensed elongated serif)\n  - Price: small but bold, under the name. No strikethrough unless genuinely on sale.\n  - **Size picker = single `\u003Cselect>` dropdown**, not a grid (Zara does this deliberately — minimalism)\n  - Color chips: small circles, inline\n  - **Single \"ADD\" button**, no \"Wishlist\", no \"Request consultation\" — just ADD\n  - Body-copy paragraph (not an accordion) with material + care text\n  - \"YOU MAY ALSO LIKE\" row at bottom\n  - No trust badges, no reviews, no \"Recommended for you\" personalization chrome\n- **Animations**: restrained — quick fades only. NO scale-on-hover, NO slide-ins. The minimalism applies to motion too.\n- **Collection sub-lines**: most editorial-fast-fashion brands run 4-8 parallel sub-capsules (Zara's Main\u002FStudio\u002FSRPLS\u002FOrigins\u002FTRF\u002FLimited Edition\u002FAthleticz\u002FJoin Life; Uniqlo's Main\u002FU\u002FC\u002FJ; H&M's Main\u002FStudio\u002FHome\u002FConscious). Add `src\u002Flib\u002Fcollections.ts` + a `list_collections()` MCP tool — these don't map onto gender\u002Fcategory axes.\n- **MCP tools** specific to editorial-minimalist fashion:\n  - `list_collections()` — parallel capsule sub-lines from `collections.ts`\n  - `find_fit(bodyShape?, occasion?, season?)` — translation tool (sibling to Canada Goose's `check_warmth`; conditions → curated picks)\n  - `get_size_guide(category, gender)` — EU\u002FUK\u002FUS size matrix with measurements. This is a **new MCP tool pattern** for any mass-fashion brand with real size charts (Zara, Uniqlo, H&M, Gap, ASOS). Luxury brands skip it (bespoke); beauty retailers skip it (shades instead).\n  - `find_store(city?, country?)` — flagship physical presence\n\n**FASHION — MASS-MARKET POP (H&M, Uniqlo, Gap, Mango, Primark, Forever 21):**\n\nCousin to editorial-minimalist but color-friendly and accessible. Distinguished from Zara\u002FCOS\u002FARKET by: bold brand accent color (H&M red, Uniqlo red, Gap navy), pop-magazine aesthetic (pink\u002Folive\u002Fcream seasonal backgrounds, NOT pure B&W), entry-level pricing (£4.99–£14.99 basics vs Zara's £19.95 floor), youth-dedicated sub-line (H&M's Divided, Gap's Teen), and first-class Baby + Home categories.\n\n- **Palette**: brand-color primary + accessible pastels. H&M red `#E50010`, Uniqlo red `#E30A18`, Gap navy `#00256C`, Mango camel. Seasonal backgrounds use soft pink \u002F olive \u002F cream \u002F camel — a color accent is expected and welcome (opposite of the Zara rule).\n- **Typography**: **bold chunky sans** (Inter Bold Extended, Helvetica Bold, Noto Sans) — NOT condensed elongated serif. The mass-market signal is confidence and clarity, not editorial drama.\n- **Hero**: color-block rotating panels (2-3 panels, each a different hero offer) OR a \"shop-by-trend\" tile row (Y2K \u002F Boho \u002F Workwear \u002F Festival \u002F Preppy). Multiple narratives surfaced, not a single editorial moment.\n- **Navigation** includes: Ladies\u002FWoman, Men, Youth sub-line (Divided\u002FTeen), **Kids, Baby, Home** — Baby and Home are first-class top-nav entries, not nested under Kids\u002FLifestyle. Uniqlo Baby sizing goes 50-100cm.\n- **Product detail view** — like editorial-minimalist but with:\n  - Color swatches as prominent circles (not discrete)\n  - Size grid XS–XXXL PLUS numerical EU 34-46 both shown\n  - **Members price** strikethrough shown (\"£29.99 \u002F H&M Member £24.99\")\n  - Tech-feature badges where applicable (HEATTECH \u002F AIRism \u002F Supima \u002F Ultra Light Down for Uniqlo; CONSCIOUS \u002F RECYCLED \u002F ORGANIC for H&M)\n  - Accessible price ladder on every tile (entry + aspirational side-by-side)\n- **Product grid** is denser than editorial-minimalist, merch-oriented, with badge flags (NEW \u002F SAVE \u002F BESTSELLER \u002F CONSCIOUS) that would be too loud for Zara but are on-brand here.\n- **Loyalty programme** is first-class chrome: H&M Members, Uniqlo IQ, Gap Good Rewards. Surface in the navbar, the PDP price block, and the book-demo-modal (rewrite as loyalty signup per SKILL.md residues).\n- **Technical-functional tech features** are product-level filters: Uniqlo's HEATTECH\u002FAIRism\u002FSupima\u002FUltra Light Down\u002FBlockTech\u002FPUFFTECH. Extend `search_products` with a `tech?` arg so customers can filter by proprietary material tech (\"HEATTECH base layer for -10°C\"). Don't overload `material` with it.\n- **MCP tools** — same as editorial-minimalist plus:\n  - `search_products` extended with `tech?` arg (HEATTECH \u002F Supima \u002F CONSCIOUS \u002F Organic Cotton \u002F Recycled)\n  - `list_collections()` — Uniqlo's Main\u002FU\u002FC\u002FJ\u002F+J\u002FJW Anderson\u002FMarimekko; H&M's Main\u002FStudio\u002FDivided\u002FConscious Exclusive + designer collabs\n\n**FASHION MARKETPLACE — ONLINE (ASOS, Shein, Nasty Gal, Boohoo, Zalando):**\n\nPure-play online retailers with substantial own-label catalogues + stocked external brands. Distinct from `RETAIL — MULTI-BRAND` (Sephora \u002F Nordstrom \u002F Net-A-Porter) which are primarily curated external-brand retailers. Distinct from `marketplace-listings` (Booking \u002F Airbnb) which is host-traveler dynamics.\n\n- **Palette**: dark-minimalist with an electric accent. ASOS true black + neon yellow; Shein black + pink; Zalando white + orange. The neon\u002Felectric accent is the \"online-only youth\" signal.\n- **Typography**: bold chunky sans with confident presence. Inter Bold Extended or Helvetica Bold Extended.\n- **Signature nav pattern** — **size-inclusive top-level entries**: Curve & Plus \u002F Petite \u002F Tall \u002F Maternity as first-class nav categories alongside Women \u002F Men \u002F Kids. This is unique to online-only fashion marketplaces (ASOS pioneered it; Boohoo \u002F Nasty Gal followed). SKIP this for Zalando\u002FNordstrom\u002FNet-A-Porter which keep size ranges as filter chips instead.\n- **Hero**: weekly editorial cover (\"Trending now\", \"Fit of the week\", \"We're obsessed with…\") + a \"shop-by-size-range\" tile row. Model-led street-style photography, NOT studio white-background.\n- **Product detail view**:\n  - Prominent brand badge above product name (\"NIKE · Air Max 90\")\n  - Size + fit info block (\"Model wears UK 8 \u002F size S, 5'10\"\") — ASOS-signature\n  - Stock indicator (\"Only 3 left in size M\")\n  - Star rating + review count from the brand's own reviews\n  - Premier \u002F Prime \u002F Saver delivery eligibility teaser\n- **Required `src\u002Flib\u002Fbrands.ts`** + `list_brands(category?, featuredOnly?)` MCP tool (same convention as multi-brand beauty retail — ASOS stocks 850+ brands).\n- **Required `src\u002Flib\u002Fcollections.ts`** for own-label sub-lines (ASOS Design \u002F Edition \u002F 4505 \u002F Weekend Collective \u002F Made In \u002F Topshop \u002F Topman).\n- **MCP tools** — substantial extension:\n  - `search_products` extended with `brand?`, `sizeRange?` (`\"curve\" | \"petite\" | \"tall\" | \"maternity\" | \"standard\"`), `gender?`\n  - `list_brands(category?, featuredOnly?)`\n  - `list_collections()`\n  - `find_fit(bodyShape?, occasion?, season?, sizeRange?)` — extended with sizeRange\n  - `get_size_guide(category, gender, sizeRange?)` — UK\u002FEU\u002FUS PLUS per-range cut measurements (curve cut differs from petite cut, not just the number)\n  - `check_delivery(postcode?, country?)` — NEW translation tool (conditions → Premier \u002F Saver \u002F Standard eligibility). Sibling to Canada Goose's `check_warmth`. General pattern: a translation tool for service eligibility is a third category beside product-search and product-recommend.\n\n**LUXURY — AMERICAN HERITAGE \u002F PREP (Ralph Lauren, Tommy Hilfiger, J.Crew, L.L. Bean, Brooks Brothers):**\n- **Hero**: Full-bleed runway OR editorial lifestyle photograph (equestrian, sailing, library, cabin interior — NOT Paris-minimalist void). Static image with 1.04 scale-on-mount is fine — most of these brands have no public video CDN.\n- **CTAs**: Square buttons, uppercase-wide tracking, \"Shop the Collection\" \u002F \"Request an Appointment\" \u002F \"Visit the Flagship\"\n- **Stats**: Minimal, serif numbers, uppercase labels — same as French luxury\n- **Collections**: 2- or 3-col grid of portrait 3:4 or 4:5 images with serif captions\n- **Fonts**: Caslon \u002F Garamond \u002F Playfair Display — NOT Didot (that reads as French and wrong)\n- **Typography**: Wide-tracked uppercase labels in burgundy or navy, italic body for pullquotes, never all-caps long-form\n- **Colors**: Navy primary, burgundy accent, cream surface, racing green or tartan secondary, antique gold highlight — avoid stark black\u002Fwhite\u002Fgold (that's French)\n- **Motion**: Slower than French luxury (1200–1600ms), no scale transforms beyond 1.04\n\n**TECH \u002F SAAS (Stripe, Notion, Linear):**\n- Split hero with copy left + product screenshot right\n- Colored CTAs (rounded-full), \"Start Building\" \u002F \"Book a Demo\"\n- Stats on dark background with bold numbers\n- Feature grid with icons (not images)\n- Code snippets as visual elements\n\n**CONSUMER (Apple, Nike, Spotify):**\n- Full-bleed hero with big bold text, keep sans-serif\n- Single prominent CTA, bold colors\n- Product-focused imagery, minimal copy\n\n**FINTECH \u002F FINANCIAL (Visa, Chase, Robinhood):**\n- Keep current template style (split, colored tiers, card visuals)\n- Blue\u002Fnavy color palette\n- Stats-heavy design, trust signals\n\n**MARKETPLACE \u002F C2C (Vinted, Depop, Etsy, eBay, Poshmark):**\n- **Hero**: carousel of category solutions with lifestyle photography (real people + items — NOT isolated product shots). Hero copy is short and action-oriented (\"Dresses, tops, denim, and outerwear — secondhand\").\n- **CTAs**: dual-intent, always two buttons — primary \"Sell Now\" (solid brand color) + secondary \"Start Browsing\" (outline or darker brand color). Never \"Shop Now\" alone; a marketplace's sellers are half the audience.\n- **Stats bar**: members \u002F markets \u002F lifetime GMV \u002F seller-fees. Example from Vinted: \"80M+ Members · 26 Markets · €10.8B Annual GMV · 0% Selling fees\". The zero-fees or low-fees stat is often the single most persuasive number — lead with it if true.\n- **Navigation**: the brand's real category tree (Women \u002F Men \u002F Designer \u002F Kids \u002F Home), plus a \"Sell\" item that routes to the seller flow.\n- **Feature tiles** (instead of product grid): Buyer Protection, Ship Fast, Designer Authentication, Bundle Discounts, Zero Fees, Wallet — these are *trust & flow* features, not products.\n- **Fonts**: utility sans-serif (Inter, Geist). Marketplaces are utility-first; serif reads luxury and is wrong.\n- **Colors**: most marketplaces use a single bold color (Vinted teal `#09B1BA`, Depop red, Etsy orange, Poshmark pink). Use the brand color boldly — stats band, hero CTAs, feature icons.\n- **No `book-demo-modal` in the classic B2B shape** — see the marketplace variant in the `book-demo-modal.tsx` guidance below.\n\n**MARKETPLACE \u002F LISTINGS (Booking, Airbnb, VRBO, Trivago, Expedia, Hotels.com, Agoda):**\n\nSimilar to C2C marketplaces but asymmetric — travellers\u002Fbuyers are the primary audience, hosts\u002Fsellers are the B-side. Different hero + CTA pattern:\n\n- **Hero**: large photographic hero (city skyline \u002F destination \u002F accommodation) with a **search form overlay** — not a static CTA button. The search form IS the primary interaction. Standard fields: destination, check-in, check-out, guests.\n- **CTAs — asymmetric, NOT dual-intent**:\n  - Primary: \"Search Stays\" \u002F \"Find a Hotel\" \u002F \"Search Flights\" — large, solid brand color, near the search form\n  - Secondary: \"List Your Property\" \u002F \"Become a Host\" — small outline button in nav or footer, routes to a host-onboarding modal\n  - Do NOT paste dual CTAs side-by-side like C2C. The search form is a primary-heavy pattern.\n- **Two signature grids** — SHIP BOTH on the homepage:\n  1. **Trending inventory grid** — 18-26 tiles of individual stays\u002Fcities\u002Froutes with real photography (Paris boutique, Tokyo capsule, Santorini cave, Maldives villa). Each tile shows image + name + price indicator (\"from €180\u002Fnight\") + city label.\n  2. **Destinations \u002F categories grid** — 24-36 tiles of countries\u002Fcities\u002Fregions with iconic destination photos (Eiffel, skyline, monument). Each tile shows image + destination name + property count (\"12,450 stays\").\n  - Both grids are what travellers actually scroll through. Skipping either breaks the marketplace feel.\n- **Stats bar**: properties \u002F countries \u002F languages \u002F support. Example from Booking: \"3M+ Properties · 220+ Countries · 40+ Languages · 24\u002F7 Support\".\n- **Navigation**: Hotels · Apartments · Villas · Hostels · B&Bs · Holiday homes · Resorts · plus \"List your property\" as the host entry.\n- **`src\u002Flib\u002Fcards.ts` repurposing**: the 9-15 `productItems` represent stay categories (Hotels\u002FApartments\u002FVillas\u002Fetc.), NOT individual properties — the same repurposing convention as C2C features but with category shape.\n- **Optional `src\u002Flib\u002Fdestinations.ts`**: listings marketplaces almost always have a destinations catalog. Create this file with `{ id, city, country, region, heroImage, propertyCount }[]` and wire a `list_destinations(region?)` MCP tool to it. Vinted uses `list_markets(region?)` for country markets; Booking uses `list_destinations(region?)` for cities; Uber would use `list_cities(country?)`. Same shape, different primary axis.\n- **Optional `src\u002Flib\u002Fexperiences.ts`** (for brands that sell **activities** alongside stays — Airbnb Experiences, Klook, Viator, GetYourGuide, Hotels.com Spots): `{ id, city, title, type, price, duration, image }[]`. Experiences aren't stays (no overnight axis) and aren't destinations (they're bookable events) — they need their own dataset. Wire a `find_experience(city?, type?)` MCP tool. Skip this file if the brand only sells stays.\n- **Premium tier within the marketplace** — Airbnb Luxe, Booking Genius, VRBO Premier Partner, Expedia One Key. These are *tiers-within-the-marketplace* that carry extra service slots (trip designer, pre-stocked pantry, airport transfer, priority support). The flat `productItems[].tier` field in the template captures the label but not the extras. If the premium tier matters to the brand story, create a `premium-tier.ts` with `{ features: string[], amenities: string[], support: string }` and add a fifth MCP tool `get_premium_tier()`. Otherwise just flag the tier with a single card in `productItems` and accept the simplification.\n- **Fonts**: utility sans-serif (Inter, Geist). Same as C2C.\n- **Colors**: a confident primary color (Booking blue `#003580`, Airbnb red `#FF5A5F`, Expedia yellow `#FFC72C`) — the primary drives the search form, stats bar, and trending grid chrome.\n\nWhen transforming, EXPLICITLY adapt the hero and category grid to match the brand's visual DNA. Don't just update text — change the layout pattern.\n\n**MARKETPLACE \u002F RENTALS — RESIDENTIAL (Joivy, Spotahome, HousingAnywhere, Uniplaces, The Student Hotel, Kabute, Casavo):**\n\n**Distinct from listings-marketplace (Booking\u002FAirbnb)** — long-term residential rentals (1–24 months), not nightly stays. The vocabulary, pricing model, transaction flow, and visual surfaces are different enough that listings-marketplace guidance leads you wrong. Verified across the Joivy transform.\n\n- **Vocabulary swap (CRITICAL — do a sweep)**:\n  - \"Stay\" → \"Rental\" or \"Tenancy\"\n  - \"Night\" \u002F \"Nights\" → \"Month\" \u002F \"Months\"\n  - \"Check-in \u002F check-out\" → \"Move-in date \u002F Move-out date\"\n  - \"Guests\" → \"Tenants\" \u002F \"Residents\" (or \"Roommates\" for co-living)\n  - \"Reserve\" \u002F \"Book this stay\" → **\"Schedule a viewing\"** or \"Apply\" or \"Request a tour\"\n  - \"Free cancellation\" → \"Lease flexibility\" \u002F \"Notice period\" (typically 30-60 days)\n  - \"Trip\" \u002F \"Vacation\" → just remove\n  - \"Hotel\" \u002F \"Resort\" → \"Building\" \u002F \"Residence\" \u002F \"Apartment block\"\n- **Hero \u002F search form fields** (different from Booking's destination\u002Fcheck-in\u002Fcheck-out\u002Fguests):\n  - **City** (dropdown of live markets)\n  - **Move-in date** (single date picker, not a range — open-ended duration)\n  - **Duration** — radio or pills: 1-3 mo \u002F 3-6 mo \u002F 6-12 mo \u002F 12+ mo\n  - **Room type** — Entire studio \u002F 1-bed \u002F Co-living room \u002F Shared apartment \u002F Family suite\n  - **Monthly budget** (single slider — €400-€2,500 typical range)\n  - Primary CTA: \"Find a home\" or \"Search rentals\" — not \"Search stays\"\n- **Stats bar** (different metrics): markets · cities · operating since · average move-in time. Example for Joivy: \"8 countries · 50+ cities · since 2007 (DoveVivo) · 24h average viewing booking\".\n- **`src\u002Flib\u002Fcards.ts` repurposing — DIFFERENT FROM LISTINGS**: `productItems` represent **rental categories** (Studio · Co-living room · 1-bed apartment · 2-bed apartment · Student studio · Shared apartment · Family suite · Pro suite), NOT stay categories (Hotels\u002FVillas). Field mapping:\n  - `issuer` → city\u002Fcountry (not gender, not house — for residential the city is the primary filter)\n  - `tier` → lease duration (\"Short-term 1-3 mo\" \u002F \"Medium 3-6 mo\" \u002F \"Long-term 6-12 mo\" \u002F \"Annual 12+ mo\")\n  - `annualFee` → monthly rent (\"€650 \u002F month\")\n  - `apr` → utilities + furnishing (\"Utilities included · Furnished\" \u002F \"Bills excluded · Unfurnished\")\n  - `rewardRate` → minimum lease (\"3 month minimum\")\n  - `signUpBonus` → onboarding offer (\"First month -50%\" \u002F \"No deposit\" \u002F \"Free Wi-Fi\" \u002F \"Move in same week\")\n  - `applyUrl` → property URL on the brand's site\n- **Property detail view** — **NOT the Airbnb gallery + booking card**. Use:\n  - Photo gallery (room + common spaces + building exterior + neighborhood)\n  - Header: building name + address + city + monthly rent + utilities-included badge\n  - **Lease terms block** (essential — lease duration, deposit amount, notice period, what's included, available-from date)\n  - **Building amenities** (Wi-Fi, kitchen, gym, common lounge, washing machine, bike storage)\n  - **Nearby** (universities, transit, supermarkets — text list, not just a map pin)\n  - **\"Schedule a viewing\"** primary CTA + \"Apply now\" secondary\n  - No \"Reserve\" button. No nightly price calculator. No \"guests\" picker.\n- **`src\u002Flib\u002Fdestinations.ts`** stays useful — same shape as listings-marketplace, just `propertyCount` is larger (Joivy has ~5,000 rooms in Milan).\n- **MCP tools** specific to residential rentals:\n  - `search_rentals(city?, duration_months?, room_type?, max_rent?, available_from?)` — instead of `search_stays`. Different param shape.\n  - `find_co_living(city?, age_range?)` — translation tool (sibling to `check_warmth`, `find_fit`, `check_delivery`). Conditions → property pick.\n  - `book_viewing(propertyId, date)` — schedule a tour, NOT a stay reservation.\n  - `get_lease_terms(propertyId)` — minimum lease, deposit, notice period, included utilities. Documenting the contract is the equivalent of Booking's \"free cancellation\" trust signal.\n  - `get_property(propertyId)`, `compare_properties(ids[])` — same as listings.\n  - **Skip**: `search_stays`, `find_experience`, `find_boutique` — wrong domain.\n- **Fonts**: clean sans-serif (Inter, Söhne). Joivy uses ABC Diatype-adjacent.\n- **Colors**: residential brands lean toward **trust-warm palettes** — deep teal (Joivy `#015962`), forest green, terracotta, navy. NOT bright vacation-marketing colors (Booking blue, Airbnb red, Expedia yellow). The vibe is \"your home\", not \"your getaway\".\n\n**MARKETPLACE \u002F RENTALS — FLEX (Habyt Flex, Cove, Sonder, Mindspace Living, Outsite, Selina Co-Live):**\n\n**Distinct from residential rentals (Joivy)** — flex-living = stays for **days OR months**, not 1+ month minimum. Habyt's pitch is \"a stay that moves with you\" — book 3 nights or 8 months in the same building, with free cancellation. Verified across the Habyt transform.\n\n- **Vocabulary swap (different from residential)**: keep \"stay\" and \"guests\" (NOT \"rental\" \u002F \"tenants\"). \"Book\" or \"Book now\" (NOT \"Schedule a viewing\"). \"Free cancellation\" is the headline trust signal, not \"lease flexibility\". The whole grammar is closer to extended-stay-hotel than to residential lease.\n- **Hero \u002F search form fields** (closer to Booking's stay form than Joivy's rental form):\n  - **City** (dropdown of live properties, NOT live cities — flex brands often have just 1-3 active buildings)\n  - **Check-in date + Check-out date** (range picker, like Booking) — NOT a single move-in date\n  - **Guests** (1-4 typical)\n  - **Unit type** — Studio \u002F 1-Bed \u002F 2-Bed \u002F Suite (per-property)\n  - Primary CTA: **\"Book now\"** or **\"Search\"** — NOT \"Find a home\" (that's residential).\n- **Pricing model — DUAL TIER**: every listing carries BOTH a per-night price (`€95\u002Fnight`) AND a per-month price (`€1,450\u002Fmo`). The PDP and the booking card need to surface both. Discount messaging: \"Stay 7+ nights for X% off\", \"Stay 30+ nights for X% off\". `cards.ts` should have `monthlyRent` AND `nightlyRent` fields (or a single `priceTiers` object).\n- **Tier mapping** (different from residential): `tier` field becomes the stay-length tier — `\"Flex 1-3 nights\"` \u002F `\"Short stay 7+ nights\"` \u002F `\"Monthly stay\"` \u002F `\"Long stay 6+ months\"` — instead of lease duration.\n- **Property catalog tends to be SMALL**: Habyt Flex has 2 active properties globally (Berlin Waterfront, Truliving Vallecas Madrid). Don't fake a 50-property catalog. Generate 5-10 unit-type variants per real property (different floors, views, slight price spread) for a 20-30 card catalog. Then list \"coming soon\" cities with `comingSoon: true` flags + a coming-soon UI badge.\n- **`destinations.ts` shape**: add `comingSoon: boolean` and `propertyCount: 0` for non-active cities. The world-map and city grid then render those with a muted \"Coming soon\" treatment instead of a fake property count.\n- **MCP tools** specific to flex-living (different signatures from residential):\n  - `search_stays(city?, checkIn?, checkOut?, guests?, unitType?, maxRent?, minNights?)` — uses **check-in\u002Fcheck-out range** like Booking, NOT `duration_months` like Joivy. Both nightly + monthly results in one response.\n  - `find_flex_living(preference)` — translation tool (sibling to `find_co_living`). Natural-language → property + unit pick. Includes nights vs. months parsing.\n  - `book_stay(propertyId, checkIn, checkOut, guests)` — supports days OR months in one tool. NOT `book_viewing`.\n  - `get_lease_terms(propertyId)` — repurposed for \"stay terms\" — free cancellation window (typically 24-48h before), minimum nights, deposit, what's included.\n  - `get_living_spaces(propertyId)` — list amenities + common spaces (rooftop pool, café, cinema room, gym, coworking — Habyt Vallecas style).\n  - `get_property(propertyId)`, `compare_properties(ids[])`, `list_destinations(country?)` — same as residential.\n  - **Skip**: `search_rentals`, `find_co_living`, `book_viewing`, `find_experience` — wrong domain (residential or hotel).\n- **No 3D Matterport tours** typically — flex brands lean on photography + video walkthrough instead. The tours.json should be `{}` and `hasTour()` returns false; the PDP's 3D-tour pill must be conditional (`{tourAvailable && \u003Cpill\u002F>}`) so it silently disappears, not breaks.\n- **Hero subhead**: \"A stay that moves with you\" \u002F \"Flexible living, anywhere you go\" \u002F \"Book for days or months\" — emphasize flexibility, NOT permanence.\n- **Trust badges** (real Habyt order): `Free cancellation · Flexible stay · Best price` — these go above the price on the PDP booking card AND on listing tiles.\n- **Colors**: flex-living brands lean **darker, more luxurious** than residential — Habyt is forest green `#00271A` + terracotta `#572411` + cream `#FFFBF1`. NOT trust-warm teal (that's residential). The vibe is \"boutique extended-stay hotel\", not \"your home\" or \"your getaway\".\n- **Fonts**: same clean modern sans (Inter, Söhne) but allow a serif accent for headings on luxury-skewed flex brands (Habyt uses a humanist sans throughout).\n\n**RETAIL — MULTI-BRAND (Sephora, Nordstrom, Net-A-Porter, Farfetch, Selfridges, MatchesFashion):**\n\nDifferent from mono-brand luxury (Dior\u002FHermès) because they stock hundreds of external brands and have to surface those brands as first-class entities. Different from marketplace (Vinted\u002FAirbnb) because they carry real inventory, not user listings.\n\n- **Hero**: large campaign carousel (3-4 slides) with brand collaborations or seasonal themes — less minimalist than luxury, more editorial\u002Fcommercial.\n- **Navigation**: by category (Makeup, Skincare, Fragrance, Hair, Men, Gifts) AND by brand (dedicated \"Brands\" entry in the nav).\n- **Signature sections** on homepage:\n  1. Nouveautés \u002F New in — 16+ products\n  2. Bestsellers — 16+ products\n  3. Shop by category — 6-8 large tiles\n  4. Featured brands — horizontal row of 20+ brand cards (logos + \"shop the brand\")\n  5. Curated routine \u002F look builder — 3-4 step walkthrough (Nettoyer → Tonifier → Traiter → Hydrater for beauty)\n- **`src\u002Flib\u002Fbrands.ts`** — REQUIRED for multi-brand retail. `{ id, name, logo, origin, categories[], featured }[]` + `list_brands(category?, featuredOnly?)` MCP tool. Sephora stocks 340+ brands and without this the agent can't answer \"what brands do you stock from Korea\".\n- **Product detail view** — e-commerce shape (NOT Airbnb listing card, NOT credit-card detail):\n  - Gallery strip (hero + 3 thumbs; thumbs can repeat with product variants)\n  - Brand name (prominent, above title) + product title + star rating + review count + trust badges (\"Clean at Sephora\", \"Cruelty-free\", \"Vegan\")\n  - Price row (with strikethrough if discounted)\n  - **Shade \u002F swatch picker** — 8-12 color chips with hover labels (required for makeup; skincare skips this)\n  - Quantity selector + \"Add to bag\" \u002F \"Ajouter au panier\" button in the brand accent color\n  - Accordion sections: Ingredients, How to use, Benefits, Reviews\n  - \"Recommandés pour vous\" \u002F \"You might also like\" — 4-card row filtered to same category\n  - No booking card, no application form — pure e-commerce\n- **Fonts**: utility sans-serif (Inter \u002F Helvetica Neue). Matches beauty\u002Fretail flat-minimalism.\n- **Colors**: most beauty retailers use a stark black\u002Fwhite palette (Sephora, Net-A-Porter) with a single accent (Sephora red `#DE1F29`). Tom Ford \u002F Charlotte Tilbury do black + gold. Farfetch does black + editorial color blocks.\n- **MCP tools** specific to beauty retail:\n  - `list_brands(category?, featuredOnly?)` — filter 340+ brands by category\n  - `find_shade_match(undertone?, coverage?, finish?, skinTone?)` — foundation\u002Flipstick recommendation\n  - `get_routine(skinType?, concern?, budget?)` — 3-4 step skincare routine\n  - `get_fragrance_notes(productId)` — top\u002Fheart\u002Fbase notes per fragrance\n  - `search_products` extended with `brand?` and `skinType?` args\n\n**OUTERWEAR \u002F TECHNICAL (Canada Goose, Arc'teryx, Moncler, The North Face, Patagonia, Mammut):**\n\nMono-brand, premium\u002Fluxury, with technical-spec-forward product detail. Sits at the intersection of American heritage (narrative-heavy, made-in-X provenance) and sportswear (gender\u002Ffit\u002Factivity filter axes). Neither the Dior shape nor the Sephora shape nor the Ralph Lauren shape fits cleanly — it's its own pattern.\n\n- **Hero**: photographic — cold\u002Farctic\u002Fmountain landscape with a single figure in the brand's flagship product. Headline anchored in conditions (\"Built for the coldest place on earth\", \"Made for the alpine\", \"Tested at -40°C\"). Primary CTA = \"Shop [Flagship Product]\"; secondary = \"Discover the Heritage\".\n- **Stats bar**: founding year · Made-in-[country] · Lifetime Warranty · sustainability badge (HUMANE DOWN \u002F RECYCLED \u002F BLUESIGN).\n- **Signature sections on homepage**: 1) Shop the flagship product line (16+ tiles with warmth\u002Fweight indicator per tile); 2) Explore by collection (Expedition, Black Label, Eco-line, Lightweight); 3) Heritage timeline (wire to `heritage.ts`); 4) \"Built for explorers\" — 4 story cards featuring real-world users (scientist, mountaineer, ranger, conservationist).\n- **Product detail view — NEITHER the Airbnb booking card NOR the Sephora shade picker NOR the credit-card detail**. New shape:\n  - Gallery strip (hero + 3-4 thumbs)\n  - Breadcrumb: Home > [Gender] > [Category] > [Collection] > [Style]\n  - Style name + collection line (\"Expedition Parka\") + price\n  - **Color swatches** (circles, 6-8 colorways) — not shade chips, smaller\n  - **Size selector grid** (XS–XXL, with sold-out strikethrough on unavailable)\n  - **Warmth \u002F technical rating bar** — horizontal 1-5 scale (Canada Goose TEI, Arc'teryx has similar tier naming, North Face has similar). Label where this product sits.\n  - **Trust badge row** — 3 pills like HUMANE DOWN · MADE IN CANADA · LIFETIME WARRANTY\n  - Single \"Add to Bag\" button in brand color\n  - Accordions: Details (fill power, shell fabric, weight in g\u002Fkg), Sizing, Care, Sustainability\n  - \"Fit\" editorial block (how it's cut)\n  - \"You might also like\" — 4 cards\n- **Fonts**: utility sans-serif, often condensed (Helvetica Neue, Inter, Neue Haas).\n- **Colors**: the brand's dominant hero color (Canada Goose black, Moncler navy, Patagonia earth-tone) + a single flag-adjacent accent (Canada red, French blue, etc.).\n- **MCP tools** specific to outerwear \u002F technical:\n  - `check_warmth(temperature_c, activity)` — a **translation tool** (conditions → product suggestion) that's neither search nor recommend nor compare. Pattern: customer asks \"what works at -25°C hiking\", tool returns TEI band + matching products. **This shape is new** — document it as a category, other brand types will need translation tools too (e.g. shoes \"what fits size 10 UK narrow\"; skincare \"what's safe during pregnancy\").\n  - `compare_parkas(ids[])` — extended comparison exposing the technical-spec axes (fill power, weight, TEI, shell fabric).\n  - `get_heritage(yearFrom?, yearTo?)` — from `heritage.ts`.\n  - `find_store(city?, country?)` — flagship + experiential retail; use `flagships.ts`'s `note` field for retail-differentiator metadata (\"Cold Room try-on\", \"Arc'teryx Pinnacle Room\", \"Patagonia Worn Wear repair\").\n  - `get_sustainability(productId?)` — sourcing + materials detail; customers ask this more than the other verticals.\n\n**`src\u002Fcomponents\u002Fwwa-panel.tsx`** — ACCOUNT CREATION FLOW:\n\nThe template's account creation asks for \"annual income\" (makes sense for credit card applications, wrong for everything else). For non-financial brands, replace the income question with something contextually relevant:\n\n| Brand Type | Replace \"annual income\" with |\n|------------|------------------------------|\n| Luxury\u002FFashion | \"What categories interest you most? (Fragrance, Bags, Fashion, Jewelry)\" |\n| E-commerce | \"What styles do you prefer?\" |\n| SaaS | \"What's your role\u002Fteam size?\" |\n| Enterprise | \"What's your company size?\" |\n| Content\u002FMedia | \"What genres do you like?\" |\n| Financial | Keep \"annual income\" — it's relevant |\n| Marketplace \u002F C2C | \"Are you mostly buying or selling?\" + follow-up category interest. Ask BOTH because the primary flow branches on this. |\n\nAlso update:\n- `lastAssistantMsg.includes(\"annual income\")` → check for the new question\n- Welcome message: \"Apply for any card\" → \"Shop\" \u002F \"Start using\" \u002F appropriate verb\n- Summary line: \"? $income\" → \"✨ Interests: preferences\"\n- Avatar background color: `1A1F71` (Visa blue) → brand primary color\n\n**`src\u002Fcomponents\u002Fwwa-panel.tsx`** — BUY\u002FCHECKOUT MESSAGES:\n\nReplace credit-card phrasing in the buy intent responses:\n- \"apply for\" → \"order\" \u002F \"shop\" \u002F \"checkout\"\n- \"card\" → \"product\" \u002F \"item\"\n- \"annual fee\" → \"price\"\n- \"Quick apply\" → \"Quick checkout\" \u002F \"Fast order\"\n- \"I'll fill the form for you\" → \"I'll place the order for you\"\n\n**`src\u002Fcomponents\u002Fworld-map.tsx`** — REGIONAL STATS:\n\nThe template has credit-card network stats (`merchants: \"12M+\"`, `banks: \"5,000+\"`, `cards: \"800M+\"`). Replace with brand-appropriate stats:\n\n| Brand Type | Regional Stats |\n|------------|----------------|\n| Luxury\u002FFashion | Boutiques per region, artisans, flagship locations |\n| SaaS | Data centers, enterprise customers, API regions |\n| Retail | Stores, distribution centers, warehouses |\n| Finance | Banks, merchants, cards (keep default) |\n\nAlso update GLOBAL_STATS: `\"4B+ Cards worldwide\"` must match the brand's reality.\n\n**`src\u002Fcomponents\u002Fcard-comparison.tsx`** — TIER BENEFITS:\n\nThe template has 20+ Visa-specific credit card benefits (Zero Liability, Auto Rental CDW, Trip Delay, Global Entry Credit, etc). REMOVE all of these and write tier benefits that apply to the brand:\n\n| Brand Type | Tier Benefit Examples |\n|------------|----------------------|\n| Luxury\u002FFashion | Free shipping, gift wrap, personalization, private shopping, birthday gift, archive access |\n| SaaS | API calls\u002Fmo, support SLA, seats, priority features, dedicated account manager |\n| Retail | Free shipping threshold, returns window, early access, member pricing |\n| Subscription | Streaming quality, devices, downloads, family sharing, ad-free |\n\nTier names `Traditional \u002F Signature \u002F Infinite` are Visa-specific — rename to match the brand's tier system (e.g., Free\u002FPro\u002FEnterprise for SaaS, Essentials\u002FSignature\u002FÉlite for luxury).\n\n### Step 3.6: Verify Zero Original References\n\nThree comprehensive checks. ALL must pass before deploying:\n\n```bash\n# 0. RE-RUN Step 2.3 visual verification for every image referenced from cards.ts \u002F solutions.ts.\n#    Open each file in Read and confirm it still shows the correct brand. Do not trust\n#    earlier verification — if an agent rewrote data files during Phase 3, image paths may\n#    have been shuffled. This check is fast (8-12 Read calls) and catches the #1 UX bug.\ngrep -oE '\"\u002Fimages\u002F[^\"]+\"' src\u002Flib\u002Fcards.ts src\u002Flib\u002Fsolutions.ts | sort -u\n# For each path listed, Read it and confirm brand match.\n\n# 1. Check for any Visa-brand text leaks\ngrep -rn \"Visa\\|visa\\.\\|#1A1F71\\|#141963\\|#1434CB\" src\u002F --include=\"*.tsx\" --include=\"*.ts\" | grep -v visaCards | grep -v VisaCard\n\n# 2. Check for credit-card terminology that doesn't fit non-card brands\ngrep -rn \"annual fee\\|annual income\\|card tier\\|Apply Now\\|cardholder\\|APR\\|Reward Rate\\|Sign-Up Bonus\\|issued by\\|Zero Liability\\|credit check\\|credit history\\|Traditional, Signature, and Infinite\\|Issuer opt\\.\" src\u002F --include=\"*.tsx\" --include=\"*.ts\" -i | grep -v node_modules\n```\n\nFix every remaining line before deployment. The `card-3d.tsx` component is allowed to keep credit-card text because it's only rendered for actual credit card brands (Visa\u002FMastercard).\n\n### Known template residues — scrub before deploy\n\nThese files ship in the template with Visa-shaped placeholders that the ordinary Phase 3 rewrites don't always catch. Verify each one explicitly before deploying:\n\n| File | What to scrub |\n|------|---------------|\n| `src\u002Fcomponents\u002Fbook-demo-modal.tsx` | Ships with B2B fields (CompanySize, AnnualRevenue, Country dropdown, SKU picker) AND an inline Visa wordmark SVG in the header. For luxury \u002F e-commerce brands, rewrite as \"Request a Private Appointment\" per the luxury pattern above. For SaaS keep B2B but relabel products. For consumer, replace entirely with a newsletter\u002Fcontact form. **For marketplace \u002F C2C brands**, rewrite as \"Open your seller account\" — fields: name + email + username + preferred market (dropdown of the brand's live markets only, NOT all countries) + account type (Personal vs Pro) + main category + expected item volume. Drop B2B revenue\u002Fsize fields entirely. **For marketplace \u002F Listings brands** (Booking, Airbnb, VRBO, Expedia), rewrite instead as \"List your property\" — fields: contact name + email + phone + property type (Hotel \u002F Apartment \u002F Villa \u002F B&B \u002F Holiday home \u002F Cabin) + number of rooms + destination (city\u002Fcountry) + property name + short description + partner-terms opt-in. Primary audience of this modal is hosts, not buyers — the buyer surface is the search form in the hero. Drop B2B revenue\u002Fsize fields. **For retail \u002F multi-brand brands** (Sephora, Nordstrom, Net-A-Porter, Farfetch), rewrite as a loyalty signup — fields: name + email + birthday (short format MM-DD for anniversary gifts) + preferred categories (multi-select chips: Makeup \u002F Skincare \u002F Fragrance \u002F Hair \u002F Men \u002F Gifts) + occasion dropdown (\"For myself\" \u002F \"As a gift\" \u002F \"Wedding\" \u002F \"Event\") + GDPR\u002Fmarketing consent checkbox. The loyalty programme name and tiers go in the header copy (e.g. Sephora's Blanche\u002FOr\u002FNoire, Nordstrom's Nordy Club). Drop B2B revenue\u002Fsize fields. In all cases, replace the header SVG with `\u003Cimg src={BRAND.logoImage} className=\"brightness-0 invert\" \u002F>`. The hero's main CTA opens this modal — an untouched modal ships the wrong form and the wrong logo on the most-clicked button. |\n| `src\u002Flib\u002Fcards.ts` field repurposing per brand type | The `ProductItem` interface is finance-shaped (`issuer`\u002F`tier`\u002F`annualFee`\u002F`apr`\u002F`rewardRate`\u002F`signUpBonus`\u002F`applyUrl`) but the field names are stable — semantics repurpose per brand. Keep a comment block at top of `cards.ts` documenting the mapping so the next maintainer doesn't report them as Visa leaks. **Per brand type:** marketplace C2C → `annualFee: \"Free\" \u002F \"€5 shipping\"`, `apr: \"All markets\"`, `rewardRate: headline benefit`, `signUpBonus: incentive`. Marketplace Listings → `annualFee: \"from €180\u002Fnight\"`, `apr: \"Entire place\"`, `rewardRate: \"★ 4.9\"`, `signUpBonus: \"Free cancellation\"`. Retail Multi-brand Beauty → `issuer: brand name` (e.g. \"Fenty Beauty\"), `tier: collection\u002Fline`, `annualFee: price (€)`, `apr: shade \u002F finish` (\"50 shades · Matte finish\"), `rewardRate: \"★ 4.6 (1.2K reviews)\"`, `signUpBonus: badge` (\"Clean at Sephora\" \u002F \"Award winner\"), `applyUrl: product URL`. Luxury mono-brand → `issuer: House name`, `tier: line` (Lady Dior \u002F Book Tote), `annualFee: price`, `apr: material\u002Fsize`, `signUpBonus: included` (engraving \u002F monogram). **Outerwear \u002F Technical** → `issuer: **gender line**` (\"Men's\" \u002F \"Women's\" \u002F \"Kids'\" \u002F \"Unisex\") — NOTE this is the inverse of beauty where `issuer` holds the brand name. For technical apparel the gender axis is the primary filter, so `issuer` carries it; the brand is implicit (mono-brand). `tier: collection` (\"Expedition\" \u002F \"Black Label\" \u002F \"Lightweight\"), `annualFee: price`, `apr: warmth rating \u002F weight` (\"TEI 4 · 2.05 kg\"), `rewardRate: fill-power` (\"625 fill\"), `signUpBonus: sustainability badge` (\"HUMANE DOWN\" \u002F \"RECYCLED\" \u002F \"MADE IN CANADA\"). **Fashion editorial-minimalist \u002F fast-fashion** → `issuer: gender line` (\"Woman\" \u002F \"Man\" \u002F \"Kids\" — same inversion as outerwear; mono-brand fashion uses issuer for gender, not brand). `tier: collection sub-line` (\"Main\" \u002F \"Studio\" \u002F \"SRPLS\" \u002F \"Origins\" \u002F \"TRF\" \u002F \"Limited Edition\" \u002F \"Join Life\"), `annualFee: price`, `apr: material\u002Fcomposition` (\"100% linen\" \u002F \"Wool blend\"), `rewardRate: size range` (\"XS – XXL\"), `signUpBonus: badge` (\"NEW\" \u002F \"JOIN LIFE\" \u002F \"LIMITED\" \u002F \"BESTSELLER\"). Also add `src\u002Flib\u002Fcollections.ts` for the parallel capsule sub-lines. Don't rename the interface properties unless you're willing to update ~12 component references. For listings marketplaces also create `src\u002Flib\u002Fdestinations.ts`; for multi-brand retail also create `src\u002Flib\u002Fbrands.ts` (brand catalogue) and optionally `src\u002Flib\u002Ffragrances.ts` (notes + perfumer); for heritage + outerwear reuse the template's `src\u002Flib\u002Fheritage.ts` + `src\u002Flib\u002Fflagships.ts` stubs. |\n| `src\u002Fcomponents\u002Fassistant-shared.tsx` EmptyState | The welcome-screen logo is **the call button** (clicking it starts the voice call). Ships with an inline Visa wordmark SVG — which means the FIRST FRAME a customer sees before any interaction shows a Visa logo. Replace the `\u003Csvg>\u003Cpath d=\"...\" \u002F>\u003C\u002Fsvg>` inside the EmptyState button with `\u003Cimg src={BRAND.logoImage} alt={BRAND.name} \u002F>`. Without this fix, every brand transform launches on a Visa logo. |\n| `src\u002Fcomponents\u002Flive-session-overlay.tsx` | Two inline SVG references render the Visa wordmark in the voice-call overlay (header + animated center). Replace with `\u003Cimg src={BRAND.logoImage} alt={BRAND.name} \u002F>` or swap the SVG path — otherwise the voice call shows Visa. Also rewrite the system-prompt text (role, CTAs, \"local banks in 200+ countries\") per brand, BUT keep the \"TOOL USE IS MANDATORY\" block verbatim — it's what makes Gemini Live actually drive the left panel. |\n| `src\u002Flib\u002Fgemini-live-client.ts` | The `show_card` \u002F `show_solution` tool descriptions include example IDs (`'chase-sapphire-preferred'`, `'tap-to-pay'`). Gemini Live reads these as strong hints about what valid IDs look like. If you leave them unchanged on a non-Visa brand, the voice call will refuse to invoke the tools or will call them with made-up IDs — and the left panel stays empty during the call. Replace both example IDs with real ids from your brand's `cards.ts` \u002F `solutions.ts` (e.g. `'jadore-edp'`, `'cruise-2026'`). This is the single most common reason voice calls \"just talk\" without updating the visible panel. |\n| `src\u002Fcomponents\u002Fagent-panel.tsx` | The mock API key uses the prefix `vsk_live_` (Visa-derived). Change to a brand-neutral `api_live_` or a brand-specific prefix (`hsk_`, `drk_`, etc). Runs through `Math.random().toString(36)` — easy to miss. |\n| `src\u002Flib\u002Fcards.ts` | The `ProductItem` interface fields (`annualFee`, `apr`, `rewardRate`, `signUpBonus`, `issuer`, `applyUrl`) all bias toward credit cards. For non-card brands, either repurpose them (document with a comment block at the top of cards.ts — e.g. `annualFee` → price, `apr` → material, `rewardRate` → craftsmanship) or rename the interface properly (updates ~12 components). The audit grep cannot tell a repurposed field from a leak. |\n| `src\u002Fcomponents\u002Fhero-section.tsx` | Often still contains hardcoded `STATS` \u002F `CARD_TIERS` arrays instead of reading from `BRAND.stats`. Replace with `BRAND.stats.map(...)` so stats come from brand-config. |\n| `src\u002Fcomponents\u002Finner-page.tsx` | Contains `PersonalPage`, `BusinessPage`, `TravelPage` route shapes that assume a payments-brand nav. Rename \u002F re-shape to match `BRAND.navItems` or delete and let `page.tsx` route dynamically. |\n\n---\n\n## PHASE 4: Build, Deploy, Verify\n\n### Step 4.0: Generate a unique, safe slug (REQUIRED)\n\n**Every transform MUST deploy under a `project-*` slug, not the raw brand name.** Two reasons:\n\n1. **Safe Browsing safety** — Chrome's brand-phishing classifier flags any subdomain that looks like a well-known brand (`booking.codiris.app`, `apple.codiris.app`, `nike.codiris.app`). Using `project-\u003Cbrand>-\u003Cunique>` breaks that exact-match heuristic. This is a hard requirement for new transforms since the Booking incident (2026-04-21).\n2. **Collision avoidance** — multiple customers transforming the same brand would race for one subdomain. A unique suffix guarantees every customer's deploy has its own URL.\n\n**The required slug shape:**\n\n```\nproject-\u003Cshort-brand>-\u003C4char-hex>\n```\n\n- `\u003Cshort-brand>` — 3-8 letters, lowercase, pointing at the brand but not the full domain. Drop the word most associated with the real brand if the full name is too recognizable. Examples:\n  - `booking.com` → `book24` (NOT `booking`)\n  - `airbnb.com` → `abnb`\n  - `dior.com` → `dior` is fine (not a phishing target yet)\n  - `nike.com` → `nk` or `nike` (borderline — prefer `nk`)\n  - `chase.com` → `chs` (fintech = high-risk — always obfuscate)\n- `\u003C4char-hex>` — generated from `openssl rand -hex 2` (4 hex chars = 65,536 combinations). Never reuse.\n\n**Generate at the start of Phase 4:**\n\n```bash\nSHORT_BRAND=\"book24\"     # replace per brand\nRANDOM_ID=$(openssl rand -hex 2)\nSLUG=\"project-${SHORT_BRAND}-${RANDOM_ID}\"\necho \"Your slug: $SLUG\"\n# e.g. project-book24-a4f2\n```\n\nSave this value — you'll use it in `brand-config.ts`, as the Vercel project name, as the Cloudflare CNAME, and as the alias.\n\n**Collision check against the registry:**\n\n```bash\ncurl -s -o \u002Ftmp\u002Fclaim.json -w \"%{http_code}\\n\" \"https:\u002F\u002Fcodiris.app\u002Fapi\u002Fwwa\u002Fregistry\u002F$SLUG\"\n```\n\n- **HTTP 404** — slug is free (expected when using the 4-char random suffix). Continue.\n- **HTTP 200** — astronomically unlikely collision. Regenerate `RANDOM_ID` and try again.\n\n**Update brand-config.ts** so every runtime reference to the deploy URL is correct:\n\n```ts\nexport const BRAND: BrandConfig = {\n  \u002F\u002F ...\n  mcpUrl: `https:\u002F\u002Fwwa.${SLUG}.codiris.app\u002Fmcp`,   \u002F\u002F replace ${SLUG} with your generated value\n  mcpServerName: `${SLUG}-agent`,                   \u002F\u002F used in MCP server name + CLI install command\n};\n```\n\n**Exceptions (grandfathered):** the original 7 brands on `codiris.app\u002Fskills` (visa, stripe, dior, ralphlauren, hermes, puma, vinted) still live at `wwa.\u003Cbrand>.codiris.app` — they pre-date this policy. Do NOT add new transforms at raw-brand subdomains; every new one gets a `project-*` slug.\n\n**After a successful deploy,** open a PR to `public\u002Fwwa-registry.json` in `wwwtowwa` adding your entry:\n\n```json\n{\n  \"slug\": \"{short-brand}\",\n  \"domain\": \"{brand}.com\",\n  \"deployed_url\": \"https:\u002F\u002Fwwa.{slug-with-random}.codiris.app\",\n  \"mcp_url\": \"https:\u002F\u002Fwwa.{slug-with-random}.codiris.app\u002Fmcp\",\n  \"type\": \"{luxury-french|luxury-heritage|fintech|saas|marketplace|marketplace-listings|sportswear|consumer}\",\n  \"color\": \"{brand primary hex}\",\n  \"first_claimed_at\": \"YYYY-MM-DD\",\n  \"owner\": \"{your-handle-or-email}\"\n}\n```\n\nNote: the registry `slug` field is the **short brand** (e.g. `booking`) so the showcase lookup groups all deploys of that brand together, while `deployed_url` carries the full `project-\u003Cbrand>-\u003Chex>` subdomain that's unique per transform.\n\n### Step 4.1: Build\n```bash\nnpm run build\n```\nFix ALL errors. Common: unterminated strings, missing images, type mismatches.\n\n### Step 4.2: Deploy\n\nCreate `.env.local` in your new project with the keys below. A stub `.env.example` ships in the template — `cp .env.example .env.local` and fill in your own values.\n\n```\nOPENAI_API_KEY=sk-…          # from https:\u002F\u002Fplatform.openai.com (fallback chat model)\nGEMINI_API_KEY=AIza…         # from https:\u002F\u002Faistudio.google.com\u002Fapikey (primary)\nGOOGLE_GENERATIVE_AI_API_KEY=AIza…  # same value as GEMINI_API_KEY (the voice client reads this name)\n```\n\nThe MCP endpoint renders without these keys — only the AI chat + voice call need them.\n\n```bash\nnpx vercel --prod --yes\n\n# Push env vars to Vercel\nsource .env.local\necho \"$OPENAI_API_KEY\"               | npx vercel env add OPENAI_API_KEY               production --force\necho \"$GEMINI_API_KEY\"               | npx vercel env add GEMINI_API_KEY               production --force\necho \"$GOOGLE_GENERATIVE_AI_API_KEY\" | npx vercel env add GOOGLE_GENERATIVE_AI_API_KEY production --force\n\nnpx vercel --prod --yes\n```\n\n### Step 4.2b: Disable Vercel Deployment Protection (if the deploy returns 401)\n\nNew Vercel projects under some team accounts default to **Standard Protection** (SSO-required). Symptom: `curl https:\u002F\u002Fwwa{brand}.vercel.app` returns **HTTP 401** with a Vercel SSO login page. Happens silently — no warning from the CLI.\n\nCheck with `curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\\n\" https:\u002F\u002F{your-vercel-url}`. If you see 401, disable protection via the Vercel API:\n\n```bash\n# Read the Vercel CLI's auth token (macOS path)\nTOKEN=$(cat \"$HOME\u002FLibrary\u002FApplication Support\u002Fcom.vercel.cli\u002Fauth.json\" | python3 -c 'import sys,json; print(json.load(sys.stdin).get(\"token\",\"\"))')\nPROJECT_ID=$(python3 -c \"import json; print(json.load(open('.vercel\u002Fproject.json'))['projectId'])\")\nTEAM_ID=$(python3 -c \"import json; print(json.load(open('.vercel\u002Fproject.json'))['orgId'])\")\n\ncurl -s -X PATCH \"https:\u002F\u002Fapi.vercel.com\u002Fv9\u002Fprojects\u002F$PROJECT_ID?teamId=$TEAM_ID\" \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"ssoProtection\":null,\"passwordProtection\":null}' \\\n  | python3 -c \"import sys,json; r=json.load(sys.stdin); print('sso:', r.get('ssoProtection'), '| pw:', r.get('passwordProtection'))\"\n```\n\nExpected output: `sso: None | pw: None`. The change takes effect within seconds — no redeploy needed.\n\nLinux path: `$HOME\u002F.local\u002Fshare\u002Fcom.vercel.cli\u002Fauth.json`. Windows path: `%APPDATA%\\com.vercel.cli\\auth.json`.\n\n### Step 4.3: Custom subdomain (OPTIONAL — requires Cloudflare token)\n\nThe `wwa.{brand}.codiris.app` alias requires a Cloudflare API token scoped to the `codiris.app` zone. **This token is not shipped with the skill** — it's private infrastructure. Two paths:\n\n**A. You have the token** (maintainer, or coordinated with Iris Lab):\n```bash\nexport CLOUDFLARE_API_TOKEN=…  # scoped to codiris.app zone, DNS edit permission\n\nZONE_ID=$(curl -s \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones?name=codiris.app\" \\\n  -H \"Authorization: Bearer $CLOUDFLARE_API_TOKEN\" \\\n  | python3 -c \"import sys,json; print(json.load(sys.stdin)['result'][0]['id'])\")\ncurl -s -X POST \"https:\u002F\u002Fapi.cloudflare.com\u002Fclient\u002Fv4\u002Fzones\u002F$ZONE_ID\u002Fdns_records\" \\\n  -H \"Authorization: Bearer $CLOUDFLARE_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"type\":\"CNAME\",\"name\":\"wwa.{domain}\",\"content\":\"cname.vercel-dns.com\",\"proxied\":false,\"ttl\":1}'\nnpx vercel domains add wwa.{domain}.codiris.app\nnpx vercel --prod --yes\n```\n\n**B. You don't have the token** (most customers):\nSkip this step. Your Vercel default URL (`https:\u002F\u002F\u003Cproject>.vercel.app`) is a fully working agentfront — the MCP endpoint, chat, and all pages work there. Update `brand-config.ts` `mcpUrl` to the Vercel URL so the displayed install command matches. Ask the registry owner (open an issue at github.com\u002FHumiris\u002Fwwa-transform) to provision the `wwa.{brand}.codiris.app` alias when you're ready to ship under the shared subdomain.\n\n### Step 4.4: Verify\n1. Check HTTP 200: `curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fwwa.{domain}.codiris.app`\n2. Use WebFetch to read the deployed page — check NO wrong-company content\n3. Check images load\n4. **MCP round-trip**: `curl -s -m 20 -X POST https:\u002F\u002Fwwa.{domain}.codiris.app\u002Fmcp -H \"Content-Type: application\u002Fjson\" -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Flist\"}'` — must return the tool list with 200\n5. Report URL to user\n\n**Preview-tool caveat:** the `preview_start` MCP tool detects `package.json` from your **session cwd**, not from `.claude\u002Flaunch.json` in the target project. If your session cwd is not the target project (e.g. you're working on `wwa.ralphlauren` from a session rooted at `wwa.visa`), `preview_start` will start the wrong dev server. Verify via `curl` against the deployed URL instead of local screenshots when working cross-project.\n\n---\n\n## QUALITY CHECKLIST\n\nBefore saying \"done\", verify:\n- [ ] Hero shows THIS company's real value prop and images\n- [ ] Stats are THIS company's real numbers\n- [ ] Products\u002Fsolutions are from THIS company's website\n- [ ] Categories make sense for THIS company (no \"Travel Cards\" for Stripe)\n- [ ] Navigation matches THIS company's actual sections\n- [ ] Inner pages have real content from THIS company\n- [ ] Chat suggestions are relevant to THIS company\n- [ ] Fallback responses reference THIS company's real products\n- [ ] All images are downloaded and loading\n- [ ] Zero references to any other company (Visa, etc.)\n- [ ] The page structure makes sense for THIS type of company\n- [ ] CTAs match what the company actually wants users to do\n- [ ] **Catalog depth meets the minimum for this brand type** (see Phase 2 \"Catalog size\" table). For e-commerce: 100+ product entries in `cards.ts`, spread across the brand's real segments (Woman\u002FMan\u002FKids\u002Fetc). Verify with `search_products` returning `count ≥ 100` via MCP.\n",{"name":5,"version":51,"description":7,"allowed-tools":52,"argument-hint":61},"2.0.0",[53,54,55,43,56,57,58,59,60],"Read","Write","Edit","Glob","Grep","Agent","WebFetch","WebSearch","\u003Cwebsite-url>","main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHumiris\u002Fwwa-transform",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill codiris-agentizer",{"tool":78,"command":79},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill codiris-agentizer",{"tool":81,"command":82},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill codiris-agentizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHumiris\u002Fwwa-transform\u002FSKILL.md",true,[86,92,98,102],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},".codex-plugin\u002Fplugin.json","REFERENCE","参考文档",1859,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHumiris\u002Fwwa-transform\u002F.codex-plugin\u002Fplugin.json",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"assets\u002Flogo-256.png","ASSET","资产文件",25594,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHumiris\u002Fwwa-transform\u002Fassets\u002Flogo-256.png",{"path":99,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":100,"sourceHtmlUrl":101},"package.json",1073,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHumiris\u002Fwwa-transform\u002Fpackage.json",{"path":103,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":104,"sourceHtmlUrl":105},"README.md",4088,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHumiris\u002Fwwa-transform\u002FREADME.md",[107,117,125,133,141,149],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":116},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":116},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":116},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":116},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":116},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":116},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]