How do I install the Platforms skill?

Run npx skillmds@latest add lucasilverentand/platforms in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Platforms safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Platforms?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Platforms free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Platforms?

lucasilverentand (@lucasilverentand) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Platforms by lucasilverentand — Agent Skill

Name: Platforms
Rating: 4.666666666666667 (3 reviews)
Author: lucasilverentand

Platforms

Apple Human Interface Guidelines by platform: iOS and iPadOS, macOS, watchOS, tvOS, and visionOS UI components, controls, navigation, and platform conventions. Use when designing, building, or auditing UI for a specific Apple platform. Pair with `foundations` for shared Apple design principles and `services` for framework integrations. User says: "design iPhone UI", "macOS component", "watchOS audit", "tvOS navigation", "visionOS layout".

File contents

Apple Platform Design

Platform-specific HIG for Apple operating systems. Use this skill when the user's question depends on device, input model, navigation conventions, or component behavior for iOS and iPadOS, macOS, watchOS, tvOS, or visionOS.

How to use

Choose the target platform from the selector below. If the user names more than one platform, read each matching glossary and compare only the relevant topics.
Read the platform glossary first. It maps UI topics to reference files under references/<platform>/.
Read only the matched references. Multi-file topics (×N) live in references/<platform>/<topic>/.
Pull in foundations for shared principles like color, typography, layout, accessibility, motion, SF Symbols, and shared UI elements.
Pull in services when the UI surfaces Apple frameworks or services like Apple Pay, HealthKit, Siri, widgets, sensors, media playback, or Wallet.
Stay platform-specific. Do not generalize a platform convention across Apple platforms unless the matching references agree.

Platform selector

Platform	Read first	Use when
iOS and iPadOS	`references/ios/glossary.md`	Designing for iPhone or iPad, auditing iOS/iPadOS UI, or checking touch-first component behavior.
macOS	`references/macos/glossary.md`	Designing for Mac, auditing desktop UI, or checking menu, window, pointer, keyboard, and productivity conventions.
watchOS	`references/watchos/glossary.md`	Designing for Apple Watch, auditing glanceable UI, or checking Digital Crown, complication, haptic, and compact interaction patterns.
tvOS	`references/tvos/glossary.md`	Designing for Apple TV, auditing living-room UI, or checking focus, remote, media, and large-screen navigation conventions.
visionOS	`references/visionos/glossary.md`	Designing for Apple Vision Pro, auditing spatial UI, or checking windows, volumes, immersive experiences, ornaments, and gaze/gesture behavior.

Routing rules

If the request is platform-agnostic, use foundations instead.
If the request is about a framework, service, or hardware capability, use services first, then come back here for platform-specific UI.
If a topic appears in both a platform reference and foundations, treat the platform reference as the override for that platform's behavior.
If the user asks for a cross-platform Apple design, compare the relevant platform references explicitly instead of blending them into one rule.

---name: platformsdescription: Apple Human Interface Guidelines by platform: iOS and iPadOS, macOS, watchOS, tvOS, and visionOS UI components, controls, navigation, and platform conventions. Use when designing, building, or auditing UI for a specific Apple platform. Pair with `foundations` for shared Apple design principles and `services` for framework integrations. User says: "design iPhone UI", "macOS component", "watchOS audit", "tvOS navigation", "visionOS layout".---# Apple Platform DesignPlatform-specific HIG for Apple operating systems. Use this skill when the user's question depends on device, input model, navigation conventions, or component behavior for iOS and iPadOS, macOS, watchOS, tvOS, or visionOS.## How to use1. **Choose the target platform** from the selector below. If the user names more than one platform, read each matching glossary and compare only the relevant topics.2. **Read the platform glossary first**. It maps UI topics to reference files under `references/<platform>/`.3. **Read only the matched references**. Multi-file topics (`×N`) live in `references/<platform>/<topic>/`.4. **Pull in `foundations`** for shared principles like color, typography, layout, accessibility, motion, SF Symbols, and shared UI elements.5. **Pull in `services`** when the UI surfaces Apple frameworks or services like Apple Pay, HealthKit, Siri, widgets, sensors, media playback, or Wallet.6. **Stay platform-specific**. Do not generalize a platform convention across Apple platforms unless the matching references agree.## Platform selector|Platform|Read first|Use when||---|---|---||iOS and iPadOS|`references/ios/glossary.md`|Designing for iPhone or iPad, auditing iOS/iPadOS UI, or checking touch-first component behavior.||macOS|`references/macos/glossary.md`|Designing for Mac, auditing desktop UI, or checking menu, window, pointer, keyboard, and productivity conventions.||watchOS|`references/watchos/glossary.md`|Designing for Apple Watch, auditing glanceable UI, or checking Digital Crown, complication, haptic, and compact interaction patterns.||tvOS|`references/tvos/glossary.md`|Designing for Apple TV, auditing living-room UI, or checking focus, remote, media, and large-screen navigation conventions.||visionOS|`references/visionos/glossary.md`|Designing for Apple Vision Pro, auditing spatial UI, or checking windows, volumes, immersive experiences, ornaments, and gaze/gesture behavior.|## Routing rules- If the request is platform-agnostic, use `foundations` instead.- If the request is about a framework, service, or hardware capability, use `services` first, then come back here for platform-specific UI.- If a topic appears in both a platform reference and `foundations`, treat the platform reference as the override for that platform's behavior.- If the user asks for a cross-platform Apple design, compare the relevant platform references explicitly instead of blending them into one rule.

Frequently asked questions