agentleFS
CarlosZieglerCarlosZiegler/zietec-skills/skills/design/apple-design-presentation/SKILL.md

apple-design-presentation

Skill1 starsChanged 51 days agoMITView on GitHub

Choose and review Apple presentation containers: alerts, action sheets, sheets, popovers, panels, windows, and share sheets. Use when interruption, task scope, dismissal, or window behavior matters.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check adaptation across the requested size classes and windowing environments.

    line 14

≈ “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 Presentation and Windows

Apply the skill

Classify the need before selecting a presentation: urgent actionable information, a choice after an intentional action, a bounded task, supplementary controls, or independent content. Choose the least disruptive container that supports that need.

Specify the presenting context, initial focus, dismissal routes, commit and cancel semantics, unsaved work, and the destination after closing. Prefer recovery through undo when it is sufficient; reserve confirmation for consequences that justify interruption.

Check adaptation across the requested size classes and windowing environments. Presentations should preserve the originating task and remain usable with a keyboard and assistive technology. Avoid building a second application inside nested sheets.

Topic references

Select the topic that matches the design decision; do not load this entire list by default.

  • Modality
  • Alerts
  • Action sheets
  • Sheets
  • Popovers
  • Panels
  • Windows
  • Activity views

Source use

These references are original operational summaries of Apple’s public HIG, checked on 2026-09-08. They are guidance for design decisions, not a reproduced manual or a guarantee of App Store acceptance.

Read only the topic references relevant to the current task. Each links to the full official page. Consult that page for exact specifications, platform exceptions, assets, and version-sensitive behavior; use current official developer documentation for APIs and availability. If live documentation is unavailable, state the snapshot date and identify assumptions instead of inventing current requirements.

The user’s product goals, selected framework, and authorized scope remain controlling. Distinguish a source recommendation from a hard platform requirement and from your own proposed implementation.

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.