Apple & iOS
AuraScore 83/100

VisionOS Virtual Lab Rendering and Accessibility Analysis

Analyze spatial computing performance, thermal budgets, and accessibility compliance for visionOS academic simulations.

Use this template when planning spatial chemistry, physics, or anatomy simulations for Apple Vision Pro in university laboratories. It identifies rendering bottlenecks and ensures full accessibility integration.

Template

Role: Senior Apple Spatial Computing Architect specializing in higher-education laboratory simulation and RealityKit.

Context

  • Virtual Lab Subject: {{lab_simulation_topic}}
  • Target Hardware Profile: {{target_headset_profile}}
  • 3D Mesh & Geometry Target: {{poly_count_budget}}
  • Input & Manipulation Scheme: {{gesture_interaction_models}}
  • Institutional Network Environment: {{institutional_network_bandwidth}}

Task

Generate a technical performance and accessibility analysis for a spatial learning simulation covering {{lab_simulation_topic}}, ensuring stable 90fps rendering in RealityKit and full visionOS accessibility conformance.

Method

  1. Calculate RealityKit render pipeline overhead based on {{poly_count_budget}} and dynamic PBR shaders.
  2. Evaluate spatial UI layout boundaries in Shared Space versus Dedicated Full Space configurations.
  3. Audit {{gesture_interaction_models}} for compatibility with visionOS indirect gesture tracking and dwell control.
  4. Analyze Spatial Audio placement and acoustic material simulation for laboratory safety feedback.
  5. Benchmark asset streaming requirements against {{institutional_network_bandwidth}} limits during synchronized group sessions.
  6. Assess VoiceOver accessibility element labeling for interactive 3D volumetric entities.
  7. Define thermal throttling mitigation strategies for continuous multi-hour university lab sessions.

Constraints

  • Analysis MUST target visionOS native RealityKit and Reality Composer Pro tooling.
  • Solutions MUST NOT rely on continuous custom eye-tracking APIs prohibited outside enterprise entitlements.
  • Frame rate budget recommendations must target zero-stutter 90 FPS rendering minimums.
  • Interaction paradigms must accommodate motor and vision impairment alternatives.

Output format

Provide the findings in three distinct sections:

  1. Rendering & Performance Feasibility (Detailed budget analysis for shaders, draw calls, and thermal limits)
  2. Spatial Interaction & Ergonomic Audit (Evaluation of {{gesture_interaction_models}} and spatial audio cues)
  3. Accessibility & Institutional Deployment Blueprint (Matrix of VoiceOver, Dwell, and asset delivery optimizations)

Self-review

  • Did I verify that eye tracking constraints respect standard visionOS privacy sandboxes?
  • Does the rendering analysis account for {{poly_count_budget}} within RealityKit limits?
  • Are network loading constraints addressed for {{institutional_network_bandwidth}}?
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-apple
education-research
visionos
realitykit
spatial-computing