lindy-reference-architecture
Reference architectures for Lindy AI integrations. Use when designing systems, planning architecture, or implementing production patterns. Trigger with phrases like "lindy architecture", "lindy design", "lindy system design", "lindy patterns".
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2.0k
- Forks
- 234
01 前言 Front Matter
- name
- lindy-reference-architecture
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Reference architectures for Lindy AI integrations. Use when designing systems, planning architecture, or implementing production patterns. Trigger with phrases like "lindy architecture", "lindy design", "lindy system design", "lindy patterns".
- allowed-tools
- Read, Write, Edit
03 SKILL.md 正文
Lindy Reference Architecture
Overview
Production-ready reference architectures for Lindy AI integrations.
Prerequisites
- Understanding of system design principles
- Familiarity with cloud services
- Production requirements defined
Architecture Patterns
Pattern 1: Basic Integration
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Client │────▶│ Backend │────▶│ Lindy AI │
│ (React) │◀────│ (Node.js) │◀────│ API │
└─────────────┘ └─────────────┘ └─────────────┘
// Simple backend integration
import express from 'express';
import { Lindy } from '@lindy-ai/sdk';
const app = express();
const lindy = new Lindy({ apiKey: process.env.LINDY_API_KEY });
app.post('/api/chat', async (req, res) => {
const { message, agentId } = req.body;
const result = await lindy.agents.run(agentId, { input: message });
res.json({ response: result.output });
});
Pattern 2: Event-Driven Architecture
┌──────────────────────────────────────────────────────────┐
│ Event Bus (Redis/SQS) │
└────┬─────────────────┬─────────────────┬────────────────┘
│ │ │
▼ ▼ ▼
┌─────────┐ ┌─────────┐ ┌─────────┐
│ Worker │ │ Worker │ │ Worker │
│ (Agent) │ │ (Agent) │ │ (Agent) │
└────┬────┘ └────┬────┘ └────┬────┘
│ │ │
└────────────────┼────────────────┘
▼
┌─────────────┐
│ Lindy AI │
│ API │
└─────────────┘
// Event-driven worker
import { Queue } from 'bullmq';
import { Lindy } from '@lindy-ai/sdk';
const lindy = new Lindy({ apiKey: process.env.LINDY_API_KEY });
const queue = new Queue('lindy-tasks');
// Producer
async function enqueueTask(agentId: string, input: string) {
await queue.add('run-agent', { agentId, input });
}
// Consumer
const worker = new Worker('lindy-tasks', async (job) => {
const { agentId, input } = job.data;
const result = await lindy.agents.run(agentId, { input });
// Emit result event
await eventBus.publish('agent.completed', {
jobId: job.id,
result: result.output,
});
});
Pattern 3: Multi-Agent Orchestration
┌─────────────────┐
│ Orchestrator │
│ Agent │
└────────┬────────┘
│
┌─────────────────┼─────────────────┐
│ │ │
▼ ▼ ▼
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Research │ │ Analysis │ │ Writing │
│ Agent │ │ Agent │ │ Agent │
└─────────────┘ └─────────────┘ └─────────────┘
// Multi-agent orchestrator
class AgentOrchestrator {
private lindy: Lindy;
private agents: Record<string, string> = {
research: 'agt_research',
analysis: 'agt_analysis',
writing: 'agt_writing',
orchestrator: 'agt_orchestrator',
};
async execute(task: string): Promise<string> {
// Step 1: Orchestrator plans the work
const plan = await this.lindy.agents.run(this.agents.orchestrator, {
input: `Plan steps for: ${task}`,
});
// Step 2: Execute each step
const steps = JSON.parse(plan.output);
const results: string[] = [];
for (const step of steps) {
const result = await this.lindy.agents.run(
this.agents[step.agent],
{ input: step.task }
);
results.push(result.output);
}
// Step 3: Synthesize results
const synthesis = await this.lindy.agents.run(this.agents.orchestrator, {
input: `Synthesize: ${results.join('\n')}`,
});
return synthesis.output;
}
}
Pattern 4: High-Availability Setup
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Load │────▶│ App │────▶│ Lindy │
│ Balancer │ │ Server 1 │ │ Primary │
└─────────────┘ └─────────────┘ └──────┬──────┘
│
┌─────────────┐ ┌──────▼──────┐
│ App │────▶│ Lindy │
│ Server 2 │ │ Fallback │
└─────────────┘ └─────────────┘
│
┌─────────────┐ ┌─────────────┐ │
│ Cache │◀────│ Shared │◀───────────┘
│ (Redis) │ │ State │
└─────────────┘ └─────────────┘
// HA client with failover
class HALindyClient {
private primary: Lindy;
private fallback: Lindy;
private cache: Redis;
async run(agentId: string, input: string) {
// Check cache first
const cached = await this.cache.get(`${agentId}:${input}`);
if (cached) return JSON.parse(cached);
try {
// Try primary
const result = await this.primary.agents.run(agentId, { input });
await this.cache.setex(`${agentId}:${input}`, 300, JSON.stringify(result));
return result;
} catch (error) {
// Fallback
console.warn('Primary failed, using fallback');
return this.fallback.agents.run(agentId, { input });
}
}
}
Output
- Architecture diagrams
- Implementation patterns
- HA/failover strategies
- Multi-agent orchestration
Error Handling
| Pattern | Failure Mode | Recovery |
|---|---|---|
| Basic | API error | Retry with backoff |
| Event-driven | Worker crash | Queue retry |
| Multi-agent | Step failure | Skip or fallback |
| HA | Primary down | Automatic failover |
Resources
Next Steps
Proceed to Flagship tier skills for enterprise features.
04 同仓库更多 Skills
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
neuropixels-analysis
Neuropixels neural recording analysis. Load SpikeGLX/OpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen/IBL curation, AI-assisted visual analysis, for Neuropixels 1.0/2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
notebooklm
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
slack-gif-creator
Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."