[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASRRMM8AC9Q0G0YQH6FSKT":3,"skill-same:01M7ASRRMM8AC9Q0G0YQH6FSKT":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ASRRMM8AC9Q0G0YQH6FSKT","xr-ux-design-and-performance-budgeting",null,"Use when designing the experience and making it hold frame rate: UX design for 3D including affordances, depth cues, text legibility, comfortable placement zones and the conventions users already expect, and performance budgeting — the frame budget, draw calls, fill rate, and the profiling method for a target device.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fvr-ar-development\u002Fskills\u002Fxr-ux-design-and-performance-budgeting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: xr-ux-design-and-performance-budgeting\ndescription: \"Use when designing the experience and making it hold frame rate: UX design for 3D including affordances, depth cues, text legibility, comfortable placement zones and the conventions users already expect, and performance budgeting — the frame budget, draw calls, fill rate, and the profiling method for a target device.\"\n---\n\n# VR and AR Development: UX Design for 3D and Performance Budgeting\n\n> **Part 4 of 5** of the *VR and AR Development* reference (plugin `vr-ar-development`), covering §10–§11. Sibling skills: `xr-perceptual-constraints-displays-and-tracking` (§0–§3), `xr-rendering-input-and-spatial-understanding` (§4–§6), `xr-platforms-audio-and-comfort` (§7–§9), `xr-reference` (§12–§17). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The perceptual constraints are human physiology and permanent; the platform and hardware landscape moves fast. See §14 → `xr-reference` for the current picture.\n\n> **Scope.** Assumes a graphics reference for the rendering fundamentals (rasterization,\n> PBR, the rendering equation) and a computer-vision reference for SLAM and multi-view\n> geometry. **This is the XR-specific layer built on top of both.**\n>\n> **⚠️ GOTCHA** boxes mark what makes users physically ill or breaks presence.\n>\n> **The three facts that make XR its own discipline:**\n> 1. **⚠️ You are rendering to a nervous system, not a screen.** The frame budget is set by\n>    human perception, and missing it doesn't drop quality — **it makes people nauseated**\n>    (§1 → `xr-perceptual-constraints-displays-and-tracking`). **No other software has this property.**\n> 2. **⚠️ Latency is the master constraint and it is not a performance metric.** Motion-to-\n>    photon under ~20 ms is the consensus threshold, and it governs your entire\n>    architecture (§1.1 → `xr-perceptual-constraints-displays-and-tracking`).\n> 3. **⚠️ Presence is fragile and asymmetric.** It takes sustained correctness to build and\n>    one bad frame, one wrong-scale object, one mistracked hand to destroy. **Everything\n>    in §9 → `xr-platforms-audio-and-comfort` and §10 is about protecting it.**\n\n---\n\n## §10. UX Design for 3D\n\n**⚠️ Text is the first thing that goes wrong.** Panel resolution and PPD (§2 → `xr-perceptual-constraints-displays-and-tracking`) mean text\nmust be **larger and closer than your instinct says**, high contrast, and **never at the\nextreme periphery.** **Test on device, always** — desktop preview is systematically\nmisleading.\n\n**Comfortable placement**: ⚠️ **content roughly 0.5–20 m; the sweet spot for reading is\naround 1–3 m.** **Keep the primary content within a modest cone around forward gaze\n(roughly ±30° horizontal, less vertically)** — ⚠️ **and remember neck strain: looking up is\nmuch worse than looking down.**\n\n**⚠️ Diegetic UI beats floating panels.** A screen welded to the face breaks presence and\nis uncomfortable; **put the interface on a wrist, a tool, a physical panel in the world.**\n\n**Scale and affordance**: ⚠️ **incorrect scale is immediately and viscerally wrong** to\nusers, even when they can't articulate why. **Objects that look grabbable must be\ngrabbable.** **Give feedback for everything** — highlight, haptic, sound — because\n⚠️ **without haptics, the visual and audio confirmation is the only signal that an\ninteraction registered.**\n\n**⚠️ Never move the camera without user input** (§1.2 → `xr-perceptual-constraints-displays-and-tracking`). **Never lock content to the head\nrigidly** — use lazy-follow \u002F body-locked positioning with damping.\n\n---\n\n## §11. Performance Budgeting\n\n**⚠️ The budget is brutal and it is per-eye.** At **90 Hz you have 11.1 ms for two eyes**;\nat 120 Hz, **8.3 ms.** ⚠️ **And on standalone hardware you're on a mobile SoC with a\nthermal ceiling — sustained performance is well below burst performance, so profile after\n20 minutes, not after 20 seconds.**\n\n**Where the time goes**: draw calls and CPU submission (⚠️ **batch aggressively; single-pass\nstereo, §4.1 → `xr-rendering-input-and-spatial-understanding`**), overdraw and fill rate (⚠️ **the usual mobile-XR killer**), bandwidth\n(TBDR, §4.4 → `xr-rendering-input-and-spatial-understanding`), shader complexity, and physics.\n\n**Levers**: aggressive LOD, occlusion culling, **baked lighting** (⚠️ **lightmaps remain\nthe best quality-per-millisecond in XR**), **FFR** (§4.3 → `xr-rendering-input-and-spatial-understanding`), texture atlasing, **GPU\ninstancing**, simplified shaders, and **reducing render scale before reducing frame rate**\n— ⚠️ **frame rate is non-negotiable in a way resolution isn't.**\n\n**⚠️ Profile on device.** The editor and a desktop GPU tell you almost nothing about a\nstandalone headset. **RenderDoc, the platform's own profilers, and frame-time histograms\nrather than averages** — ⚠️ **because a 1% frame spike is a visible, presence-breaking\nhitch and averages hide it completely.**\n","# VR and AR Development: UX Design for 3D and Performance Budgeting\n\n> **Part 4 of 5** of the *VR and AR Development* reference (plugin `vr-ar-development`), covering §10–§11. Sibling skills: `xr-perceptual-constraints-displays-and-tracking` (§0–§3), `xr-rendering-input-and-spatial-understanding` (§4–§6), `xr-platforms-audio-and-comfort` (§7–§9), `xr-reference` (§12–§17). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The perceptual constraints are human physiology and permanent; the platform and hardware landscape moves fast. See §14 → `xr-reference` for the current picture.\n\n> **Scope.** Assumes a graphics reference for the rendering fundamentals (rasterization,\n> PBR, the rendering equation) and a computer-vision reference for SLAM and multi-view\n> geometry. **This is the XR-specific layer built on top of both.**\n>\n> **⚠️ GOTCHA** boxes mark what makes users physically ill or breaks presence.\n>\n> **The three facts that make XR its own discipline:**\n> 1. **⚠️ You are rendering to a nervous system, not a screen.** The frame budget is set by\n>    human perception, and missing it doesn't drop quality — **it makes people nauseated**\n>    (§1 → `xr-perceptual-constraints-displays-and-tracking`). **No other software has this property.**\n> 2. **⚠️ Latency is the master constraint and it is not a performance metric.** Motion-to-\n>    photon under ~20 ms is the consensus threshold, and it governs your entire\n>    architecture (§1.1 → `xr-perceptual-constraints-displays-and-tracking`).\n> 3. **⚠️ Presence is fragile and asymmetric.** It takes sustained correctness to build and\n>    one bad frame, one wrong-scale object, one mistracked hand to destroy. **Everything\n>    in §9 → `xr-platforms-audio-and-comfort` and §10 is about protecting it.**\n\n---\n\n## §10. UX Design for 3D\n\n**⚠️ Text is the first thing that goes wrong.** Panel resolution and PPD (§2 → `xr-perceptual-constraints-displays-and-tracking`) mean text\nmust be **larger and closer than your instinct says**, high contrast, and **never at the\nextreme periphery.** **Test on device, always** — desktop preview is systematically\nmisleading.\n\n**Comfortable placement**: ⚠️ **content roughly 0.5–20 m; the sweet spot for reading is\naround 1–3 m.** **Keep the primary content within a modest cone around forward gaze\n(roughly ±30° horizontal, less vertically)** — ⚠️ **and remember neck strain: looking up is\nmuch worse than looking down.**\n\n**⚠️ Diegetic UI beats floating panels.** A screen welded to the face breaks presence and\nis uncomfortable; **put the interface on a wrist, a tool, a physical panel in the world.**\n\n**Scale and affordance**: ⚠️ **incorrect scale is immediately and viscerally wrong** to\nusers, even when they can't articulate why. **Objects that look grabbable must be\ngrabbable.** **Give feedback for everything** — highlight, haptic, sound — because\n⚠️ **without haptics, the visual and audio confirmation is the only signal that an\ninteraction registered.**\n\n**⚠️ Never move the camera without user input** (§1.2 → `xr-perceptual-constraints-displays-and-tracking`). **Never lock content to the head\nrigidly** — use lazy-follow \u002F body-locked positioning with damping.\n\n---\n\n## §11. Performance Budgeting\n\n**⚠️ The budget is brutal and it is per-eye.** At **90 Hz you have 11.1 ms for two eyes**;\nat 120 Hz, **8.3 ms.** ⚠️ **And on standalone hardware you're on a mobile SoC with a\nthermal ceiling — sustained performance is well below burst performance, so profile after\n20 minutes, not after 20 seconds.**\n\n**Where the time goes**: draw calls and CPU submission (⚠️ **batch aggressively; single-pass\nstereo, §4.1 → `xr-rendering-input-and-spatial-understanding`**), overdraw and fill rate (⚠️ **the usual mobile-XR killer**), bandwidth\n(TBDR, §4.4 → `xr-rendering-input-and-spatial-understanding`), shader complexity, and physics.\n\n**Levers**: aggressive LOD, occlusion culling, **baked lighting** (⚠️ **lightmaps remain\nthe best quality-per-millisecond in XR**), **FFR** (§4.3 → `xr-rendering-input-and-spatial-understanding`), texture atlasing, **GPU\ninstancing**, simplified shaders, and **reducing render scale before reducing frame rate**\n— ⚠️ **frame rate is non-negotiable in a way resolution isn't.**\n\n**⚠️ Profile on device.** The editor and a desktop GPU tell you almost nothing about a\nstandalone headset. **RenderDoc, the platform's own profilers, and frame-time histograms\nrather than averages** — ⚠️ **because a 1% frame spike is a visible, presence-breaking\nhitch and averages hide it completely.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fvr-ar-development\u002Fskills\u002Fxr-ux-design-and-performance-budgeting",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill xr-ux-design-and-performance-budgeting",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill xr-ux-design-and-performance-budgeting",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill xr-ux-design-and-performance-budgeting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fvr-ar-development\u002Fskills\u002Fxr-ux-design-and-performance-budgeting\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]