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

apple-design-foundations

Skill1 starsChanged 52 days agoMITView on GitHub

Design or review the visual foundations of an Apple-platform interface: layout, typography, color, appearance, materials, motion, icons, imagery, branding, and interface writing.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Start from the existing visual system and the content hierarchy.

    line 10
  2. Distinctive:

    Prefer system behavior for adaptive typography, color, materials, and controls.

    line 12

≈ “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 Visual Design Foundations

Apply the skill

Start from the existing visual system and the content hierarchy. Decide which values should be semantic roles, which belong to the brand, and which must adapt to platform or accessibility settings. Read only the references for the layers being changed.

Prefer system behavior for adaptive typography, color, materials, and controls. Document custom choices in terms of purpose and state, not merely fixed pixels. Separate content surfaces from the navigation and control layer when choosing materials. Do not apply a visual trend uniformly to every surface.

Validate the composition with representative content, large text, light and dark appearances, increased contrast, reduced motion, and relevant window sizes. For an icon or asset deliverable, inspect the current platform specifications and preview the actual small-size and appearance variants before declaring it ready.

Topic references

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

  • Layout
  • Typography
  • Color
  • Dark Mode
  • Materials
  • Motion
  • Icons
  • SF Symbols
  • App icons
  • Images
  • Branding
  • Writing

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.