Under plugins/patternfly/<plugin-name>/skills/. For example, a React testing skill goes in plugins/patternfly/pf-react/skills/pf-my-skill/SKILL.md.
- Fork this repo (
ai-helpers) instead - Your PF skills now live under
plugins/patternfly/— the internal structure is the same - If you had an open PR on the old repo, re-target it here. See MIGRATION.md for the full timeline.
No. The PatternFly contributions section is self-contained. PF PRs are reviewed by PF maintainers — you don't interact with UXD tooling at all.
PatternFly is part of the UXD organization. The repo hosts skills for all UXD teams — PatternFly is the largest and most visible, but not the only one. Your PF skills are clearly separated under plugins/patternfly/ with their own maintainers, labels, and review process.
Most PF skills don't require the MCP server — they work with local files and project context. Skills that reference PF documentation will still work but may produce less specific output. To install the MCP server for full functionality:
claude mcp add pf-mcp -- npx -y @anthropic/patternfly-mcp@latestYou don't need to add labels manually. The auto-label workflow applies labels based on which files you changed. Issue templates also auto-apply routing labels.
make scaffold PLUGIN=<plugin-name> SKILL=<skill-name>This creates the directory and a starter SKILL.md with correct frontmatter. See CONTRIBUTING-SKILLS.md for the full guide.
make scaffold-plugin PLUGIN=<name> DESC="what it helps people do"Then add the plugin to both marketplace configs and open a PR. See CONTRIBUTING.md for details.
make validateThis runs manifest validation (plugin-level plugin.json parity between .claude-plugin/ and .cursor-plugin/, JSON validity, name consistency) and skill integrity checks. Marketplace configs (marketplace.json) are validated independently — they can differ between platforms. If make validate passes, your PR will pass CI.
Do not run make docs or scripts/generate-plugins-md.sh in a contribution PR. After merge to main, CI regenerates PLUGINS.md, the README plugin table and badge counts, the CONTRIBUTING-SKILLS plugin table, and per-plugin READMEs.
Your skill likely contains tool-specific references. Skills must be tool-agnostic — avoid mentioning "Claude," "Cursor," or tool-specific APIs. Use "Assistant:" instead of "Claude:" in examples. See the security rules and quality checklist.
- Skill — a task that produces a result ("generate tests," "audit accessibility"). Invoked explicitly.
- Agent — domain knowledge the AI follows automatically ("always use these coding standards"). Loaded by context.
See CONTRIBUTING-SKILLS.md for the full explanation.