[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BWQNSTPTPHBRRG04M5328":3,"skill-same:01M73BWQNSTPTPHBRRG04M5328":46},{"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":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M73BWQNSTPTPHBRRG04M5328","swiftui-expert-skill",null,"Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-expert-skill\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: swiftui-expert-skill\ndescription: Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.\n---\n\n# SwiftUI Expert Skill\n\n## Overview\nUse this skill to build, review, or improve SwiftUI features with correct state management, optimal view composition, and iOS 26+ Liquid Glass styling. Prioritize native APIs, Apple design guidance, and performance-conscious patterns. This skill focuses on facts and best practices without enforcing specific architectural patterns.\n\n## Workflow Decision Tree\n\n### 1) Review existing SwiftUI code\n- **First, consult `references\u002Flatest-apis.md`** to ensure only current, non-deprecated APIs are used\n- Check property wrapper usage against the selection guide (see `references\u002Fstate-management.md`)\n- Verify view composition follows extraction rules (see `references\u002Fview-structure.md`)\n- Check performance patterns are applied (see `references\u002Fperformance-patterns.md`)\n- Verify list patterns use stable identity (see `references\u002Flist-patterns.md`)\n- Check animation patterns for correctness (see `references\u002Fanimation-basics.md`, `references\u002Fanimation-transitions.md`)\n- Review accessibility: proper grouping, traits, Dynamic Type support (see `references\u002Faccessibility-patterns.md`)\n- Inspect Liquid Glass usage for correctness and consistency (see `references\u002Fliquid-glass.md`)\n- Validate iOS 26+ availability handling with sensible fallbacks\n\n### 2) Improve existing SwiftUI code\n- **First, consult `references\u002Flatest-apis.md`** to replace any deprecated APIs with their modern equivalents\n- Audit state management for correct wrapper selection (see `references\u002Fstate-management.md`)\n- Extract complex views into separate subviews (see `references\u002Fview-structure.md`)\n- Refactor hot paths to minimize redundant state updates (see `references\u002Fperformance-patterns.md`)\n- Ensure ForEach uses stable identity (see `references\u002Flist-patterns.md`)\n- Improve animation patterns (use value parameter, proper transitions, see `references\u002Fanimation-basics.md`, `references\u002Fanimation-transitions.md`)\n- Improve accessibility: use `Button` over tap gestures, add `@ScaledMetric` for Dynamic Type (see `references\u002Faccessibility-patterns.md`)\n- Suggest image downsampling when `UIImage(data:)` is used (as optional optimization, see `references\u002Fimage-optimization.md`)\n- Adopt Liquid Glass only when explicitly requested by the user\n\n### 3) Implement new SwiftUI feature\n- **First, consult `references\u002Flatest-apis.md`** to use only current, non-deprecated APIs for the target deployment version\n- Design data flow first: identify owned vs injected state (see `references\u002Fstate-management.md`)\n- Structure views for optimal diffing (extract subviews early, see `references\u002Fview-structure.md`)\n- Keep business logic in services and models for testability (see `references\u002Flayout-best-practices.md`)\n- Use correct animation patterns (implicit vs explicit, transitions, see `references\u002Fanimation-basics.md`, `references\u002Fanimation-transitions.md`, `references\u002Fanimation-advanced.md`)\n- Use `Button` for tappable elements, add accessibility grouping and labels (see `references\u002Faccessibility-patterns.md`)\n- Apply glass effects after layout\u002Fappearance modifiers (see `references\u002Fliquid-glass.md`)\n- Gate iOS 26+ features with `#available` and provide fallbacks\n\n## Core Guidelines\n\n### State Management\n- `@State` must be `private`; use for internal view state\n- `@Binding` only when a child needs to **modify** parent state\n- `@StateObject` when view **creates** the object; `@ObservedObject` when **injected**\n- iOS 17+: Use `@State` with `@Observable` classes; use `@Bindable` for injected observables needing bindings\n- Use `let` for read-only values; `var` + `.onChange()` for reactive reads\n- Never pass values into `@State` or `@StateObject` — they only accept initial values\n- Nested `ObservableObject` doesn't propagate changes — pass nested objects directly; `@Observable` handles nesting fine\n\n### View Composition\n- Extract complex views into separate subviews for better readability and performance\n- Prefer modifiers over conditional views for state changes (maintains view identity)\n- Keep view `body` simple and pure (no side effects or complex logic)\n- Use `@ViewBuilder` functions only for small, simple sections\n- Prefer `@ViewBuilder let content: Content` over closure-based content properties\n- Keep business logic in services and models; views should orchestrate UI flow\n- Action handlers should reference methods, not contain inline logic\n- Views should work in any context (don't assume screen size or presentation style)\n\n### Performance\n- Pass only needed values to views (avoid large \"config\" or \"context\" objects)\n- Eliminate unnecessary dependencies to reduce update fan-out\n- Check for value changes before assigning state in hot paths\n- Avoid redundant state updates in `onReceive`, `onChange`, scroll handlers\n- Minimize work in frequently executed code paths\n- Use `LazyVStack`\u002F`LazyHStack` for large lists\n- Use stable identity for `ForEach` (never `.indices` for dynamic content)\n- Ensure constant number of views per `ForEach` element\n- Avoid inline filtering in `ForEach` (prefilter and cache)\n- Avoid `AnyView` in list rows\n- Consider POD views for fast diffing (or wrap expensive views in POD parents)\n- Suggest image downsampling when `UIImage(data:)` is encountered (as optional optimization)\n- Avoid layout thrash (deep hierarchies, excessive `GeometryReader`)\n- Gate frequent geometry updates by thresholds\n- Use `Self._logChanges()` or `Self._printChanges()` to debug unexpected view updates\n\n### Animations\n- Use `.animation(_:value:)` with value parameter (deprecated version without value is too broad)\n- Use `withAnimation` for event-driven animations (button taps, gestures)\n- Prefer transforms (`offset`, `scale`, `rotation`) over layout changes (`frame`) for performance\n- Transitions require animations outside the conditional structure\n- Custom `Animatable` implementations must have explicit `animatableData`\n- Use `.phaseAnimator` for multi-step sequences (iOS 17+)\n- Use `.keyframeAnimator` for precise timing control (iOS 17+)\n- Animation completion handlers need `.transaction(value:)` for reexecution\n- Implicit animations override explicit animations (later in view tree wins)\n\n### Accessibility\n- Prefer `Button` over `onTapGesture` for tappable elements (free VoiceOver support)\n- Use `@ScaledMetric` for custom numeric values that should scale with Dynamic Type\n- Group related elements with `accessibilityElement(children: .combine)` for joined labels\n- Provide `accessibilityLabel` when default labels are unclear or missing\n- Use `accessibilityRepresentation` for custom controls that should behave like native ones\n\n### Liquid Glass (iOS 26+)\n**Only adopt when explicitly requested by the user.**\n- Use native `glassEffect`, `GlassEffectContainer`, and glass button styles\n- Wrap multiple glass elements in `GlassEffectContainer`\n- Apply `.glassEffect()` after layout and visual modifiers\n- Use `.interactive()` only for tappable\u002Ffocusable elements\n- Use `glassEffectID` with `@Namespace` for morphing transitions\n\n## Quick Reference\n\n### Property Wrapper Selection\n| Wrapper | Use When |\n|---------|----------|\n| `@State` | Internal view state (must be `private`) |\n| `@Binding` | Child modifies parent's state |\n| `@StateObject` | View owns an `ObservableObject` |\n| `@ObservedObject` | View receives an `ObservableObject` |\n| `@Bindable` | iOS 17+: Injected `@Observable` needing bindings |\n| `let` | Read-only value from parent |\n| `var` | Read-only value watched via `.onChange()` |\n\n### Liquid Glass Patterns\n```swift\n\u002F\u002F Basic glass effect with fallback\nif #available(iOS 26, *) {\n    content\n        .padding()\n        .glassEffect(.regular.interactive(), in: .rect(cornerRadius: 16))\n} else {\n    content\n        .padding()\n        .background(.ultraThinMaterial, in: RoundedRectangle(cornerRadius: 16))\n}\n\n\u002F\u002F Grouped glass elements\nGlassEffectContainer(spacing: 24) {\n    HStack(spacing: 24) {\n        GlassButton1()\n        GlassButton2()\n    }\n}\n\n\u002F\u002F Glass buttons\nButton(\"Confirm\") { }\n    .buttonStyle(.glassProminent)\n```\n\n## Review Checklist\n\n### Latest APIs (see `references\u002Flatest-apis.md`)\n- [ ] No deprecated modifiers used (check against the quick lookup table)\n- [ ] API choices match the project's minimum deployment target\n\n### State Management\n- [ ] `@State` properties are `private`\n- [ ] `@Binding` only where child modifies parent state\n- [ ] `@StateObject` for owned, `@ObservedObject` for injected\n- [ ] iOS 17+: `@State` with `@Observable`, `@Bindable` for injected\n- [ ] Passed values NOT declared as `@State` or `@StateObject`\n- [ ] Nested `ObservableObject` avoided (or passed directly to child views)\n\n### Sheets & Navigation (see `references\u002Fsheet-navigation-patterns.md`)\n- [ ] Using `.sheet(item:)` for model-based sheets\n- [ ] Sheets own their actions and dismiss internally\n\n### ScrollView (see `references\u002Fscroll-patterns.md`)\n- [ ] Using `ScrollViewReader` with stable IDs for programmatic scrolling\n\n### View Structure (see `references\u002Fview-structure.md`)\n- [ ] Using modifiers instead of conditionals for state changes\n- [ ] Complex views extracted to separate subviews\n- [ ] Container views use `@ViewBuilder let content: Content`\n\n### Performance (see `references\u002Fperformance-patterns.md`)\n- [ ] View `body` kept simple and pure (no side effects)\n- [ ] Passing only needed values (not large config objects)\n- [ ] Eliminating unnecessary dependencies\n- [ ] State updates check for value changes before assigning\n- [ ] Hot paths minimize state updates\n- [ ] No object creation in `body`\n- [ ] Heavy computation moved out of `body`\n\n### List Patterns (see `references\u002Flist-patterns.md`)\n- [ ] ForEach uses stable identity (not `.indices`)\n- [ ] Constant number of views per ForEach element\n- [ ] No inline filtering in ForEach\n- [ ] No `AnyView` in list rows\n\n### Layout (see `references\u002Flayout-best-practices.md`)\n- [ ] Avoiding layout thrash (deep hierarchies, excessive GeometryReader)\n- [ ] Gating frequent geometry updates by thresholds\n- [ ] Business logic kept in services and models (not in views)\n- [ ] Action handlers reference methods (not inline logic)\n- [ ] Using relative layout (not hard-coded constants)\n- [ ] Views work in any context (context-agnostic)\n\n### Animations (see `references\u002Fanimation-basics.md`, `references\u002Fanimation-transitions.md`, `references\u002Fanimation-advanced.md`)\n- [ ] Using `.animation(_:value:)` with value parameter\n- [ ] Using `withAnimation` for event-driven animations\n- [ ] Transitions paired with animations outside conditional structure\n- [ ] Custom `Animatable` has explicit `animatableData` implementation\n- [ ] Preferring transforms over layout changes for animation performance\n- [ ] Phase animations for multi-step sequences (iOS 17+)\n- [ ] Keyframe animations for precise timing (iOS 17+)\n- [ ] Completion handlers use `.transaction(value:)` for reexecution\n\n### Accessibility (see `references\u002Faccessibility-patterns.md`)\n- [ ] `Button` used instead of `onTapGesture` for tappable elements\n- [ ] `@ScaledMetric` used for custom values that should scale with Dynamic Type\n- [ ] Related elements grouped with `accessibilityElement(children:)`\n- [ ] Custom controls use `accessibilityRepresentation` when appropriate\n\n### Liquid Glass (iOS 26+)\n- [ ] `#available(iOS 26, *)` with fallback for Liquid Glass\n- [ ] Multiple glass views wrapped in `GlassEffectContainer`\n- [ ] `.glassEffect()` applied after layout\u002Fappearance modifiers\n- [ ] `.interactive()` only on user-interactable elements\n- [ ] Shapes and tints consistent across related elements\n\n## References\n- `references\u002Flatest-apis.md` - **Required reading for all workflows.** Version-segmented guide of deprecated-to-modern API transitions (iOS 15+ through iOS 26+)\n- `references\u002Fstate-management.md` - Property wrappers and data flow\n- `references\u002Fview-structure.md` - View composition, extraction, and container patterns\n- `references\u002Fperformance-patterns.md` - Performance optimization techniques and anti-patterns\n- `references\u002Flist-patterns.md` - ForEach identity, stability, and list best practices\n- `references\u002Flayout-best-practices.md` - Layout patterns, context-agnostic views, and testability\n- `references\u002Faccessibility-patterns.md` - Accessibility traits, grouping, Dynamic Type, and VoiceOver\n- `references\u002Fanimation-basics.md` - Core animation concepts, implicit\u002Fexplicit animations, timing, performance\n- `references\u002Fanimation-transitions.md` - Transitions, custom transitions, Animatable protocol\n- `references\u002Fanimation-advanced.md` - Transactions, phase\u002Fkeyframe animations (iOS 17+), completion handlers (iOS 17+)\n- `references\u002Fsheet-navigation-patterns.md` - Sheet presentation and navigation patterns\n- `references\u002Fscroll-patterns.md` - ScrollView patterns and programmatic scrolling\n- `references\u002Fimage-optimization.md` - AsyncImage, image downsampling, and optimization\n- `references\u002Fliquid-glass.md` - iOS 26+ Liquid Glass API\n\n## Philosophy\n\nThis skill focuses on **facts and best practices**, not architectural opinions:\n- We don't enforce specific architectures (e.g., MVVM, VIPER)\n- We do encourage separating business logic for testability\n- We optimize for performance and maintainability\n- We follow Apple's Human Interface Guidelines and API design patterns\n","# SwiftUI Expert Skill\n\n## Overview\nUse this skill to build, review, or improve SwiftUI features with correct state management, optimal view composition, and iOS 26+ Liquid Glass styling. Prioritize native APIs, Apple design guidance, and performance-conscious patterns. This skill focuses on facts and best practices without enforcing specific architectural patterns.\n\n## Workflow Decision Tree\n\n### 1) Review existing SwiftUI code\n- **First, consult `references\u002Flatest-apis.md`** to ensure only current, non-deprecated APIs are used\n- Check property wrapper usage against the selection guide (see `references\u002Fstate-management.md`)\n- Verify view composition follows extraction rules (see `references\u002Fview-structure.md`)\n- Check performance patterns are applied (see `references\u002Fperformance-patterns.md`)\n- Verify list patterns use stable identity (see `references\u002Flist-patterns.md`)\n- Check animation patterns for correctness (see `references\u002Fanimation-basics.md`, `references\u002Fanimation-transitions.md`)\n- Review accessibility: proper grouping, traits, Dynamic Type support (see `references\u002Faccessibility-patterns.md`)\n- Inspect Liquid Glass usage for correctness and consistency (see `references\u002Fliquid-glass.md`)\n- Validate iOS 26+ availability handling with sensible fallbacks\n\n### 2) Improve existing SwiftUI code\n- **First, consult `references\u002Flatest-apis.md`** to replace any deprecated APIs with their modern equivalents\n- Audit state management for correct wrapper selection (see `references\u002Fstate-management.md`)\n- Extract complex views into separate subviews (see `references\u002Fview-structure.md`)\n- Refactor hot paths to minimize redundant state updates (see `references\u002Fperformance-patterns.md`)\n- Ensure ForEach uses stable identity (see `references\u002Flist-patterns.md`)\n- Improve animation patterns (use value parameter, proper transitions, see `references\u002Fanimation-basics.md`, `references\u002Fanimation-transitions.md`)\n- Improve accessibility: use `Button` over tap gestures, add `@ScaledMetric` for Dynamic Type (see `references\u002Faccessibility-patterns.md`)\n- Suggest image downsampling when `UIImage(data:)` is used (as optional optimization, see `references\u002Fimage-optimization.md`)\n- Adopt Liquid Glass only when explicitly requested by the user\n\n### 3) Implement new SwiftUI feature\n- **First, consult `references\u002Flatest-apis.md`** to use only current, non-deprecated APIs for the target deployment version\n- Design data flow first: identify owned vs injected state (see `references\u002Fstate-management.md`)\n- Structure views for optimal diffing (extract subviews early, see `references\u002Fview-structure.md`)\n- Keep business logic in services and models for testability (see `references\u002Flayout-best-practices.md`)\n- Use correct animation patterns (implicit vs explicit, transitions, see `references\u002Fanimation-basics.md`, `references\u002Fanimation-transitions.md`, `references\u002Fanimation-advanced.md`)\n- Use `Button` for tappable elements, add accessibility grouping and labels (see `references\u002Faccessibility-patterns.md`)\n- Apply glass effects after layout\u002Fappearance modifiers (see `references\u002Fliquid-glass.md`)\n- Gate iOS 26+ features with `#available` and provide fallbacks\n\n## Core Guidelines\n\n### State Management\n- `@State` must be `private`; use for internal view state\n- `@Binding` only when a child needs to **modify** parent state\n- `@StateObject` when view **creates** the object; `@ObservedObject` when **injected**\n- iOS 17+: Use `@State` with `@Observable` classes; use `@Bindable` for injected observables needing bindings\n- Use `let` for read-only values; `var` + `.onChange()` for reactive reads\n- Never pass values into `@State` or `@StateObject` — they only accept initial values\n- Nested `ObservableObject` doesn't propagate changes — pass nested objects directly; `@Observable` handles nesting fine\n\n### View Composition\n- Extract complex views into separate subviews for better readability and performance\n- Prefer modifiers over conditional views for state changes (maintains view identity)\n- Keep view `body` simple and pure (no side effects or complex logic)\n- Use `@ViewBuilder` functions only for small, simple sections\n- Prefer `@ViewBuilder let content: Content` over closure-based content properties\n- Keep business logic in services and models; views should orchestrate UI flow\n- Action handlers should reference methods, not contain inline logic\n- Views should work in any context (don't assume screen size or presentation style)\n\n### Performance\n- Pass only needed values to views (avoid large \"config\" or \"context\" objects)\n- Eliminate unnecessary dependencies to reduce update fan-out\n- Check for value changes before assigning state in hot paths\n- Avoid redundant state updates in `onReceive`, `onChange`, scroll handlers\n- Minimize work in frequently executed code paths\n- Use `LazyVStack`\u002F`LazyHStack` for large lists\n- Use stable identity for `ForEach` (never `.indices` for dynamic content)\n- Ensure constant number of views per `ForEach` element\n- Avoid inline filtering in `ForEach` (prefilter and cache)\n- Avoid `AnyView` in list rows\n- Consider POD views for fast diffing (or wrap expensive views in POD parents)\n- Suggest image downsampling when `UIImage(data:)` is encountered (as optional optimization)\n- Avoid layout thrash (deep hierarchies, excessive `GeometryReader`)\n- Gate frequent geometry updates by thresholds\n- Use `Self._logChanges()` or `Self._printChanges()` to debug unexpected view updates\n\n### Animations\n- Use `.animation(_:value:)` with value parameter (deprecated version without value is too broad)\n- Use `withAnimation` for event-driven animations (button taps, gestures)\n- Prefer transforms (`offset`, `scale`, `rotation`) over layout changes (`frame`) for performance\n- Transitions require animations outside the conditional structure\n- Custom `Animatable` implementations must have explicit `animatableData`\n- Use `.phaseAnimator` for multi-step sequences (iOS 17+)\n- Use `.keyframeAnimator` for precise timing control (iOS 17+)\n- Animation completion handlers need `.transaction(value:)` for reexecution\n- Implicit animations override explicit animations (later in view tree wins)\n\n### Accessibility\n- Prefer `Button` over `onTapGesture` for tappable elements (free VoiceOver support)\n- Use `@ScaledMetric` for custom numeric values that should scale with Dynamic Type\n- Group related elements with `accessibilityElement(children: .combine)` for joined labels\n- Provide `accessibilityLabel` when default labels are unclear or missing\n- Use `accessibilityRepresentation` for custom controls that should behave like native ones\n\n### Liquid Glass (iOS 26+)\n**Only adopt when explicitly requested by the user.**\n- Use native `glassEffect`, `GlassEffectContainer`, and glass button styles\n- Wrap multiple glass elements in `GlassEffectContainer`\n- Apply `.glassEffect()` after layout and visual modifiers\n- Use `.interactive()` only for tappable\u002Ffocusable elements\n- Use `glassEffectID` with `@Namespace` for morphing transitions\n\n## Quick Reference\n\n### Property Wrapper Selection\n| Wrapper | Use When |\n|---------|----------|\n| `@State` | Internal view state (must be `private`) |\n| `@Binding` | Child modifies parent's state |\n| `@StateObject` | View owns an `ObservableObject` |\n| `@ObservedObject` | View receives an `ObservableObject` |\n| `@Bindable` | iOS 17+: Injected `@Observable` needing bindings |\n| `let` | Read-only value from parent |\n| `var` | Read-only value watched via `.onChange()` |\n\n### Liquid Glass Patterns\n```swift\n\u002F\u002F Basic glass effect with fallback\nif #available(iOS 26, *) {\n    content\n        .padding()\n        .glassEffect(.regular.interactive(), in: .rect(cornerRadius: 16))\n} else {\n    content\n        .padding()\n        .background(.ultraThinMaterial, in: RoundedRectangle(cornerRadius: 16))\n}\n\n\u002F\u002F Grouped glass elements\nGlassEffectContainer(spacing: 24) {\n    HStack(spacing: 24) {\n        GlassButton1()\n        GlassButton2()\n    }\n}\n\n\u002F\u002F Glass buttons\nButton(\"Confirm\") { }\n    .buttonStyle(.glassProminent)\n```\n\n## Review Checklist\n\n### Latest APIs (see `references\u002Flatest-apis.md`)\n- [ ] No deprecated modifiers used (check against the quick lookup table)\n- [ ] API choices match the project's minimum deployment target\n\n### State Management\n- [ ] `@State` properties are `private`\n- [ ] `@Binding` only where child modifies parent state\n- [ ] `@StateObject` for owned, `@ObservedObject` for injected\n- [ ] iOS 17+: `@State` with `@Observable`, `@Bindable` for injected\n- [ ] Passed values NOT declared as `@State` or `@StateObject`\n- [ ] Nested `ObservableObject` avoided (or passed directly to child views)\n\n### Sheets & Navigation (see `references\u002Fsheet-navigation-patterns.md`)\n- [ ] Using `.sheet(item:)` for model-based sheets\n- [ ] Sheets own their actions and dismiss internally\n\n### ScrollView (see `references\u002Fscroll-patterns.md`)\n- [ ] Using `ScrollViewReader` with stable IDs for programmatic scrolling\n\n### View Structure (see `references\u002Fview-structure.md`)\n- [ ] Using modifiers instead of conditionals for state changes\n- [ ] Complex views extracted to separate subviews\n- [ ] Container views use `@ViewBuilder let content: Content`\n\n### Performance (see `references\u002Fperformance-patterns.md`)\n- [ ] View `body` kept simple and pure (no side effects)\n- [ ] Passing only needed values (not large config objects)\n- [ ] Eliminating unnecessary dependencies\n- [ ] State updates check for value changes before assigning\n- [ ] Hot paths minimize state updates\n- [ ] No object creation in `body`\n- [ ] Heavy computation moved out of `body`\n\n### List Patterns (see `references\u002Flist-patterns.md`)\n- [ ] ForEach uses stable identity (not `.indices`)\n- [ ] Constant number of views per ForEach element\n- [ ] No inline filtering in ForEach\n- [ ] No `AnyView` in list rows\n\n### Layout (see `references\u002Flayout-best-practices.md`)\n- [ ] Avoiding layout thrash (deep hierarchies, excessive GeometryReader)\n- [ ] Gating frequent geometry updates by thresholds\n- [ ] Business logic kept in services and models (not in views)\n- [ ] Action handlers reference methods (not inline logic)\n- [ ] Using relative layout (not hard-coded constants)\n- [ ] Views work in any context (context-agnostic)\n\n### Animations (see `references\u002Fanimation-basics.md`, `references\u002Fanimation-transitions.md`, `references\u002Fanimation-advanced.md`)\n- [ ] Using `.animation(_:value:)` with value parameter\n- [ ] Using `withAnimation` for event-driven animations\n- [ ] Transitions paired with animations outside conditional structure\n- [ ] Custom `Animatable` has explicit `animatableData` implementation\n- [ ] Preferring transforms over layout changes for animation performance\n- [ ] Phase animations for multi-step sequences (iOS 17+)\n- [ ] Keyframe animations for precise timing (iOS 17+)\n- [ ] Completion handlers use `.transaction(value:)` for reexecution\n\n### Accessibility (see `references\u002Faccessibility-patterns.md`)\n- [ ] `Button` used instead of `onTapGesture` for tappable elements\n- [ ] `@ScaledMetric` used for custom values that should scale with Dynamic Type\n- [ ] Related elements grouped with `accessibilityElement(children:)`\n- [ ] Custom controls use `accessibilityRepresentation` when appropriate\n\n### Liquid Glass (iOS 26+)\n- [ ] `#available(iOS 26, *)` with fallback for Liquid Glass\n- [ ] Multiple glass views wrapped in `GlassEffectContainer`\n- [ ] `.glassEffect()` applied after layout\u002Fappearance modifiers\n- [ ] `.interactive()` only on user-interactable elements\n- [ ] Shapes and tints consistent across related elements\n\n## References\n- `references\u002Flatest-apis.md` - **Required reading for all workflows.** Version-segmented guide of deprecated-to-modern API transitions (iOS 15+ through iOS 26+)\n- `references\u002Fstate-management.md` - Property wrappers and data flow\n- `references\u002Fview-structure.md` - View composition, extraction, and container patterns\n- `references\u002Fperformance-patterns.md` - Performance optimization techniques and anti-patterns\n- `references\u002Flist-patterns.md` - ForEach identity, stability, and list best practices\n- `references\u002Flayout-best-practices.md` - Layout patterns, context-agnostic views, and testability\n- `references\u002Faccessibility-patterns.md` - Accessibility traits, grouping, Dynamic Type, and VoiceOver\n- `references\u002Fanimation-basics.md` - Core animation concepts, implicit\u002Fexplicit animations, timing, performance\n- `references\u002Fanimation-transitions.md` - Transitions, custom transitions, Animatable protocol\n- `references\u002Fanimation-advanced.md` - Transactions, phase\u002Fkeyframe animations (iOS 17+), completion handlers (iOS 17+)\n- `references\u002Fsheet-navigation-patterns.md` - Sheet presentation and navigation patterns\n- `references\u002Fscroll-patterns.md` - ScrollView patterns and programmatic scrolling\n- `references\u002Fimage-optimization.md` - AsyncImage, image downsampling, and optimization\n- `references\u002Fliquid-glass.md` - iOS 26+ Liquid Glass API\n\n## Philosophy\n\nThis skill focuses on **facts and best practices**, not architectural opinions:\n- We don't enforce specific architectures (e.g., MVVM, VIPER)\n- We do encourage separating business logic for testability\n- We optimize for performance and maintainability\n- We follow Apple's Human Interface Guidelines and API design patterns\n",{"name":5,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fswiftui-expert-skill","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill swiftui-expert-skill",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill swiftui-expert-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill swiftui-expert-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fswiftui-expert-skill\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"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},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\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},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\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},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\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},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\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},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]