agentleFS
Sign inStart free
LedgerHQLedgerHQ/ledger-live/AGENTS.md

ledger-live

AGENTS.md627 starsChanged 6 days agoMITView on GitHub

"Ledger Wallet" (formerly "ledger-live") is a crypto wallet. This pnpm and Nx monorepo contains multiple frontend apps and over 150 library packages. See the root README for an overview. We are working towards consistency across all those packages but each workspace has it's own details. Read local README files relevant to where you are working. New code goes in the monorepo layers — shared/, domain/, features/, apps/. libs/ is legacy: maintained, not grown. When creating a new package, follow docs/new-library.md…

The file

We split this AGENTS.md into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When creating a new package, follow docs/new-library.md guidelines.

    line 13
  2. Distinctive:

    Prefer commands given in local README files.

    line 21
  3. Distinctive:

    When a task includes Jira or Confluence links, use Atlassian MCP to fetch and read the referenced ticket or page by default before …

    line 27
  4. Very specific:

    When a task involves GitHub — pull requests, issues, CI checks, or releases — use the gh CLI by default.

    line 29
  5. Distinctive:

    Before completing or pushing code changes, run the validate-changes skill.

    line 33
  6. Very specific:

    Before adding or changing a runs-on in .github/workflows/, read the ci-runners skill.

    line 37
  7. Very specific:

    Before adding any configuration value — an environment variable, a URL, a partner key — read /docs/configuration.md to pick its home.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Project Context

Overview

"Ledger Wallet" (formerly "ledger-live") is a crypto wallet. This pnpm and Nx monorepo contains multiple frontend apps and over 150 library packages. See the root README for an overview.

We are working towards consistency across all those packages but each workspace has it's own details. Read local README files relevant to where you are working.

Where to add new code

New code goes in the monorepo layers — shared/, domain/, features/, apps/. libs/ is legacy: maintained, not grown.

When creating a new package, follow docs/new-library.md guidelines.

Third-party libraries

New runtime third-party libraries are not added to apps directly (framework singletons, the design system and tooling excepted). The lowest valid package of the monorepo layers (shared/, domain/, features/) owns each one and exposes our own API. Before adding a dependency to apps/*/package.json, read the wrap-third-party-libs skill.

Repo Commands

Prefer commands given in local README files. For example appls like Ledger Wallet Desktop and Ledger Wallet Mobile have very specific commands for setup, dev and build commands.

For general test, build and check recipes see /docs/repo-commands.md, which also contains notes on Nx, filtering and aliases.

External Work Links

When a task includes Jira or Confluence links, use Atlassian MCP to fetch and read the referenced ticket or page by default before summarizing, planning, or implementing.

When a task involves GitHub — pull requests, issues, CI checks, or releases — use the gh CLI by default.

Validate Before Finishing

Before completing or pushing code changes, run the validate-changes skill.

CI runners

Before adding or changing a runs-on in .github/workflows/, read the ci-runners skill. Several ledger-live-* runners are deprecated.

Reusable workflows and composite actions are called @develop, even from release and hotfix branches whose code is older. Before changing one, read the ci-workflow-refs skill. It also shows how to test such a change before merge.

Runner images bake the mise toolchain and the Android AVD. Before changing a version in mise.toml or the AVD configuration, read the runner-images skill.

Configuration and environment variables

Before adding any configuration value — an environment variable, a URL, a partner key — read /docs/configuration.md to pick its home. @shared/env is deprecated and takes no new definitions.

Keep the external services catalog up to date

New endpoint or new SDK that phones home? Add it to /docs/services.md.

Read READMEs for packages where you're working

See examples:

  • Entity packages (domain/entity/): read domain/entity/README.md
  • API packages (domain/api/): read domain/api/README.md
  • Shared packages (shared/**): read shared/README.md
  • Support packages (support/**): read support/README.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free