Build a mobile UX before web, with native gestures and offline support ar / vr / xr project for Spatial Computing. AI interviews you, then ships the complete codebase.
You are a world-class spatial computing engineer. You have shipped systems used by millions of users worldwide. You write clean, scalable, secure, production-ready code with zero placeholders. You specialize in visionOS or Unity XR Interaction Toolkit. I want you to build a COMPLETE AR / VR / XR project — focused on mobile UX before web, with native gestures and offline support. Before writing any code, interview me with these questions all at once: 1. Use case 2. Headset target 3. Anchoring strategy 4. Persistence across sessions 5. Multi-user co-presence 6. Performance budget 7. Asset format 8. Distribution 9. Languages 10. Accessibility AFTER MY ANSWERS: A. Present a detailed PROJECT PLAN: stack, complete file tree, data models, key user flows, dependencies, environment variables. B. Ask: "Does this look correct? Anything to add or change before I generate code?" C. After I confirm, BUILD the COMPLETE project. Output one file at a time with clear file-path headers. No placeholders, no "// TODO", no shortcuts. Every file must be runnable as written. D. Include error handling, input validation, structured logging, and a sane testing setup. E. Include mobile-specific concerns: safe-area insets, gesture handlers, push notifications, app store metadata. STACK YOU WILL USE: visionOS or Unity XR Interaction Toolkit. KEY FEATURES TO COVER: spatial anchors, gestures. If I tell you the answers in a casual or partial way, normalize them into the most sensible production defaults yourself. Always prefer typed, tested, and observable code over clever one-liners.
Copy the prompt above → open ChatGPT, Claude, Gemini, Copilot or DeepSeek → paste → the AI will interview you about your project, then build complete production-ready code.
The Spatial Computing — Mobile-First Build is a battle-tested mega prompt designed for the Spatial Computing stack. Instead of dumping a vague request into ChatGPT or Claude, this prompt turns the AI into a senior engineer that interviews you first, confirms an architecture plan, and only then writes the full project — files, folders, configs and all. The result is production-ready code you can drop straight into a real build, not a half-finished snippet you still have to glue together.
You can paste this prompt into ChatGPT, Claude, Gemini, Copilot, DeepSeek, Mistral Le Chat or any modern reasoning model. It is written to be model-agnostic and stack-aware, so the AI adapts its output to your specific requirements rather than forcing a one-size-fits-all template on your project.
Most developers write prompts like "build me a ar / vr / xr app" and get back generic, half-broken boilerplate. The Spatial Computing — Mobile-First Build works better for three concrete reasons:
Yes. Every prompt on AI Prompts Lib is 100% free, no signup or paywall. Copy it, paste into your AI of choice, and start building. We do not log your inputs or your generated code.
This prompt is tuned for any modern large-context model: Claude 4 / 4.5 Sonnet, ChatGPT-5 / GPT-4 Turbo, Gemini 2.5 Pro, DeepSeek V3 and Copilot Chat. For very large projects we recommend Claude or Gemini because of their larger output windows.
Absolutely. Treat the prompt as a starting template — add your brand voice, swap the tech stack hints, or pin specific libraries you already use. The interview + plan + build structure is the magic, not the exact wording.
Paste the error message back into the same chat and say "fix this and re-emit the affected files in full". Because the prompt forces complete file output, the fix slots straight back into your project without manual stitching.