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/game-controls.md

View on GitHub
# Game Controls

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

---

Precise, intuitive game controls enhance gameplay and can increase a player's immersion in the game.

On various platforms, a game can support input from physical game controllers or default system interactions, like touch, a remote, or a mouse and keyboard. Players might prefer to use physical game controllers, but there are two important reasons to also support a platform's default interaction methods:

- Even though most platforms support physical game controllers, not every player might have access to one.
- Players appreciate games that let them use the platform interaction method they're most familiar with.

To reach the widest audience and provide the best experience for each platform, keep these factors in mind when choosing the input methods to support.

## Touch controls

For mobile games, supporting touch interaction means that you can provide virtual controls on top of game content while also letting players interact with game elements by touching them directly. You can use a touch controller framework to add these virtual controls to your game. Keep the following guidelines in mind to create an enjoyable touch control experience.

Determine whether it makes sense to display virtual controls on top of game content. In general, virtual game controls benefit games that offer a large number of actions or require players to control movement. However, sometimes gameplay is more immersive and effective when players can interact directly with in-game objects. Look for opportunities to reduce the amount of virtual controls that overlap your game content by associating actions with in-game gestures instead. For example, consider letting players tap objects to select them instead of adding a virtual selection button.

Place virtual buttons where they're easy to access. Take into account the device's boundaries and safe areas as well as comfortable locations for controls. Make sure to position buttons where they don't overlap system features like the Home indicator or Dynamic Island on phones. Place frequently used buttons near a player's thumb, avoiding the circular regions where players expect movement and camera input to happen. Place secondary controls, like menus, at the top of the screen.

Make sure controls are large enough. Make sure frequently used controls are a minimum size of 44x44 points, and less important controls, such as menus, are a minimum size of 28x28 points to accommodate people's fingers.

Always include visible and tactile press states. A virtual control feels unresponsive without a visual and physical press state. Help players understand when they successfully interact with a button by adding a visual press state effect, such as a glow, that they can see even when their finger is covering the control. Combine this press state with sound and haptics to enhance the feeling of feedback.

Use symbols that communicate the actions they perform. Choose artwork that visually represents the action each button performs, such as a graphic of a weapon to represent an attack. Avoid using abstract shapes or controller-based naming like A, X, or R1 as artwork, which makes it harder for players to understand and remember what specific controls do.

Show and hide virtual controls to reflect gameplay. Take advantage of the dynamic nature of touch controls and adapt what controls players see onscreen depending on their context. You can hide controls when an action isn't available or relevant, letting you reduce clutter and help players concentrate on what's important. For example, consider hiding movement controls until a player touches the screen to reduce the amount of UI overlapping your game content.

Combine functionality into a single control. Consider redesigning game mechanics that require players to press multiple buttons at the same time or in a sequence. Leverage gestures such as double tap and touch and hold to provide different variations of the same action, such as touch and hold to use a special powered up version of an attack. For multiple actions, such as walking or sprinting, consider combining the actions into a single control.

Map movement and camera controls to predictable behavior. Typically, players expect to control movement using the left side of their screen, and control camera direction using the right side of their screen. Maximize the amount of space that players can control both movement and the camera direction by using as large of an input area as possible. For movement control, opt to show a virtual thumbstick wherever the player lands their thumb instead of a static thumbstick position. For camera control, opt to use direct touch to pan the camera instead of a virtual thumbstick.

## Physical controllers

Support the platform's default interaction method. A game controller is an optional purchase, but every mobile device has a touchscreen, every desktop has a keyboard and a trackpad or mouse. If you support game controllers, try to make sure there's a fallback for using the platform's default interaction method.

Tell people about game controller requirements. You can note that your game requires a physical game controller. Remember that people can open your game at any time, even without a connected controller. If your app requires a game controller, check for its presence and gracefully prompt people to connect one.

Automatically detect whether a controller is paired. Instead of having players manually set up a physical game controller, you can automatically detect whether a controller is paired and get its profile.

Customize onscreen content to match the connected game controller. To simplify your game's code, a game controller framework assigns standard names to controller elements based on their placement, but the colors and symbols on an actual game controller may differ. Be sure to use the connected controller's labeling scheme when referring to controls or displaying related content in your interface.

Map controller buttons to expected UI behavior. Outside of gameplay, players expect to navigate your game's UI in a way that matches the familiar behavior of the platform they're playing on. When not controlling gameplay, follow these conventions:

| Button | Expected behavior for UI |
|--------|--------------------------|
| A | Activates a control |
| B | Cancels an action or returns to previous screen |
| X | — |
| Y | — |
| Left shoulder | Navigates left to a different screen or section |
| Right shoulder | Navigates right to a different screen or section |
| Left trigger | — |
| Right trigger | — |
| Left/right thumbstick | Moves selection |
| Directional pad | Moves selection |
| Home/logo | Reserved for system controls |
| Menu | Opens game settings or pauses gameplay |

Support multiple connected controllers. If there are multiple controllers connected, use labels and glyphs that match the one that the player is actively using. If your game supports multiplayer, use the appropriate labels and symbols when referring to a specific player's controller. If you need to refer to buttons on multiple controllers, consider listing them together.

Prefer using symbols, not text, to refer to game controller elements. A game controller framework makes system icon set available for most elements, including the buttons on various brands of game controllers. Using symbols instead of text descriptions can be especially helpful for players who aren't experienced with controllers because it doesn't require them to hunt for a specific button label during gameplay.

## Keyboards

Keyboard players appreciate using keyboard bindings to speed up their interactions with apps and games.

Prioritize single-key commands. Single-key commands are generally easier and faster for players to perform, especially while they're simultaneously using a mouse or trackpad. For example, you might use the first letter of a menu item as a shortcut, such as I for Inventory or M for Map; you might also map the game's main action to the Space bar, taking advantage of the key's relatively large size.

Test key binding comfort using a standard keyboard. For example, if a key binding uses the Control key (^) on a non-standard keyboard, consider remapping it to the Command key (⌘) on a standard keyboard. On standard keyboards, the Command key is conveniently located next to the Space bar, making it especially easy to reach when players are using the W, A, S, and D keys.

Take the proximity of keys into account. For example, if players navigate using the W, A, S, and D keys, consider using nearby keys to define other high-value commands. Similarly, if there's a group of closely related actions, it can work well to map their bindings to keys that are physically close together, such as using the number keys for inventory categories.

Let players customize key bindings. Although players tend to expect a reasonable set of defaults, many people need to customize a game's key bindings for personal comfort and play style.

## Mobile platforms

No additional considerations.

## Desktop

No additional considerations.

## Related

Designing for games
Gestures
Keyboards
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