Compétences Apple HIG: Selection and Input Controls

📦

Apple HIG: Selection and Input Controls

Name: Apple HIG: Selection and Input Controls
Author: sickn33

Sûr

Obtenir des recommandations Apple HIG pour les contrôles de sélection et de saisie

Concevoir des formulaires et des interfaces de sélection sans les recommandations Apple HIG entraîne des expériences utilisateur incohérentes. Cette compétence fournit les autorisatives Apple Human Interface Guidelines pour les sélecteurs, interrupteurs, curseurs, steppers, champs de texte et autres contrôles de saisie.

Prend en charge: Claude Codex Code(CC)

📊 70 Adéquat

Télécharger le ZIP du skill

Importer dans Claude

Allez dans Paramètres → Capacités → Skills → Importer un skill

Activez et commencez à utiliser

Tester

Utilisation de "Apple HIG: Selection and Input Controls". What control should I use for a yes/no preference in Settings?

Résultat attendu:

Use a toggle for binary on/off preferences in Settings. Per Apple HIG, toggles show immediate effect in Settings screens - changes apply instantly without a Save button. Ensure the toggle has a clear label describing what it controls, and the on state represents the enabled or active condition.

Utilisation de "Apple HIG: Selection and Input Controls". How many options work best in a segmented control?

Résultat attendu:

Segmented controls work best with 2 to 5 mutually exclusive options of roughly equal importance. Each segment should have a short label. For more than 5 options, use a picker instead. All options in a segmented control must be visible at once - they do not scroll.

Audit de sécurité

Sûr

v1 • 2/25/2026

This skill contains only markdown documentation files with Apple Human Interface Guidelines content. All static analysis findings are false positives: backticks are markdown formatting for code references, URLs are documentation links to developer.apple.com, and flagged patterns are natural language in documentation context. No executable code, network requests, or system operations present.

Fichiers analysés

1,199

Lignes analysées

résultats

Total des audits

Aucun problème de sécurité trouvé

Audité par: claude

Score de qualité

Architecture

100

Maintenabilité

Contenu

Communauté

100

Sécurité

Conformité aux spécifications

Ce que vous pouvez construire

Conception de formulaire pour application iOS

Concevoir un écran de paramètres avec interrupteurs, sélecteurs et champs de texte qui respecte les conventions Apple HIG pour la gestion d'état et la validation.

Sélection de contrôles multi-plateforme

Déterminer le contrôle de sélection approprié pour différentes plateformes lors de la création d'une application multi-plateforme avec des modèles UX cohérents.

Vérification de conformité d'accessibilité

S'assurer que les contrôles de formulaire ont des étiquettes, indices et traits VoiceOver appropriés pour les utilisateurs handicapés.

Essayez ces prompts

Recommandation de contrôle de base

I need a control for a binary on/off setting in my iOS settings screen. What does Apple HIG recommend?

Sélection de plusieurs options

I have 4 mutually exclusive sorting options for a list. Should I use a segmented control or a picker? What does Apple HIG say?

Recommandations spécifiques à la plateforme

I'm building a macOS app that needs to let users select multiple email recipients. What control should I use according to Apple HIG?

Examen complet de formulaire

Review my form design: it has a toggle for notifications, a picker for frequency (5 options), a slider for volume, and a text field for a custom message. Provide HIG guidance on each control's state management, validation, and accessibility.

Bonnes pratiques

Always show the current selection state clearly - users must see what is selected at all times
Prefer standard system controls over custom implementations for consistency and accessibility
Use toggles for binary states in Settings (immediate effect) and modal forms (commit on confirmation)
Configure text field keyboard types to match expected input (email, URL, number, phone)
Provide meaningful default values and introductory labels for form controls
Include VoiceOver labels, hints, and traits for all interactive controls

Éviter

Using segmented controls with more than 5 options or with options of unequal importance
Using a picker for only 2 options when a segmented control or toggle would be clearer
Placing a Save button in Settings screens where toggles should apply changes immediately
Using custom controls that break standard iOS or macOS interaction patterns
Leaving text fields without appropriate keyboard type configuration for the expected input

Foire aux questions

When should I use a toggle versus a checkbox?

Apple HIG recommends toggles for on/off states in iOS and macOS. Toggles show immediate effect in Settings screens. Checkboxes are not part of Apple's standard control set for these platforms - use toggles instead for binary choices.

What's the difference between a picker and a segmented control?

Use segmented controls for 2 to 5 mutually exclusive options that should all be visible at once. Use pickers for longer option lists, dates, times, or structured data. Pickers take less space but require an extra tap to reveal options.

Do changes from toggles apply immediately or require confirmation?

In Settings screens, toggle changes apply immediately without a Save button. In modal forms or wizards, changes typically commit when the user taps Done or Confirm. Follow the context convention your app establishes.

Are combo boxes available on iOS?

No, combo boxes are macOS only. They are not supported in iOS, iPadOS, tvOS, visionOS, or watchOS. For iOS, use a picker or action sheet for similar functionality.

What keyboard type should I use for numeric input?

Apple HIG recommends the number keyboard for numeric-only input. For decimal numbers, use the decimal pad. For phone numbers, use the phone pad. Match the keyboard type to the expected input format for better user experience.

How do I make my form controls accessible?

Provide clear labels for all controls, use introductory labels to describe expected input, add VoiceOver hints explaining what each control does, and ensure controls have appropriate accessibility traits. Test with VoiceOver to verify the experience.