メニュー
Load when a frontend task needs Apple-platform design guidance or physical, gesture-driven, velocity-aware, interruptible interaction; skip generic visual styling and use review-animations for report-only motion review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | apple-design |
| description | Load when a frontend task needs Apple-platform design guidance or physical, gesture-driven, velocity-aware, interruptible interaction; skip generic visual styling and use review-animations for report-only motion review. |
| license | MIT |
| metadata | {"source":"emilkowalski/skills skills/apple-design","upstream_commit":"7bb7061b5cf7de15ea1aeaf00fbd9e6592a20fce","adaptation":"Narrow routing and progressive disclosure; volatile API and browser claims require current evidence."} |
Use Apple interface principles when the platform context or interaction genuinely benefits from direct manipulation, velocity continuity, interruptibility, spatial consistency, or physical feedback. Do not apply Apple visual styling by default.
Read references/interface-principles.md when designing or implementing gesture-driven UI, springs, drag or sheet interactions, momentum, translucent materials, typography, or accessibility adaptations.
This Skill owns Apple and physical-interaction guidance. It does not own general frontend styling, animation terminology, or review verdicts. Use frontend-design for production UI, animation-vocabulary for naming, and review-animations for report-only motion review.
Load when a task needs a throwaway prototype, state-model sanity check, UI variant, image-assisted visual mockup, mock interaction, or playable design; do not use for production feature work.
Load when a user describes a Web animation or motion effect without knowing its name and needs the precise term or close alternatives; use only for naming, not design, implementation, or review.
Load when a task needs polished product UI, web pages, landing pages, dashboards, React components, HTML/CSS layouts, or styling; skip routine frontend logic and reports.
Load when a task needs React or Next.js frontend logic, component patterns, state, forms, routing, accessibility, or responsive behavior; use frontend-design for visual direction.
Load when an existing Web product, especially a dashboard, dense-data view, or multi-step app, needs a deep evidence-backed experience review; report findings only, and use design-taste-frontend for marketing-page direction, code-review for source diffs, web-design-guidelines for checklist compliance, or frontend-design for implementation.
Load when existing animation or motion code, a motion diff, or a rendered interaction needs an evidence-backed craft review; report findings only and use code-review for general source review.
