lucid-sdk-reference

Explain Lucid Extension SDK patterns and document manipulation workflows.

Updated Jul 12, 2024
One-click install
npx skills add https://github.com/GreenShoesLLC/quodsi_lucidchart_package --skill lucid-sdk-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lucid-sdk-reference
Source: https://github.com/GreenShoesLLC/quodsi_lucidchart_package/tree/main/.claude/skills/lucid-sdk-reference
Command: npx skills add https://github.com/GreenShoesLLC/quodsi_lucidchart_package --skill lucid-sdk-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers overcome the complexity of building Lucid extensions by providing structured guidance on the Lucid Extension SDK, proxy architecture, custom shapes, UI components, and document manipulation patterns.

Core Features & Use Cases

  • SDK Architecture Guidance: Explains EditorClient, DocumentProxy, PageProxy, BlockProxy, LineProxy, and other core SDK concepts for extension development.
  • Extension Development Patterns: Provides implementation approaches for panels, modals, menus, data connectors, storage, and communication between extension components.
  • Lucid-Specific Development Support: Covers Quodsi shape libraries, model storage patterns, custom block handling, and troubleshooting for Lucid extension projects.

Quick Start

Use the lucid-sdk-reference skill to help me implement a Lucid extension feature using the appropriate SDK classes and patterns.

Frequently Asked Questions about lucid-sdk-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Lucid extension using the EditorClient and document proxies?

Lucid extension development uses EditorClient alongside DocumentProxy, PageProxy, and BlockProxy to manipulate documents. The SDK provides structured patterns for custom shapes, panels, modals, and menus, enabling you to create interactive extensions that integrate data directly into Lucidchart documents.

What is the Lucid Extension SDK architecture for custom shapes and data integrations?

The Lucid Extension SDK architecture centers on EditorClient and proxy classes like BlockProxy and LineProxy for document manipulation. Custom shapes are handled through shape libraries, while data integrations use proxies and storage patterns to connect external data sources into Lucidchart visual workflows.

How do I implement panels and modals in a Lucidchart extension?

Panels and modals in Lucidchart extensions are implemented through the Extension SDK using EditorClient to manage UI components. The SDK provides specific patterns for creating interactive panels, modals, and menus, along with communication channels between these extension components and the underlying document.

Can I use TypeScript to develop Lucid extensions with custom block handling?

Yes, Lucid extensions are developed using TypeScript with the Extension SDK. Custom block handling uses BlockProxy classes and Quodsi-specific architecture patterns, allowing you to create shape libraries, manipulate block properties, and implement model storage patterns within your extension.

What's the best way to troubleshoot proxy architecture issues in Lucid extension development?

Troubleshooting Lucid extension proxy architecture involves examining DocumentProxy, PageProxy, and BlockProxy interactions within the SDK. The Skill provides guidance on identifying common issues with model storage patterns, custom block handling, and data connector implementations specific to Quodsi architecture.

Why does my Lucid extension lose data when manipulating BlockProxy objects?

BlockProxy data persistence in Lucid extensions requires proper use of model storage patterns and SDK communication channels. The Skill explains how to correctly implement storage and data integration workflows, ensuring your custom shapes and block properties maintain their state during document manipulation.