Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add HalidSaglam/saglitzdesign-mcp --skill apple-platform-designgit clone --depth 1 https://github.com/HalidSaglam/saglitzdesign-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/halidsaglam/saglitzdesign-mcp/apple-platform-design)<a href="https://agentmods.dev/skills/halidsaglam/saglitzdesign-mcp/apple-platform-design"><img src="https://agentmods.dev/badge/skills/halidsaglam/saglitzdesign-mcp/apple-platform-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/halidsaglam/saglitzdesign-mcp/apple-platform-design"><img src="https://agentmods.dev/badge/skills/halidsaglam/saglitzdesign-mcp/apple-platform-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00095 | $0.01122 |
| Opus 5 | $0.00048 | $0.00561 |
| Sonnet 5 | $0.00019 | $0.00224 |
| Haiku 4.5 | $0.00010 | $0.00112 |
Grade A, and why
apple-platform-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apple Platform Design
Apple apps feel native because they respect platform conventions, use system materials and motion, and get the small physical details right. Copying a web or Android design onto iOS/macOS reads as foreign instantly.
Full depth is in the SaglitzDesign MCP (
npx saglitzdesign-mcp). Related documents includeapple-hig-liquid-glass,ios-app-design,macos-app-design,wwdc-design-principles,apple-accessibility,apple-shipping-readinessandapple-intelligence-design; useful tools includeaudit_apple_ui(point it at the Xcode project directory — it reads configuration and Swift source; directory only, no snippet mode),get_design_language,compare_design_languages(what to port from Android and what not to) andget_component_recipe(component, "swiftui")for real SwiftUI code; and the/saglitzdesign:build_mobile_app_uiand/saglitzdesign:port_to_platformworkflows.
Core HIG principles
- Hierarchy, harmony, consistency — content-first (defer to content), clear focus, familiar patterns.
- Respect system conventions: back gestures, share sheet, context menus, safe areas. Don't reinvent them. Which conventions apply is per-platform — text scaling is one that differs, see the iOS and macOS sections below.
Liquid Glass (iOS 26 / macOS Tahoe)
- Translucent, layered materials convey hierarchy — the navigation layer floats in glass over content. Use it for chrome (tab bars, toolbars, sheets), not everywhere.
- Capsule controls; content shows through with adaptive tint. Verify contrast/legibility over busy content (add a scrim if needed); adoption should be tasteful, not a gimmick.
Fluid-interface principles (WWDC "Designing Fluid Interfaces")
- Response: kill latency — respond to touch instantly.
- Direct manipulation: 1:1 finger tracking during gestures.
- Interruptibility (most important): every animation is redirectable mid-flight.
- Behavior over animation: use springs; hand off gesture velocity into the release; project momentum to where the gesture is going.
- Rubber-banding at boundaries; symmetric, anchored motion paths.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 53 lines · 95 tokens per session scan A d096dad0c0a2
apple-platform-design is a skill published in the GitHub repository HalidSaglam/saglitzdesign-mcp (5 stars, last pushed 7d ago), licensed MIT. It adds 95 tokens to every session and 1,122 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
readable-measure
Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use typography-scale.
von-restorff-effect
Apply the Von Restorff Effect — the element that differs from its neighbours is the one remembered. Use when a single action must dominate. For overall ordering rather than single-element emphasis, use visual-hierarchy.
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
color-system
Build a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use dark-mode-design; for chart palettes use data-visualization; for multi-brand token architecture use theming-system (design-systems).