Compétences Apple HIG: Inputs
📦

Apple HIG: Inputs

Sûr

获取 Apple 输入设计指南

Apple 平台输入方法需要特定于平台的设计模式。此技能为所有 Apple 平台上的手势、键盘、控制器和空间交互提供官方的人机界面指南。

Prend en charge: Claude Codex Code(CC)
🥉 73 Bronze
1

Télécharger le ZIP du skill

2

Importer dans Claude

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

3

Activez et commencez à utiliser

Tester

Utilisation de "Apple HIG: Inputs". What gestures should I support for navigating between screens?

Résultat attendu:

  • Use standard swipe gestures for navigation:
  • - Swipe from left edge: back (iOS standard)
  • - Swipe from right edge: forward
  • - Pinch to zoom: adjust content scale
  • - Two-finger swipe: undo or redo
  • Avoid overriding system gestures. Use built-in gesture recognizers for accessibility support.

Utilisation de "Apple HIG: Inputs". How do I support Apple Pencil for text entry?

Résultat attendu:

  • Enable Scribble support in all text fields:
  • - Scribble works automatically in standard text components
  • - Ensure custom text fields adopt UIIndirectScribbleInteraction
  • - Hide placeholder text when writing begins
  • - Keep text fields stationary while writing
  • - Provide adequate writing space (expand field before input)

Utilisation de "Apple HIG: Inputs". What keyboard shortcuts should I implement?

Résultat attendu:

  • Implement standard shortcuts plus app-specific actions:
  • - Standard: Cmd+C (copy), Cmd+V (paste), Cmd+Z (undo), Cmd+Shift+Z (redo)
  • - File: Cmd+N (new), Cmd+W (close), Cmd+S (save)
  • - View: Cmd+0 (zoom to fit), Cmd++ (zoom in), Cmd+- (zoom out)
  • - Make custom shortcuts visible in Command key overlay
  • - Ensure full keyboard navigation with logical tab order

Audit de sécurité

Sûr
v1 • 2/25/2026

Static analysis detected 905 potential security issues across 13 files (1673 lines). All findings are false positives from legitimate documentation content. Markdown backtick syntax for code symbols was misidentified as shell execution. HTTP URLs are legitimate Apple Developer Documentation links. C2 keyword detections are normal UI terminology (control, command, etc.). No actual security risks found.

13
Fichiers analysés
1,673
Lignes analysées
0
résultats
1
Total des audits
Aucun problème de sécurité trouvé
Audité par: claude

Score de qualité

45
Architecture
100
Maintenabilité
87
Contenu
50
Communauté
100
Sécurité
65
Conformité aux spécifications

Ce que vous pouvez construire

为 iOS 应用设计手势快捷操作

iOS 开发者需要为照片编辑应用添加自定义滑动手势。使用此技能了解标准手势模式,避免与系统手势冲突,并实现正确的识别器配置。

为 iPadOS 应用添加键盘快捷键

生产力应用开发者正在添加 Command 键快捷键。使用此技能了解标准快捷键约定,实现完整的键盘导航,并在 Command 键覆盖层中使快捷键可被发现。

实现 Apple Pencil 绘图功能

笔记应用需要 Apple Pencil 支持。使用此技能了解压力感应、倾斜、悬停交互、Scribble 文本输入以及区分 Pencil 和手指输入。

Essayez ces prompts

Basic gesture guidance
What standard gestures should my iOS app support?
Apple Pencil implementation
How do I add Apple Pencil support to my drawing app? What sensors and interactions should I implement?
Keyboard shortcut design
What keyboard shortcuts should I provide for my productivity app? How do they appear in the Command key overlay?
visionOS spatial input planning
What input methods and interaction patterns should I design for in my visionOS immersive experience?

Bonnes pratiques

  • Support multiple input methods simultaneously - design for touch, pointer, keyboard, and Pencil together rather than in isolation
  • Use built-in gesture recognizers and platform APIs instead of implementing custom gesture handlers - this ensures accessibility support and consistent edge case handling
  • Provide consistent visual and haptic feedback for every input action - users should always know their interaction was registered

Éviter

  • Override system gestures like edge swipes for notifications or Home screen - this creates conflicting interactions and frustrates users
  • Require mode switches before Apple Pencil can draw - users expect immediate marking when Pencil touches screen
  • Hide keyboard shortcuts from the Command key overlay - undiscoverable shortcuts reduce productivity for power users

Foire aux questions

Should I support Apple Pencil or touch input?
Support both. Let users choose when to switch between Apple Pencil and finger input. Ensure controls respond to both input types so users do not need to switch modes to activate UI elements.
What is the difference between focus and hover on visionOS?
Focus indicates keyboard or controller navigation target on tvOS and visionOS. Hover is the visionOS-specific eye tracking effect that shows content will respond when user looks at it. They serve different purposes and can appear independently.
Do I need to support game controllers?
Game controller support is optional but recommended for games on iOS, tvOS, and Mac. Map to extended gamepad profile with sensible defaults. Always provide touch or keyboard alternatives for non-game apps.
How do I handle keyboard avoidance?
Use the keyboard avoidance APIs to adjust your layout when the software keyboard appears. Never cover essential content with the keyboard. Move or resize the active text field into view before input begins.
What are the standard gestures I must support?
Standard gestures include tap to activate, swipe to scroll and navigate, pinch to zoom, long press for context menus, and drag to move. Never override system edge swipes for Home, back, notifications, or app switching.
Can I create custom gestures?
Yes, but prefer using standard recognizers. If you create custom gestures, make them discoverable with hints or coaching. Avoid requiring multiple simultaneous interactions as these are hard to discover and inaccessible.