You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scoping story for a skill that helps existing React apps adopt PatternFly incrementally. Detects custom components that have PF equivalents, suggests replacement paths, and guides migration from other design systems (Bootstrap, MUI, custom) to PF6. Current migration skills assume the app is already on PF — this fills the migrate-to-PF gap for external adopters and teams like Ansible moving from custom UI.
AC:
Research: identify the 10 most common custom component patterns that PF replaces
Research: map Bootstrap and MUI components to PF6 equivalents
Decision: define scope boundaries (what the skill covers vs what's manual)
Output: implementation story with clear AC ready for development
**Eval requirement: **Create a corresponding eval issue (Eval: pf-{skill-name}), link it to this story, and the eval must pass before the skill can be marked Done.
Scoping story for a skill that helps existing React apps adopt PatternFly incrementally. Detects custom components that have PF equivalents, suggests replacement paths, and guides migration from other design systems (Bootstrap, MUI, custom) to PF6. Current migration skills assume the app is already on PF — this fills the migrate-to-PF gap for external adopters and teams like Ansible moving from custom UI.
AC:
Research: identify the 10 most common custom component patterns that PF replaces
Research: map Bootstrap and MUI components to PF6 equivalents
Decision: define scope boundaries (what the skill covers vs what's manual)
Output: implementation story with clear AC ready for development
**Eval requirement: **Create a corresponding eval issue (Eval: pf-{skill-name}), link it to this story, and the eval must pass before the skill can be marked Done.
Jira Issue: PF-4484