[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P9RDQJHMFX75T8JDZ3A25":3,"skill-same:01M71P9RDQJHMFX75T8JDZ3A25":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":57,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M71P9RDQJHMFX75T8JDZ3A25","visionos-engineer",null,"Use when an org role acts as visionOS engineer and must build Vision Pro spatial apps with SwiftUI, RealityKit and ARKit: windows, volumes, immersion. Covers scene-type choice, gaze-sized hit targets and platform interaction conventions.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fvisionos-engineer\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"visionos engineer","visionos","engineer","query","monomind","when","palette","org","impact","interaction","apps","frontend","immersion","mobile","vision","fix","context","choice","windows","swift","2026-11-10 13:02:02",false,"---\nname: visionos-engineer\ndescription: \"Use when an org role acts as visionOS engineer and must build Vision Pro spatial apps with SwiftUI, RealityKit and ARKit: windows, volumes, immersion. Covers scene-type choice, gaze-sized hit targets and platform interaction conventions.\"\ntags: [\"frontend\",\"engineering\",\"swift\",\"mobile\"]\ntools: [\"monograph_query\",\"monograph_context\",\"monograph_impact\",\"monodesign_detect\",\"monodesign_fix\",\"monodesign_palette\"]\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# visionOS Engineer — Best Practices\n\n## Focus\nBuilds spatial computing experiences for Apple Vision Pro using SwiftUI, RealityKit, and ARKit — windows, volumes, and immersive spaces that respect the platform's unique input and interaction model.\n\n## Best practices\n- Start with window-based apps when possible — existing SwiftUI skills and iOS\u002FiPadOS code transfer directly, minimizing platform-specific rework.\n- Design hit targets generously (minimum ~60pt) to account for the imprecision of eye-tracking-based gaze selection before a pinch confirms.\n- Choose the right scene type deliberately — windows for 2D content, volumes for bounded 3D content, full spaces for immersive experiences — don't default to full immersion when a window suffices.\n- Specify preferred interface orientation explicitly (`UIPreferredDefaultInterfaceOrientation`) since visionOS has no screen rotation concept.\n- Use Reality Composer Pro for 3D content authoring and iterate with Live Preview on-device rather than guessing at spatial layout from the simulator alone.\n- Design for comfort: avoid forcing rapid head movement, sustained close-range focus, or motion that could induce discomfort during extended sessions.\n- Layer spatial audio and depth cues to reinforce object placement rather than relying on visual cues alone.\n\n## Common pitfalls\n- Porting a flat iOS UI directly into a volume\u002Fspace without rethinking depth and spatial hierarchy.\n- Undersized or ambiguous hit targets that fail with gaze-based selection.\n- Ignoring comfort guidelines, producing experiences that fatigue or disorient users on longer sessions.\n- Treating the simulator as sufficient for spatial\u002Finteraction validation instead of testing on-device.\n\n## Tools & techniques\n- RealityKit for real-time 3D rendering and physics; ARKit for scene understanding and anchoring to the real environment.\n- Reality Composer Pro for authoring, previewing, and iterating on 3D\u002Fspatial content with Live Preview.\n- Xcode's visionOS simulator for early iteration, backed by on-device testing before shipping.\n- Apple's Human Interface Guidelines for visionOS as the authoritative source for spatial interaction and comfort standards.\n","# visionOS Engineer — Best Practices\n\n## Focus\nBuilds spatial computing experiences for Apple Vision Pro using SwiftUI, RealityKit, and ARKit — windows, volumes, and immersive spaces that respect the platform's unique input and interaction model.\n\n## Best practices\n- Start with window-based apps when possible — existing SwiftUI skills and iOS\u002FiPadOS code transfer directly, minimizing platform-specific rework.\n- Design hit targets generously (minimum ~60pt) to account for the imprecision of eye-tracking-based gaze selection before a pinch confirms.\n- Choose the right scene type deliberately — windows for 2D content, volumes for bounded 3D content, full spaces for immersive experiences — don't default to full immersion when a window suffices.\n- Specify preferred interface orientation explicitly (`UIPreferredDefaultInterfaceOrientation`) since visionOS has no screen rotation concept.\n- Use Reality Composer Pro for 3D content authoring and iterate with Live Preview on-device rather than guessing at spatial layout from the simulator alone.\n- Design for comfort: avoid forcing rapid head movement, sustained close-range focus, or motion that could induce discomfort during extended sessions.\n- Layer spatial audio and depth cues to reinforce object placement rather than relying on visual cues alone.\n\n## Common pitfalls\n- Porting a flat iOS UI directly into a volume\u002Fspace without rethinking depth and spatial hierarchy.\n- Undersized or ambiguous hit targets that fail with gaze-based selection.\n- Ignoring comfort guidelines, producing experiences that fatigue or disorient users on longer sessions.\n- Treating the simulator as sufficient for spatial\u002Finteraction validation instead of testing on-device.\n\n## Tools & techniques\n- RealityKit for real-time 3D rendering and physics; ARKit for scene understanding and anchoring to the real environment.\n- Reality Composer Pro for authoring, previewing, and iterating on 3D\u002Fspatial content with Live Preview.\n- Xcode's visionOS simulator for early iteration, backed by on-device testing before shipping.\n- Apple's Human Interface Guidelines for visionOS as the authoritative source for spatial interaction and comfort standards.\n",{"name":5,"tags":48,"tools":50,"source":57,"license":14,"description":7},[34,49,42,36],"engineering",[51,52,53,54,55,56],"monograph_query","monograph_context","monograph_impact","monodesign_detect","monodesign_fix","monodesign_palette","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fvisionos-engineer",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add monoes\u002Fmonomind --skill visionos-engineer",{"tool":72,"command":73},"bunx","bunx skills add monoes\u002Fmonomind --skill visionos-engineer",{"tool":75,"command":76},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill visionos-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fvisionos-engineer\u002FSKILL.md",true,[],[81,102,135,162,187,214],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":43},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[88,89,90,91,25,40,92,93,31,26,94,95,27,96,97,98,99,100,30,101],"zk","zk steward","steward","zero-knowledge","design","knowledge","snark","review","security review","stark","zettelkasten","cryptography","security","blockchain",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":118,"publishedAt":43},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[110,113],{"categoryNo":111,"categoryName":112,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[119,120,121,25,122,123,28,124,26,125,126,127,128,129,130,131,132,133,39,134],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","ZeRO",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":145,"publishedAt":43},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000031","产品经理",[129,146,147,148,149,93,150,28,151,152,153,128,154,155,156,157,158,159,160,161],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":43},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000033","数据分析师",[26,129,173,174,175,176,93,160,28,177,178,179,180,153,181,182,183,184,185,186],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":199,"publishedAt":43},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":197,"categoryName":198,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[200,201,202,203,175,204,205,206,207,31,208,209,210,26,27,181,211,212,213,183],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":43},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[220],{"categoryNo":197,"categoryName":198,"taxonomyType":20,"taxonomyTypeDesc":21},[202,222,223,224,225,226,227,175,228,229,125,230,231,232,27,181,233,234,183,235],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]