figma-sync-handoff

Flag Figma library or Code Connect follow-up needs after UI-kit component work.

2|Updated Dec 2, 2024
One-click install
npx skills add https://github.com/TechsioCZ/new-engine --skill figma-sync-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-sync-handoff
Source: https://github.com/TechsioCZ/new-engine/tree/main/libs/ui/skills/figma-sync-handoff
Command: npx skills add https://github.com/TechsioCZ/new-engine --skill figma-sync-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing design handoff governance by flagging when Figma libraries or Code Connect follow-ups are needed after UI-kit component work, without editing Figma or triggering MCP actions.

Core Features & Use Cases

  • Reminder-driven governance for Figma library or Code Connect follow-ups after component work.
  • Reference to the official workflows, pointing to the component-to-figma skill for the correct procedure.
  • Non-destructive process that never edits Figma or runs Figma MCP actions; records follow-ups as reminders.

Quick Start

Review the suggested reminder path and reference the official component-to-figma workflow for follow-up steps.

Frequently Asked Questions about figma-sync-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track Figma library changes after UI-kit component work?

To track Figma library changes after UI-kit component work, you can generate reminders that flag necessary follow-ups. This approach records governance needs without directly editing Figma libraries or triggering automated actions.

What is the best way to manage Code Connect follow-ups without editing Figma?

Managing Code Connect follow-ups without editing Figma involves flagging necessary mapping updates as reminders. This governance method references official component-to-figma workflows to satisfy tracking requirements while avoiding direct Figma modifications.

Can I use reminders for design handoff governance instead of direct Figma edits?

Yes, you can use reminders for design handoff governance instead of direct Figma edits. This method flags when Figma libraries or Code Connect mappings need attention after component work, ensuring reviews happen without automated actions.

Does this approach run Figma MCP actions automatically?

No, this approach does not run Figma MCP actions automatically. It is a non-destructive process that records follow-up needs as reminders, avoiding any automated Figma actions or direct library edits.

When do I need to flag Code Connect mapping updates?

You need to flag Code Connect mapping updates when UI-kit component changes affect existing mappings. Generating a reminder ensures the official component-to-figma workflow is referenced for the correct follow-up procedure.

Why use reminders for Figma library follow-ups instead of direct edits?

Using reminders for Figma library follow-ups prevents unintended automated edits. This governance requirement ensures that changes affecting public UI-kit visuals are reviewed through the official component-to-figma workflow.