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/entering-data.md

View on GitHub
# Entering Data

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

---

When you need information from people, design ways that make it easy for them to provide it without making mistakes.

Entering information can be a tedious process regardless of the interaction methods people use. Improve the experience by:

- Pre-gathering as much information as possible to minimize the amount of data that people need to supply
- Supporting all available input methods so people can choose the method that works for them

## Best practices

Get information from the system whenever possible. Don't ask people to enter information that you can gather automatically — such as from settings — or by getting their permission, such as their location or calendar information.

Be clear about the data you need. For example, you might display a prompt in a text field — like "username@company.com" — or provide an introductory label that describes the information, like "Email." You can also prefill fields with reasonable default values, which can minimize decision making and speed data entry.

Use a secure text-entry field when appropriate. If your app or game needs sensitive data, use a field that obscures people's input as they enter it, typically by displaying a small filled circle symbol for each character.

Never prepopulate a password field. Always ask people to enter their password or use biometric or keychain authentication.

When possible, offer choices instead of requiring text entry. It's usually easier and more efficient to choose from lists of options than to type information, even when a keyboard is conveniently available. When it makes sense, consider using a picker, menu, or other selection component to give people an easy way to provide the information you need.

As much as possible, let people provide data by dragging and dropping it or by pasting it. Supporting these interactions can ease data entry and make your experience feel more integrated with the rest of the system.

Dynamically validate field values. People can get frustrated when they have to go back and correct mistakes after filling out a lengthy form. When you verify values as soon as people enter them — and provide feedback as soon as you detect a problem — you give them the opportunity to correct errors right away. For numeric data in particular, consider using a number formatter, which automatically configures a text field to accept only numeric values. You can also configure a formatter to display the value in a specific way, such as with a certain number of decimal places, as a percentage, or as currency.

When data entry is necessary, make sure people understand that they must provide the required data before they can proceed. For example, if you include a Next or Continue button after a set of text fields, make the button available only after people enter the data you require.

## Desktop

Consider using an expansion tooltip to show the full version of clipped or truncated text in a field. An expansion tooltip behaves like a regular tooltip, appearing when the pointer rests on top of a field. Apps running on desktop can use an expansion tooltip to help people view the complete data they entered when a text field is too small to display it.

## Related

Text fields
Virtual keyboards
Keyboards
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