jpskill.com
📦 その他 コミュニティ 🟡 少し慣れが必要 👤 幅広いユーザー

📦 Hig Platforms

hig-platforms

Appleが定める、iPhoneやiPadなどの各デバイスに

⏱ よくある定型作業 半日 → 数分

📺 まず動画で見る(YouTube)

▶ 【Claude Code完全入門】誰でも使える/Skills活用法/経営者こそ使うべき ↗

※ jpskill.com 編集部が参考用に選んだ動画です。動画の内容と Skill の挙動は厳密には一致しないことがあります。

📜 元の英語説明(参考)

Apple Human Interface Guidelines for platform-specific design.

🇯🇵 日本人クリエイター向け解説

一言でいうと

Appleが定める、iPhoneやiPadなどの各デバイスに

※ jpskill.com 編集部が日本のビジネス現場向けに補足した解説です。Skill本体の挙動とは独立した参考情報です。

⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。

🎯 このSkillでできること

下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。

📦 インストール方法 (3ステップ)

  1. 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
  2. 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
  3. 3. 展開してできたフォルダを、ホームフォルダの .claude/skills/ に置く
    • · macOS / Linux: ~/.claude/skills/
    • · Windows: %USERPROFILE%\.claude\skills\

Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。

詳しい使い方ガイドを見る →
最終更新
2026-05-17
取得日時
2026-05-17
同梱ファイル
8

💬 こう話しかけるだけ — サンプルプロンプト

  • Hig Platforms の使い方を教えて
  • Hig Platforms で何ができるか具体例で見せて
  • Hig Platforms を初めて使う人向けにステップを案内して

これをClaude Code に貼るだけで、このSkillが自動発動します。

📖 Claude が読む原文 SKILL.md(中身を展開)

この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。

Apple HIG: Platform Design

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

  1. Each platform has a distinct identity. Do not port designs between platforms. Respect each platform's conventions, interaction models, and user expectations.

  2. iOS: touch-first. Direct manipulation on a handheld screen. Optimize for one-handed use. Navigation uses tab bars and push/pop stacks.

  3. iPadOS: expanded canvas. Support Split View, Slide Over, and Stage Manager. Use sidebars and multi-column layouts. Support pointer and keyboard alongside touch.

  4. macOS: pointer and keyboard. Dense information display is acceptable. Use menu bars, toolbars, and keyboard shortcuts extensively. Windows are resizable with precise control.

  5. tvOS: remote and focus. Viewed from a distance. Design for the Siri Remote with focus-based navigation. Large text, simple layouts, linear navigation.

  6. visionOS: spatial interaction. 3D environment using windows, volumes, and spaces. Eye tracking for targeting, indirect gestures for interaction. Respect ergonomic comfort zones.

  7. watchOS: glanceable and brief. Information consumable at a glance. Brief interactions. Digital Crown, haptics, and complications for timely content.

  8. Games: own paradigm. Free to define in-game interaction models, but still respect platform conventions for system interactions (notifications, accessibility, controllers).

Reference Index

Reference Topic Key content
designing-for-ios.md iOS Touch, tab bars, navigation stacks, gestures, screen sizes, safe areas
designing-for-ipados.md iPadOS Multitasking, sidebars, pointer, keyboard, Apple Pencil, Stage Manager
designing-for-macos.md macOS Menu bars, toolbars, window management, keyboard shortcuts, dense layouts, Dock
designing-for-tvos.md tvOS Focus engine, Siri Remote, lean-back experience, content-forward, parallax
designing-for-visionos.md visionOS Spatial computing, windows/volumes/spaces, eye tracking, hand gestures, depth
designing-for-watchos.md watchOS Glanceable UI, Digital Crown, complications, notifications, haptics
designing-for-games.md Games Controllers, immersive experiences, platform-specific conventions, accessibility

Decision Framework

  1. Identify the primary use context. On the go (iOS/watchOS), at a desk (macOS), on the couch (tvOS), spatial environment (visionOS)?

  2. Match input to interaction. Touch for direct manipulation, pointer for precision, gaze+gesture for spatial, Digital Crown for quick scrolling, remote for focus navigation.

  3. Adapt, don't replicate. A macOS sidebar becomes a tab bar on iPhone. A visionOS volume has no equivalent on watchOS. Translate intent, not implementation.

  4. Leverage platform strengths. Live Activities on iOS, Desktop Widgets on macOS, complications on watchOS, immersive spaces on visionOS.

  5. Maintain brand consistency while respecting each platform's visual language and interaction patterns.

Output Format

  1. Platform-specific recommendations citing relevant HIG sections.
  2. Platform differences table comparing navigation, input, layout, and conventions.
  3. Implementation notes per platform including recommended APIs and adaptation strategies.

Questions to Ask

  1. Which platforms are you targeting?
  2. New app or adapting an existing one? If existing, which platform is the base?
  3. SwiftUI or UIKit/AppKit?
  4. Need to support older OS versions?
  5. Primary use context? (On the go, desk, couch, spatial, glanceable?)

Related Skills

  • hig-foundations -- Shared principles (color, typography, accessibility, layout) across platforms
  • hig-patterns -- Interaction patterns that manifest differently per platform
  • hig-components-layout -- Navigation structures (tab bars, sidebars, split views) that vary by platform
  • hig-components-content -- Content display that adapts across platforms

Built by Raintree Technology · More developer tools

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

同梱ファイル

※ ZIPに含まれるファイル一覧。`SKILL.md` 本体に加え、参考資料・サンプル・スクリプトが入っている場合があります。