southleft/skills-for-figma

setup-design-tokens-figma

Bootstrap a complete design-token system in Figma in one atomic step — create a variable collection, its modes (e.g.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/southleft/skills-for-figma --skill setup-design-tokens-figma

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

setup-design-tokens-figma — atomic token-system bootstrap

Create a variable collection + modes + all variables in a single use_figma call. This is the fastest way to stand up a new token system (or a new collection within one). Because it runs as one atomic script, either everything is created or nothing is (failed scripts apply no changes).

Skill boundaries

  • `use_figma` rules — load the official `figma-use` skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level await + return (no IIFE, no figma.closePlugin(); console.log is not returned), inputs inlined as const at the top of each script, colors in 0–1 range, load fonts before any text op, await figma.getNodeByIdAsync(...), and atomic errors (a failed script applies nothing — read the error, fix, retry).
  • Incremental CRUD / batch edits to an existing system → manage-variables-figma.
  • Sync from a code token file → import-tokens-figma.

Workflow

  1. Agree the v1 scope. List the collection name, the modes (first one is the default), and the

full token set with per-mode values. Lock this before writing — it's much cheaper than editing afterward.

  1. Fill the constants in `scripts/setup-tokens.js`: COLLECTION_NAME,

MODES, TOKENS (values keyed by mode name), and optional per-variable SCOPES.

  1. Run via use_figma (skillNames: "setup-design-tokens-figma"). It returns

{ collectionId, modes, created, errors }.

  1. Validate with get_variable_defs or the export-tokens-figma read script, then screenshot if

you also created swatches.

Notes

  • Two-tier systems: create primitives (raw values) with this skill, then create semantic

tokens that alias them using import-tokens-figma (which has the alias pass) or manage-variables-figma. Keep primitives single-mode and put theming on the semantic layer.

  • Set scopes: the default ALL_SCOPES clutters every property picker. Pass SCOPES for the

surfaces each token belongs to (FRAME_FILL/SHAPE_FILL for backgrounds, TEXT_FILL for text, GAP for spacing, CORNER_RADIUS for radii, WIDTH_HEIGHT for sizing).

  • Keep one bootstrap per collection. Multiple collections = multiple runs.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
southleft
커뮤니티

analyze-component-set-figma

Analyze a Figma COMPONENTSET as a state machine for code generation — extract variant axes (state/size/etc.), map state variants to CSS pseudo-classes (hover→:hover, focus→:focus-visible, disabled→:disabled, error→[aria-invalid]), and compute per-variant visual diffs (only what changes per state). Use when generating an interactive component from a Figma variant set — triggers: 'analyze this component set', 'turn these variants into CSS states', 'generate a button/input/checkbox from Figma varia

설치 수
1
GitHub Stars
14
업데이트
6월 1일
southleft
커뮤니티

annotations-figma

Read and write designer annotations on Figma nodes — node-level design specs that pin properties (fills, width, fontSize, etc.) and carry plain or markdown notes. Use when the user wants to document or inspect interaction specs, animation timings, easing, accessibility requirements, or implementation notes attached directly to a node. Triggers: 'add an annotation', 'annotate this node/component', 'read the annotations on…', 'what specs are pinned to this element', 'list annotation categories', '

설치 수
1
GitHub Stars
14
업데이트
6월 1일
southleft
커뮤니티

audit-accessibility-figma

Deep accessibility scorecard for a single Figma component or component set — state coverage (default/hover/focus/disabled/error/active/loading), focus-indicator quality and contrast, non-color state differentiation, target size, annotation completeness, and color-blind simulation (protanopia/deuteranopia/tritanopia), all rolled into per-category 0–100 scores and prioritized recommendations. Use when the user wants to vet ONE component before shipping it: triggers 'audit this component', 'accessi

설치 수
1
GitHub Stars
14
업데이트
6월 1일
southleft
커뮤니티

check-design-parity-figma

Compare a Figma node's actual specs against a code spec (the values your component renders) and get a 0–100 parity score, a list of discrepancies, and fix suggestions. Use to detect design-to-code DRIFT: triggers 'check design parity', 'does my code match the Figma', 'compare this component to the design', 'is my implementation faithful', 'find differences between design and code', 'verify the build matches Figma', 'design QA against code', 'parity score'. Reads the node's visual / typography /

설치 수
1
GitHub Stars
14
업데이트
6월 1일