Use 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.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
npx nx run adoption-tool:report # full markdown table (GitHub/PR/terminal)
npx nx run adoption-tool:report-summary # Slack-ready bulleted summary instead
npx nx run adoption-tool:report-json # machine-readable snapshot (also always written to report.json)
npx nx run adoption-tool:owners # maps each consumer repo to its catalog team / code owners (readable summary)
npx nx run adoption-tool:discover # diffs data/consumers.json against a fresh code search, never writes it
Reports cover production consumers only. Append --status internal-tool
or --status all when the user asks about internal tools or every consumer.
Logic and details live in
internals/adoption-tool — read its
README and source rather than duplicating them here. Use report for a full
table, report-summary for Slack — present whichever one printed as-is,
don't reformat it yourself. A non-zero exit means some repos couldn't be
read (shown as unresolved) — say so rather than presenting the table as
complete. For a repo discover finds, hand-edit
internals/adoption-tool/data/consumers.json (with its status) if it is a
real consumer, or internals/adoption-tool/data/ignored-repos.json (with a
reason) if it is a prototype or experiment.
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.