intercom-reference-architecture
Implement Intercom reference architecture with layered project structure. Use when designing new Intercom integrations, reviewing project structure, or establishing architecture standards for Intercom applications. Trigger with phrases like "intercom architecture", "intercom project structure", "how to organize intercom", "intercom layout", "intercom design patterns".
What this skill does
# Intercom Reference Architecture
## Overview
Production-ready architecture for Intercom integrations with layered separation, type-safe SDK usage, webhook processing, contact sync, and Help Center management.
## Project Structure
```
my-intercom-app/
├── src/
│ ├── intercom/
│ │ ├── client.ts # Singleton IntercomClient wrapper
│ │ ├── types.ts # Extended Intercom types
│ │ └── errors.ts # Custom error classes
│ ├── services/
│ │ ├── contacts.service.ts # Contact CRUD + search + merge
│ │ ├── conversations.service.ts # Conversation lifecycle
│ │ ├── articles.service.ts # Help Center article management
│ │ └── events.service.ts # Data event tracking
│ ├── webhooks/
│ │ ├── router.ts # Topic-based event routing
│ │ ├── signature.ts # X-Hub-Signature verification
│ │ └── handlers/
│ │ ├── conversation.handler.ts
│ │ └── contact.handler.ts
│ ├── sync/
│ │ ├── contact-sync.ts # CRM <-> Intercom contact sync
│ │ └── company-sync.ts # Company data sync
│ ├── api/
│ │ ├── health.ts # Health check endpoint
│ │ └── webhooks.ts # Webhook endpoint
│ └── cache/
│ └── intercom-cache.ts # LRU + Redis caching layer
├── tests/
│ ├── unit/
│ │ ├── contacts.test.ts
│ │ └── webhooks.test.ts
│ └── integration/
│ └── intercom.integration.test.ts
├── config/
│ ├── development.json
│ ├── staging.json
│ └── production.json
└── package.json
```
## Layer Architecture
```
┌─────────────────────────────────────────────┐
│ API / Webhook Layer │
│ Express routes, webhook endpoints │
├─────────────────────────────────────────────┤
│ Service Layer │
│ contacts.service, conversations.service │
│ Business logic, orchestration │
├─────────────────────────────────────────────┤
│ Intercom Client Layer │
│ intercom-client SDK, error handling │
│ Caching, rate limit management │
├─────────────────────────────────────────────┤
│ Infrastructure │
│ Redis cache, job queue, monitoring │
└─────────────────────────────────────────────┘
```
## Instructions
### Step 1: Client Layer
```typescript
// src/intercom/client.ts
import { IntercomClient, IntercomError } from "intercom-client";
let instance: IntercomClient | null = null;
export function getClient(): IntercomClient {
if (!instance) {
const token = process.env.INTERCOM_ACCESS_TOKEN;
if (!token) throw new Error("INTERCOM_ACCESS_TOKEN required");
instance = new IntercomClient({ token });
}
return instance;
}
// Typed error wrapper
export class IntercomServiceError extends Error {
constructor(
message: string,
public readonly statusCode: number,
public readonly code: string,
public readonly retryable: boolean,
public readonly requestId?: string
) {
super(message);
this.name = "IntercomServiceError";
}
static from(err: unknown): IntercomServiceError {
if (err instanceof IntercomError) {
const retryable = err.statusCode === 429 || (err.statusCode ?? 0) >= 500;
return new IntercomServiceError(
err.message,
err.statusCode ?? 500,
err.body?.errors?.[0]?.code ?? "unknown",
retryable,
err.body?.request_id
);
}
return new IntercomServiceError(
(err as Error).message, 500, "internal", false
);
}
}
```
### Step 2: Contacts Service
```typescript
// src/services/contacts.service.ts
import { getClient, IntercomServiceError } from "../intercom/client";
import { Intercom } from "intercom-client";
export class ContactsService {
private client = getClient();
async findOrCreate(params: {
email: string;
externalId: string;
name?: string;
customAttributes?: Record<string, any>;
}): Promise<Intercom.Contact> {
// Search first to avoid 409 conflicts
const existing = await this.client.contacts.search({
query: { field: "external_id", operator: "=", value: params.externalId },
});
if (existing.data.length > 0) {
return existing.data[0];
}
return this.client.contacts.create({
role: "user",
externalId: params.externalId,
email: params.email,
name: params.name,
customAttributes: params.customAttributes,
});
}
async syncFromCRM(crmUser: {
id: string;
email: string;
name: string;
plan: string;
company: string;
}): Promise<Intercom.Contact> {
const contact = await this.findOrCreate({
email: crmUser.email,
externalId: crmUser.id,
name: crmUser.name,
customAttributes: {
plan: crmUser.plan,
company_name: crmUser.company,
last_synced_at: Math.floor(Date.now() / 1000),
},
});
return contact;
}
async mergeLead(leadId: string, userId: string): Promise<Intercom.Contact> {
return this.client.contacts.merge({ from: leadId, into: userId });
}
async *searchAll(
query: Intercom.SearchRequest["query"]
): AsyncGenerator<Intercom.Contact> {
let startingAfter: string | undefined;
do {
const page = await this.client.contacts.search({
query,
pagination: { per_page: 50, starting_after: startingAfter },
});
for (const contact of page.data) yield contact;
startingAfter = page.pages?.next?.startingAfter ?? undefined;
} while (startingAfter);
}
}
```
### Step 3: Conversations Service
```typescript
// src/services/conversations.service.ts
import { getClient } from "../intercom/client";
export class ConversationsService {
private client = getClient();
async replyAsAdmin(
conversationId: string,
adminId: string,
body: string
): Promise<void> {
await this.client.conversations.reply({
conversationId,
type: "admin",
adminId,
body,
});
}
async addNote(
conversationId: string,
adminId: string,
note: string
): Promise<void> {
await this.client.conversations.reply({
conversationId,
type: "note",
adminId,
body: note,
});
}
async closeWithMessage(
conversationId: string,
adminId: string,
message?: string
): Promise<void> {
await this.client.conversations.close({
conversationId,
adminId,
body: message,
});
}
async getOpenConversationsForAdmin(adminId: string) {
return this.client.conversations.search({
query: {
operator: "AND",
value: [
{ field: "state", operator: "=", value: "open" },
{ field: "admin_assignee_id", operator: "=", value: adminId },
],
},
sort: { field: "updated_at", order: "descending" },
});
}
}
```
### Step 4: Articles Service (Help Center)
```typescript
// src/services/articles.service.ts
import { getClient } from "../intercom/client";
export class ArticlesService {
private client = getClient();
async createArticle(params: {
title: string;
body: string;
authorId: string;
parentId?: string; // Collection ID
state?: "published" | "draft";
}) {
return this.client.articles.create({
title: params.title,
body: params.body,
authorId: params.authorId,
parentId: params.parentId,
state: params.state || "draft",
});
}
async *listAll() {
const response = await this.client.articles.list();
for await (const article of response) {
yield article;
}
}
async listCollections() {
return this.client.helpCenter.listCollections();
}
}
```
### Step 5: Data Flow
```
┌──────────────┐ Webhook POST ┌───────────────┐
│ Intercom │ ─────────────────▶ │ Webhook │
│ Platform │ │ Router │
│ │ ◀── API calls ──── │ │
└────────────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.