platform-design-skills / visionos
AGENTS.md603 starsChanged 8 months agoMITView on GitHub
Spatial computing design skill based on Apple Human Interface Guidelines for Apple Vision Pro. Provide authoritative design guidance for visionOS apps covering spatial layout, eye and hand input, windows, volumes, immersive spaces, materials, and ornaments. This skill activates when tasks involve: - visionOS or Apple Vision Pro development - Spatial UI design and layout - Eye and hand input implementation - RealityKit or RealityComposer Pro - Mixed reality or immersive experience design - Window, volume, or immersive space architecture
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/ipados/AGENTS.mdAGENTS.md
- skills/macos/AGENTS.mdAGENTS.md
- skills/tvos/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
We split this AGENTS.md into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
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 48
Never head-lock UI — all content must be world-anchored
- Distinctive: line 49
Never place interactive elements below 60pt in size
- Distinctive: line 50
Never skip hover/gaze feedback on interactive elements
- Distinctive: line 51
Never use gaze direction for analytics or content decisions (privacy violation)
- Distinctive: line 52
Never force immersion on launch — start in the Shared Space
- Distinctive: line 53
Never trap users in full immersion with no exit
- Distinctive: line 54
Never place content behind the user
- Distinctive: line 55
Never position windows or objects closer than ~0.5m (personal space)
- Distinctive: line 56
Never use opaque backgrounds in shared space (except media)
- Distinctive: line 57
Never omit accessibility labels on interactive elements and 3D objects
≈ “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
visionOS Design Guidelines
Spatial computing design skill based on Apple Human Interface Guidelines for Apple Vision Pro.
Purpose
Provide authoritative design guidance for visionOS apps covering spatial layout, eye and hand input, windows, volumes, immersive spaces, materials, and ornaments.
Skill Files
| File | Contents |
SKILL.md | Complete design guidelines with rules, checklist, and anti-patterns |
rules/_sections.md | Categorized rule reference with severity levels |
metadata.json | Version, references, and abstract |
Usage
This skill activates when tasks involve:
- visionOS or Apple Vision Pro development
- Spatial UI design and layout
- Eye and hand input implementation
- RealityKit or RealityComposer Pro
- Mixed reality or immersive experience design
- Window, volume, or immersive space architecture
Rule Categories
| # | Category | Impact |
| 1 | Spatial Layout | CRITICAL |
| 2 | Eye & Hand Input | CRITICAL |
| 3 | Windows | HIGH |
| 4 | Volumes | HIGH |
| 5 | Immersive Spaces | HIGH |
| 6 | Materials & Depth | MEDIUM |
| 7 | Ornaments | MEDIUM |
| 8 | Accessibility | CRITICAL |
Priority Levels
- CRITICAL: Violations break core spatial UX or cause user discomfort
- HIGH: Violations degrade experience significantly
- MEDIUM: Violations miss polish or platform conventions
Never Do
- Never head-lock UI — all content must be world-anchored
- Never place interactive elements below 60pt in size
- Never skip hover/gaze feedback on interactive elements
- Never use gaze direction for analytics or content decisions (privacy violation)
- Never force immersion on launch — start in the Shared Space
- Never trap users in full immersion with no exit
- Never place content behind the user
- Never position windows or objects closer than ~0.5m (personal space)
- Never use opaque backgrounds in shared space (except media)
- Never omit accessibility labels on interactive elements and 3D objects
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.