Agent skill · software engineering · jeremylongshore
lucidchart-sdk-patterns
Apply supported patterns with Lucid lucid-package and lucid-extension-sdk while treating installed types as authoritative. Use when implementing or reviewing editor extensions. Trigger with "Lucid SDK pattern".
Why this skill is useful
Adds a structured SDK client with OAuth management, error handling, and query building for Lucidchart's API that isn't covered in public documentation.
What it needs
Requires node 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 SDK Implementation Patterns Overview Implement an editor-extension feature from the installed SDK, project manifest, and official guidance—never from guessed type names or stale snippets. Prerequisites Existing extension project with lockfile, manifest, scripts, and pinned versions Defined user behavior, document/data boundary, scopes, and test fixture Current official Extension API and package CLI references Tool Discipline Use Read, Glob, and Grep to inspect source, installed declarations, manifests, and tests; use WebFetch for current official docs; use Write or Edit only for bounded local changes and evidence. Current Contract lucid-package supplies project tooling and lucid-extension-sdk supplies supported APIs and types. Official Lucid AI guidance says to consult documentation and types, avoid guessing APIs, use correct pnpm mode syntax, and request least extension scopes. Authentication Editor bundles must not contain server secrets. Put source OAuth and confidential credentials behind an approved connector/server boundary. Review manifest scopes before any developer install. Instructions 1. Read repository instructions, package manifest, Lucid manifest, lockfile, scripts, and relevant tests. 2. Inspect installed SDK declaration/source files for the exact API, callback, return, error, and availability contract. 3. Re-fetch the corresponding official topic and note version/documentation drift. 4. Design a thin typed boundary that validates external data and converts errors into explicit user-safe states. 5. Implement the smallest feature using existing project patterns; avoid global mutable state and undocumented object shapes. 6. Add tests for success, invalid input, unavailable context, insufficient scope, cancellation, and partial failure. 7. Run project type/build/manifest/test commands using installed --help and correct package-manager argument passing. 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-sdk-patterns