layout-convergence

Normalize auto-layout and rebind background tokens in Figma screens.

Updated Apr 19, 2026

Search Tags:#layout #convergence #spacing #autolayout #design-systems #background-ownership

Ready to run

npx skills add https://github.com/mayzhangmin/ucd-figma-skills-playground --skill layout-convergence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: layout-convergence
Source: https://github.com/mayzhangmin/ucd-figma-skills-playground/tree/main/skills/layout-convergence
Command: npx skills add https://github.com/mayzhangmin/ucd-figma-skills-playground --skill layout-convergence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Screen drift after major rebuilds is common; this skill polishes spacing, background ownership, auto-layout, and container structure without reopening component choices so the UI aligns with reference screenshots.

Core Features & Use Cases

Lock the semantic scope before edits to ensure component families and wording remain stable
Audit ownership by layout layer: page wrapper, section container, content stack, and component internals
Normalize auto-layout and apply hug/fill principles to reduce pixel drift
Rebind background tokens to the correct owner wrapper without altering component internals
Perform targeted convergence passes to fix one aspect at a time and verify against the reference

Quick Start

Run a convergence pass on the target screen to lock the semantic scope, audit ownership, and normalize auto-layout before pixel tuning.

Frequently Asked Questions about layout-convergence

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

FAQPage Schema

How do I fix Figma layout drift without changing component families?▼

Fix Figma layout drift by running convergence passes that polish auto-layout, spacing, and container ownership while locking the semantic scope. This aligns the screen to the reference without requiring a full component migration.

Why does my Figma screen drift from the reference after an auto-layout rebuild?▼

Screen drift usually happens because auto-layout hug/fill principles and background token ownership layers were normalized incorrectly during the rebuild. Auditing ownership by layout layer and rebinding background tokens resolves the pixel drift.

What's the best way to normalize auto-layout and fix background ownership in Figma?▼

Normalize auto-layout by auditing ownership layers from page wrapper to component internals, applying hug/fill principles, and rebinding background tokens to the correct owner wrapper without altering component internals.

Can I fix spacing and container structure without reselecting Figma components?▼

Yes, you can polish spacing and container structure without reselecting components by locking the semantic scope before edits. This ensures component families remain stable while you normalize auto-layout and apply token binding.

When should I use a targeted convergence pass instead of a full Figma migration?▼

Use a targeted convergence pass when a Figma screen is largely built but drifts from the reference due to auto-layout or background ownership issues. It fixes one aspect at a time without reopening component choices.