Use when generating or editing an Nx version plan in .nx/version-plans/ — the bump type must always be `patch`, one package per file.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
When generating an Nx version plan in .nx/version-plans/, the bump type
in the frontmatter MUST always be patch — never minor, never major —
regardless of the nature of the change (new feature, new component, new prop,
breaking change, refactor, fix, etc.).
---
'@ledgerhq/lumen-ui-rnative': patch
---
feat(Select): add render prop and SelectButtonTrigger
minor from feat(...) commits.major from breaking changes.Each release plan file MUST list a single package in its frontmatter — never
group multiple packages in the same file. If a change affects N packages,
create N separate version-plan-<timestamp>-<pkg>.md files, one per package.
---
'@ledgerhq/lumen-ui-react': patch
---
feat(Select): add render prop and SelectButtonTrigger
---
'@ledgerhq/lumen-ui-rnative': patch
---
feat(Select): add render prop and SelectButtonTrigger
Do NOT do this:
---
'@ledgerhq/lumen-ui-react': patch
'@ledgerhq/lumen-ui-rnative': patch
---
Each version-plan file names the package for the paths that changed. This is the single source for the mapping; other skills link here rather than restating it.
| Path | Package |
|---|---|
libs/ui-react/ | @ledgerhq/lumen-ui-react |
libs/ui-rnative/ | @ledgerhq/lumen-ui-rnative |
libs/design-core/ | @ledgerhq/lumen-design-core |
libs/utils-shared/ | @ledgerhq/lumen-utils-shared |
libs/lint-plugin/ | @ledgerhq/lumen-lint-plugin |
Filename convention: version-plan-<timestamp>-<pkg-slug>.md, where the slug is
the short name (ui-react, ui-rnative, utils-shared, …).
Any change to production source under libs/*/src/ requires a plan. Exemptions
are defined authoritatively in nx.json under
release.versionPlans.ignorePatternsForPlanCheck: *.test.* / *.spec.*,
*.stories.*, *.md, *.mdx, *.figma.@(ts|tsx), tsconfig*.json, eslint
configs, jest.config.*, test-setup.*, *.snap, .storybook/**. A PR
touching only these needs no plan.
internals/* is outside release.projects, so a PR touching only internals/*
never needs a plan.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Creates 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.
The English summary is being prepared. Showing the original description.
Use 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.
The English summary is being prepared. Showing the original description.
Use 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.
The English summary is being prepared. Showing the original description.
Use when writing or editing Storybook MDX docs (*.mdx) — the two-tab Overview/Implementation structure, story-backed `<Source>` examples, and doc table guidelines.
The English summary is being prepared. Showing the original description.
Use when creating or editing Storybook stories (*.stories.tsx, React or React Native) — story layout, controls, and export naming conventions.
The English summary is being prepared. Showing the original description.
Use 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.
The English summary is being prepared. Showing the original description.