figma-change-flow

Name: figma-change-flow
Availability: InStock
Author: dadafinger

Applies planning and prototype changes to existing Figma nodes through a repeatable workflow.

Updated May 10, 2026

Search Tags:#workflow #figma #prototype #spec sync #design update #node revision

Ready to run

npx skills add https://github.com/dadafinger/dadafinger-skills --skill figma-change-flow-dadafinger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: figma-change-flow
Source: https://github.com/dadafinger/dadafinger-skills/tree/main/proprium/cursor/skills/figma-change-flow
Command: npx skills add https://github.com/dadafinger/dadafinger-skills --skill figma-change-flow-dadafinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping Figma design files synchronized with updated planning specs is error-prone when done manually, especially when only specific nodes or documentation frames need revision. This Skill provides a repeatable workflow for reflecting spec changes into existing Figma files without rebuilding them from scratch. ## Core Features & Use Cases - Spec-to-Figma Updates: Reflect updated planning specifications into existing Figma nodes and frames. - Targeted Node Revision: Revise specific Figma node URLs rather than regenerating entire files. - Documentation Frame Management: Create or update documentation frames inside a Figma file. - Use Case: After a spec markdown is revised, point the Skill at the affected Figma node URLs and have the changes applied consistently following the shared workflow instructions. ## Quick Start Ask the assistant to apply the updated spec changes to the existing Figma file using the figma-change-flow workflow and provide the target node URLs.

Frequently Asked Questions about figma-change-flow

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

FAQPage Schema

How do I update existing Figma nodes from a revised spec?▼

Provide the updated spec content and the target Figma node URLs, then follow the figma-change-flow workflow. The Skill loads its source-of-truth instructions and applies the changes to the existing nodes rather than creating a new file.

Can I revise only specific Figma node URLs instead of the whole file?▼

Yes, the workflow is designed for targeted revision of specific node URLs within an existing Figma file. You identify the nodes to change and the Skill applies updates only to those targets.

Does this Skill create new Figma files from scratch?▼

No, it focuses on modifying existing Figma nodes and creating or updating documentation frames within an existing file. New file generation from html or md specs is handled by a separate planning-figma workflow.

Where are the actual workflow instructions stored?▼

The Cursor entry point delegates to the source-of-truth file at agent-shared/skills/figma-change-flow/SKILL.md. That file is read at execution time and its directives govern the update process.

When should I not use the Figma change flow?▼

Avoid it when you need to generate a brand-new Figma frame structure from html or md specs, since this workflow assumes existing nodes. It is also unsuitable for read-only spec format reviews of Figma files.