klaviyo-reference-architecture
Implement Klaviyo reference architecture with best-practice project layout. Use when designing new Klaviyo integrations, reviewing project structure, or establishing architecture standards for email/SMS marketing applications. Trigger with phrases like "klaviyo architecture", "klaviyo project structure", "klaviyo design", "how to organize klaviyo", "klaviyo layout".
What this skill does
# Klaviyo Reference Architecture
## Overview
Production-ready architecture for Klaviyo integrations: layered project structure, service patterns, event-driven sync, and the `klaviyo-api` SDK wired into a real application.
## Prerequisites
- TypeScript project with `klaviyo-api` installed
- Understanding of layered architecture
- Redis (for caching/queuing) and database (for audit/sync state)
## Project Structure
```
src/
├── klaviyo/ # SDK layer (thin wrappers)
│ ├── session.ts # ApiKeySession singleton
│ ├── api.ts # Lazy API client getters
│ ├── types.ts # Shared Klaviyo types
│ └── errors.ts # Error parsing/classification
├── services/ # Business logic layer
│ ├── profile-sync.ts # Bidirectional profile sync
│ ├── event-tracker.ts # Server-side event tracking
│ ├── campaign-manager.ts # Campaign create/send
│ ├── list-manager.ts # List/subscription management
│ └── segment-query.ts # Segment membership queries
├── webhooks/ # Inbound webhook handlers
│ ├── router.ts # Topic-based event routing
│ ├── verify.ts # HMAC-SHA256 signature verification
│ └── handlers/
│ ├── profile-events.ts # profile.created, profile.updated
│ ├── list-events.ts # list.member.added/removed
│ └── campaign-events.ts # campaign.sent, delivered
├── jobs/ # Background jobs
│ ├── profile-sync-job.ts # Scheduled bidirectional sync
│ ├── list-cleanup-job.ts # Unengaged profile suppression
│ └── metrics-export-job.ts # Export Klaviyo metrics to BI
├── middleware/
│ └── klaviyo-rate-limiter.ts # Request queue + retry logic
├── config/
│ └── klaviyo.ts # Environment-specific config
└── health/
└── klaviyo.ts # Health check endpoint
```
## Layer Architecture
```
┌──────────────────────────────────────────────┐
│ API / Webhook Layer │
│ Express routes, webhook handlers │
├──────────────────────────────────────────────┤
│ Service Layer │
│ profile-sync, event-tracker, campaigns │
│ Business logic, orchestration, validation │
├──────────────────────────────────────────────┤
│ Klaviyo SDK Layer │
│ ApiKeySession, ProfilesApi, EventsApi │
│ Error parsing, retry logic │
├──────────────────────────────────────────────┤
│ Infrastructure Layer │
│ Cache (Redis), Queue (BullMQ), │
│ Database (Prisma), Monitoring (OTel) │
└──────────────────────────────────────────────┘
```
**Rules:**
- API layer calls Service layer only
- Service layer calls SDK layer and Infrastructure
- SDK layer never calls upward
- Webhooks are treated as API endpoints
## Instructions
### Step 1: Config Layer
```typescript
// src/config/klaviyo.ts
export interface KlaviyoConfig {
privateKey: string;
publicKey: string;
webhookSecret: string;
environment: 'development' | 'staging' | 'production';
rateLimits: { burstPerSecond: number; steadyPerMinute: number };
cache: { enabled: boolean; ttlMs: number };
}
export function loadConfig(): KlaviyoConfig {
const env = process.env.NODE_ENV || 'development';
return {
privateKey: process.env.KLAVIYO_PRIVATE_KEY || '',
publicKey: process.env.KLAVIYO_PUBLIC_KEY || '',
webhookSecret: process.env.KLAVIYO_WEBHOOK_SIGNING_SECRET || '',
environment: env as KlaviyoConfig['environment'],
rateLimits: { burstPerSecond: 75, steadyPerMinute: 700 },
cache: {
enabled: env !== 'development',
ttlMs: env === 'production' ? 300000 : 60000,
},
};
}
```
### Step 2: Service Layer -- Profile Sync
```typescript
// src/services/profile-sync.ts
import { ProfilesApi, ProfileEnum } from 'klaviyo-api';
import { getSession } from '../klaviyo/session';
import { withRateLimitRetry } from '../middleware/klaviyo-rate-limiter';
export class ProfileSyncService {
private profilesApi: ProfilesApi;
constructor() {
this.profilesApi = new ProfilesApi(getSession());
}
/** Sync a user from your DB to Klaviyo (upsert) */
async syncToKlaviyo(user: {
email: string;
firstName?: string;
lastName?: string;
phone?: string;
metadata?: Record<string, any>;
}): Promise<string> {
const result = await withRateLimitRetry(() =>
this.profilesApi.createOrUpdateProfile({
data: {
type: ProfileEnum.Profile,
attributes: {
email: user.email,
firstName: user.firstName,
lastName: user.lastName,
phoneNumber: user.phone,
properties: {
...user.metadata,
lastSyncedAt: new Date().toISOString(),
syncSource: 'app-db',
},
},
},
})
);
return result.body.data.id;
}
/** Fetch a Klaviyo profile and sync back to your DB */
async syncFromKlaviyo(email: string): Promise<any> {
const result = await withRateLimitRetry(() =>
this.profilesApi.getProfiles({
filter: `equals(email,"${email}")`,
fieldsProfile: ['email', 'first_name', 'last_name', 'phone_number', 'properties'],
})
);
const profile = result.body.data[0];
if (!profile) return null;
return {
klaviyoId: profile.id,
email: profile.attributes.email,
firstName: profile.attributes.firstName,
lastName: profile.attributes.lastName,
phone: profile.attributes.phoneNumber,
properties: profile.attributes.properties,
};
}
}
```
### Step 3: Service Layer -- Event Tracker
```typescript
// src/services/event-tracker.ts
import { EventsApi, ProfileEnum } from 'klaviyo-api';
import { getSession } from '../klaviyo/session';
import { withRateLimitRetry } from '../middleware/klaviyo-rate-limiter';
export class EventTracker {
private eventsApi: EventsApi;
constructor() {
this.eventsApi = new EventsApi(getSession());
}
async trackPurchase(order: {
email: string;
orderId: string;
total: number;
items: Array<{ sku: string; name: string; qty: number; price: number }>;
}): Promise<void> {
await withRateLimitRetry(() =>
this.eventsApi.createEvent({
data: {
type: 'event',
attributes: {
metric: { data: { type: 'metric', attributes: { name: 'Placed Order' } } },
profile: { data: { type: 'profile', attributes: { email: order.email } } },
properties: {
orderId: order.orderId,
items: order.items,
itemCount: order.items.reduce((sum, i) => sum + i.qty, 0),
},
value: order.total,
uniqueId: order.orderId,
time: new Date().toISOString(),
},
},
})
);
}
async trackCustomEvent(email: string, eventName: string, properties: Record<string, any>): Promise<void> {
await withRateLimitRetry(() =>
this.eventsApi.createEvent({
data: {
type: 'event',
attributes: {
metric: { data: { type: 'metric', attributes: { name: eventName } } },
profile: { data: { type: 'profile', attributes: { email } } },
properties,
time: new Date().toISOString(),
},
},
})
);
}
}
```
### Step 4: Data Flow Diagram
```
Your App Klaviyo
───────── ───────
User signs up ──→ ProfileSyncService.syncToKlaviyo()
│
▼
POST /api/profiles/ ──→ Profile created
│
▼
Welcome Flow triggered
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.