patternfly

A guide for building interfaces with PatternFly, a design system that provides reusable components, layout guidance, design tokens, and accessibility rules.

In plain words
What is it for?
Use it when creating or changing PatternFly React interfaces, especially when selecting components, arranging layouts, applying styles, or checking accessibility.
Why use it?
It keeps PatternFly-based interfaces consistent and avoids guessing how components or accessibility behavior should be implemented.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/redhatinsights/nxtcm-components/patternfly
Any agent
npx skills add RedHatInsights/nxtcm-components --skill patternfly
Clone the repo
git clone --depth 1 https://github.com/RedHatInsights/nxtcm-components

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 711 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00711
Opus 5 $0.00000 $0.00356
Sonnet 5 $0.00000 $0.00142
Haiku 4.5 $0.00000 $0.00071

Measured 2d ago against content hash 480a4eab3707, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

patternfly scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/patternfly/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PatternFly application development

Use this guide when building or modifying UI that follows PatternFly. PatternFly is the source of truth for components, design guidelines, layout, design tokens, and accessibility.


PatternFly MCP (required)

Before implementing PatternFly UI, check whether patternfly-mcp is enabled.

If unavailable: do not guess APIs, props, or accessibility behavior. Stop and offer: (1) enable PatternFly MCP (preferred), or (2) user-approved fallback to patternfly.org. Wait for the user's choice before proceeding.

If available: searchPatternFlyDocsusePatternFlyDocs; match the repo's PF major version (e.g. v6); use returned schemas to validate props.

Doc priority: MCP → patternfly.org (fallback) → other sources only if PatternFly is silent.


Rules

  • Use PatternFly React (and documented extensions/component groups) instead of native HTML or one-off custom UI when an official component exists.
  • Follow PatternFly design guidelines for how components are used and combined. Spacing, hierarchy, layout, and UX patterns should match documented guidance, especially when assembling multiple components into a view.
  • Import from the project's PF packages (@patternfly/react-core, @patternfly/react-table, @patternfly/react-icons, etc.). Do not duplicate PF CSS or add parallel styling systems.
  • Prop values: use exported enums/constants (AlertVariant.danger), not magic strings.
  • Layout: PF primitives (Page, Flex, Grid, Stack, etc.); one primary layout per region.
  • Styling: tokens/utilities (e.g. pf-v6-u-* for v6); custom CSS only when docs do not cover the need.
  • Implement ARIA roles, labels, and keyboard behavior exactly as specified in PatternFly component documentation.
  • Forms: use Form / FormGroup with documented validated / error patterns; associate labels, descriptions, and errors with inputs—do not rely on placeholder text alone.
  • Icon-only controls need accessible names (aria-label or visible text); use @patternfly/react-icons, not ad-hoc SVG copies.
  • Add checkAccessibility in component tests when the project provides it:

Read the full file on GitHub · 50 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 50 lines · 0 tokens per session scan A 480a4eab3707

Subscribe to this mod's changes

patternfly is a skill published in the GitHub repository RedHatInsights/nxtcm-components (2 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 711 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens