사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/appariciojunior/video-editor-skills --skill figma-roundtrip시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Figma ↔ motion kit
Creators design better in Figma than in prompts. Keep every kit component mirrored as an editable board and let them edit there.
Set up once
- A page in their brand file (e.g. "Claude - Editable") with a section per kit version ("Motion kit v1", "Vlog kit v1").
- One board per component at the video's frame size, real copy, every layer named.
- Colours and type bound to variables (a "Motion" collection: ink, paper, accent/highlighter, greys; font sizes and paddings as numbers) so a colour change is one edit.
- Use the Figma MCP (load its
figma-useskill before writing to the file). Record the file key and page in CLAUDE.md.
When they say "I changed the boards"
- Read each changed board's layers: fonts, weights, sizes, line heights, paddings, positions, which variables they use, corner radius, strokes.
- Port the differences into the components and
brand.json(tokens first, component code only for layout). - Render preview stills of the same components and compare side by side with the boards.
- List what changed ("title Light 120 → Regular 108, padding 64 → 80, label now uppercase mono").
When the kit changes in code
(e.g. a narrow-frame layout, a caption-safe band) update the matching boards so the two never drift, or tell the creator which boards are now out of date.
Learned taste (ask your creator, these are examples)
Light/regular at big sizes, never heavy bold; monospace light uppercase labels; 80 px padding; lots of space; one smooth move per element; no device mockups (they add little); prefer text overlays and personal notes.
