apple-sheets
Skill1 starsChanged 4 days agoMITView on GitHub
Apple-native guidance for sheets, action sheets, menus, popovers, modal surfaces, scrims, detents, and bottom-sheet interactions. Use when designing, reviewing, or implementing modal presentation on Apple platforms with SwiftUI or native system components.
In this repository21 other files it gives its agents.
- animation-vocabularySkill
- apple-chartsSkill
- apple-hig-componentsSkill
- apple-hig-foundationsSkill
- apple-hig-getting-startedSkill
- apple-hig-inputsSkill
- apple-hig-patternsSkill
- apple-hig-technologiesSkill
- batch-commitSkill
- fluid-interface-designSkill
- git-change-controlSkill
- improve-animationsSkill
- marketing-art-directionSkill
- marketing-product-mediaSkill
- marketing-reference-forensicsSkill
- marketing-visual-qaSkill
- message-delivery-integritySkill
- production-verificationSkill
- product-marketing-personasSkill
- security-auditSkill
- systems-builder-writingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 11 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when designing, reviewing, or implementing Apple-platform sheets, action sheets, confirmation dialogs, menus, popovers, …
- Distinctive: line 15
Prefer system presentation APIs first.
- Very specific: line 26
Use .sheet for a focused task or detail surface related to the current screen.
- Very specific: line 27
Use .confirmationDialog for action-sheet style decisions, especially destructive choices or short option lists triggered by a user action.
- Very specific: line 28
Use Menu for nonmodal command groups that should not interrupt the task.
- Very specific: line 29
Use Popover on iPad/macOS for contextual controls anchored to a source.
- Distinctive: line 30
Use full-screen cover only for immersive flows, authentication, capture, or tasks that need a complete context break.
- Distinctive: line 35
Use material, shadow, and scroll-edge blending to separate a sheet from content.
- Distinctive: line 36
Keep the sheet's top edge soft: drag indicator, close controls, and pinned headers should sit on the same surface material as the content …
- Distinctive: line 39
Avoid nested borders, bordered controls inside bordered cards, and extra separators after the final row in a section.
- Very specific: line 51
Prefer .sheet, .presentationDetents, .presentationDragIndicator, .presentationCornerRadius, and .presentationBackground for native …
- Distinctive: line 53
Put the scrim and sheet in one root overlay that ignores safe areas.
- Very specific: line 55
Use .regularMaterial or an adaptive UIColor.systemGroupedBackground blend.
- Distinctive: line 56
Add a soft top scroll-edge treatment when controls overlap scroll content.
- Very specific: line 57
Use @Environment(\.colorScheme) for adaptive foregrounds, scrims, and shadows.
- Distinctive: line 59
Use SF Symbols only when the symbol improves recognition.
- Distinctive: line 60
Do not repeat similar icons in a related command group.
- Distinctive: line 61
Keep destructive actions separated and tinted with the destructive role.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Apple Sheets
Use this skill when designing, reviewing, or implementing Apple-platform sheets, action sheets, confirmation dialogs, menus, popovers, bottom sheets, stacked sheets, modal overlays, custom presentation panels, or sheet dismissal and drag behavior.
Source Model
- Sheets help people complete a scoped task that is closely related to the current context.
- Action sheets present choices related to an action the user initiated; keep them brief, focused, and clearly tied to the source action.
- WWDC 2025 design system guidance emphasizes content-first structure, legible floating controls, concentric geometry, soft scroll-edge effects, and consistent component anatomy across devices.
- Prefer system presentation APIs first. Custom sheets are acceptable only when the product interaction cannot be expressed with the platform presentation while preserving native motion, accessibility, and appearance.
Primary references:
- https://developer.apple.com/design/human-interface-guidelines/sheets
- https://developer.apple.com/design/human-interface-guidelines/action-sheets
- https://developer.apple.com/videos/play/wwdc2025/356/
Source baseline reviewed against official Apple Developer material on 2026-11-09.
Presentation Choice
- Use
.sheetfor a focused task or detail surface related to the current screen. - Use
.confirmationDialogfor action-sheet style decisions, especially destructive choices or short option lists triggered by a user action. - Use
Menufor nonmodal command groups that should not interrupt the task. - Use
Popoveron iPad/macOS for contextual controls anchored to a source; adapt to sheets on compact iPhone where appropriate. - Use full-screen cover only for immersive flows, authentication, capture, or tasks that need a complete context break.
Visual Rules
- The sheet surface must feel native to the current appearance. In light mode, avoid pure white-on-white seams; in dark mode, avoid a flat black slab.
- Use material, shadow, and scroll-edge blending to separate a sheet from content. Do not use hard dividers or opaque header bands to solve legibility.
- Keep the sheet's top edge soft: drag indicator, close controls, and pinned headers should sit on the same surface material as the content below.
- Match shapes concentrically. A rounded sheet should contain controls whose radii, inset, and spacing feel derived from the parent geometry.
- Scrims should recede the background without fighting the sheet. Make the scrim adaptive to light/dark appearance.
- Avoid nested borders, bordered controls inside bordered cards, and extra separators after the final row in a section.
Motion Rules
- Entry and exit must share one spatial path. If a sheet rises from the bottom, it should dismiss downward with velocity-aware spring motion.
- Sheet movement should be interruptible. Drag progress should map directly to sheet position and continue from the current visual state on release.
- Scroll views inside sheets should scroll normally until they reach the top. Only then should a downward pull transfer to interactive dismissal.
- Stacked sheets should preserve depth: dismissing the front sheet should restore the previous sheet without a visual reset.
- Respect Reduce Motion by shortening duration and avoiding decorative movement while preserving state changes.
SwiftUI Guidance
- Prefer
.sheet,.presentationDetents,.presentationDragIndicator,.presentationCornerRadius, and.presentationBackgroundfor native presentation. - For custom bottom sheets:
- Put the scrim and sheet in one root overlay that ignores safe areas.
- Build the sheet surface once, then place the drag indicator, close affordance, and scroll content on that same surface.
- Use
.regularMaterialor an adaptiveUIColor.systemGroupedBackgroundblend; avoid separate header rectangles. - Add a soft top scroll-edge treatment when controls overlap scroll content.
- Use
@Environment(\.colorScheme)for adaptive foregrounds, scrims, and shadows.
- For action menus:
- Use SF Symbols only when the symbol improves recognition.
- Do not repeat similar icons in a related command group; use labels for clarity.
- Keep destructive actions separated and tinted with the destructive role.
Review Checklist
- The source action and sheet purpose are obvious.
- Text, buttons, drag handles, and close controls are legible in light and dark mode.
- The sheet has no hard top seam, accidental border, or mismatched header background.
- Last rows in grouped sections do not render trailing dividers.
- Background content recedes, but the sheet still feels connected to the originating context.
- Drag-to-dismiss, tap-outside dismissal, keyboard behavior, Dynamic Type, Reduce Motion, and VoiceOver labels have been tested.
- For screenshots, capture both light and dark appearances plus at least one active sheet/menu state.
Attribution
Apple, SwiftUI, SF Symbols, and related product names are trademarks of Apple Inc. This independently written skill is not affiliated with or endorsed by Apple.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

