From primeng
Apply current PrimeNG accessibility and icon guidance. Use for semantics, names, labels, focus and keyboard behavior, component accessibility, PrimeIcons, custom icons, and icon-bearing controls.
How this skill is triggered — by the user, by Claude, or both
Slash command
/primeng:primeng-accessibility-iconsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Inspect existing Angular templates, native semantics, labels and descriptions, error/status messaging, focus handling, keyboard interaction, icon packages, custom icon templates, and nearby component conventions.
Inspect existing Angular templates, native semantics, labels and descriptions, error/status messaging, focus handling, keyboard interaction, icon packages, custom icon templates, and nearby component conventions.
Use get_guide only for the current routed accessibility, icons, or custom-icons concept relevant to the request. Use get_component for component-specific accessibility metadata, supported icon inputs/templates, and exact output or keyboard contracts. Inspect returned section metadata before requesting an example. Do not generalize behavior between components or invent ARIA attributes, PrimeIcons names, templates, inputs, outputs, or keyboard interactions.
Preserve native semantics and accessible names. Treat icon-only and custom-content controls according to returned component and accessibility guidance. Call validate_usage once on final component code and repeat only after a reported issue. Then separately test focus order, keyboard operation, visible focus, announced names/states, contrast, and responsive behavior when those outcomes matter. Do not call version routinely.
accessibility-icons: get_guide -> get_component -> validate_usage; maximum 3.Report PrimeNG-only resource/public citations, static validation, and the runtime or assistive-technology checks actually performed.
npx claudepluginhub primefaces/primeui-plugins --plugin primengCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.