Rename plugin directories from pf-* prefixed names to descriptive, domain-based names so users browsing the marketplace immediately understand what each plugin does.
Before
After
pf-react
react
pf-styling
design-tokens
pf-a11y
a11y
pf-figma
figma
pf-workflow
issue-management + repo-management
The pf- prefix moves to the skill level, where it distinguishes PatternFly-specific skills from generic ones. Plugin names become domain-only.
This is a prerequisite for the GitLab UXD AI helpers fork — domain-based plugin names let both repos contribute skills to the same plugin directory without merge conflicts. With pf- on plugins, the GitLab fork would need duplicate plugins (e.g. pf-a11y AND a11y), which fragments the user experience.
PR: https://github.com/patternfly/ai-helpers/pull/new/rename-plugins-to-domain-names
Acceptance criteria:
-
All plugin dirs use domain-based names (no pf- prefix on plugin dirs)
-
pf-workflow is split into issue-management and repo-management
-
Marketplace configs, contributing docs, and auto-generated docs are updated
-
No skills are lost in the rename — all existing skills land in the correct new plugin
Jira Issue: PF-3908
Rename plugin directories from
pf-*prefixed names to descriptive, domain-based names so users browsing the marketplace immediately understand what each plugin does.Before
After
pf-react
react
pf-styling
design-tokens
pf-a11y
a11y
pf-figma
figma
pf-workflow
issue-management + repo-management
The
pf-prefix moves to the skill level, where it distinguishes PatternFly-specific skills from generic ones. Plugin names become domain-only.This is a prerequisite for the GitLab UXD AI helpers fork — domain-based plugin names let both repos contribute skills to the same plugin directory without merge conflicts. With
pf-on plugins, the GitLab fork would need duplicate plugins (e.g.pf-a11yANDa11y), which fragments the user experience.PR: https://github.com/patternfly/ai-helpers/pull/new/rename-plugins-to-domain-names
Acceptance criteria:
All plugin dirs use domain-based names (no
pf-prefix on plugin dirs)pf-workflowis split intoissue-managementandrepo-managementMarketplace configs, contributing docs, and auto-generated docs are updated
No skills are lost in the rename — all existing skills land in the correct new plugin
Jira Issue: PF-3908