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/modality.md

View on GitHub
# Modality

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

---

Modality is a design technique that presents content in a separate, dedicated mode that prevents interaction with the parent view and requires an explicit action to dismiss.

Presenting content modally can:

- Ensure that people receive critical information and, if necessary, act on it
- Provide options that let people confirm or modify their most recent action
- Help people perform a distinct, narrowly scoped task without losing track of their previous context
- Give people an immersive experience or help them concentrate on a complex task

Depending on the platform, you might use different components to present these types of modal experiences. For example, all platforms can present an alert, which is a modal view that delivers important information related to your app or game. In addition, each platform may define various types of modal views for presenting context-specific options, such as activity views, sheets, and confirmation dialogs or action sheets. To help people perform a distinct task, mobile platform apps tend to use sheets or popovers, but tablet and desktop apps might also just use a separate window.

To provide a temporary experience, like viewing media, or to help people perform a distinct, multistep task, like editing content, apps can offer a full-screen modal experience. In contrast, apps may also offer nonmodal types of full-screen experiences.

## Best practices

Present content modally only when there's a clear benefit. A modal experience takes people out of their current context and requires an action to dismiss, so it's important to use modality only when it helps people focus or make choices that affect their content or device.

Aim to keep modal tasks simple, short, and streamlined. If a modal task is too complicated, people can lose track of the task they suspended when they entered the modal view, especially if the modal view obscures their previous context.

Take care to avoid creating a modal experience that feels like an app within your app. In particular, presenting a hierarchy of views within a modal task can make people forget how to retrace their steps. If a modal task must contain subviews, provide a single path through the hierarchy and avoid including buttons that people might mistake for the button that dismisses the modal view.

Consider using a full-screen modal style for in-depth content or a complex task. A modal experience that fills a window or the device display minimizes distractions, so it can work well for presenting videos, photos, or camera views, or to support a multistep task like marking up a document or editing a photo.

Always give people an obvious way to dismiss a modal view. In general, it works well to follow the platform conventions people already know. For example, in mobile platforms apps, people typically expect to find a button in the top toolbar or swipe down; in desktop apps, people expect to find a button in the main content view.

When necessary, help people avoid data loss by getting confirmation before closing a modal view. Regardless of whether people use a dismiss gesture or a button, if closing the view could result in the loss of user-generated content, be sure to explain the situation and give people ways to resolve it. For example, in mobile, you might present an action sheet that includes a save option.

Make it easy to identify a modal view's task. When people enter a modal view, they switch away from their previous context and might not return to it right away. When you provide a title that names the modal view's task — or additional text that describes the task or provides guidance — you can help people keep their place in your app.

Let people dismiss a modal view before presenting another one. Allowing multiple modal views to be visible at the same time tends to create visual clutter and can make your app seem scattered and disorganized. People need to remember the context they were in before a modal view appears, so presenting multiple views adds to people's cognitive load, especially when a modal view hides another one by appearing on top of it. Although an alert can appear on top of all other content — including other modal views — you never want to display more than one alert at the same time.

## Platform considerations

No additional considerations for mobile and desktop platforms.

## Related

Sheets Alerts Popovers Action sheets Activity views
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