[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ABEXP8HV6NPXKCM4HS4090":3,"skill-same:01M7ABEXP8HV6NPXKCM4HS4090":78},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7ABEXP8HV6NPXKCM4HS4090","swiftui-performance-audit",null,"Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU\u002Fmemory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.","jjonesdev\u002Fpersonal-development-environment","jjonesdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F36642060?v=4","01M7ABDJ8E65BGK15CQ2MGVKES","Jordan","01M7ABDJ9M8SE7F0DHQ91ATWDM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: swiftui-performance-audit\ndescription: Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU\u002Fmemory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.\n---\n\n# SwiftUI Performance Audit\n\n## Quick start\n\nUse this skill to diagnose SwiftUI performance issues from code first, then request profiling evidence when code review alone cannot explain the symptoms.\n\n## Workflow\n\n1. Classify the symptom: slow rendering, janky scrolling, high CPU, memory growth, hangs, or excessive view updates.\n2. If code is available, start with a code-first review using `references\u002Fcode-smells.md`.\n3. If code is not available, ask for the smallest useful slice: target view, data flow, reproduction steps, and deployment target.\n4. If code review is inconclusive or runtime evidence is required, guide the user through profiling with `references\u002Fprofiling-intake.md`.\n5. Summarize likely causes, evidence, remediation, and validation steps using `references\u002Freport-template.md`.\n\n## 1. Intake\n\nCollect:\n- Target view or feature code.\n- Symptoms and exact reproduction steps.\n- Data flow: `@State`, `@Binding`, environment dependencies, and observable models.\n- Whether the issue shows up on device or simulator, and whether it was observed in Debug or Release.\n\nAsk the user to classify the issue if possible:\n- CPU spike or battery drain\n- Janky scrolling or dropped frames\n- High memory or image pressure\n- Hangs or unresponsive interactions\n- Excessive or unexpectedly broad view updates\n\nFor the full profiling intake checklist, read `references\u002Fprofiling-intake.md`.\n\n## 2. Code-First Review\n\nFocus on:\n- Invalidation storms from broad observation or environment reads.\n- Unstable identity in lists and `ForEach`.\n- Heavy derived work in `body` or view builders.\n- Layout thrash from complex hierarchies, `GeometryReader`, or preference chains.\n- Large image decode or resize work on the main thread.\n- Animation or transition work applied too broadly.\n\nUse `references\u002Fcode-smells.md` for the detailed smell catalog and fix guidance.\n\nProvide:\n- Likely root causes with code references.\n- Suggested fixes and refactors.\n- If needed, a minimal repro or instrumentation suggestion.\n\n## 3. Guide the User to Profile\n\nIf code review does not explain the issue, ask for runtime evidence:\n- A trace export or screenshots of the SwiftUI timeline and Time Profiler call tree.\n- Device\u002FOS\u002Fbuild configuration.\n- The exact interaction being profiled.\n- Before\u002Fafter metrics if the user is comparing a change.\n\nUse `references\u002Fprofiling-intake.md` for the exact checklist and collection steps.\n\n## 4. Analyze and Diagnose\n\n- Map the evidence to the most likely category: invalidation, identity churn, layout thrash, main-thread work, image cost, or animation cost.\n- Prioritize problems by impact, not by how easy they are to explain.\n- Distinguish code-level suspicion from trace-backed evidence.\n- Call out when profiling is still insufficient and what additional evidence would reduce uncertainty.\n\n## 5. Remediate\n\nApply targeted fixes:\n- Narrow state scope and reduce broad observation fan-out.\n- Stabilize identities for `ForEach` and lists.\n- Move heavy work out of `body` into derived state updated from inputs, model-layer precomputation, memoized helpers, or background preprocessing. Use `@State` only for view-owned state, not as an ad hoc cache for arbitrary computation.\n- Use `equatable()` only when equality is cheaper than recomputing the subtree and the inputs are truly value-semantic.\n- Downsample images before rendering.\n- Reduce layout complexity or use fixed sizing where possible.\n\nUse `references\u002Fcode-smells.md` for examples, Observation-specific fan-out guidance, and remediation patterns.\n\n## 6. Verify\n\nAsk the user to re-run the same capture and compare with baseline metrics.\nSummarize the delta (CPU, frame drops, memory peak) if provided.\n\n## Outputs\n\nProvide:\n- A short metrics table (before\u002Fafter if available).\n- Top issues (ordered by impact).\n- Proposed fixes with estimated effort.\n\nUse `references\u002Freport-template.md` when formatting the final audit.\n\n## References\n\n- Profiling intake and collection checklist: `references\u002Fprofiling-intake.md`\n- Common code smells and remediation patterns: `references\u002Fcode-smells.md`\n- Audit output template: `references\u002Freport-template.md`\n- Add Apple documentation and WWDC resources under `references\u002F` as they are supplied by the user.\n- Optimizing SwiftUI performance with Instruments: `references\u002Foptimizing-swiftui-performance-instruments.md`\n- Understanding and improving SwiftUI performance: `references\u002Funderstanding-improving-swiftui-performance.md`\n- Understanding hangs in your app: `references\u002Funderstanding-hangs-in-your-app.md`\n- Demystify SwiftUI performance (WWDC23): `references\u002Fdemystify-swiftui-performance-wwdc23.md`\n","# SwiftUI Performance Audit\n\n## Quick start\n\nUse this skill to diagnose SwiftUI performance issues from code first, then request profiling evidence when code review alone cannot explain the symptoms.\n\n## Workflow\n\n1. Classify the symptom: slow rendering, janky scrolling, high CPU, memory growth, hangs, or excessive view updates.\n2. If code is available, start with a code-first review using `references\u002Fcode-smells.md`.\n3. If code is not available, ask for the smallest useful slice: target view, data flow, reproduction steps, and deployment target.\n4. If code review is inconclusive or runtime evidence is required, guide the user through profiling with `references\u002Fprofiling-intake.md`.\n5. Summarize likely causes, evidence, remediation, and validation steps using `references\u002Freport-template.md`.\n\n## 1. Intake\n\nCollect:\n- Target view or feature code.\n- Symptoms and exact reproduction steps.\n- Data flow: `@State`, `@Binding`, environment dependencies, and observable models.\n- Whether the issue shows up on device or simulator, and whether it was observed in Debug or Release.\n\nAsk the user to classify the issue if possible:\n- CPU spike or battery drain\n- Janky scrolling or dropped frames\n- High memory or image pressure\n- Hangs or unresponsive interactions\n- Excessive or unexpectedly broad view updates\n\nFor the full profiling intake checklist, read `references\u002Fprofiling-intake.md`.\n\n## 2. Code-First Review\n\nFocus on:\n- Invalidation storms from broad observation or environment reads.\n- Unstable identity in lists and `ForEach`.\n- Heavy derived work in `body` or view builders.\n- Layout thrash from complex hierarchies, `GeometryReader`, or preference chains.\n- Large image decode or resize work on the main thread.\n- Animation or transition work applied too broadly.\n\nUse `references\u002Fcode-smells.md` for the detailed smell catalog and fix guidance.\n\nProvide:\n- Likely root causes with code references.\n- Suggested fixes and refactors.\n- If needed, a minimal repro or instrumentation suggestion.\n\n## 3. Guide the User to Profile\n\nIf code review does not explain the issue, ask for runtime evidence:\n- A trace export or screenshots of the SwiftUI timeline and Time Profiler call tree.\n- Device\u002FOS\u002Fbuild configuration.\n- The exact interaction being profiled.\n- Before\u002Fafter metrics if the user is comparing a change.\n\nUse `references\u002Fprofiling-intake.md` for the exact checklist and collection steps.\n\n## 4. Analyze and Diagnose\n\n- Map the evidence to the most likely category: invalidation, identity churn, layout thrash, main-thread work, image cost, or animation cost.\n- Prioritize problems by impact, not by how easy they are to explain.\n- Distinguish code-level suspicion from trace-backed evidence.\n- Call out when profiling is still insufficient and what additional evidence would reduce uncertainty.\n\n## 5. Remediate\n\nApply targeted fixes:\n- Narrow state scope and reduce broad observation fan-out.\n- Stabilize identities for `ForEach` and lists.\n- Move heavy work out of `body` into derived state updated from inputs, model-layer precomputation, memoized helpers, or background preprocessing. Use `@State` only for view-owned state, not as an ad hoc cache for arbitrary computation.\n- Use `equatable()` only when equality is cheaper than recomputing the subtree and the inputs are truly value-semantic.\n- Downsample images before rendering.\n- Reduce layout complexity or use fixed sizing where possible.\n\nUse `references\u002Fcode-smells.md` for examples, Observation-specific fan-out guidance, and remediation patterns.\n\n## 6. Verify\n\nAsk the user to re-run the same capture and compare with baseline metrics.\nSummarize the delta (CPU, frame drops, memory peak) if provided.\n\n## Outputs\n\nProvide:\n- A short metrics table (before\u002Fafter if available).\n- Top issues (ordered by impact).\n- Proposed fixes with estimated effort.\n\nUse `references\u002Freport-template.md` when formatting the final audit.\n\n## References\n\n- Profiling intake and collection checklist: `references\u002Fprofiling-intake.md`\n- Common code smells and remediation patterns: `references\u002Fcode-smells.md`\n- Audit output template: `references\u002Freport-template.md`\n- Add Apple documentation and WWDC resources under `references\u002F` as they are supplied by the user.\n- Optimizing SwiftUI performance with Instruments: `references\u002Foptimizing-swiftui-performance-instruments.md`\n- Understanding and improving SwiftUI performance: `references\u002Funderstanding-improving-swiftui-performance.md`\n- Understanding hangs in your app: `references\u002Funderstanding-hangs-in-your-app.md`\n- Demystify SwiftUI performance (WWDC23): `references\u002Fdemystify-swiftui-performance-wwdc23.md`\n",{"name":5,"description":7},"main","0c02bab690f38eceef5a55f709116efcf36fe555","skills\u002Fswiftui-performance-audit","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment","https:\u002F\u002Fgithub.com\u002Fjjonesdev","2026-08-15 21:23:35",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add jjonesdev\u002Fpersonal-development-environment --skill swiftui-performance-audit",{"tool":36,"command":37},"bunx","bunx skills add jjonesdev\u002Fpersonal-development-environment --skill swiftui-performance-audit",{"tool":39,"command":40},"pnpm","pnpm dlx skills add jjonesdev\u002Fpersonal-development-environment --skill swiftui-performance-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002FSKILL.md",true,[44,50,54,58,62,66,70,74],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",242,"https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcode-smells.md",3753,"https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Fcode-smells.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fdemystify-swiftui-performance-wwdc23.md",1813,"https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Fdemystify-swiftui-performance-wwdc23.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Foptimizing-swiftui-performance-instruments.md",1837,"https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Foptimizing-swiftui-performance-instruments.md",{"path":63,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fprofiling-intake.md",1904,"https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Fprofiling-intake.md",{"path":67,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Freport-template.md",1201,"https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Freport-template.md",{"path":71,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Funderstanding-hangs-in-your-app.md",1267,"https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Funderstanding-hangs-in-your-app.md",{"path":75,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Funderstanding-improving-swiftui-performance.md",2262,"https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Funderstanding-improving-swiftui-performance.md",[79,86,93,100,107,115],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7ABFBNYZC1DAWC6G1XRYVG2","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7ABF69N6XJBRPN5A6SMDSY6","swiftui-view-refactor","Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage. Use when cleaning up a SwiftUI view, splitting long bodies, removing inline actions or side effects, reducing computed `some View` helpers, or standardizing `@Observable` and view model initialization patterns.","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-view-refactor\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7ABF1EG3P0Z0PRFC4QJMRZF","swiftui-ui-patterns","Best practices and example-driven guidance for building SwiftUI views and components, including navigation hierarchies, custom view modifiers, and responsive layouts with stacks and grids. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens with VStack\u002FHStack, managing @State or @Binding, building declarative iOS interfaces, or needing component-specific patterns and examples.","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-ui-patterns\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7ABET3FZRCKP9X97MGDV9FK","swiftui-liquid-glass","Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-liquid-glass\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7ABEMCS33HVVTG9EPATGXEN","swift-concurrency","Diagnose Swift Concurrency issues, refactor callback-based code to async\u002Fawait, and guide Swift 6 migration when working with tasks, actors, @MainActor, Sendable, data races, thread safety, or concurrency-related compiler and linter warnings.","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswift-concurrency\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fswift-concurrency\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7ABEDXSQTA834AHVTQK8XE0","jj-write-like-me","Draft, rewrite, reply, or critique writing in the user's preferred personal voice, modeled from the supplied user2 communication samples. Use for documents, essays, announcements, email, Slack, direct messages, updates, requests, reminders, explanations, pushback, relationship notes, or whenever the user asks to make writing sound like them, use their voice, improve a draft without losing their personality, or check whether a message matches their style.","https:\u002F\u002Fgithub.com\u002Fjjonesdev\u002Fpersonal-development-environment\u002Fblob\u002Fmain\u002Fskills\u002Fjj-write-like-me\u002FSKILL.md",[],[]]