[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F17PWKYP8PBY0HPY31QPM8":3,"skill-same:01M7F17PWKYP8PBY0HPY31QPM8":54},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7F17PWKYP8PBY0HPY31QPM8","ios-route-planner",null,"Turn an iOS app idea or feature request into an Apple-native route before code is written — framework and symbol choices, state\u002Fdata boundary, native surface, permission\u002Fentitlement\u002Fprivacy matrix, fallback states, and a proportional verification plan. Use when starting a new iOS\u002FiPadOS\u002FwatchOS\u002FCarPlay\u002FApp Clip\u002FvisionOS app or feature, choosing between Apple frameworks, or untangling framework, permission, or system-surface confusion in an existing project.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-ops\u002Fskills\u002Fios-route-planner\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ios-route-planner\ndescription: Turn an iOS app idea or feature request into an Apple-native route before code is written — framework and symbol choices, state\u002Fdata boundary, native surface, permission\u002Fentitlement\u002Fprivacy matrix, fallback states, and a proportional verification plan. Use when starting a new iOS\u002FiPadOS\u002FwatchOS\u002FCarPlay\u002FApp Clip\u002FvisionOS app or feature, choosing between Apple frameworks, or untangling framework, permission, or system-surface confusion in an existing project.\nallowed-tools: Read, Grep, Glob, Write\nlast_verified: 2026-08-19\n---\n\n# iOS Route Planner\n\n## Overview\n\nTurn an idea into a route record and evidence plan before framework choices harden\ninto implementation. This skill plans; the domain skills build. Hand off once the\nroute is chosen:\n\n| Lane | Skill |\n| --- | --- |\n| Targets, modules, extensions, schemes | [ios-project-target-architect](..\u002Fios-project-target-architect\u002FSKILL.md) |\n| SwiftUI screens and Liquid Glass | [ios-native-design](..\u002Fios-native-design\u002FSKILL.md) |\n| Foundation Models, Vision, Core ML, Speech, Translation | [ios-on-device-intelligence](..\u002Fios-on-device-intelligence\u002FSKILL.md) |\n| Camera, audio, media, NFC, MusicKit, ShazamKit | [ios-media-and-inputs](..\u002Fios-media-and-inputs\u002FSKILL.md) |\n| Persistence, sync, HealthKit, accessories | [ios-data-and-device-services](..\u002Fios-data-and-device-services\u002FSKILL.md) |\n| StoreKit, Apple Pay, sign-in, Keychain, crypto | [ios-commerce-identity-and-security](..\u002Fios-commerce-identity-and-security\u002FSKILL.md) |\n| Widgets, Live Activities, extensions, background | [ios-system-surfaces-and-background](..\u002Fios-system-surfaces-and-background\u002FSKILL.md) |\n| Watch, CarPlay, App Clips, calling, push | [ios-companion-communications](..\u002Fios-companion-communications\u002FSKILL.md) |\n| AR, RealityKit, Metal, SpriteKit, Game Center | [ios-spatial-graphics-and-games](..\u002Fios-spatial-graphics-and-games\u002FSKILL.md) |\n| Tests, device proof, privacy manifest, TestFlight | [ios-release-proof](..\u002Fios-release-proof\u002FSKILL.md) |\n\n`outcome -> narrow Apple route -> state\u002Fdata boundary -> native surface -> permission\u002Fentitlement -> lifecycle\u002Ffallback -> verification evidence`\n\n## Read before acting\n\n- Inspect the actual repository and target: Xcode project\u002Fworkspace, schemes,\n  deployment target, platforms\u002Fdevice families, modules, persistence, networking,\n  extensions, entitlements, `Info.plist`, privacy manifest, existing system\n  surfaces, and current tests. If no target exists, label the work bootstrap.\n- Start from the [knowledge-base index](..\u002Fios-knowledge-base\u002Freferences\u002FREADME.md),\n  the [framework selection questionnaire](..\u002Fios-knowledge-base\u002Freferences\u002F00-foundations\u002F06-framework-selection-questionnaire.md),\n  and the [idea-to-route recipe](..\u002Fios-knowledge-base\u002Freferences\u002F50-capability-recipes\u002F00-idea-to-route.md).\n- The [capability-first SDK atlas](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F10-capability-first-apple-sdk-atlas.md),\n  [framework catalog](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F00-framework-catalog.md), and\n  [availability and device matrix](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F08-framework-availability-and-device-matrix.md)\n  are large. Grep them for the framework or capability name; do not read them whole.\n- Before relying on a symbol, availability condition, entitlement, or system\n  behavior, re-open the official page listed in the matching\n  [source registry](..\u002Fios-knowledge-base\u002Freferences\u002Fsources\u002FREADME.md) file.\n  The knowledge base was last checked against iOS 26 \u002F Xcode 26 in August 2026.\n\n## Route workflow\n\n1. **Intake.** State the outcome in one sentence. Record entry point, primary\n   action, accepted result, consequence of error, offline requirement, privacy\n   sensitivity, supported platforms, and non-goals.\n2. **Classify the capability:** present\u002Fedit, persist\u002Fsync, capture\u002Fanalyze,\n   communicate, locate\u002Fmap\u002Fweather, use protected data, control a device,\n   transact\u002Fauthenticate, expose to the system, share\u002Fexport, run in the\n   background, spatial\u002Fgraphics\u002Fgame, or companion surface.\n3. **Select the narrowest Apple route** that owns the capability. Prefer\n   system-owned surfaces and first-party frameworks before a custom service.\n   Name concrete symbols and rejected alternatives, and list which signatures\n   still need an Xcode check.\n4. **Draw the handoff:** `input -> framework operation -> normalized evidence ->\n   deterministic validation -> domain truth -> derived presentation -> system\u002Fcompanion handoff`.\n   Keep UI state, persistence, model output, and external system state distinct.\n5. **Build the state matrix before the happy path:** ready, denied, restricted,\n   unsupported, unavailable, loading, partial, stale, interrupted, cancelled,\n   empty, invalid, conflict, completed — where relevant. Keep a manual or\n   local-first path when it satisfies the goal.\n6. **List configuration:** permissions, usage descriptions, entitlements,\n   background modes, App Groups, associated domains, accounts\u002Fservices, language\n   or model assets, hardware, server dependencies. Mark each `to-verify`; never\n   infer it from a framework name.\n7. **Choose proportional evidence:** source, compile, fixture, simulator,\n   physical device, two-device\u002Faccessory\u002Fvehicle, system surface, signed\n   artifact, TestFlight\u002FApp Store, production. Name what each proves and what it\n   cannot.\n8. **Record the route** in the project's planning docs or the\n   [design brief template](..\u002Fios-knowledge-base\u002Freferences\u002F90-templates\u002Fdesign-brief.md),\n   then stop unless the user asked for the build. If they did, hand the first\n   narrow slice to the owning lane skill.\n\n## Fast path\n\nFor one feature, compare only the plausible lanes against outcome ownership,\ntarget availability, setup cost, fallback, and required proof. Pick the route\nwith the least irreversible configuration; record the rest as rejected or\ndeferred. Freeze `outcome -> trusted input -> smallest transformation ->\nuser-visible destination` and plan one slice with one source, one failure path,\nand one proof task.\n\n## Route record\n\n| Field | Required content |\n| --- | --- |\n| Outcome and consequence | User task, primary action, acceptable failure, reversibility |\n| Selected route | Frameworks, symbols, platforms, rejected alternatives, open API questions |\n| Data boundary | Source, normalization, persistence, sync, retention, deletion |\n| UI\u002Fsystem boundary | Screen, extension, Watch\u002FCarPlay\u002Fspatial surface, deep link, fallback |\n| State\u002Flifecycle | Permission, availability, cancel\u002Finterrupt\u002Fbackground\u002Faccount states |\n| Trust boundary | Validation, authorization, confirmation, idempotency, side effects |\n| Configuration | Entitlements, usage strings, privacy manifest, modes, domains, servers |\n| Tests | Fixtures, unit\u002FUI\u002Faccessibility\u002Fperformance, device and system runs |\n| Evidence gaps | Claims not yet proven and the next smallest verification |\n\n## Change boundary\n\nMay inspect the project and write scoped planning, route, permission, and\nverification documents. Do not infer authorization for new accounts, cloud\nstorage, analytics, paid services, background execution, health data,\nproduction credentials, deployment, or contacting users.\n\nThe capability decision table and refusal list are in `references\u002Fdetails.md`.\n","# iOS Route Planner\n\n## Overview\n\nTurn an idea into a route record and evidence plan before framework choices harden\ninto implementation. This skill plans; the domain skills build. Hand off once the\nroute is chosen:\n\n| Lane | Skill |\n| --- | --- |\n| Targets, modules, extensions, schemes | [ios-project-target-architect](..\u002Fios-project-target-architect\u002FSKILL.md) |\n| SwiftUI screens and Liquid Glass | [ios-native-design](..\u002Fios-native-design\u002FSKILL.md) |\n| Foundation Models, Vision, Core ML, Speech, Translation | [ios-on-device-intelligence](..\u002Fios-on-device-intelligence\u002FSKILL.md) |\n| Camera, audio, media, NFC, MusicKit, ShazamKit | [ios-media-and-inputs](..\u002Fios-media-and-inputs\u002FSKILL.md) |\n| Persistence, sync, HealthKit, accessories | [ios-data-and-device-services](..\u002Fios-data-and-device-services\u002FSKILL.md) |\n| StoreKit, Apple Pay, sign-in, Keychain, crypto | [ios-commerce-identity-and-security](..\u002Fios-commerce-identity-and-security\u002FSKILL.md) |\n| Widgets, Live Activities, extensions, background | [ios-system-surfaces-and-background](..\u002Fios-system-surfaces-and-background\u002FSKILL.md) |\n| Watch, CarPlay, App Clips, calling, push | [ios-companion-communications](..\u002Fios-companion-communications\u002FSKILL.md) |\n| AR, RealityKit, Metal, SpriteKit, Game Center | [ios-spatial-graphics-and-games](..\u002Fios-spatial-graphics-and-games\u002FSKILL.md) |\n| Tests, device proof, privacy manifest, TestFlight | [ios-release-proof](..\u002Fios-release-proof\u002FSKILL.md) |\n\n`outcome -> narrow Apple route -> state\u002Fdata boundary -> native surface -> permission\u002Fentitlement -> lifecycle\u002Ffallback -> verification evidence`\n\n## Read before acting\n\n- Inspect the actual repository and target: Xcode project\u002Fworkspace, schemes,\n  deployment target, platforms\u002Fdevice families, modules, persistence, networking,\n  extensions, entitlements, `Info.plist`, privacy manifest, existing system\n  surfaces, and current tests. If no target exists, label the work bootstrap.\n- Start from the [knowledge-base index](..\u002Fios-knowledge-base\u002Freferences\u002FREADME.md),\n  the [framework selection questionnaire](..\u002Fios-knowledge-base\u002Freferences\u002F00-foundations\u002F06-framework-selection-questionnaire.md),\n  and the [idea-to-route recipe](..\u002Fios-knowledge-base\u002Freferences\u002F50-capability-recipes\u002F00-idea-to-route.md).\n- The [capability-first SDK atlas](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F10-capability-first-apple-sdk-atlas.md),\n  [framework catalog](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F00-framework-catalog.md), and\n  [availability and device matrix](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F08-framework-availability-and-device-matrix.md)\n  are large. Grep them for the framework or capability name; do not read them whole.\n- Before relying on a symbol, availability condition, entitlement, or system\n  behavior, re-open the official page listed in the matching\n  [source registry](..\u002Fios-knowledge-base\u002Freferences\u002Fsources\u002FREADME.md) file.\n  The knowledge base was last checked against iOS 26 \u002F Xcode 26 in August 2026.\n\n## Route workflow\n\n1. **Intake.** State the outcome in one sentence. Record entry point, primary\n   action, accepted result, consequence of error, offline requirement, privacy\n   sensitivity, supported platforms, and non-goals.\n2. **Classify the capability:** present\u002Fedit, persist\u002Fsync, capture\u002Fanalyze,\n   communicate, locate\u002Fmap\u002Fweather, use protected data, control a device,\n   transact\u002Fauthenticate, expose to the system, share\u002Fexport, run in the\n   background, spatial\u002Fgraphics\u002Fgame, or companion surface.\n3. **Select the narrowest Apple route** that owns the capability. Prefer\n   system-owned surfaces and first-party frameworks before a custom service.\n   Name concrete symbols and rejected alternatives, and list which signatures\n   still need an Xcode check.\n4. **Draw the handoff:** `input -> framework operation -> normalized evidence ->\n   deterministic validation -> domain truth -> derived presentation -> system\u002Fcompanion handoff`.\n   Keep UI state, persistence, model output, and external system state distinct.\n5. **Build the state matrix before the happy path:** ready, denied, restricted,\n   unsupported, unavailable, loading, partial, stale, interrupted, cancelled,\n   empty, invalid, conflict, completed — where relevant. Keep a manual or\n   local-first path when it satisfies the goal.\n6. **List configuration:** permissions, usage descriptions, entitlements,\n   background modes, App Groups, associated domains, accounts\u002Fservices, language\n   or model assets, hardware, server dependencies. Mark each `to-verify`; never\n   infer it from a framework name.\n7. **Choose proportional evidence:** source, compile, fixture, simulator,\n   physical device, two-device\u002Faccessory\u002Fvehicle, system surface, signed\n   artifact, TestFlight\u002FApp Store, production. Name what each proves and what it\n   cannot.\n8. **Record the route** in the project's planning docs or the\n   [design brief template](..\u002Fios-knowledge-base\u002Freferences\u002F90-templates\u002Fdesign-brief.md),\n   then stop unless the user asked for the build. If they did, hand the first\n   narrow slice to the owning lane skill.\n\n## Fast path\n\nFor one feature, compare only the plausible lanes against outcome ownership,\ntarget availability, setup cost, fallback, and required proof. Pick the route\nwith the least irreversible configuration; record the rest as rejected or\ndeferred. Freeze `outcome -> trusted input -> smallest transformation ->\nuser-visible destination` and plan one slice with one source, one failure path,\nand one proof task.\n\n## Route record\n\n| Field | Required content |\n| --- | --- |\n| Outcome and consequence | User task, primary action, acceptable failure, reversibility |\n| Selected route | Frameworks, symbols, platforms, rejected alternatives, open API questions |\n| Data boundary | Source, normalization, persistence, sync, retention, deletion |\n| UI\u002Fsystem boundary | Screen, extension, Watch\u002FCarPlay\u002Fspatial surface, deep link, fallback |\n| State\u002Flifecycle | Permission, availability, cancel\u002Finterrupt\u002Fbackground\u002Faccount states |\n| Trust boundary | Validation, authorization, confirmation, idempotency, side effects |\n| Configuration | Entitlements, usage strings, privacy manifest, modes, domains, servers |\n| Tests | Fixtures, unit\u002FUI\u002Faccessibility\u002Fperformance, device and system runs |\n| Evidence gaps | Claims not yet proven and the next smallest verification |\n\n## Change boundary\n\nMay inspect the project and write scoped planning, route, permission, and\nverification documents. Do not infer authorization for new accounts, cloud\nstorage, analytics, paid services, background execution, health data,\nproduction credentials, deployment, or contacting users.\n\nThe capability decision table and refusal list are in `references\u002Fdetails.md`.\n",{"name":5,"description":7,"allowed-tools":24,"last_verified":25},"Read, Grep, Glob, Write",1787097600000,"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fios-ops\u002Fskills\u002Fios-route-planner","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill ios-route-planner",{"tool":40,"command":41},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill ios-route-planner",{"tool":43,"command":44},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill ios-route-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-ops\u002Fskills\u002Fios-route-planner\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdetails.md","REFERENCE","参考文档",6847,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-ops\u002Fskills\u002Fios-route-planner\u002Freferences\u002Fdetails.md",[55,61,68,75,82,89],{"skillNo":56,"name":57,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]