Menu
Enforce import boundaries inside the devtools scope. Use for any work in "devtools/**".
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/LedgerHQ/ledger-live --skill devtools-import-boundaryThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Place and organize Ledger Wallet code in the DDD monorepo. Use when creating, moving, or reviewing code under apps, features, domain, shared, or support; deciding which layer owns a concern; structuring packages and flow steps; or checking package names, dependency boundaries, platform variants, and legacy imports.
A new-architecture package (shared/, domain/, features/) exposes its API through barrels that contain nothing but `export *`, and keeps its private code in an internals location. Read this when creating a package under shared/, domain/ or features/, when editing any `index.*` file, or when a `lint:structure` check fails.
A new-architecture package (shared/, domain/, features/) exposes its API through barrels that contain nothing but `export *`, and keeps its private code in an internals location. Read this when creating a package under shared/, domain/ or features/, when editing any `index.*` file, or when a `lint:structure` check fails.
Based on SOC occupation classification
| name | devtools-import-boundary |
| description | Enforce import boundaries inside the devtools scope. Use for any work in "devtools/**". |
Every @devtools/* package is self-contained. The only permitted cross-package imports within the devtools scope are listed in the table below; all others are forbidden.
| Package | May import from @devtools/* |
|---|---|
@devtools/registry | any @devtools/<tool> |
@devtools/shell | @devtools/transport, @devtools/registry |
@devtools/bindings | @devtools/registry only |
@devtools/wire | @devtools/transport, @devtools/protocols |
@devtools/protocols | @devtools/transport only |
@devtools/relay | @devtools/transport only |
@devtools/transport-panel | @devtools/transport only |
@devtools/<tool> | none |
All other @devtools/* → @devtools/* imports are forbidden.
The devtools architecture decouples tools from the shell through the registry. The shell lazy-loads tools via metadata.loader; tools never know the shell exists. If a tool imports the shell or another tool directly:
If bindings or shell import a tool package directly (instead of through the registry):
DevToolsConfig.import() split point disappears, defeating code-splitting.Cross-cutting concerns (shared types, utilities) must not live in a tool package. Extract them to a standalone library with no @devtools/* scope, then import that from whichever packages need it.
App state and wiring for a tool arrive as props, built in @devtools/bindings — the single sanctioned bridge to Ledger Live internals. A tool that needs more data from the app gets new props, not a new import.
When adding a new package under devtools/, its README.md must state:
@devtools/* packages it may import, per the table above.@devtools/* imports are forbidden, with a pointer to this rule.