hig-components-controls
Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual...
Best use case
hig-components-controls is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual...
Teams using hig-components-controls should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hig-components-controls/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hig-components-controls Compares
| Feature / Agent | hig-components-controls | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual...
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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. 2. **Prefer standard system controls.** Built-in controls provide consistency and accessibility. Custom controls introduce a learning curve and may break assistive features. 3. **Toggles for binary states.** On or off. In Settings-style screens, changes take effect immediately. In modal forms, changes commit on confirmation. 4. **Segmented controls for mutually exclusive options.** 2-5 items, roughly equal importance, short labels. 5. **Sliders for continuous values.** When precise numeric input is not critical. Provide min/max labels or icons for range endpoints. 6. **Pickers for long option lists.** Too many options for a segmented control. Works well for dates, times, structured data. 7. **Steppers for small, precise adjustments.** Increment/decrement in fixed steps. Display current value next to the stepper with reasonable min/max bounds. 8. **Text fields for short, single-line input.** Text views for multi-line. Configure keyboard type to match expected input (email, URL, number). 9. **Combo boxes: text input + selection list.** macOS. Type a value or choose from a predefined list when custom values are valid. 10. **Token fields: discrete values as visual tokens.** macOS. For email recipients, tags, or collections of discrete items. 11. **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 | Reference | Topic | Key content | |---|---|---| | [controls.md](references/controls.md) | General controls | States, affordance, system controls | | [toggles.md](references/toggles.md) | Toggles | On/off, immediate effect | | [segmented-controls.md](references/segmented-controls.md) | Segmented controls | 2-5 options, equal weight | | [sliders.md](references/sliders.md) | Sliders | Continuous range, min/max labels | | [steppers.md](references/steppers.md) | Steppers | Fixed steps, bounded values | | [pickers.md](references/pickers.md) | Pickers | Dates, times, long option sets | | [combo-boxes.md](references/combo-boxes.md) | Combo boxes | macOS, type or select, custom values | | [text-fields.md](references/text-fields.md) | Text fields | Short input, keyboard types, validation | | [text-views.md](references/text-views.md) | Text views | Multi-line, comments, descriptions | | [labels.md](references/labels.md) | Labels | Placement, VoiceOver support | | [token-fields.md](references/token-fields.md) | Token fields | macOS, chips, tags, recipients | | [virtual-keyboards.md](references/virtual-keyboards.md) | Virtual keyboards | Email, URL, number keyboard types | | [rating-indicators.md](references/rating-indicators.md) | Rating indicators | Star ratings, display-only | | [gauges.md](references/gauges.md) | Gauges | Level indicators, range display | ## 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.
Related Skills
hig-components-dialogs
Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views.
hig-components-search
Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.
hig-components-system
Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts.
hig-components-status
Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings.
hig-components-menus
Apple HIG guidance for menu and button components including menus, context menus, dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons, pull-down buttons, disclosure...
hig-components-layout
Apple Human Interface Guidelines for layout and navigation components.
core-components
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
pinia
Pinia official Vue state management library, type-safe and extensible. Use when defining stores, working with state/getters/actions, or implementing store patterns in Vue apps.
pingdom-automation
Automate Pingdom tasks via Rube MCP (Composio). Always search tools first for current schemas.
angular-performance
Angular performance: NgOptimizedImage, @defer, lazy loading, SSR. Trigger: When optimizing Angular app performance, images, or lazy loading.
perf-web-optimization
Optimize web performance: bundle size, images, caching, lazy loading, and overall page speed. Use when site is slow, reducing bundle size, fixing layout shifts, improving Time to Interactive, or optimizing for Lighthouse scores. Triggers on: web performance, bundle size, page speed, slow site, lazy loading. Do NOT use for Core Web Vitals-specific fixes (use core-web-vitals), running Lighthouse audits (use perf-lighthouse), or Astro-specific optimization (use perf-astro).
perf-lighthouse
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, and set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget. Do NOT use for fixing specific performance issues (use perf-web-optimization or core-web-vitals) or Astro-specific optimization (use perf-astro).