design-migrate

To migrate legacy CSS styles to the --zaq-* token system, you can use this Skill to parse existing styles, apply new token-based styles, and verify changes. It converts legacy ZAQ web UI styling to the modern token system for consistency.

Yes, you can perform a design-led CSS migration using a Figma frame URL. The Skill supports design-led migrations, existing file audits, and full codebase sweeps to apply the new --zaq-* token-based styling system.

Yes, you need Elixir and Phoenix knowledge along with familiarity with ZAQ UI structure to use this CSS conversion tool. The Skill requires this technical background to accurately parse and migrate legacy styles to the token system.

The best way to enforce styling rules for UI components during a codebase sweep is using this Skill, which enforces role-based constraints for buttons, forms, modals, and tables. It provides a human-validation table to review and approve changes before applying them.

Yes, this migration tool supports incremental updates for large codebases. It maintains UI integrity during large-scale migrations by allowing you to run targeted file migrations and verify changes progressively before full application.

You should use a token system for UI modernization instead of legacy CSS to ensure styling consistency and efficiency across your application. The --zaq-* token system enforces role-based constraints for chrome, buttons, and forms to maintain UI coherence.