Agent skill · software engineering · jeremylongshore
lucidchart-reference-architecture
Design a contract-grounded Lucid integration architecture across REST, Standard Import, editor extensions, and optional data connectors. Use when making system and boundary decisions. Trigger with "design Lucid architecture".
Why this skill is useful
Adds a complete integration architecture with executable code for syncing and exporting diagrams from Lucidchart, which the AI wouldn't generate on its own.
What it needs
Requires node, postgresql, rabbitmq, redis installed locally. Requires lucidchart account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lucid Integration Reference Architecture Overview Select the smallest supported Lucid surface for the requirement and document trust, data, failure, and ownership boundaries before implementation. Prerequisites Functional requirements, data classification, users, service objectives, and failure tolerance Known Lucid product, ownership model, and plan/account constraints Current official contracts for candidate surfaces Tool Discipline Use Read, Glob, and Grep to inspect the system and constraints, WebFetch for current Lucid contracts, and Write or Edit only for architecture records and diagrams in the approved project. Current Contract Use REST operations for documented server-side document/account workflows. Use Standard Import for deterministic file-driven document creation. Use an editor extension for in-editor UI, document content, and document data behavior. Add a data connector only when server-side source authentication, scheduled refresh, or documented connector webhook behavior is required. Authentication Map each boundary to a principal: human/API key, OAuth user, OAuth account, extension, connector runtime, and upstream source. Define scopes, secret storage, rotation, revocation, consent, and audit evidence. Instructions 1. Capture actors, use cases, latency, volume, data classes, residency, ownership, and recovery objectives. 2. Re-fetch the candidate surface documentation; reject capabilities supported only by memory or third-party examples. 3. Draw component, trust-boundary, data-flow, and failure/recovery views. 4. For every edge, specify schema, identity, authorization, validation, retry/idempotency, retention, and observability. 5. Compare at least two viable options on complexity, supportability, least privilege, failure isolation, and reversibility. 6. Explicitly exclude unsupported generic document webhooks, document locking, universal quotas, and unverified cost assumptions. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-reference-architecture