ledger-live: Skill for Claude Code

.agents/skills/mvvm-architecture/SKILL.md

mvvm-architecture is a skill for Claude Code, Codex from LedgerHQ/ledger-live. It costs 48 tokens per session (862 once invoked), scanned A, original, MIT.

A set of rules for building desktop and mobile app features with the Model-View-ViewModel, or MVVM, pattern. It organizes feature code into areas such as screens, reusable components, hooks, utilities, and integration tests.

In plain words
What is it for?
Use it when planning, reviewing, or developing new TypeScript or TSX features in those apps, especially when deciding where screens, components, hooks, utilities, and tests belong.
Why use it?
It gives new code a consistent structure and makes it easier to find, reuse, and test parts of a feature across the Ledger Live desktop and mobile apps.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is LedgerHQ/ledger-live's own configuration. It tells Claude Code and Codex how to work on ledger-live itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ledger-live configures →

Reuse

Borrowing it

Nothing to install: this file belongs to LedgerHQ/ledger-live. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/LedgerHQ/ledger-live/develop/.agents/skills/mvvm-architecture/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/LedgerHQ/ledger-live

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mvvm-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/ledgerhq/ledger-live/mvvm-architecture/github.svg)](https://agentmods.dev/skills/ledgerhq/ledger-live/mvvm-architecture)
Your own site
<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/mvvm-architecture"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/mvvm-architecture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mvvm-architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/mvvm-architecture"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/mvvm-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 862 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00862
Opus 5 $0.00024 $0.00431
Sonnet 5 $0.00010 $0.00172
Haiku 4.5 $0.00005 $0.00086

Measured 10d ago against content hash 955ed85af0de, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mvvm-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/mvvm-architecture/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MVVM Architecture

The new standard for desktop and mobile apps

  • New code for ledger-live-desktop and ledger-live-mobile must go into src/mvvm/
  • Eventually no feature code within these apps will live outside of src/mvvm
  • New features, screens, components, hooks, and utilities belong in src/mvvm/
  • Code changes with src/mvvm must conform to these mvvm patterns
  • Code reviews enforce strict adherence

Folder Structure

src/mvvm/
├── features/
│   └── FeatureName/
│       ├── __integrations__/    ← mandatory integration tests
│       ├── components/          ← reusable UI across screens
│       ├── screens/             ← individual screen folders
│       ├── hooks/               ← feature-specific hooks
│       └── utils/               ← feature-scoped utilities
├── components/                  ← global shared UI
├── hooks/
└── utils/

Feature Folder Responsibilities

  • components/ gathers reusable UI elements across multiple screens.
  • screens/ contains individual screen folders and their private building blocks.
  • hooks/ contains feature-specific reusable hooks.
  • utils/ contains feature-scoped utilities.

Nesting Guidelines

  • Place elements inside the closest folder matching their reuse scope.
  • Screen-specific building blocks stay inside the screen folder.
  • Feature-level components belong to FeatureName/components/.
  • Global shared UI belongs to src/mvvm/components/.

Component & File Patterns

  • Each component in its own folder with index.tsx as entry.
  • ViewModel hooks always named use<ComponentName>ViewModel.ts.
  • Support files alongside: types.ts, styles.ts.
  • Use List / Detail naming for multi-view workflows.
  • Utilities stay in utils/, separate from component folders.

ViewModel Pattern

Components needing external logic use Container → ViewModel → View:

  • The ViewModel produces data and handlers.
  • The View receives everything via props — no direct hook calls to external systems.

Read the full file on GitHub · 97 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 97 lines · 48 tokens per session scan A 955ed85af0de

Subscribe to this mod's changes

mvvm-architecture is a skill published in the GitHub repository LedgerHQ/ledger-live (617 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 862 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

animate-expo

Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…

emilkowalski/skills · 112 tokens

leanback-to-compose-tv-migration

Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…

android/skills · 151 tokens

maui-data-binding

Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or…

dotnet/skills · 180 tokens

migrate-xml-views-to-jetpack-compose

Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android…

android/skills · 98 tokens

web-haptics

Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.

lochie/web-haptics · 47 tokens

axiom-swiftui

Use when building, fixing, or improving ANY SwiftUI UI — views, navigation, layout, animations, performance, architecture, gestures, debugging, iOS 26 features.

CharlesWiltgen/Axiom · 41 tokens