lucidchart-local-dev-loop
/lucidchart-local-dev-loop
Run a fast, secretless local development loop for Lucid editor extensions and data connectors using official tooling. Use when implementing or debugging Lucid integrations. Trigger with "run Lucid locally".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Run a fast, secretless local development loop for Lucid editor extensions and data connectors using official tooling. Use when implementing or debugging Lucid integrations. Trigger with "run Lucid locally".
Triggers from the description
Arguments
/lucidchart-local-dev-loop [project-path] [test-focus]
Original author description
Run a fast, secretless local development loop for Lucid editor extensions and data connectors using official tooling. Use when implementing or debugging Lucid integrations. Trigger with "run Lucid locally".
How it works
- Overview
- Prerequisites
- Tool Discipline
- Current Contract
- Authentication
- Instructions
- Approval Boundaries
- Output
- Error Handling
- Example
SKILL.md preview
--- name: lucidchart-local-dev-loop description: 'Run a fast, secretless local development loop for Lucid editor extensions and data connectors using official tooling. Use when implementing or debugging Lucid integrations. Trigger with "run Lucid locally".' argument-hint: "[project-path] [test-focus]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.8.0 author: Jeremy Longshore <jeremy@intentsolutions.io> license: MIT tags: [saas, lucidchart, local-development, extension-sdk, testing] model: inherit effort: medium compatibility: Designed for Claude Code; developer-mode installation and any live source connection require approval from the project and data owners --- # Lucid Local Development Loop ## Overview Establish a repeatable edit-build-test loop for an existing Lucid extension or connector, grounded in the installed project and official `lucid-package` tooling. ## Prerequisites - A local project with lockfile, manifest, and documented runtime versions - Synthetic fixtures and no production credentials by default - A disposable Lucid developer test target when UI verification is needed ## Tool Discipline Use `Read`, `Glob`, and `Grep` to inspect the project, `WebFetch` for official CLI/SDK guidance, and `Write` or `Edit` only for scoped source, fixture, test, or local documentation changes. ## Current Contract Lucid maintains `lucid-package` and `lucid-extension-sdk`. Project scripts and installed CLI `--help` define the exact runnable commands; official guidance warns against guessing SDK types or pnpm argument syntax. ## Authentication Keep the default loop offline and fixture-driven. Developer-mode access uses a dedicated least-privilege identity; connector/source secrets remain in an approved local secret provider and never enter bundles or snapshots. ## Instructions 1. Read repository instructions, manifest, package manager, lockfile, scripts, SDK versions, and test configuration. 2. Query installed command help and compare it with current official CLI and SDK documentation. 3. Select the narrowest loop: type/build, manifest validation, unit fixture, connector contract, or editor smoke test. 4. Run the existing deterministic command before editing and preserve its receipt. 5. Make one bounded change, rerun the narrow check, then run all affected local gates. 6. For developer-mode testing, preview scopes, bundle identity, test document, and expected mutations before installation. 7. Record command, duration, changed files, fixture digest, expected/actual result, and cleanup. ## Approval Boundaries Do not add dependencies, install into a Lucid account, contact a live source, or change registered application settings without approval. ## Output Return environment/version evidence, selected loop, commands, test receipts, changed files, developer-mode actions, cleanup, and remaining drift. ## Error Handling | Condition | Response | |---|---| | Project command and docs disagree | Trust installed help/project scripts, investigate version drift, and document it. | | Test requires production data | Replace it with a representative synthetic fixture. | | Developer installation mutates unexpected data | Stop, capture evidence, and remove the test artifact if approved. | ## Example ```text focus=extension-build; package-manager=pnpm; fixture-sha256=...; narrow=pass; affected-gates=pass; live-data=no ``` ## Resources - [Official documentation map](references/official-docs.md) ## Next Steps Encode the proven commands in CI with the same pinned runtime, lockfile, and synthetic fixtures.
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 1 KB
Versions
The database has no other skills named lucidchart-local-dev-loop.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version e5181e824586 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100lucidchart-performance-tuning
Measure and improve Lucid Standard Import, export, editor extension, or data connector performance without weakening correctness. Use when Lucid workflows are slow or resource-heavy. Trigger with "optimize Lucid performance". - 100lucidchart-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". - 100linear-local-dev-loop
Set up local Linear development environment and testing workflow. Use when configuring local development, testing integrations, or setting up a development workflow with Linear. Trigger with phrases like "linear local development", "linear dev setup", "test linear locally",… - 100cursor-local-dev-loop
Optimize local development workflow with Cursor. Triggers on "cursor workflow", "cursor development loop", "cursor productivity", "cursor daily workflow". Use when working with cursor local dev loop functionality. Trigger with phrases like "cursor local dev loop", "cursor loop", "cursor".