yerzong/TEMP-LEAGUE / .claude/skills/apple-design
apple-design
VerifiedCross-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.
references/hig/offering-help.md
View on GitHub# Offering Help
> Source: [https://developer.apple.com/design/human-interface-guidelines/offering-help](https://developer.apple.com/design/human-interface-guidelines/offering-help)
---
Offering helpAlthough the most effective experiences are approachable and intuitive, you can provide contextual help when necessary.
## Best practices
Let your app's tasks inform the types of help people might need. For example, you might help people perform simple, one- or two-step tasks by displaying an inline view that succinctly describes the task. In contrast, if your app or game supports complex or multistep tasks you might want to provide a tutorial that teaches people how to accomplish larger goals. In general, directly relate the help you provide to the precise action or task people are doing right now and make it easy for people to dismiss or avoid the help if they don't need it.
Use relevant and consistent language and images in your help content. Always make sure guidance is appropriate for the current context. Be sure the terms and descriptions you use are consistent with the platform. For example, don't write copy that tells people to click a button on a mobile device or tap a menu item on a desktop.
Make sure all help content is inclusive.
Avoid bloating your help content by explaining how standard components or patterns work. Instead, describe the specific action or task that a standard element performs in your app or game. If your experience introduces a unique control or expects people to use an input device in a nonstandard way, orient people quickly, preferring animation or graphics to educate instead of a lengthy description.
Creating tipsA tip is a small, transient view that briefly describes how to use a feature in your app. Tips are a great way to teach people about new or less obvious features in your app, or help them discover faster ways to accomplish a task.
Use the most appropriate tip type for your app's user interface. Display a popover tip when you want to preserve the content flow, or an inline tip when you want to ensure that surrounding information is visible. You can use an annotation-style inline tip when pointing to a specific UI element, or a hint-style tip when it's not related to a specific piece of UI.
PopoverAnnotationHintUse tips for simple features. Tips work best on features that are easy to describe and that people can complete with a few simple steps. If a feature requires more than three actions, it's probably too complicated for a tip.
Make tips short, actionable, and engaging. A tip's goal is to encourage people to try new features. Use direct, action-oriented language to describe what the feature does and explain how to use it. Keep your tips to one or two sentences and avoid including content that's promotional or related to a different feature or user flow. Promotional content is anything that advertises, sells, or isn't aligned with the current context of what the person is doing.
Define rules to help ensure your tips reach the intended audience. Not everyone benefits from every tip. For example, people who've already used a feature won't appreciate viewing a tip that describes it. Use parameter-based or event-based eligibility rules to control when a tip appears, and only display a tip if someone might benefit from its use. When your app has more than one tip, set the display frequency so tips display at a reasonable cadence — for example, once every 24 hours.
If there's an image or symbol that people associate with the feature, consider including it in the tip, and prefer the filled variant. For example, a tip with a star can help people understand that the tip is related to favorites.
If the feature is represented by an image that the tip connects to directly, avoid repeating the same image in both the tip and the UI.
Use buttons to direct people to information or options. If your feature has settings people can customize, or you want to redirect people to an area where they can learn more about a feature, consider adding a button. Buttons can take people directly to the settings where they make adjustments. Or if there's more information people might find useful, add a button to take them to additional resources, such as a setup flow.
## Platform considerations
### Mobile
No additional considerations.
### Desktop
A tooltip (called a help tag in user documentation) displays a small, transient view that briefly describes how to use a component in the interface. Tooltips can appear when a person holds the pointer over an element.
Describe only the control that people indicate interest in. When people want to know how to use a specific control, they don't want to learn how to use nearby controls or how to perform a larger task.
Explain the action or task the control initiates. It often works well to begin the description with a verb — for example, "Restore default settings" or "Add or remove a language from the list."In general, avoid repeating a control's name in its tooltip. Repeating the name takes up space in the tooltip and rarely adds value to the description.
Be brief. As much as possible, limit tooltip content to a maximum of 60 to 75 characters (note that localization often changes the length of text). To make a description brief and direct, consider using a sentence fragment and omitting articles. If you need a lot of text to describe a control, consider simplifying your interface design.
Use sentence case. Sentence case tends to appear more casual and approachable. If you write complete sentences, omit ending punctuation unless it's required to be consistent with your app's style.
Consider offering context-sensitive tooltips. For example, you could provide different text for a control's different states.
## Related
OnboardingFeedbackWritingHelp menu
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |