New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Structure Flow

by LedgerHQ in LedgerHQ/ledger-live

Place and organize Ledger Wallet code in the monorepo layers.

MITAuto-check passedDevelopment

Install Structure Flow

skills CLI
$ npx skills add LedgerHQ/ledger-live --skill structure-flow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LedgerHQ/ledger-live structure-flow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LedgerHQ/ledger-live.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/structure-flow .claude/skills/structure-flow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
structure-flow
GitHub stars
622
Token cost
~1.7k tokens
SKILL.md length
505 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Place and organize Ledger Wallet code in the monorepo layers.

  • Reviewing code under apps
  • SKILL.md covers Choose The Owner, Organize The Package, Respect Boundaries and Name Packages, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Deciding which layer owns a concern

What it does

Structure Flow is an agent skill from LedgerHQ/ledger-live. Place and organize Ledger Wallet code in the monorepo layers. 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.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Monorepo tooling. The repository describes itself as: Mono-repository for Ledger Wallet apps and related packages. The licence is MIT.

When your agent uses it

  • Reviewing code under apps
  • Deciding which layer owns a concern
  • Structuring packages and flow steps
  • Checking package names

Example prompts

  • “/structure-flow”

What it can do on your machine

Read from SKILL.md and the folder at commit 30d7883. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • ledgerhq.atlassian.net

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Structure Flow loads about 1.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 505 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LedgerHQ/ledger-live at commit 30d7883, republished under its MIT licence (© LedgerHQ). 505 words, ~1,748 tokens.

Download SKILL.mdSave it as .claude/skills/structure-flow/SKILL.md (or your agent's skills folder).
name
structure-flow
description
Place and organize Ledger Wallet code in the monorepo layers. 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.

Structure And Flow

Use the lowest layer that can own the concern without depending on a higher layer.

Read the canonical architecture guide and the package creation checklist before creating a package.

Upstream source: Structure & Flow

Choose The Owner

ConcernLocationOwnsDoes not own
Platform entry pointapps/<app>Screens, global routing, store composition, analytics host wiring, observability, app glueReusable feature internals
User-visible capabilityfeatures/flow/<feature>Business-aware UI, user journeys, local state, flow routingApp-specific screen composition
Capability shared across flowsfeatures/platform/<feature>Hooks, selectors, NFR rules, React glue, and components shared by several flows or use casesSingle-flow internals and fully generic components
Business objectdomain/entity/<entity>Runtime schema, inferred type, defaults, mocks, selectors, sliceNetwork calls and feature state
Network/data accessdomain/api/<name>API contracts, calls, transformations, RTK Query, thunksUI and app composition
Business-agnostic primitive or componentshared/<name>Generic schemas, utilities, Redux primitives, and components without domain or feature knowledgeDomain or app knowledge
Development-only toolingsupport/<name>Shared test, TypeScript, lint, and format configurationRuntime code

Use these distinctions:

  • Keep feature-scoped state in its features/flow package; do not promote it to an entity.
  • Keep an element in features/flow when it belongs to one flow or use case.
  • Move a feature-level element to features/platform when several flows or use cases need it, especially when it connects them to the domain.
  • Keep fully generic, business-agnostic elements in shared or the existing design-system package.
  • Keep app screens in each app. Let them compose exported flow entry points.
  • Keep .web and .native variants beside each other inside the owning feature.

Organize The Package

Every unit is a private package with package.json, src/, explicit exports, and no cross-package relative imports.

text
features/flow/<feature>/src/
├── components/                # shared by several steps
├── hooks/
├── router/                    # flow-local routing only
├── state/                     # feature-scoped state
├── steps/<StepName>/
│   ├── components/            # used only by this step
│   ├── viewModel.ts           # state and orchestration
│   ├── view.ts                # rendering and callbacks
│   ├── view.test.ts
│   └── index.ts
├── utils/
└── index.ts                   # minimal public API

domain/entity/<entity>/src/
├── schema.ts
├── schema.mock.ts
├── selectors.ts
├── slice.ts
└── index.ts

domain/api/<name>/src/
├── api.ts
└── index.ts

Colocate tests with the files they cover. Add folders only when they group files that change together.

Every index.ts above is a barrel: only export * from "./x" lines, with private code kept in an internals location. See package-public-api for the rules and the lint:structure check that enforces them.

Show full SKILL.md (182 more words)Show less

Respect Boundaries

Dependencies flow downward:

text
apps → features/flow → features/platform → domain → shared

More precisely:

SourceMay depend on
sharedshared
domain/entitydomain/entity, shared
domain/apidomain/api, domain/entity, shared
features/platformfeatures/platform, domain, shared
features/flowfeatures/flow, features/platform, domain, shared
appsAny new-architecture layer
supportDevelopment tooling only; consume it through devDependencies
  • Never import internal legacy libs/* packages from shared, domain, or features.
  • Let legacy code consume new architecture only as migration glue.
  • Inject private new-architecture packages into published legacy packages at the app composition root.
  • Import another package through its npm name, never through a relative path.
  • Let Nx infer tags from paths; do not add manual tags unless local tooling requires them.

Name Packages

LocationPackage name
shared/<name>@shared/<name>
domain/entity/<name>@domain/entity-<name>
domain/api/<name>@domain/api-<name>
features/platform/<name>@features/platform-<name>
features/flow/<name>@features/flow-<name>
support/<name>@support/<name>

Review

  • Confirm the concern sits in the lowest valid layer.
  • Confirm folders express ownership and colocation, not arbitrary categories.
  • Confirm apps only compose reusable flows and platform concerns.
  • Confirm feature, entity, API, and development-only state have distinct owners.
  • Confirm imports follow the dependency table and package public APIs.
  • Confirm every index.* is a pure barrel and no package re-exports another — see package-public-api.

© LedgerHQ, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/structure-flow of LedgerHQ/ledger-live.

Open the folder on GitHubat commit 30d7883

Compare with similar skills

Structure Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Structure Flow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Structure Flow this skillLedgerHQ/ledger-live622—~1.7kAutomated safety check: PassMIT
Nx Importnrwl/nx29k6 repos~3.5kAutomated safety check: PassMIT
Nx Workspacenomcopter/react-mosaic4.8k8 repos~1.9kAutomated safety check: PassCustom licence
Electron Multi-Process ArchitectureiOfficeAI/AionUi33k1 repos~1.8kAutomated safety check: PassApache-2.0
Nx Run Tasksnomcopter/react-mosaic4.8k8 repos~613Automated safety check: PassCustom licence
Astro Developerwithastro/astro63k1 repos~1.5kAutomated safety check: PassCustom licence

Similar skills

  • Nx Import

    nrwl/nx

    Import, merge, or combine repositories into an Nx workspace using nx import.

    29k GitHub starsUsed in 6 repos~3.5k tokens
    DevelopmentAuto-check passed

  • Nx Workspace

    nomcopter/react-mosaic

    Explore and understand Nx workspaces. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 8 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Electron Multi-Process Architecture

    iOfficeAI/AionUi

    Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.

    33k GitHub starsUsed in 1 repo~1.8k tokens
    DevelopmentAuto-check passed

  • Nx Run Tasks

    nomcopter/react-mosaic

    Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 8 repos~613 tokens
    DevelopmentAuto-check passed

  • Astro Developer

    withastro/astro

    Official

    Comprehensive guide for developing in the Astro monorepo. An agent skill from withastro/astro.

    63k GitHub starsUsed in 1 repo~1.5k tokens
    DevelopmentAuto-check passed

  • Migrate Internal Package into Ghost

    TryGhost/Ghost

    Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

More from LedgerHQ/ledger-live

All 50 skills in this repo

  • Impacting PRs

    LedgerHQ/ledger-live

    Find which open PRs are impacted by a migration/sunset/refactor and notify their authors — blocking review when the old path is already gone from develop, heads-up comment when it is only deprecated…

    622 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Cloud Sync Module

    LedgerHQ/ledger-live

    Write, review or debug a cloudSyncModule.ts — a CloudSyncDataManager that syncs one slice of user data through Ledger Sync (Cloud Sync).

    622 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Codeownership

    LedgerHQ/ledger-live

    Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live.

    622 GitHub stars~687 tokensUpdated today
    Auto-check passed

  • Coin Families Contract

    LedgerHQ/ledger-live

    Coin-specific families logic must live in families/. An agent skill from LedgerHQ/ledger-live.

    622 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Data Layer Advanced

    LedgerHQ/ledger-live

    Structure a Ledger Wallet data layer where one API response serves several entities.

    622 GitHub stars~509 tokensUpdated today
    Auto-check passed

  • Debug Rn Native Crash

    LedgerHQ/ledger-live

    Investigate native React Native crashes (Fabric/Hermes/iOS) in ledger-live-mobile when JS error logs are missing or unhelpful.

    622 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Structure Flow

What does Structure Flow do?

Place and organize Ledger Wallet code in the monorepo layers. Structure Flow is an agent skill from LedgerHQ/ledger-live. Place and organize Ledger Wallet code in the monorepo layers.

When should I use Structure Flow?

Structure Flow fits situations like: reviewing code under apps; deciding which layer owns a concern; structuring packages and flow steps; checking package names.

How do I install Structure Flow in Claude Code?

Run `npx skills add LedgerHQ/ledger-live --skill structure-flow -a claude-code`. Or copy the skill folder (.agents/skills/structure-flow in LedgerHQ/ledger-live) into .claude/skills/structure-flow in your project. Claude Code loads it when a task matches its description.

How do I install Structure Flow in Codex?

Run `npx skills add LedgerHQ/ledger-live --skill structure-flow -a codex`. Or copy the skill folder (.agents/skills/structure-flow in LedgerHQ/ledger-live) into .agents/skills/structure-flow in your project. Codex loads it when a task matches its description.

Can I use Structure Flow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LedgerHQ/ledger-live --skill structure-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/structure-flow, .gemini/skills/structure-flow, .github/skills/structure-flow and .opencode/skills/structure-flow in your project.

What does Structure Flow need to run?

SKILL.md names no scripts, command-line tools or credentials: Structure Flow is instructions for the agent only.

Does Structure Flow access the network?

SKILL.md names 1 domain. As links in the text: ledgerhq.atlassian.net. This is read from the text; nothing was executed.

Is Structure Flow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Structure Flow use?

Structure Flow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Structure Flow use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Structure Flow?

Skills that share tags, products or a category with Structure Flow: Nx Import (nrwl/nx, 29k stars), Nx Workspace (nomcopter/react-mosaic, 4.8k stars), Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars) and Nx Run Tasks (nomcopter/react-mosaic, 4.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Structure Flow?

LedgerHQ (a GitHub organization) maintains it in LedgerHQ/ledger-live, which has 622 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 8, 2026.

Source: LedgerHQ/ledger-live on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.