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.
What this skill does
# 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 it
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.