sozercan

swiftui-ui-patterns

@sozercan/swiftui-ui-patterns
sozercan
556
17 forks
Updated 1/18/2026
View on GitHub

Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.

Installation

$skills install @sozercan/swiftui-ui-patterns
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Repositorysozercan/kaset
Path.github/skills/swiftui-ui-patterns/SKILL.md
Branchmain
Scoped Name@sozercan/swiftui-ui-patterns

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

More by sozercan

View all
swiftui-view-refactor
556

Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view's layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.

swiftui-liquid-glass
556

Implement, review, or improve SwiftUI features using the iOS 26+ / macOS 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.

swiftui-performance-audit
556

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory 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.

swift-concurrency
556

Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).