apple-design-controls
Choose and specify Apple UI controls for actions, selection, values, text entry, and forms. Use for button semantics, pickers, toggles, fields, sliders, and keyboard behavior.
SKILL.mdskills/design/apple-design-controls/SKILL.md
GitHubApple Controls and Data Entry
Apply the skill
Identify the value or action first: immediate command, binary state, exclusive choice, continuous range, discrete increment, or free-form content. Use that distinction to choose the component instead of choosing by appearance.
Specify labels, current value, enabled conditions, feedback, validation timing, error recovery, and accessibility semantics for the controls actually involved. A custom drawing that resembles a control still needs its full interaction contract.
Verify keyboard and focus behavior, large text, localization, and adjacent hit regions. Keep required information visible after a placeholder disappears. Read the relevant platform section before treating a control style as universal; macOS, iOS, watchOS, and visionOS use some similarly named controls differently.
Topic references
Select the topic that matches the design decision; do not load this entire list by default.
- Buttons
- Toggles
- Pickers
- Segmented controls
- Pop-up buttons
- Pull-down buttons
- Sliders
- Steppers
- Text fields
- Text views
- Token fields
- Combo boxes
- Color wells
- Digit entry views
- Disclosure controls
- Virtual keyboards
Source use
These references are original operational summaries of Apple’s public HIG, checked on 2026-09-08. They are guidance for design decisions, not a reproduced manual or a guarantee of App Store acceptance.
Read only the topic references relevant to the current task. Each links to the full official page. Consult that page for exact specifications, platform exceptions, assets, and version-sensitive behavior; use current official developer documentation for APIs and availability. If live documentation is unavailable, state the snapshot date and identify assumptions instead of inventing current requirements.
The user’s product goals, selected framework, and authorized scope remain controlling. Distinguish a source recommendation from a hard platform requirement and from your own proposed implementation.