miro-reference-architecture
Implement a production-ready reference architecture for Miro REST API v2 integrations with layered design, caching, and event processing. Trigger with phrases like "miro architecture", "miro project structure", "how to organize miro integration", "miro design patterns".
Best use case
miro-reference-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement a production-ready reference architecture for Miro REST API v2 integrations with layered design, caching, and event processing. Trigger with phrases like "miro architecture", "miro project structure", "how to organize miro integration", "miro design patterns".
Teams using miro-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/miro-reference-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How miro-reference-architecture Compares
| Feature / Agent | miro-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?
Implement a production-ready reference architecture for Miro REST API v2 integrations with layered design, caching, and event processing. Trigger with phrases like "miro architecture", "miro project structure", "how to organize miro integration", "miro design patterns".
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
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
# Miro Reference Architecture
## Overview
Production-ready architecture for Miro REST API v2 integrations. Layered design with a board service, item factory, webhook event processor, and caching layer.
## Architecture Diagram
```
┌──────────────────────────────────────────────────────────┐
│ API / UI Layer │
│ Express routes, Next.js API routes, CLI commands │
├──────────────────────────────────────────────────────────┤
│ Service Layer │
│ BoardService, ItemService, SyncService │
│ (business logic, orchestration, validation) │
├──────────────────────────────────────────────────────────┤
│ Miro Client Layer │
│ MiroApiClient (REST v2), TokenManager (OAuth 2.0) │
│ ItemFactory (typed creation), ConnectorBuilder │
├──────────────────────────────────────────────────────────┤
│ Infrastructure Layer │
│ Cache (LRU/Redis), Queue (PQueue), Monitor (metrics) │
│ WebhookProcessor (signature + idempotency) │
└──────────────────────────────────────────────────────────┘
│
▼
https://api.miro.com/v2/
```
## Project Structure
```
src/
├── miro/
│ ├── client.ts # MiroApiClient — wraps fetch with auth, retries, monitoring
│ ├── token-manager.ts # OAuth 2.0 token lifecycle (refresh, storage)
│ ├── item-factory.ts # Typed item creation (sticky notes, shapes, cards, etc.)
│ ├── connector-builder.ts # Fluent API for creating connectors
│ ├── types.ts # TypeScript types for all Miro v2 responses
│ └── errors.ts # MiroApiError, MiroAuthError, MiroRateLimitError
├── services/
│ ├── board-service.ts # Board CRUD + member management
│ ├── item-service.ts # Item CRUD + tag operations
│ ├── sync-service.ts # Two-way sync between Miro and your database
│ └── search-service.ts # Find items by content, type, or tag
├── webhooks/
│ ├── handler.ts # Express/serverless webhook endpoint
│ ├── processor.ts # Event routing and processing
│ └── idempotency.ts # Duplicate event prevention
├── cache/
│ ├── board-cache.ts # Board metadata cache
│ └── item-cache.ts # Item data cache with webhook invalidation
├── config/
│ ├── miro.ts # Environment-based Miro configuration
│ └── index.ts # Config loader
└── monitoring/
├── metrics.ts # Prometheus counters/histograms for Miro API
└── health.ts # Health check endpoint
```
## Core Components
### MiroApiClient
```typescript
// src/miro/client.ts
export class MiroApiClient {
constructor(
private tokenManager: TokenManager,
private cache: ItemCache,
private monitor: MiroMetrics,
) {}
async fetch<T>(path: string, method = 'GET', body?: unknown): Promise<T> {
const token = await this.tokenManager.getValidToken();
const start = performance.now();
const response = await fetch(`https://api.miro.com${path}`, {
method,
headers: {
'Authorization': `Bearer ${token}`,
'Content-Type': 'application/json',
},
...(body ? { body: JSON.stringify(body) } : {}),
});
const duration = performance.now() - start;
this.monitor.recordRequest(method, path, response.status, duration);
this.monitor.updateRateLimit(response);
if (response.status === 429) {
const retryAfter = parseInt(response.headers.get('Retry-After') ?? '5', 10);
throw new MiroRateLimitError(retryAfter);
}
if (!response.ok) {
const error = await response.json().catch(() => ({}));
throw new MiroApiError(response.status, error.message, error.code);
}
if (response.status === 204) return null as T;
return response.json() as T;
}
// Paginated fetch — returns all pages
async fetchAll<T>(path: string, limit = 50): Promise<T[]> {
const items: T[] = [];
let cursor: string | undefined;
do {
const params = new URLSearchParams({ limit: String(limit) });
if (cursor) params.set('cursor', cursor);
const result = await this.fetch<PaginatedResponse<T>>(
`${path}?${params}`
);
items.push(...result.data);
cursor = result.cursor;
} while (cursor);
return items;
}
}
```
### Board Service
```typescript
// src/services/board-service.ts
export class BoardService {
constructor(
private api: MiroApiClient,
private cache: BoardCache,
) {}
async getBoard(boardId: string): Promise<MiroBoard> {
const cached = await this.cache.get(boardId);
if (cached) return cached;
const board = await this.api.fetch<MiroBoard>(`/v2/boards/${boardId}`);
await this.cache.set(boardId, board, 120); // 2 min TTL
return board;
}
async createBoard(params: CreateBoardParams): Promise<MiroBoard> {
return this.api.fetch<MiroBoard>('/v2/boards', 'POST', {
name: params.name,
description: params.description,
teamId: params.teamId,
policy: {
sharingPolicy: { access: params.access ?? 'private' },
permissionsPolicy: { sharingAccess: 'team_members_and_collaborators' },
},
});
}
async shareBoard(boardId: string, emails: string[], role: BoardRole): Promise<void> {
await this.api.fetch(`/v2/boards/${boardId}/members`, 'POST', {
emails,
role, // 'viewer' | 'commenter' | 'editor' | 'coowner'
});
}
async getMembers(boardId: string): Promise<BoardMember[]> {
return this.api.fetchAll(`/v2/boards/${boardId}/members`);
}
}
```
### Webhook Processor
```typescript
// src/webhooks/processor.ts
export class WebhookProcessor {
private handlers = new Map<string, EventHandler[]>();
on(eventType: string, handler: EventHandler): void {
const existing = this.handlers.get(eventType) ?? [];
existing.push(handler);
this.handlers.set(eventType, existing);
}
async process(event: MiroBoardEvent): Promise<void> {
// Type-based routing
const key = `${event.item.type}:${event.type}`; // e.g., 'sticky_note:create'
const handlers = [
...(this.handlers.get(key) ?? []),
...(this.handlers.get(`*:${event.type}`) ?? []), // Wildcard item type
...(this.handlers.get('*:*') ?? []), // Catch-all
];
for (const handler of handlers) {
await handler(event);
}
}
}
// Usage
const processor = new WebhookProcessor();
processor.on('sticky_note:create', async (event) => {
console.log(`New sticky note on board ${event.boardId}: ${event.item.id}`);
await syncService.syncItem(event.boardId, event.item.id);
});
processor.on('*:delete', async (event) => {
console.log(`Item deleted from board ${event.boardId}: ${event.item.id}`);
await database.deleteItem(event.item.id);
});
```
### Connector Builder (Fluent API)
```typescript
// src/miro/connector-builder.ts
export class ConnectorBuilder {
private config: any = { style: {} };
constructor(private api: MiroApiClient, private boardId: string) {}
from(itemId: string, snapTo?: SnapPosition): this {
this.config.startItem = { id: itemId, ...(snapTo ? { snapTo } : {}) };
return this;
}
to(itemId: string, snapTo?: SnapPosition): this {
this.config.endItem = { id: itemId, ...(snapTo ? { snapTo } : {}) };
return this;
}
caption(text: string, position = 0.5): this {
this.config.captions = [{ content: text, position }];
return this;
}
dashed(): this { this.config.style.strokeStyle = 'dashed'; return this; }
curved(): this { this.config.shape = 'curved'; return this; }
arrow(): this { this.config.style.endStrokeCap = 'stealth'; return this; }
async build(): Promise<MiroConnector> {
return this.api.fetch(`/v2/boards/${this.boardId}/connectors`, 'POST', this.config);
}
}
// Usage
const connector = await new ConnectorBuilder(api, boardId)
.from(taskId, 'right')
.to(dependencyId, 'left')
.caption('depends on')
.dashed()
.arrow()
.build();
```
## Data Flow
```
User Action (or cron job)
│
▼
┌─────────────┐
│ Service │ ←── Business logic
│ Layer │
└──────┬──────┘
│
┌────┴────┐
│ │
▼ ▼
┌──────┐ ┌──────┐
│Cache │ │ Miro │ ←── api.miro.com/v2
│Layer │ │Client│
└──────┘ └──────┘
Miro Board Change
│
▼
┌─────────────┐
│ Webhook │ ←── Signature verification
│ Handler │
└──────┬──────┘
│
▼
┌─────────────┐
│ Processor │ ←── Idempotency + routing
└──────┬──────┘
│
┌────┴────┐
│ │
▼ ▼
┌──────┐ ┌──────┐
│Cache │ │ DB │ ←── Sync + invalidation
│Inval │ │Sync │
└──────┘ └──────┘
```
## Configuration
```typescript
// src/config/miro.ts
export interface MiroConfig {
clientId: string;
clientSecret: string;
accessToken?: string;
environment: 'development' | 'staging' | 'production';
cache: { enabled: boolean; ttlSeconds: number };
rateLimit: { maxConcurrency: number; requestsPerSecond: number };
webhook: { secret: string; callbackUrl: string };
}
export function loadMiroConfig(): MiroConfig {
return {
clientId: requireEnv('MIRO_CLIENT_ID'),
clientSecret: requireEnv('MIRO_CLIENT_SECRET'),
accessToken: process.env.MIRO_ACCESS_TOKEN,
environment: (process.env.NODE_ENV ?? 'development') as MiroConfig['environment'],
cache: {
enabled: process.env.MIRO_CACHE_ENABLED !== 'false',
ttlSeconds: parseInt(process.env.MIRO_CACHE_TTL ?? '120'),
},
rateLimit: {
maxConcurrency: parseInt(process.env.MIRO_MAX_CONCURRENCY ?? '5'),
requestsPerSecond: parseInt(process.env.MIRO_RPS ?? '10'),
},
webhook: {
secret: process.env.MIRO_WEBHOOK_SECRET ?? '',
callbackUrl: process.env.MIRO_WEBHOOK_URL ?? '',
},
};
}
```
## Error Handling
| Layer | Error Type | Handling |
|-------|-----------|----------|
| Client | 429 Rate Limited | Exponential backoff with `Retry-After` |
| Client | 401 Token Expired | Auto-refresh via TokenManager |
| Service | Item Not Found | Return null, log, continue |
| Webhook | Invalid Signature | Return 401, do not process |
| Webhook | Duplicate Event | Skip via idempotency check |
| Cache | Redis Down | Fall through to API directly |
## Resources
- [Miro REST API Reference](https://developers.miro.com/docs/rest-api-reference-guide)
- [Miro Node.js Client](https://developers.miro.com/docs/miro-nodejs-api-client)
- [Miro App Examples (GitHub)](https://github.com/miroapp/app-examples)
## Next Steps
For multi-environment setup, see `miro-multi-env-setup`.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".