TheGoat395/Codex-Skills / skills/radix-accessible-primitives
radix-accessible-primitives
VerifiedRepair Radix parts, portals and focus mechanics.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 980 B |
| agents/openai.yaml | config | 290 B |
| references/radix-accessible-primitives-guide.md | markdown | 3.5 KB |
references/radix-accessible-primitives-guide.md
View on GitHub# Radix Accessible Primitives Guide
## Purpose
Get robust interaction semantics while keeping full control over visual design.
## Use When
- A custom interactive component would otherwise require complex keyboard and focus behavior.
- The project already uses Radix directly or through shadcn/ui.
- Dialogs, menus, popovers, tabs, tooltips, accordions, switches, or selects need to be accessible and custom-styled.
## Do Not Use When
- A native HTML element fully solves the interaction.
- The project uses a different accessible component library consistently.
- The task is visual-only and no interactive primitive is needed.
## Discovery Questions
- Which user interaction pattern is needed and does Radix provide it?
- What semantics, keyboard behavior, and focus management are required?
- How should data-state and data-disabled attributes map to styling?
- Does the primitive need controlled or uncontrolled state?
## Decision Tree
- Choose native HTML first when it is enough.
- Use Radix for complex composite widgets that need proven accessibility behavior.
- Style parts with project tokens and data attributes.
- Keep focus management, portals, refs, and aria attributes intact.
- Test keyboard and screen-reader-relevant behavior after styling.
## Implementation Rules
- Do not remove Radix props, refs, or data attributes without understanding the behavior.
- Style every state: open, closed, highlighted, selected, disabled, checked, unchecked.
- Keep overlay, portal, and z-index behavior coordinated with the design system.
- Use tooltips for supplementary hints, not required information.
- Prefer predictable interaction patterns over novelty for controls.
## Useful Patterns
- Dropdown menu: trigger, content, item, separator, shortcut, disabled, focus/highlight.
- Dialog: title, description, close, overlay, content, focus restore, mobile sizing.
- Tabs: list, trigger, selected state, panel, keyboard navigation.
- Switch/radio/checkbox: visible state, label, focus ring, disabled behavior.
## Anti-Patterns
- Rebuilding a complex menu from divs and click handlers.
- Animating Radix content while ignoring focus and escape behavior.
- Hiding labels because the primitive seems to work visually.
- Using Radix for simple static layout.
## QA Checklist
- Test keyboard behavior: Tab, Shift+Tab, Enter, Space, Escape, Arrow keys where relevant.
- Verify the intended modality. Modal dialogs/popovers require appropriate focus containment; nonmodal popovers need normal Tab flow and intentional focus return. Radix Popover defaults to `modal=false`; do not introduce a focus trap for a nonmodal design.
- Inspect open/closed/selected/disabled styles.
- Run available accessibility checks.
## Acceptance Criteria
- The component behaves like the expected accessible pattern.
- Styling is custom and premium, not default or generic.
- Accessibility remains intact after visual customization.
## Shared scope
For applicable substantial web work, reuse the [shared scoped web contract](../../website-operating-rules/references/scoped-web-contract.md) when available. Preserve current authorization, stack and requested scope; this optional reference does not require another planning or approval cycle.
## Official Source Anchors
- Radix Primitives introduction: https://www.radix-ui.com/primitives/docs/overview/introduction
- shadcn/ui docs: https://ui.shadcn.com/docs
- MDN focus-visible: https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/:focus-visible
Modality reference: [Radix Popover](https://www.radix-ui.com/primitives/docs/components/popover).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |