coin-families-contract
Skill628 starsChanged 5 days agoMITView on GitHub
Coin-specific families logic must live in families/. Generic UI uses the families contract only (no if (family === "evm") in shared code). Use when working in "**/families/**", "**/mvvm/**", "**/renderer/**" and "**/screens/**".
In this repository71 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- analyticsSkill
- batch-feature-devSkill
- ci-runnersSkill
- ci-workflow-refsSkill
- cleanupSkill
- client-idsSkill
- cloud-sync-moduleSkill
- codeownershipSkill
- coin-modulesSkill
- commentsSkill
- configurationSkill
- console-logSkill
- create-changesetSkill
- create-prSkill
- data-layer-advancedSkill
- debug-rn-native-crashSkill
- dependency-patchesSkill
- detect-data-leaksSkill
- device-intent-executorSkill
- devtools-import-boundarySkill
- dialogs-sliceSkill
- docs-migrateSkill
- docs-update-or-createSkill
- domain-dataSkill
- e2e-desktop-add-or-updateSkill
- e2e-desktop-onboardSkill
- e2e-earnSkill
- e2e-mobile-add-or-updateSkill
- e2e-mobile-onboardSkill
- e2e-swapSkill
- errorsSkill
- feature-devSkill
- fix-ciSkill
- flow-packageSkill
- get-pr-commentsSkill
- git-conventionsSkill
- i18n-keysSkill
- impacting-prsSkill
- knip-migrationSkill
- ldls-nativeSkill
- ldls-webSkill
- ledger-wallet-cliSkill
- legacy-migrationSkill
- mvvm-architectureSkill
- new-packageSkill
- package-public-apiSkill
- pnpm-resolutionSkill
- prefer-set-hasSkill
- pre-reviewSkill
- react-generalSkill
- rebuild-to-fix-lib-import-errorsSkill
- remove-feature-flagSkill
- run-buildsSkill
- run-e2e-ciSkill
- runner-imagesSkill
- run-testsSkill
- slack-pr-messageSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 25
Desktop: Add an optional property to LLDCoinFamily in apps/ledger-live-desktop/src/renderer/families/types.ts (e.g.
- Very specific: line 26
Mobile: Use the same idea: a typed contract (or generated map like noAssociatedAccountsByFamily) that families can optionally fill.
- Very specific: line 30
Put the component or logic in families/<family>/ (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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.
Files
Coin families contract (Desktop & Mobile UI)
Principle: Coin-specific UI and behavior must live in families/. Generic screens, hooks, and components must not branch on family === "evm" (or any family name). They must use the families contract: optional slots defined in the family type, implemented per family, and consumed via a single lookup (e.g. useLLDCoinFamily(currency.family).SlotName). This keeps generic code family-agnostic and supports modularisation and lazy loading.
Do not do (anti-patterns)
- Generic code (outside
families/<family>/):if (currency.family === "evm")/if (transaction.family === "solana")to render or behave differently.- Coin-specific hooks or logic in shared ViewModels / screens (e.g. Canton onboarding branch inside a generic Scan Device VM).
- Importing a specific coin module (e.g.
@ledgerhq/coin-canton) in generic UI to branch on that coin.
- Exception: Type-narrowing inside a family folder (e.g.
invariant(transaction.family === "bitcoin", "...")infamilies/bitcoin/) is acceptable; the rule applies to generic (shared) code only.
Do (correct pattern)
Define a slot on the contract
- Desktop: Add an optional property to
LLDCoinFamilyinapps/ledger-live-desktop/src/renderer/families/types.ts(e.g.NoAssociatedAccounts?: React.ComponentType<...>). - Mobile: Use the same idea: a typed contract (or generated map like
noAssociatedAccountsByFamily) that families can optionally fill.
- Desktop: Add an optional property to
Implement only in the family
- Put the component or logic in
families/<family>/(e.g.families/hedera/NoAssociatedAccounts.tsx) and add it to the family object (Desktop: the default export offamilies/<family>/index.ts, loaded on demand throughloaders.ts; Mobile: in the generated aggregation if applicable).
- Put the component or logic in
- Use the contract in generic code
- Generic code looks up by family and uses the slot if present, with no
if (family === "hedera"): - Desktop:
useLLDCoinFamily(currency.family).NoAssociatedAccounts→ use it when defined. The hook lives inapps/ledger-live-desktop/src/renderer/families/useLLDCoinFamily.tsand is imported from~/renderer/families. It suspends while the family chunk loads, so it needs a<Suspense>boundary above it. Outside React,importLLDCoinFamily(name)from the same module returns a promise. - Mobile: e.g.
getCustomNoAssociatedAccounts(currency)returning a component from a family map, then pass it to the screen (e.g. asCustomNoAssociatedAccountsin route params).
- Generic code looks up by family and uses the slot if present, with no
Reference example: Scan Device "no associated accounts"
- Contract (Desktop):
apps/ledger-live-desktop/src/renderer/families/types.ts—NoAssociatedAccounts?: React.ComponentType<AddAccountsStepProps>onLLDCoinFamily. - Family implementation:
apps/ledger-live-desktop/src/renderer/families/hedera/NoAssociatedAccounts.tsxandhedera/index.tsexporting it in the family object. - Generic usage (Desktop):
apps/ledger-live-desktop/src/mvvm/features/AddAccountDrawer/screens/ScanAccounts/useScanAccounts.ts:useLLDCoinFamily(currency.family).NoAssociatedAccounts, with no Hedera-specific branch. - Generic usage (Mobile):
useScanDeviceAccountsViewModel.ts:getCustomNoAssociatedAccounts(currency)from~/generated/NoAssociatedAccounts; result passed asCustomNoAssociatedAccountsto the NoAssociatedAccounts screen. Noif (family === "hedera")in the VM.
When you need new coin-specific behavior in a generic flow (e.g. post-add-account navigation, custom empty state): extend the contract (add a new optional slot and document it), implement it in the relevant family folder, and have the generic code only read from the contract. Do not add new if (family === "…") branches in shared UI.
Paths
- Desktop:
apps/ledger-live-desktop/src/renderer/families/: contract intypes.ts, implementations per family, one dynamic import per family inloaders.ts, lookup throughuseLLDCoinFamily; generic code underrenderer/,mvvm/. - Mobile:
apps/ledger-live-mobile/src/families/— family-specific UI and flows; generic code undermvvm/,screens/. Use generated maps or a small helper (e.g.getCustomNoAssociatedAccounts) so generic code never branches on family name.
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
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.

