Verwendung
- Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
- Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
- Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/appariciojunior/video-editor-skills --skill figma-roundtripVor dem Start
- Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
- Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.
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.
