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.