platform-design-skills / ipados
AGENTS.md603 starsChanged 8 months agoMITView on GitHub
iPad-specific HIG rules extending iOS patterns for the larger, multitasking-capable canvas. Reference: Apple HIG - Designing for iPadOS
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/android/AGENTS.mdAGENTS.md
- skills/ios/AGENTS.mdAGENTS.md
- skills/macos/AGENTS.mdAGENTS.md
- skills/tvos/AGENTS.mdAGENTS.md
- skills/visionos/AGENTS.mdAGENTS.md
- skills/watchos/AGENTS.mdAGENTS.md
- skills/web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- android-design-guidelinesSkill
- ios-design-guidelinesSkill
- ipados-design-guidelinesSkill
- macos-design-guidelinesSkill
- tvos-design-guidelinesSkill
- visionos-design-guidelinesSkill
- watchos-design-guidelinesSkill
- web-design-guidelinesSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
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
- Distinctive: line 29
Toolbar at top: instead of bottom navigation
- Distinctive: line 34
Never scale up an iPhone layout to fill the iPad screen — redesign for the larger canvas
- Distinctive: line 35
Never opt out of multitasking — every app must work in Split View and Slide Over
- Distinctive: line 36
Never use bottom tab bars in regular width — use sidebar navigation
- Distinctive: line 37
Never show popovers as full-screen sheets — anchor popovers to their source element
- Distinctive: line 38
Never hardcode pixel dimensions for specific iPad models
- Distinctive: line 39
Never omit hover states for interactive elements — trackpad users need visual feedback
- Distinctive: line 40
Never override system keyboard shortcuts (Cmd+H, Cmd+Tab, Cmd+Space)
- Distinctive: line 41
Never ignore drag and drop — at minimum support dragging text, images, and URLs
- Distinctive: line 42
Never block the keyboard from dismissing modal sheets on iPad
- Distinctive: line 43
Never present iPhone-style modals when a popover or inspector is more appropriate
- Distinctive: line 44
Never omit accessibility labels on icon-only buttons or custom interactive elements
- Distinctive: line 45
Never disable Dynamic Type scaling or clamp text size — iPad users rely on large type too
- Distinctive: line 46
Never create keyboard focus paths that trap or skip interactive elements in Split View
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.
Files
iPadOS Design Guidelines Skill
iPad-specific HIG rules extending iOS patterns for the larger, multitasking-capable canvas.
Reference: Apple HIG - Designing for iPadOS
Categories & Impact
| # | Category | Impact | Key Focus |
| 1 | Responsive Layout | CRITICAL | Adaptive layouts, size classes, column-based design |
| 2 | Multitasking | CRITICAL | Split View, Slide Over, Stage Manager, resizable windows |
| 3 | Navigation | CRITICAL | Sidebar, three-column layout, toolbar placement |
| 4 | Pointer & Trackpad | HIGH | Hover effects, magnetism, right-click, drag and drop |
| 5 | Keyboard | HIGH | Cmd shortcuts, discoverability overlay, tab navigation |
| 6 | Apple Pencil | MEDIUM | Scribble, hover detection, PencilKit |
| 7 | Drag and Drop | HIGH | Inter-app, multi-item, spring-loaded, Universal Control |
| 8 | External Display | MEDIUM | Extended content, AirPlay, display lifecycle |
| 9 | Accessibility | CRITICAL | VoiceOver labels, Dynamic Type, pointer accessibility, Full Keyboard Access |
Key Differentiators from iOS
- Sidebar replaces tab bar in regular width size class
- Multitasking is mandatory -- app must function at all split sizes
- Pointer support expected -- hover states, magnetism, right-click menus
- Keyboard shortcuts required -- Cmd+key for all major actions with discoverability overlay
- Drag and drop across apps -- first-class interaction pattern
- Stage Manager -- freely resizable windows, multiple scenes
- Toolbar at top instead of bottom navigation
- Three-column layouts for deep hierarchies
Never Do
- Never scale up an iPhone layout to fill the iPad screen — redesign for the larger canvas
- Never opt out of multitasking — every app must work in Split View and Slide Over
- Never use bottom tab bars in regular width — use sidebar navigation
- Never show popovers as full-screen sheets — anchor popovers to their source element
- Never hardcode pixel dimensions for specific iPad models
- Never omit hover states for interactive elements — trackpad users need visual feedback
- Never override system keyboard shortcuts (Cmd+H, Cmd+Tab, Cmd+Space)
- Never ignore drag and drop — at minimum support dragging text, images, and URLs
- Never block the keyboard from dismissing modal sheets on iPad
- Never present iPhone-style modals when a popover or inspector is more appropriate
- Never omit accessibility labels on icon-only buttons or custom interactive elements
- Never disable Dynamic Type scaling or clamp text size — iPad users rely on large type too
- Never create keyboard focus paths that trap or skip interactive elements in Split View
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
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.