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

apple-design-principles

Skill1 starsChanged 51 days agoMITView on GitHub

Apply Apple’s Human Interface Guidelines design principles to product concepts, design tradeoffs, or interface critiques for Apple platforms. Use for reasoning about experience quality rather than detailed component specifications.

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:

    When producing a concept, show how the proposed interaction resolves the decision.

    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 Design Principles

Apply the skill

Identify the person, task, context, and intended feeling before evaluating the interface. Read the principles reference and choose the principles that explain the actual decision; do not force an eight-part report onto every request.

For competing proposals, state what each improves, what it costs, and which tradeoff best serves the product’s purpose. Tie every critique to an observable behavior or a concrete revision. Preserve the product’s identity and the user’s requested scope. A design recommendation does not authorize redesigning unrelated flows.

When producing a concept, show how the proposed interaction resolves the decision. When reviewing, lead with consequential problems and actionable changes; distinguish observed failures from questions that need user testing.

Topic references

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

  • Design principles

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.