figma-icon-finder
Identify PatternFly icons in Figma mockups and provide the correct React import statements. Use when implementing a design from Figma, verifying icon usage in a prototype, or finding the correct icon imports for React components. Requires Figma MCP.
Best use case
figma-icon-finder is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Identify PatternFly icons in Figma mockups and provide the correct React import statements. Use when implementing a design from Figma, verifying icon usage in a prototype, or finding the correct icon imports for React components. Requires Figma MCP.
Teams using figma-icon-finder should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/figma-icon-finder/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How figma-icon-finder Compares
| Feature / Agent | figma-icon-finder | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Identify PatternFly icons in Figma mockups and provide the correct React import statements. Use when implementing a design from Figma, verifying icon usage in a prototype, or finding the correct icon imports for React components. Requires Figma MCP.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Figma Icon Finder
Analyze Figma design mockups to identify PatternFly icons and provide the correct import statements for React implementation.
## Workflow
### Step 1: Get the design image
- If `$ARGUMENTS` contains an image file path (`.png`, `.jpg`, `.jpeg`, `.webp`): read and analyze it
- If `$ARGUMENTS` contains a Figma URL: ask the user to provide a screenshot
- If no arguments: ask the user for a screenshot path
### Step 2: Load icon reference
Read `references/common-icons.md` for the full categorized icon list with visual descriptions and usage patterns.
### Step 3: Analyze the design
Examine the image and identify all icons. For each icon:
1. Note its visual characteristics (shape, style, filled vs outlined)
2. Consider its context (where it appears, what action it represents)
3. Match to PatternFly icons using the reference and visual similarity
4. If uncertain, list candidates with confidence levels
### Step 4: Categorize icons
Separate identified icons into two groups:
**Explicit import icons** — icons you need to import from `@patternfly/react-icons`:
- Action icons (edit, delete, copy, etc.)
- Status indicators used standalone
- Navigation and object icons
**Component-managed icons** — icons automatically handled by PatternFly components (no import needed):
- Checkbox states → `Checkbox` component
- Tree expand/collapse → `TreeView` component
- Sort indicators → `Table` with sort props
- Search input icons → `SearchInput` component
- Dropdown/Select carets → `Dropdown`/`Select` components
- Pagination controls → `Pagination` component
Ask the user their preferred output detail level (brief vs detailed) and whether to include component-managed icons in the report.
### Step 5: Generate report
**Brief format** — for each icon, show the component usage and a combined import statement:
```tsx
// Modal close button (top-right corner)
<TimesCircleIcon />
// Error status indicator
<Icon status="danger"><ExclamationCircleIcon /></Icon>
```
```typescript
import { TimesCircleIcon, ExclamationCircleIcon } from '@patternfly/react-icons';
import { Icon } from '@patternfly/react-core';
```
**Detailed format** — for each icon, include:
- Visual description and location in the design
- PatternFly match with confidence level
- Import statement and usage example
- Context-specific notes (accessibility, status wrapping, etc.)
- A combined copy-paste-ready import block at the end
For status icons, always show the `Icon` wrapper pattern:
```tsx
import { Icon } from '@patternfly/react-core';
<Icon status="success"><CheckCircleIcon /></Icon>
<Icon status="danger"><ExclamationCircleIcon /></Icon>
<Icon status="warning"><ExclamationTriangleIcon /></Icon>
<Icon status="info"><InfoCircleIcon /></Icon>
```
### Accessibility reminders
- Interactive icons in buttons need `aria-label` or visible text
- Decorative icons should have `aria-hidden="true"`
- Status icons should use the `Icon` wrapper with `status` prop
## Edge Cases
- **Multiple possible matches**: list all candidates with confidence levels and recommend based on semantic context
- **Low-quality image**: request a higher-resolution screenshot and provide best guesses
- **Component-managed icons**: explain that no import is needed and which component handles itRelated Skills
icon-finder
Find Red Hat Design System icons (@rhds/icons) by keyword or use case with visual previews. Use when choosing an icon for a UI element or looking up available icons.
figma-changes
Diff Figma designs to identify what changed and generate code update checklists. Use when syncing code with updated designs or reviewing what changed between iterations. Requires Figma MCP.
pf-unit-test-generator
Generate a unit test file for a React component using Testing Library. Use when adding test coverage to new or existing components.
pf-prototype-mode
Enable prototype mode for React apps with grayscale styling and a banner overlay. Use when demoing early concepts, presenting wireframes, or preventing stakeholders from fixating on visual polish.
pf-project-scaffolder
Scaffolds PatternFly React projects with PF6-safe dependencies, imports, and starter layout. Use when creating a new PatternFly app or bootstrapping a migration sandbox.
pf-import-checker
Audit and fix invalid PatternFly import paths across packages. Use when imports fail, modules are unresolved, or after upgrading PatternFly versions.
pf-component-structure
Audit PatternFly React component nesting, wrapper hierarchies, and layout structure. Use when scanning for hierarchy violations or debugging spacing caused by missing wrapper components.
write-example-description
Write and refine example descriptions for PatternFly.org component and demo pages. Use when authoring or updating the prose in PatternFly example markdown files.
summarize-jira-issues
Summarize your current sprint workload from Jira — assigned issues, contributor roles, and priorities. Use when checking what's left in the sprint or deciding what to work on next.
semantic-release-troubleshooting
Diagnose and fix semantic-release issues when a specific version is not being released. Use when semantic-release skips a version, fails to release, or when troubleshooting after git push --force, squashed commits, permission errors, or reference already exists.
quarterly-initiative-report
Generate quarterly Jira status reports with RAG assessment, blocker tracking, and next-quarter recommendations. Use when preparing quarterly initiative reviews or tracking epic progress.
pf-tokens
Build CSS design tokens for PatternFly core and copy them to the PatternFly repository. Use when regenerating tokens after design changes or during release preparation.