跳到正文
cccskills
免费在 GitHub 公开

figma-to-code

Use 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.

中文简介正在准备中。当前显示原文说明。

集成工具Figma
查看安装方法

包含的文件(1)

  • SKILL.md3.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Figma → code

Use the Figma MCP server to read the design. This skill covers only the variable → token derivation — the part that is specific to extracting from Figma. For the full token lists, cva, useStyleSheet and the rest, see component-styling.

Route by the lib you're implementing in (see the Libraries table in AGENTS.md): web → the Tailwind mapping; React Native → the themeJS mapping.

React web (libs/ui-react) — Figma variable → Tailwind class

Combine the Tailwind prefix for the CSS property with the unique part of the token name (the segment after the last hyphen of the CSS variable).

Figma showsPrefixWriteNot
background-color: var(--background-base)bg-bg-basebg-background-base
color: var(--text-on-accent)text-text-on-accenttext-text-on-accent
border-color: var(--border-muted)border-border-mutedborder-border-muted
padding: var(--spacing-4)p-p-4p-spacing-4
border-radius: var(--radius-lg)rounded-rounded-lgrounded-radius-lg
border-width: var(--border-width)borderborderborder-width
border-width: var(--border-width-active)borderborder-2border-width-active
  • Typography: Figma shows a style-name comment like /* body/3 */. No prefix — replace / with -: body-3.
  • Drop shadow: Figma shows /* box-shadow/sm */. Prefix shadow-, take the unique part after the last -: shadow-sm. Values: shadow-sm…shadow-2xl.

React Native (libs/ui-rnative) — Figma variable → themeJS path

There are no classnames on RN. The same Figma variable maps to a path on the t object inside useStyleSheet((t) => …) (same token vocabulary as web, JS object shape — see component-styling/references/rnative.md).

Figma showsthemeJS path
var(--background-base)t.colors.bg.base
var(--text-on-accent)t.colors.text.onAccent
var(--border-muted)t.colors.border.muted
var(--spacing-4)t.spacings.s4
var(--radius-lg)t.borderRadius.lg
typography /* body/3 */t.typographies.body3
  • Colours are nested under a category key (bg / text / border), and kebab segments become camelCase keys (on-accent → onAccent).
  • Spacings and sizes are s-prefixed by pixel value: --spacing-4 → t.spacings.s4, --spacing-16 → t.spacings.s16; sizes likewise (t.sizes.s112, plus t.sizes.full for 100%).
  • Border radius keys are named, not pixel values: none, xs, sm, md, lg, xl, 2xl, full (so t.borderRadius['2xl']).
  • Typography keys are camelCase: body/3 → t.typographies.body3, body/2-semi-bold → t.typographies.body2SemiBold.
  • Source of truth for the key sets: libs/design-core/src/lib/themes/js/primitives/primitives.others.ts (spacings, sizes, borderRadius) and the per-brand theme.*.ts colour objects. Confirm a key there rather than inventing one.

When a Figma size has no token (both platforms)

  1. Use the closest available token (e.g. 112 for Figma's 108, 96 for 90).
  2. Document the deviation in a code comment.
  3. Consider requesting the token be added if it's needed often.
// ✅ Web — closest token, documented
<Tile className='w-112' size='md' /> // 112px (closest to Figma's 108px)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。

LedgerHQ/lumen232026年10月17日 更新

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.

中文简介正在准备中。当前显示原文说明。

LedgerHQ/lumen232026年10月17日 更新

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.

中文简介正在准备中。当前显示原文说明。

LedgerHQ/lumen232026年10月17日 更新

Use when writing or editing Storybook MDX docs (*.mdx) — the two-tab Overview/Implementation structure, story-backed `<Source>` examples, and doc table guidelines.

中文简介正在准备中。当前显示原文说明。

LedgerHQ/lumen232026年10月17日 更新

Use when creating or editing Storybook stories (*.stories.tsx, React or React Native) — story layout, controls, and export naming conventions.

中文简介正在准备中。当前显示原文说明。

LedgerHQ/lumen232026年10月17日 更新

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.

中文简介正在准备中。当前显示原文说明。

LedgerHQ/lumen232026年10月17日 更新

查看 LedgerHQ 的全部技能

报告此技能的问题