🎯 Agent Guide

← Back to Documentation

Quick Start

Goal: Create a new email case study that follows brand guidelines, accessibility standards, and consistent design patterns.

Step 1: Research the Brand

  1. Check if brand kit exists:
    ls /root/lare-labs/brand-kits/{brand-name}*
  2. If no brand kit, research:
    • Real brand colors from their website
    • Typography they use
    • Imagery style (lifestyle vs product vs abstract)
    • Brand voice (professional, playful, luxury, edgy)

Step 2: Choose Template Type

Step 3: Image Requirements (MUST BE CONTEXTUAL)

Never use: Generic placeholders, emojis as UI elements, off-brand imagery

Step 4: Accessibility Checklist

Before saving the email, verify:

Step 5: File Structure

Save email to:

/root/lare-labs/website/public/case-studies/{brand-name}/{brand-name}-v{N}.html

Update index in /root/lare-labs/CASE_STUDY_INDEX.md

Step 6: Testing & Deploy

  1. Build the project:
    cd /root/lare-labs/website && npm run build
  2. Check for errors
  3. Deploy:
    export VERCEL_TOKEN=$(cat /root/.env.master | grep VERCEL_TOKEN | cut -d'"' -f2)
    npx vercel --token "$VERCEL_TOKEN" --prod --yes

Common Mistakes to Avoid

  1. Dark mode CSS — Don't use prefers-color-scheme. It's broken in email.
  2. Emojis as icons — Use actual images or Lucide icons.
  3. Generic colors — Match the brand's actual palette.
  4. No alt text — Always describe images.
  5. Fixed widths — Use percentages for mobile.

Example Command Flow

# 1. Check brand kit
cat /root/lare-labs/brand-kits/joy-organics-draft.json

# 2. Copy template
cp /root/lare-labs/design-system/templates/editorial.html \
   /root/lare-labs/website/public/case-studies/joy-organics/joy-organics-v3.html

# 3. Edit with brand colors and imagery
# ... edit file ...

# 4. Test build
cd /root/lare-labs/website && npm run build

# 5. Deploy
export VERCEL_TOKEN=$(cat /root/.env.master | grep VERCEL_TOKEN | cut -d'"' -f2)
npx vercel --token "$VERCEL_TOKEN" --prod --yes