콘텐츠로 이동

Spatial

You will produce a spatial design spec for the experience described in $ARGUMENTS.

Input

Parse $ARGUMENTS. Expect: - An experience (e.g., "Vision Pro productivity app", "Quest VR training", "iOS ARKit product viewer", "HoloLens medical training", "WebXR exhibit"). - Optionally: mode (VR / AR / MR / WebXR), platform, use case, audience, session length.

If ambiguous, ask one clarifying question — but only one. Otherwise apply reasonable defaults and proceed.

Steps

  1. Pick mode + platform to determine which knowledge files apply (VR vs AR; Vision Pro vs Quest vs HoloLens vs mobile).

  2. Apply the spatial-designer playbook:

  3. Spatial geometry (coordinate system, height, comfort distance, FOV).
  4. Anchoring per UI element (world / wrist / hand / head / object).
  5. Locomotion if VR (teleport / smooth / hybrid + comfort options).
  6. Input methods + accessibility alternatives (hand / controller / gaze / voice).
  7. UI elements with sizing, states, audio.
  8. Comfort options (locomotion, vignette, motion, flashing).
  9. Accessibility across vision / hearing / motor / cognitive.
  10. Onboarding.
  11. Korean / regional considerations.

  12. Performance budget.

  13. Output using the structure in PLAYBOOK.md step 12.

Done when

  • Mode + platform + use case + audience explicit.
  • Spatial geometry specified.
  • Anchoring per UI element documented.
  • Locomotion options if VR (with comfort defaults).
  • Input methods + alternatives.
  • UI elements with sizing + states.
  • Comfort options addressed.
  • Accessibility plan covering vision / hearing / motor / cognitive / photosensitive / mobility.
  • Onboarding planned.
  • Korean / regional considerations if applicable.
  • Performance budget stated.
  • "Don't" catches 2-3 misuses.
  • Verification phase from PLAYBOOK.md passes.