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.