xr-interface-architect
Designs spatial UI layouts, prototypes hand gesture interactions, creates 3D menu systems, and plans gaze-based navigation for AR/VR/XR applications. Provides ergonomic placement guidelines, comfort zone thresholds, input latency budgets, and accessibility fallback patterns for immersive interfaces across platforms including Meta Quest, Apple Vision Pro, and WebXR. Use when the user asks about spatial computing interfaces, VR/AR UI design, mixed reality interactions, hand tracking UX, HUD design, holographic displays, headset UI, immersive environment layouts, 3D interface design, cockpit dashboards, or comfort-zone-compliant panel placement.
96
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers specific capabilities, includes a comprehensive set of natural trigger terms, and clearly delineates both what the skill does and when it should be used. It occupies a distinct niche in spatial/immersive computing UI design with minimal risk of conflicting with other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Designs spatial UI layouts', 'prototypes hand gesture interactions', 'creates 3D menu systems', 'plans gaze-based navigation', and further specifies deliverables like 'ergonomic placement guidelines, comfort zone thresholds, input latency budgets, and accessibility fallback patterns'. | 3 / 3 |
Completeness | Clearly answers both 'what' (designs spatial UI layouts, prototypes gestures, creates 3D menus, provides ergonomic guidelines) and 'when' with an explicit 'Use when...' clause listing numerous trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'spatial computing interfaces', 'VR/AR UI design', 'mixed reality interactions', 'hand tracking UX', 'HUD design', 'holographic displays', 'headset UI', '3D interface design', 'cockpit dashboards', and specific platform names like 'Meta Quest', 'Apple Vision Pro', 'WebXR'. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a very clear niche in AR/VR/XR spatial interface design with highly specific triggers like 'comfort-zone-compliant panel placement', 'hand tracking UX', and 'gaze-based navigation' that are unlikely to conflict with general UI or web design skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent domain-specific content: precise numeric thresholds, executable code in multiple frameworks, structured JSON templates, and a well-validated workflow. Its main weakness is that all content lives in a single file without progressive disclosure to separate reference material from the core workflow, which is a minor issue given the content density. Overall, it is one of the stronger skill files one could encounter.
Suggestions
Consider splitting the code snippets and layout templates into a referenced file (e.g., TEMPLATES.md or CODE_EXAMPLES.md) to improve progressive disclosure and keep the main skill leaner.
The accessibility fallback table and ergonomic thresholds could also be referenced as separate quick-reference files, with the SKILL.md providing a summary and links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section delivers domain-specific thresholds, values, and patterns that Claude would not inherently know (e.g., exact arc sizes, latency budgets, comfort zone angles). No filler explanations of what AR/VR is or how Unity works. Every token earns its place. | 3 / 3 |
Actionability | Provides fully executable Unity C# and Three.js code snippets, copy-paste-ready JSON layout templates, specific numeric thresholds, and concrete input model patterns. Guidance is precise and immediately usable. | 3 / 3 |
Workflow Clarity | The 6-step XR Menu Design Workflow is clearly sequenced with explicit validation checklists at Steps 2 and 5, an iteration/feedback loop at Step 6, and specific measurable criteria (neck rotation < 30°, depth > 0.4 m, latency budgets). This is a strong example of validation checkpoints and error recovery. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and logical grouping, but everything is inline in a single file. For a skill of this length (~150+ lines), some content like the full code snippets or the accessibility table could be split into referenced files. No external references are provided. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-agents
- Commit
010799b
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.