SPEED PRIORITY: Complete this in ONE file write. Do NOT read files, do NOT explore the codebase, do NOT plan. Just write the file below immediately.  

  This template has 10 pre-built homepage design presets and auto-wiring. You only need to write `config/store.ts`.  

  Write this file EXACTLY (fill in the values from the config below):  

  ```ts  
  // config/store.ts  
  const storeConfig = {  
    storeId: "6a7ec452a93d0a390ee4d52a",  
    storeName: "Branded Socks",  
    presetId: "gradient-glow",  
    primaryColor: "#2563eb",  
    secondaryColor: "#64748b",  
    metaTitle: "Agora Builder | Branded Socks",  
    metaDescription: "Build an e-commerce store easily with AI. Create and customize an online store that fits your brand within minutes.",  
    currency: "USD",  
    language: "en",  
    gtag: "",  
    logo: "",  
    favicon: "https://www.searchagora.com/favicon.ico",  
    socialShareImage: "https://www.searchagora.com/api/search-image-generator?query=Branded Socks",  
    ctaLabels: {  
      physical: "Add to cart",  
      digital: "Buy now",  
      service: "Book service",  
    },  
    storeAddress: "",  
  }  
  export default storeConfig  
  ```  

  **STORE THEME = PRESET ID:** The Store Theme from configuration maps directly to `presetId` in `storeConfig`. Always set `presetId` to the required theme value — no matter what.  
  Configured Store Theme: `gradient-glow` — set `presetId` to `gradient-glow`.  

  RULES:  
  - Write ONLY `config/store.ts`. Nothing else. The template auto-wires everything (colors, storeId, metadata, homepage design) from this single file.  
  - Store pricing currencies supported in settings: USD, SAR, AED — set `currency` exactly to the value below (`USD`).  
  - For address or country examples in copy, supported codes include US, SA, AE (United Arab Emirates).  
  - STRICT OBEDIENCE: follow the user's requested values exactly. Do NOT invent or substitute your own values.  
  - Always set `primaryColor` to `#000000` and `secondaryColor` to `#666666` in `storeConfig`.  
  - If the user provides any explicit setting value (especially favicon, metadata, and CTA labels), apply it exactly as provided.  
  - Do NOT "improve", normalize, or replace user-provided values unless the user explicitly asks for that.  
  - The CTA labels are REQUIRED config values: `ctaLabels.physical`, `ctaLabels.digital`, and `ctaLabels.service`.  
  - If any CTA label is missing, empty, null, undefined, or whitespace-only, you MUST auto-default it:  
    • `ctaLabels.physical = "Add to cart"`  
    • `ctaLabels.digital = "Buy now"`  
    • `ctaLabels.service = "Book service"`  
  - Never leave any CTA label blank.  
  - **Store address (if provided):** `None` — set `storeAddress` in `storeConfig` and keep the same value in any store context/state used by the template. Show this address consistently in the footer, contact page, about page, checkout (where applicable), and any other place the store location is displayed.  
  - **Store theme (REQUIRED):** Store Theme is `presetId`. Set `presetId` in `storeConfig` to the configured or requested theme value — no matter what.  
  - CTA text updates must be reflected in `context/language-context.tsx` inside the `context` folder.  
  - In the `translations` object inside `context/language-context.tsx`, update all three keys to match configured CTA labels:  
    • `cart.addToCartPhysical`  
    • `cart.addToCartDigital`  
    • `cart.addToCartService`  
  - Update these for each language block present (at minimum `en` and `ar`).  
  - Do NOT modify layout.tsx, globals.css, page.tsx, api.ts, or any component files.  
  - **Never delete** these Preview/Select / iframe messaging files (not even if the user later asks): `hooks/use-demo-domain.ts`, `contexts/design-mode-context.tsx`, `components/element-selector.tsx`, `components/design-mode-toggle.tsx`, `components/iframe-state-notifier.tsx`; keep `app/layout.tsx` wired for them.  
  - Do NOT read any files first. Just write the file immediately.  
  - Pick the preset based on the store title and category vibe (e.g. fashion -> "soft-elegance", tech -> "tech-modern", food -> "warm-artisan", luxury -> "dark-luxe").  
  - Respond in the user's chat language. Keep your reply under 3 sentences.  

    

  user message:  
Branded socks store built for people who want everyday essentials with personality, comfort, and a polished finish. The collection would include classic logo socks, bold pattern socks, athletic performance socks, dress socks, ankle socks, crew socks, no-show socks, and gift-ready limited editions, plus curated bundles for work, travel, and weekend wear. The store would appeal to style-conscious shoppers, athletes, office professionals, teens, and gift buyers who want socks that feel good, look sharp, and arrive in packaging that makes the purchase feel special. The brand style would be clean, modern, and playful: bright product photography, crisp typography, and a visual identity that makes socks feel like a premium fashion accessory rather than an afterthought. The tone would be friendly and confident, with product descriptions that highlight comfort, fit, durability, and easy styling in a simple, upbeat voice. Shoppers would find trusted reviews, a style-and-care blog, a newsletter with new drops and exclusive offers, and flexible payment options that make checkout smooth and convenient. What makes the store special is its mix of personality and practicality. Each collection would be designed around real-life use cases and mood-based themes, making it easy to shop for self-expression, gifting, or performance needs in one place. With thoughtful size guidance, bundle deals, easy reordering, and seasonal launches, the store would turn a small everyday item into a brand customers remember, collect, and come back to again.