appariciojunior/video-editor-skills

figma-roundtrip

Keeps a video motion-graphics kit and its editable Figma boards in sync - the creator designs and tweaks in Figma, Claude ports the changes into the Remotion components and brand tokens, and mirrors code changes back.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
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-use skill before writing to the file). Record the file key and page in CLAUDE.md.

When they say "I changed the boards"

  1. Read each changed board's layers: fonts, weights, sizes, line heights, paddings, positions, which variables they use, corner radius, strokes.
  2. Port the differences into the components and brand.json (tokens first, component code only for layout).
  3. Render preview stills of the same components and compare side by side with the boards.
  4. 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.

同じリポジトリから

関連する Skills

すべての Skills
appariciojunior
コミュニティ

captions

Clean, readable burned-in style subtitles from the verbatim transcript - stutters and fillers removed, spoken slang written correctly, one short line at a time, names checked, every line read by Claude before import into DaVinci Resolve. Use for "subtitles", "captions", "legendas", or when the creator reports wrong words in the captions.

1時間の導入数
1
GitHub Stars
435
更新日
10月23日
appariciojunior
コミュニティ

motion-overlays

Brand motion graphics for creator videos - a Remotion component kit (key phrases, lists, lower thirds, journeys, big words…) timed to the creator's words from a beats sheet, rendered as transparent ProRes and placed on V2+ in DaVinci Resolve, with face-safe and caption-safe layouts. Use for "overlays", "motion graphics", "make it interesting", "graphics", or when overlays cover the face or fight the captions.

1時間の導入数
1
GitHub Stars
435
更新日
10月23日
appariciojunior
コミュニティ

resolve-scripting

Practical DaVinci Resolve Studio scripting knowledge for building edits from code - timelines from a template, frame-exact appends, zoom, grades, custom frame sizes, subtitles, renders, and the traps that silently fail or crash Resolve 21. Use when writing or debugging any script that talks to Resolve.

1時間の導入数
1
GitHub Stars
435
更新日
10月23日
appariciojunior
コミュニティ

rough-cut

Editorial rules for choosing what to keep in talking-head footage (retakes, false starts, spoken notes to the editor, fillers) and the keep-list / moments formats that a planner script turns into frame-exact cuts. Use when deciding a cut, revising one from feedback, or writing keep.json.

1時間の導入数
1
GitHub Stars
435
更新日
10月23日