How does it help during the brainstorming phase?

During brainstorming, the skill identifies which specific One-UI tools (like common-table or signal-store) are required based on the legacy components you are migrating.

Does this skill provide implementation checklists?

Yes, it includes detailed checklists for various tools to ensure that developers follow best practices, such as avoiding BehaviorSubjects in favor of signals.

Which frameworks is this migration planning optimized for?

While the principles can be adapted, it is highly optimized for Angular-based migrations involving Signal Stores, Transloco, and One-UI shared components.

What is the One-UI Migration Planning skill?

It is a specialized Claude Code skill that helps developers plan the migration of legacy codebases into the One-UI design system using structured workflows.

One-UI Migration Planning

Name: One-UI Migration Planning
Author: Michael0520

byMichael0520

Design Tools

Streamlines the architectural planning of legacy UI migrations into the One-UI ecosystem with automated tool mapping.

About

The One-UI Migration Planning skill is designed to bridge the gap between legacy frontend architectures and modern One-UI standards. By integrating with specialized 'superpowers' workflows, it ensures that every migration plan—from brainstorming to task execution—is grounded in specific tool requirements. It automatically maps legacy components like forms, tables, and dialogs to their modern One-UI equivalents, providing detailed verification checklists for Signal Stores, Form Builders, and validation logic. This skill is essential for maintaining technical compliance and architectural consistency during complex UI refactoring projects.

Key Features

Automated mapping of legacy components to One-UI documentation
Standardized task templates for domain, feature, and UI layers
Comprehensive tool reference requirements for consistent migrations
Integration with superpower brainstorming and plan-writing workflows
Technical verification checklists for Signal Store and Form implementation
0 GitHub stars

Use Cases

Drafting comprehensive implementation plans for complex feature migrations
Ensuring technical compliance during the architectural design phase of a UI rewrite
Refactoring legacy Angular forms and tables to modern One-UI standards

About

Key Features

Automated mapping of legacy components to One-UI documentation
Standardized task templates for domain, feature, and UI layers
Comprehensive tool reference requirements for consistent migrations
Integration with superpower brainstorming and plan-writing workflows
Technical verification checklists for Signal Store and Form implementation
0 GitHub stars

Use Cases

Drafting comprehensive implementation plans for complex feature migrations
Ensuring technical compliance during the architectural design phase of a UI rewrite
Refactoring legacy Angular forms and tables to modern One-UI standards