sickn33/antigravity-awesome-skills/hig-components-controls

Apple HIG: Selection and Input Controls

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

1. Clear current state. Users must always see what is selected. Toggles show on/off, segmented controls highlight the active segment, pickers display the current selection.

1. Prefer standard system controls. Built-in controls provide consistency and accessibility. Custom controls introduce a learning curve and may break assistive features.

1. Toggles for binary states. On or off. In Settings-style screens, changes take effect immediately. In modal forms, changes commit on confirmation.

1. Segmented controls for closely related choices. Usually a small set; macOS also supports multiple selection and momentary actions. Keep a control’s selection/action behavior consistent.

1. Sliders for continuous values. When precise numeric input is not critical. Provide min/max labels or icons for range endpoints.

1. Pickers for long option lists. Too many options for a segmented control. Works well for dates, times, structured data.

1. Steppers for small, precise adjustments. Increment/decrement in fixed steps. Display current value next to the stepper with reasonable min/max bounds.

1. Text fields for short, single-line input. Text views for multi-line. Configure keyboard type to match expected input (email, URL, number).

1. Combo boxes: text input + selection list. macOS. Type a value or choose from a predefined list when custom values are valid.

1. Token fields: discrete values as visual tokens. macOS. For email recipients, tags, or collections of discrete items.

1. Gauges and rating indicators display values. Gauges show a value within a range. Rating indicators show ratings (often stars). Display-only; use interactive variants for input.

Reference Index

Output Format

1. Control recommendation with rationale and why alternatives are less suitable.
2. State management -- how the control communicates current state and whether changes apply immediately or on confirmation.
3. Validation approach -- when to show errors and how to communicate rules.
4. Accessibility -- labels, traits, hints for VoiceOver.

Questions to Ask

1. What type of data? (Boolean, choice from fixed set, numeric, free-form text?)
2. How many options?
3. Which platforms? (Combo boxes and token fields are macOS-only)
4. Settings screen or inline form?

Related Skills

• hig-components-menus -- Buttons and pop-up buttons complementing selection controls
• hig-components-dialogs -- Sheets and popovers containing forms
• hig-components-search -- Search fields sharing text input patterns
• hig-inputs -- Keyboard, pointer, gesture interactions with controls
• hig-foundations -- Typography, color, layout for control styling

Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Example

User request:

Choose between a picker and segmented control for five related filters in an iPhone app, and explain state and VoiceOver behavior.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Reference scope

Bundled Apple documentation is a static snapshot; check the linked primary page and target OS/API availability before platform-specific implementation. The controls.md page concerns WidgetKit system controls, not every in-app input control. The rating-indicator reference describes macOS NSLevelIndicator, which can be editable; a custom rating UI on other platforms is a separate design. Visual labels do not replace accessibility names. Keyboard type and formatters assist input but do not replace locale-aware validation, and secure fields do not encrypt stored/transmitted data. No Apple runtime or image-asset availability was tested here.