Claude Skills by LedgerHQ

github.com/LedgerHQ

17 skillsA× 170 installs83 views

Code ConnectACreates and maintains Figma Code Connect files (`*.figma.tsx`) that map Figma components to code via the parser-based `figma.connect()` API. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.tsx files.designgoreactVotes: 0GitHub stars: 23
Component AnatomyAUse when creating, naming, or placing a file or folder in libs/*, or when modifying or adding a file to an existing component (even when the barrel isn't touched) — component vs utility naming, the one-responsibility-per-file layout, when a folder needs an `index.ts` barrel (public API only), and the required set of files a component needs per lib. Load this before scaffolding or restructuring a component so the layout matches the codebase.developmentreacttestingVotes: 0GitHub stars: 23
Component ArchitectureAUse when designing or changing a component's public API, its composition, or its state model in libs/ui-react or libs/ui-rnative — layering (core vs internal vs primitives), BaseProps/Props splits, converting a component to compound / changing its composition with createSafeContext, controlled/uncontrolled state, prop-naming conventions, and cross-platform API parity. Load this before shaping a new component, changing its props, or refactoring its composition.developmenttypescriptgoVotes: 0GitHub stars: 23
Component MdxAUse when writing or editing Storybook MDX docs (*.mdx) — the two-tab Overview/Implementation structure, story-backed `<Source>` examples, and doc table guidelines.designreactdocumentationVotes: 0GitHub stars: 23
Component StoriesAUse when creating or editing Storybook stories (*.stories.tsx, React or React Native) — story layout, docs source type, controls, and export naming conventions.documentationtypescriptreactVotes: 0GitHub stars: 23
Component StylingAUse when building or styling a component in libs/ui-react or libs/ui-rnative — the cross-platform styling principles, plus routing to the platform mechanics: Tailwind + cva + cn on web, useStyleSheet + themeJS + lx on React Native. Load this before writing component styles.designreactgitVotes: 0GitHub stars: 23
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Component TestingAUse when writing or editing component tests in libs/ui-react or libs/ui-rnative — shared structure and coverage conventions, plus the per-platform runner: Vitest + React Testing Library on web, Jest + React Native Testing Library on RN. Load this before writing tests.testingreactnodeVotes: 0GitHub stars: 23
Context7AUse when researching external libraries/frameworks (React, Radix, Tailwind, etc.) — reach for the Context7 MCP to get up-to-date docs. Not for internal codebase or design-system-token questions.documentationreactapiVotes: 0GitHub stars: 23
Disabled ContextAUse when a component has a `disabled` state/variant, or when building a compound component that owns a disabled state — inherit/provide it via the shared disabled context so state flows from parent to sub-components.developmentVotes: 0GitHub stars: 23
Figma To CodeAUse when implementing or updating a component from a Figma link — how to turn the Figma design variables into code tokens, on both platforms: Tailwind classnames for libs/ui-react and themeJS (`t.*`) paths for libs/ui-rnative. For the full token catalogues and styling mechanics, see component-styling.designgoreactVotes: 0GitHub stars: 23
Figma Token SyncASync processed CSS design tokens with JavaScript theme objects for React Native. Use when aligning tokens after Figma sync, checking token consistency, or updating JS theme files manually.developmentjavascripttypescriptVotes: 0GitHub stars: 23
NxANx workspace commands and guidelines for running tasks, generators, and using Nx MCP toolstoolsVotes: 0GitHub stars: 23
Open PrAOpen a PR from the current branch to `main`: commit if needed, ensure an Nx version plan exists, push, and create the PR with a filled-in description and testing steps. Run only when the user explicitly asks to open/create a PR.documentationgobashVotes: 0GitHub stars: 23
Pr ReviewAReview a PR or the current branch for a Lumen design-system change — routes each changed file to React (web/Tailwind) or React Native (useStyleSheet) guidelines, checks the Nx version plan, and reports a flat, severity-scored finding list. Use when the user asks to review a PR, review code changes, check a branch, do a local code review, or provides a GitHub PR URL.designgobashVotes: 0GitHub stars: 23
Release Notes SlackATurn raw Lumen release content (a dump of the LedgerHQ/lumen GitHub Releases page) into one minimalist Slack announcement, drafted to #lumen-releases. Use whenever the user pastes one or more `@ledgerhq/lumen-*` package releases, a chunk of the Releases page, or asks to "announce", "format", "post", or "write release notes / a Slack message" for new Lumen versions. Trigger it even when the user just drops the raw release text with no instructions, or says things like "new Lumen release", "for...documentationrustgoVotes: 0GitHub stars: 23
Release PlanAUse when generating or editing an Nx version plan in .nx/version-plans/ — the bump type must always be `patch`, one package per file.developmentreactVotes: 0GitHub stars: 23
Lumen Adoption ReportAUse when asked to check Lumen version adoption across consumer repos, generate the Lumen adoption report, or find which repos are behind on a Lumen package version, or who owns those repos.toolsbashgitVotes: 0GitHub stars: 23