agentleFS
inttegrointtegro/labor/skills/apple-sheets/SKILL.md

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.

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
  1. Distinctive:

    Use this skill when designing, reviewing, or implementing Apple-platform sheets, action sheets, confirmation dialogs, menus, popovers, …

    line 8
  2. Distinctive:

    Prefer system presentation APIs first.

    line 15
  3. Very specific:

    Use .sheet for a focused task or detail surface related to the current screen.

    line 26
  4. Very specific:

    Use .confirmationDialog for action-sheet style decisions, especially destructive choices or short option lists triggered by a user action.

    line 27
  5. Very specific:

    Use Menu for nonmodal command groups that should not interrupt the task.

    line 28
  6. Very specific:

    Use Popover on iPad/macOS for contextual controls anchored to a source.

    line 29
  7. Distinctive:

    Use full-screen cover only for immersive flows, authentication, capture, or tasks that need a complete context break.

    line 30
  8. Distinctive:

    Use material, shadow, and scroll-edge blending to separate a sheet from content.

    line 35
  9. Distinctive:

    Keep the sheet's top edge soft: drag indicator, close controls, and pinned headers should sit on the same surface material as the content …

    line 36
  10. Distinctive:

    Avoid nested borders, bordered controls inside bordered cards, and extra separators after the final row in a section.

    line 39
  11. Very specific:

    Prefer .sheet, .presentationDetents, .presentationDragIndicator, .presentationCornerRadius, and .presentationBackground for native …

    line 51
  12. Distinctive:

    Put the scrim and sheet in one root overlay that ignores safe areas.

    line 53
  13. Very specific:

    Use .regularMaterial or an adaptive UIColor.systemGroupedBackground blend.

    line 55
  14. Distinctive:

    Add a soft top scroll-edge treatment when controls overlap scroll content.

    line 56
  15. Very specific:

    Use @Environment(\.colorScheme) for adaptive foregrounds, scrims, and shadows.

    line 57
  16. Distinctive:

    Use SF Symbols only when the symbol improves recognition.

    line 59
  17. Distinctive:

    Do not repeat similar icons in a related command group.

    line 60
  18. Distinctive:

    Keep destructive actions separated and tinted with the destructive role.

    line 61

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

Source baseline reviewed against official Apple Developer material on 2026-11-09.

Presentation Choice

  • Use .sheet for a focused task or detail surface related to the current screen.
  • Use .confirmationDialog for action-sheet style decisions, especially destructive choices or short option lists triggered by a user action.
  • Use Menu for nonmodal command groups that should not interrupt the task.
  • Use Popover on 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 .presentationBackground for 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 .regularMaterial or an adaptive UIColor.systemGroupedBackground blend; 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.