Skip to content

yerzong/TEMP-LEAGUE / .claude/skills/apple-design

apple-design

Verified

Cross-platform UI/UX design reviewer grounded in Apple Human Interface Guidelines principles. Use this skill to audit, review, critique, or improve any UI/UX design for mobile apps (iOS, Flutter, React Native) or desktop apps (macOS, Tauri, Electron). Triggers when the user mentions: design review, UI audit, HIG compliance, improving app design, design feedback, accessibility audit, or any request to check or improve a design against professional standards. Also use when the user uploads screenshots, mockups, wireframes, or design specs of a mobile or desktop app and wants feedback. Even if they just say "review my design" or "is this good UI", use this skill. Works for native and cross-platform frameworks including Flutter, Tauri, Electron, React Native, SwiftUI, and AppKit/UIKit.

FileKindSize
README.mdmarkdown4.7 KB
SKILL.mdskill md12.2 KB
references/hig-lookup.mdmarkdown3.0 KB
references/hig/accessibility.mdmarkdown12.9 KB
references/hig/app-icons.mdmarkdown8.7 KB
references/hig/apple-pay.mdmarkdown23.8 KB
references/hig/apple-pencil-and-scribble.mdmarkdown12.3 KB
references/hig/augmented-reality.mdmarkdown19.1 KB
references/hig/branding.mdmarkdown2.9 KB
references/hig/charting-data.mdmarkdown5.9 KB
references/hig/collaboration-and-sharing.mdmarkdown4.8 KB
references/hig/color.mdmarkdown11.6 KB
references/hig/dark-mode.mdmarkdown6.7 KB
references/hig/drag-and-drop.mdmarkdown12.0 KB
references/hig/entering-data.mdmarkdown3.4 KB
references/hig/feedback.mdmarkdown3.2 KB
references/hig/file-management.mdmarkdown9.7 KB
references/hig/focus-and-selection.mdmarkdown6.2 KB
references/hig/game-controls.mdmarkdown9.1 KB
references/hig/generative-ai.mdmarkdown14.4 KB
references/hig/gestures.mdmarkdown6.0 KB
references/hig/going-full-screen.mdmarkdown4.3 KB
references/hig/icons.mdmarkdown9.9 KB
references/hig/images.mdmarkdown2.8 KB
references/hig/in-app-purchase.mdmarkdown14.7 KB
references/hig/inclusion.mdmarkdown12.8 KB
references/hig/keyboards.mdmarkdown14.9 KB
references/hig/launching.mdmarkdown3.4 KB
references/hig/layout.mdmarkdown15.3 KB
references/hig/liquid-glass.mdmarkdown8.4 KB
references/hig/live-viewing-apps.mdmarkdown6.2 KB
references/hig/loading.mdmarkdown2.6 KB
references/hig/machine-learning.mdmarkdown33.2 KB
references/hig/managing-accounts.mdmarkdown5.2 KB
references/hig/managing-notifications.mdmarkdown5.9 KB
references/hig/maps.mdmarkdown11.2 KB
references/hig/materials.mdmarkdown1.4 KB
references/hig/modality.mdmarkdown4.5 KB
references/hig/motion.mdmarkdown3.4 KB
references/hig/multitasking.mdmarkdown4.6 KB
references/hig/offering-help.mdmarkdown5.7 KB
references/hig/onboarding.mdmarkdown4.3 KB
references/hig/playing-audio.mdmarkdown7.0 KB
references/hig/playing-haptics.mdmarkdown9.8 KB
references/hig/playing-video.mdmarkdown8.4 KB
references/hig/pointing-devices.mdmarkdown18.8 KB
references/hig/printing.mdmarkdown3.1 KB
references/hig/privacy.mdmarkdown12.0 KB
references/hig/ratings-and-reviews.mdmarkdown2.9 KB
references/hig/right-to-left.mdmarkdown8.7 KB
references/hig/searching.mdmarkdown3.8 KB
references/hig/settings.mdmarkdown5.9 KB
references/hig/sf-symbols.mdmarkdown13.8 KB
references/hig/typography.mdmarkdown9.0 KB
references/hig/undo-and-redo.mdmarkdown3.8 KB
references/hig/writing.mdmarkdown8.1 KB

references/hig/gestures.md

View on GitHub
# Gestures

> Source: [https://developer.apple.com/design/human-interface-guidelines/gestures](https://developer.apple.com/design/human-interface-guidelines/gestures)

---

A gesture is a physical motion that a person uses to directly affect an object in an app or game on their device.

Depending on the device they're using, people can make gestures on a touchscreen, or on a range of input devices such as a trackpad, mouse, remote, or game controller that includes a touch surface.

Every platform supports basic gestures like tap, swipe, and drag. Although the precise movements that make up basic gestures can vary per platform and input device, people are familiar with the underlying functionality of these gestures and expect to use them everywhere.

## Best practices

Give people more than one way to interact with your app. People commonly prefer or need to use other inputs — such as their voice, keyboard, or accessibility features — to interact with their devices. Don't assume that people can use a specific gesture to perform a given task.

In general, respond to gestures in ways that are consistent with people's expectations. People expect most gestures to work the same regardless of their current context. For example, people expect tap to activate or select an object. Avoid using a familiar gesture like tap or swipe to perform an action that's unique to your app; similarly, avoid creating a unique gesture to perform a standard action like activating a button or scrolling a long view.

Handle gestures as responsively as possible. Useful gestures enhance the experience of direct manipulation and provide immediate feedback. As people perform a gesture in your app, provide feedback that helps them predict its results and, if necessary, communicates the extent and type of movement required to complete the action.

Indicate when a gesture isn't available. If you don't clearly communicate why a gesture doesn't work, people might think your app has frozen or they aren't performing the gesture correctly, leading to frustration. For example, if someone tries to drag a locked object, the UI may not indicate that the object's position has been locked; or if they try to activate an unavailable button, the button's unavailable state may not be clearly distinct from its available state.

## Custom gestures

Add custom gestures only when necessary. Custom gestures work best when you design them for specialized tasks that people perform frequently and that aren't covered by existing gestures, like in a game or drawing app. If you decide to implement a custom gesture, make sure it's:

- Discoverable
- Straightforward to perform
- Distinct from other gestures
- Not the only way to perform an important action in your app or game

Make custom gestures easy to learn. Offer moments in your app to help people quickly learn and perform custom gestures, and make sure to test your interactions in real use scenarios. If you're finding it difficult to use simple language and graphics to describe a gesture, it may mean people will find the gesture difficult to learn and perform.

Use shortcut gestures to supplement standard gestures, not replace them. While you may supply a custom gesture to quickly access parts of your app, people also need simple, familiar ways to navigate and perform actions, even if it means an extra tap or two. For example, in an app that supports navigation through a hierarchy of views, people expect to find a Back button in a top toolbar that lets them return to the previous view with a single tap. To help accelerate this action, many apps also offer a shortcut gesture — such as swiping from the side of a window or touchscreen — while continuing to provide the Back button.

Avoid conflicting with gestures that access system UI. Several platforms offer gestures for accessing system behaviors. It's important to avoid defining custom gestures that might conflict with these interactions, as people expect these controls to work consistently. In specific circumstances within games or immersive experiences, developers can work around this by deferring the system gesture.

## Mobile platforms

In addition to the standard gestures supported in all platforms, mobile supports a few other gestures that people expect:

| Gesture | Common action |
|---------|---------------|
| Three-finger swipe | Initiate undo (left swipe); initiate redo (right swipe) |
| Three-finger pinch | Copy selected text (pinch in); paste copied text (pinch out) |
| Four-finger swipe | Switch between apps |
| Shake | Initiate undo; initiate redo |

Consider allowing simultaneous recognition of multiple gestures if it enhances the experience. Although simultaneous gestures are unlikely to be useful in nongame apps, a game might include multiple onscreen controls — such as a joystick and firing buttons — that people can operate at the same time.

## Desktop

People primarily interact with desktop using a keyboard and mouse. In addition, they can make standard gestures on a trackpad, magic mouse, or a game controller that includes a touch surface.

## Standard gestures

The system provides APIs that support the familiar gestures people use with their devices, whether they use a touchscreen or an input device like a trackpad, mouse, remote, or game controller.

| Gesture | Supported in | Common action |
|---------|-------------|---------------|
| Tap | Mobile and desktop platforms | Activate a control; select an item |
| Swipe | Mobile and desktop platforms | Reveal actions and controls; dismiss views; scroll |
| Drag | Mobile and desktop platforms | Move a UI element |
| Touch (or pinch) and hold | Mobile and desktop platforms | Reveal additional controls or functionality |
| Double tap | Mobile and desktop platforms | Zoom in; zoom out if already zoomed in |
| Zoom | Mobile and desktop platforms | Zoom a view; magnify content |
| Rotate | Mobile and desktop platforms | Rotate a selected item |

For guidance on supporting additional gestures and button presses on specific input devices, see Pointing devices, Remotes, and Game controls.

## Related

Feedback
Eyes
Playing haptics
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall