lucid-agents

Lucid Agents

Use this skill to make changes that match the installed Lucid release channel and preserve the framework's extension-owned architecture. Inspect the project before proposing code; package versions and generated adapter shape are part of the API.

Start with project evidence

Run the bundled inspector from the skill directory:

node scripts/inspect-project.mjs /absolute/path/to/project

Read its JSON before editing. Also inspect the project's package.json, lockfile, AGENTS.md, agent builder, adapter bootstrap, entrypoint definitions, and service-ui.config.ts when present.

Treat its channel result as a guardrail:

• stable: use APIs present in the installed registry package versions.
• next: use the checked-out workspace source and package READMEs as truth.
• mixed: stop implementation until the user selects registry packages or local/workspace packages consistently.
• unknown: locate the actual Lucid dependency source before writing SDK code.

Never silently upgrade packages, replace an adapter, add a payment protocol, or change a public route. State such changes explicitly and get authorization when they expand the request.

Use the source-of-truth order

When examples disagree, prefer evidence in this order:

1. Installed TypeScript declarations and package source for the project's exact version.
2. Package README and tests for that same version or checkout.
3. Generated template files and their local AGENTS.md.
4. This skill's references.
5. General documentation, blog posts, or memory.

Do not invent an API to reconcile conflicting examples. Explain the version mismatch and choose the form supported by the project.

Preserve the runtime model

• Compose capabilities with createAgent(...).use(extension()).build().
• Let each domain package own its runtime behavior and configuration.
• Register every public operation once as a typed entrypoint.
• Let adapters bind runtime.http.routes or delegate to runtime.http.handlers.
• Do not create adapter-local registries, paywalls, manifests, or authorization flows.
• Keep secrets server-side and read them from environment variables.
• Use durable stores for production state that must survive process restarts.
• Prefer the project's existing package versions and patterns over a broad refactor.