OpenParable
Skip to content
← Back to skills

Devtools Import Boundary

Development
devtools-import-boundary

Devtools Import Boundary is an Agent Skill for development published in the LedgerHQ/ledger-live repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Enforce import boundaries inside the devtools scope. Use for any work in "devtools/**".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/LedgerHQ/ledger-live/blob/HEAD/.agents/skills/devtools-import-boundary/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/devtools-import-boundary, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

DevTools import boundaries

Every @devtools/* package is self-contained. The only permitted cross-package import within the devtools scope is from @devtools/registry, and only from the two packages explicitly designed for it.

Rules

PackageMay import from @devtools/*
@devtools/shell@devtools/registry only
@devtools/bindings@devtools/registry only
@devtools/<tool>nothing from @devtools/*

All other @devtools/* → @devtools/* imports are forbidden.

Why

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:

  • The lazy-load boundary collapses — the tool is bundled eagerly.
  • A circular dependency becomes likely (tool → shell → registry → tool).
  • The tool can no longer be rendered standalone, outside the shell.

If bindings or shell import a tool package directly (instead of through the registry):

  • The registry's discriminated union is bypassed and TypeScript loses the narrowing guarantee on DevToolsConfig.
  • The import() split point disappears, defeating code-splitting.

Consequences of a violation

  • Tool imports shell or registry: The tool becomes coupled to shell internals; standalone rendering and unit-testing break.
  • Tool imports another tool: Cross-tool coupling; removing or renaming one tool requires editing the other.
  • Shell or bindings import a tool directly: Eager bundle; code-split lost; registry union integrity broken.

Correct pattern

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.

Documentation

When adding a new package under devtools/, its README.md must state:

  • Whether it may import from @devtools/registry (yes for shell and bindings, no for tool packages).
  • That it must not import any other @devtools/* package, with a pointer to this rule.