Agent skill · software engineering · jeremylongshore
miro-reference-architecture
Analyze requirements and design tenant-safe Miro boundaries across Web SDK, backend OAuth, REST adapters, queues, reconciliation, and approval-gated live operations. Use when planning a Miro integration. Trigger with \"miro integration reference architecture\".
Why this skill is useful
Adds a complete production-ready architecture with specific components and integration patterns for Miro API that the AI wouldn't generate on its own.
What it needs
Requires miro account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Miro Integration Reference Architecture Overview Put each capability at the correct browser, backend, tenant, and persistence boundary; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Approved Miro application, tenant, and board scope Current repository and deployment evidence Named owner, success criteria, and rollback or recovery boundary Tool Discipline Use Read, Glob, and Grep to inspect the repository, configuration names, adapters, tests, and evidence. Use WebFetch only for current official Miro documentation. Use Write or Edit after confirming the requested mode, target environment, tenant, board, and approval boundary. These declared tools do not call authenticated Miro APIs or deployment CLIs; implement client, configuration, and test changes, then return exact operator commands or an approval-gated handoff for live execution. Current Contract Web SDK operates in loaded board contexts; REST requires OAuth Authorization Code. Hybrid apps configure SDK authorization for backend REST authentication. Tokens must bind to app, user, team, and scopes. Durable change capture requires reconciliation because REST webhooks were retired. Authentication For REST work, use OAuth 2.0 Authorization Code with the narrowest Miro scopes. Bind each encrypted token record to its user, application, authorized team, and granted scopes. Never print access tokens, refresh tokens, client secrets, authorization codes, or board content. Instructions 1. Map actors, tenants, boards, data classes, journeys, and destructive operations. 2. Assign in-board interaction to Web SDK and durable orchestration to backend REST. 3. Define OAuth callback, rotating encrypted token storage, tenant authorization, and revocation. 4. Add weighted queues, cursor checkpoints, operation records, reconciliation, and safe telemetry. 5. Design failures for auth loss, tenant mismatch, 429, ambiguous writes, drift, and outage. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-reference-architecture