pf-catalog-interaction-patterns
/pf-catalog-interaction-patterns
Catalog interaction patterns (click, hover, keyboard, drag) across PatternFly components. Use when selecting a component for a specific interaction need, describing UI behavior without naming a component, or building prototypes that require interaction-based component lookup.
- Author
- rh-uxd ↗
- Repository
- ai-helpers ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 9
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Catalog interaction patterns (click, hover, keyboard, drag) across PatternFly components. Use when selecting a component for a specific interaction need, describing UI behavior without naming a component, or building prototypes that require interaction-based component lookup.
Original author description
Catalog interaction patterns (click, hover, keyboard, drag) across PatternFly components. Use when selecting a component for a specific interaction need, describing UI behavior without naming a component, or building prototypes that require interaction-based component lookup.
How it works
- PatternFly MCP
- When to use this skill
- Interaction catalog
- Workflow
- Output format
- Common misconception
SKILL.md preview
--- name: pf-catalog-interaction-patterns description: Catalog interaction patterns (click, hover, keyboard, drag) across PatternFly components. Use when selecting a component for a specific interaction need, describing UI behavior without naming a component, or building prototypes that require interaction-based component lookup. version: 0.1.0 --- Find the right PatternFly component for a given interaction pattern. This skill indexes components by **how users interact with them**, complementing component-centric documentation that answers "what can this component do?" ## PatternFly MCP If `@patternfly/patternfly-mcp` is available, use it to fetch full documentation, props, and examples **after** identifying the right component from this catalog. ## When to use this skill - "I need a component that lets users reorder items" - "What supports keyboard shortcuts?" - "Which components can expand/collapse content?" - "What's the right component for a toggle action?" - Prototyping a UI and need to select components based on required interactions ## Interaction catalog The catalog lives in `references/interaction-catalog.md`. It maps interaction patterns to components, organized by category (Click, Hover, Keyboard, Drag, Focus, Selection). Read the reference file for the full mapping. ## Workflow ### Finding a component for an interaction 1. User describes the interaction they need (e.g., "reveal help text on hover"). 2. Look up the interaction category in `references/interaction-catalog.md`. 3. Return matching components with a one-line summary of how each supports that interaction. 4. If the user wants implementation details, use the PatternFly MCP to fetch full docs. ### Verifying component capabilities 1. User asks what interactions a component supports. 2. Search the catalog for that component name. 3. Return all interaction patterns the component appears in. ## Output format When returning matches: ``` ## Components supporting [interaction pattern] | Component | How it supports this interaction | |-----------|----------------------------------| | Tooltip | Displays on hover after configurable delay; auto-positions | | Truncate | Shows full text on hover when content overflows | ``` When listing a component's interactions: ``` ## Interactions supported by [Component] - **Click**: Opens/closes the panel - **Keyboard**: Enter/Space to toggle; Escape to close - **Focus**: Traps focus when open; restores on close ``` ## Common misconception **Popovers, Menus, and Dropdowns are click-triggered** — PatternFly does not trigger these on hover. Only Tooltip and Truncate respond to hover.
Files in this package (9)
- SKILL.md 3 KB
- eval/eval.yaml 4 KB
- eval/cases/drag-reorder-items/annotations.yaml 1 KB
- eval/cases/drag-reorder-items/input.yaml 1 KB
- eval/cases/hover-reveal-content/annotations.yaml 1 KB
- eval/cases/hover-reveal-content/input.yaml 1 KB
- eval/cases/negative-non-pf/annotations.yaml 1 KB
- eval/cases/negative-non-pf/input.yaml 1 KB
- references/interaction-catalog.md 7 KB
Versions
The database has no other skills named pf-catalog-interaction-patterns.
Database snapshot: 13.11.2026 · package version 24996a6e661d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100pf-a11y-keyboard
Test keyboard accessibility of PatternFly UIs via live browser interaction. Use when validating keyboard navigation, focus management, or interaction patterns in a running application. - 100interaction-design
User flow design, micro-interactions, and interface behavior patterns with state management for all interaction conditions. Use when designing natural interactions, feedback systems, or handling error states. - 100interaction-patterns-components
Use when choosing, critiquing, or designing UI interaction patterns and reusable components for web, mobile, SaaS, dashboards, or design systems. - 100interaction-patterns
UI interaction patterns: skeleton loading, infinite scroll, progressive disclosure, modal/drawer/inline selection, drag-and-drop, tab overflow, toasts. Use when implementing loading states, pagination, overlays, reorderable lists, or notifications. - 100pf-screenshot-mapping
Maps screenshots and UI mockups (any fidelity) to PatternFly 6 layout and building-block components. Output uses PF Component Mapping (regions, PF6 direction including structure and behavior, doc links) and PF Gaps & Recommendations (structural gaps/stretches and design-system… - 100write-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.