lucidchart-reference-architecture
Reference Architecture for Lucidchart. Trigger: "lucidchart reference architecture".
Best use case
lucidchart-reference-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Reference Architecture for Lucidchart. Trigger: "lucidchart reference architecture".
Teams using lucidchart-reference-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lucidchart-reference-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lucidchart-reference-architecture Compares
| Feature / Agent | lucidchart-reference-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Reference Architecture for Lucidchart. Trigger: "lucidchart reference architecture".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Lucidchart Reference Architecture
## Overview
Design a version-controlled integration layer for the Lucidchart diagramming platform. Document versioning is the primary driver, so every shape mutation is tracked for diff, rollback, and branch operations while an async export pipeline renders diagrams without blocking collaboration.
## Instructions
1. Provision the prerequisites below and register a Lucidchart OAuth2 application.
2. Deploy the document sync service to reconcile local snapshots with Lucidchart state.
3. Start the collaboration event consumer to capture shape deltas in real time.
4. Configure the export worker pool with deduplication via Redis SETNX.
5. Tune the sync interval and version retention policy for your document volume.
## Prerequisites
- Node.js 18+, TypeScript 5, PostgreSQL 15, Redis 7, RabbitMQ or SQS
- Lucidchart OAuth2 credentials with `document:read`, `document:write`, `export` scopes
## Architecture Diagram
```
Client --> API Gateway --> DocumentSyncService --> Lucidchart API
|
+--------------+--------------+
v v v
Version DB Collab Event Export Worker
(snapshots) Consumer (PNG/SVG/PDF)
```
## Service Layer
```typescript
class DocumentSyncService {
constructor(
private api: LucidchartApiClient,
private versions: VersionStore,
private events: EventPublisher
) {}
async syncDocument(docId: string): Promise<DocumentSnapshot> {
const remote = await this.api.getDocument(docId);
const local = await this.versions.getLatest(docId);
if (!local || remote.revision > local.revision) {
const snapshot = await this.versions.save(docId, remote);
await this.events.publish('document.synced', { docId, revision: remote.revision });
return snapshot;
}
return local;
}
async exportDiagram(docId: string, format: ExportFormat): Promise<string> {
await this.events.publish('export.requested', { docId, format });
return this.api.requestExport(docId, format);
}
}
```
## Caching Strategy
```typescript
class DocumentCache {
constructor(private redis: RedisClient) {}
async getMetadata(docId: string): Promise<DocumentMeta | null> {
const raw = await this.redis.get(`doc:meta:${docId}`);
return raw ? JSON.parse(raw) : null;
}
async setMetadata(docId: string, meta: DocumentMeta): Promise<void> {
await this.redis.setEx(`doc:meta:${docId}`, 120, JSON.stringify(meta));
}
async deduplicateExport(docId: string, format: string): Promise<boolean> {
const key = `export:lock:${docId}:${format}`;
return (await this.redis.setNX(key, '1')) === true;
}
}
// TTLs: doc metadata 2 min, shape data not cached (version store is truth)
```
## Event Pipeline
```typescript
class CollabEventConsumer {
constructor(private queue: MessageQueue, private versions: VersionStore) {}
async start(): Promise<void> {
await this.queue.subscribe('collab.shape_changed', async (evt: ShapeEvent) => {
await this.versions.recordDelta(evt.docId, evt.revision, evt.delta);
});
await this.queue.subscribe('collab.user_joined', async (evt: PresenceEvent) => {
await this.versions.recordCollaborator(evt.docId, evt.userId);
});
}
}
class ExportWorker {
async processExport(job: ExportJob): Promise<void> {
const url = await this.api.pollExportStatus(job.exportId);
const buffer = await this.api.downloadExport(url);
await this.storage.upload(`exports/${job.docId}/${job.format}`, buffer);
}
}
```
## Data Model
```typescript
interface DocumentSnapshot {
docId: string; revision: number; title: string;
pages: Page[]; collaborators: string[]; capturedAt: Date;
}
interface Page {
pageId: string; title: string;
shapes: Shape[]; connectors: Connector[];
}
interface Shape {
id: string; type: string; text: string;
position: { x: number; y: number };
size: { width: number; height: number };
}
interface ExportJob {
exportId: string; docId: string;
format: 'png' | 'svg' | 'pdf'; requestedAt: Date;
}
```
## Output
Running this architecture produces a versioned document store with full revision history, a real-time collaboration delta stream, and on-demand diagram exports to PNG, SVG, or PDF with deduplication.
## Scaling Considerations
- Partition the version store by document ID to isolate write-heavy diagrams
- Export workers are stateless; scale horizontally based on queue depth
- Deduplicate concurrent export requests for the same document/format via Redis SETNX
- Distribute sync jobs across OAuth tokens to respect per-user rate limits
## Error Handling
| Component | Failure Mode | Recovery |
|-----------|-------------|----------|
| Lucidchart API | 429 rate limit | Exponential backoff, pause sync for that token |
| Version Store | Write conflict | Retry with latest revision, merge divergent deltas |
| Export Worker | Render timeout | Re-queue lower priority, notify after 3 failures |
| Collab Consumer | Out-of-order events | Buffer and reorder by revision before applying |
| Redis | Cache eviction | Rebuild metadata from version store on next read |
## Examples
```bash
# Sync a document and capture its current revision
curl http://localhost:3000/api/documents/abc123/sync
# Request a PNG export of a specific diagram
curl -X POST http://localhost:3000/api/documents/abc123/export?format=png
```
## Resources
- [Lucidchart API Reference](https://developer.lucid.co/reference/overview)
## Next Steps
See `lucidchart-deploy-integration`.Related Skills
workhuman-reference-architecture
Workhuman reference architecture for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman reference architecture".
wispr-reference-architecture
Wispr Flow reference architecture for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr reference architecture".
windsurf-reference-architecture
Implement Windsurf reference architecture with optimal project structure and AI configuration. Use when designing workspace configuration for Windsurf, setting up team standards, or establishing architecture patterns that maximize Cascade effectiveness. Trigger with phrases like "windsurf architecture", "windsurf project structure", "windsurf best practices", "windsurf team setup", "optimize for cascade".
windsurf-architecture-variants
Choose workspace architectures for different project scales in Windsurf. Use when deciding how to structure Windsurf workspaces for monorepos, multi-service setups, or polyglot codebases. Trigger with phrases like "windsurf workspace strategy", "windsurf monorepo", "windsurf project layout", "windsurf multi-service", "windsurf workspace size".
webflow-reference-architecture
Implement Webflow reference architecture — layered project structure, client wrapper, CMS sync service, webhook handlers, and caching layer for production integrations. Trigger with phrases like "webflow architecture", "webflow project structure", "how to organize webflow", "webflow integration design", "webflow best practices".
vercel-reference-architecture
Implement a Vercel reference architecture with layered project structure and best practices. Use when designing new Vercel projects, reviewing project structure, or establishing architecture standards for Vercel applications. Trigger with phrases like "vercel architecture", "vercel project structure", "vercel best practices layout", "how to organize vercel project".
vercel-architecture-variants
Choose and implement Vercel architecture blueprints for different scales and use cases. Use when designing new Vercel projects, choosing between static, serverless, and edge architectures, or planning how to structure a multi-project Vercel deployment. Trigger with phrases like "vercel architecture", "vercel blueprint", "how to structure vercel", "vercel monorepo", "vercel multi-project".
veeva-reference-architecture
Veeva Vault reference architecture for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva reference architecture".
vastai-reference-architecture
Implement Vast.ai reference architecture for GPU compute workflows. Use when designing ML training pipelines, structuring GPU orchestration, or establishing architecture patterns for Vast.ai applications. Trigger with phrases like "vastai architecture", "vastai design pattern", "vastai project structure", "vastai ml pipeline".
twinmind-reference-architecture
Production architecture for meeting AI systems using TwinMind: transcription pipeline, memory vault, action item workflow, and calendar integration. Use when implementing reference architecture, or managing TwinMind meeting AI operations. Trigger with phrases like "twinmind reference architecture", "twinmind reference architecture".
together-reference-architecture
Together AI reference architecture for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together reference architecture".
techsmith-reference-architecture
TechSmith reference architecture for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith reference architecture".