affaan-m/ECC/docs/zh-CN/skills/swiftui-patterns/SKILL.md
swiftui-patterns
Use it for design tasks; the detail page covers purpose, installation, and practical steps.
- Source repository stars
- 234,327
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-27
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
适用于 Apple 平台的现代 SwiftUI 模式,用于构建声明式、高性能的用户界面。涵盖 Observation 框架、视图组合、类型安全导航和性能优化。
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/swiftui-patterns"Inspect the Agent Skill "swiftui-patterns" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/docs/zh-CN/skills/swiftui-patterns/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
何时激活
构建 SwiftUI 视图和管理状态时(@State、@Observable、@Binding) 使用 NavigationStack 设计导航流程时 构建视图模型和数据流时 优化列表和复杂布局的渲染性能时 在 SwiftUI 中使用环境值和依赖注入时
构建 SwiftUI 视图和管理状态时(@State、@Observable、@Binding)使用 NavigationStack 设计导航流程时构建视图模型和数据流时 - 02
状态管理
使用 @Observable(而非 ObservableObject)—— 它跟踪属性级别的变更,因此 SwiftUI 只会重新渲染读取了已变更属性的视图:
使用 @Observable(而非 ObservableObject)—— 它跟踪属性级别的变更,因此 SwiftUI 只会重新渲染读取了已变更属性的视图:用 @Environment 替换 @EnvironmentObject: - 03
属性包装器选择
Review the “属性包装器选择” section in the pinned source before continuing.
Review and apply the “属性包装器选择” source section. - 04
@Observable ViewModel
使用 @Observable(而非 ObservableObject)—— 它跟踪属性级别的变更,因此 SwiftUI 只会重新渲染读取了已变更属性的视图:
使用 @Observable(而非 ObservableObject)—— 它跟踪属性级别的变更,因此 SwiftUI 只会重新渲染读取了已变更属性的视图:
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 62/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 234,327 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/swiftui-patterns/SKILL.md
- Commit
- 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
SwiftUI 模式
适用于 Apple 平台的现代 SwiftUI 模式,用于构建声明式、高性能的用户界面。涵盖 Observation 框架、视图组合、类型安全导航和性能优化。
何时激活
- 构建 SwiftUI 视图和管理状态时(
@State、@Observable、@Binding) - 使用
NavigationStack设计导航流程时 - 构建视图模型和数据流时
- 优化列表和复杂布局的渲染性能时
- 在 SwiftUI 中使用环境值和依赖注入时
状态管理
属性包装器选择
选择最适合的最简单包装器:
| 包装器 | 使用场景 |
|---|---|
@State | 视图本地的值类型(开关、表单字段、Sheet 展示) |
@Binding | 指向父视图 @State 的双向引用 |
@Observable 类 + @State | 拥有多个属性的自有模型 |
@Observable 类(无包装器) | 从父视图传递的只读引用 |
@Bindable | 指向 @Observable 属性的双向绑定 |
@Environment | 通过 .environment() 注入的共享依赖项 |
@Observable ViewModel
使用 @Observable(而非 ObservableObject)—— 它跟踪属性级别的变更,因此 SwiftUI 只会重新渲染读取了已变更属性的视图:
@Observable
final class ItemListViewModel {
private(set) var items: [Item] = []
private(set) var isLoading = false
var searchText = ""
private let repository: any ItemRepository
init(repository: any ItemRepository = DefaultItemRepository()) {
self.repository = repository
}
func load() async {
isLoading = true
defer { isLoading = false }
items = (try? await repository.fetchAll()) ?? []
}
}
消费 ViewModel 的视图
struct ItemListView: View {
@State private var viewModel: ItemListViewModel
init(viewModel: ItemListViewModel = ItemListViewModel()) {
_viewModel = State(initialValue: viewModel)
}
var body: some View {
List(viewModel.items) { item in
ItemRow(item: item)
}
.searchable(text: $viewModel.searchText)
.overlay { if viewModel.isLoading { ProgressView() } }
.task { await viewModel.load() }
}
}
环境注入
用 @Environment 替换 @EnvironmentObject:
// Inject
ContentView()
.environment(authManager)
// Consume
struct ProfileView: View {
@Environment(AuthManager.self) private var auth
var body: some View {
Text(auth.currentUser?.name ?? "Guest")
}
}
视图组合
提取子视图以限制失效
将视图拆分为小型、专注的结构体。当状态变更时,只有读取该状态的子视图会重新渲染:
struct OrderView: View {
@State private var viewModel = OrderViewModel()
var body: some View {
VStack {
OrderHeader(title: viewModel.title)
OrderItemList(items: viewModel.items)
OrderTotal(total: viewModel.total)
}
}
}
用于可复用样式的 ViewModifier
struct CardModifier: ViewModifier {
func body(content: Content) -> some View {
content
.padding()
.background(.regularMaterial)
.clipShape(RoundedRectangle(cornerRadius: 12))
}
}
extension View {
func cardStyle() -> some View {
modifier(CardModifier())
}
}
导航
类型安全的 NavigationStack
使用 NavigationStack 与 NavigationPath 来实现程序化、类型安全的路由:
@Observable
final class Router {
var path = NavigationPath()
func navigate(to destination: Destination) {
path.append(destination)
}
func popToRoot() {
path = NavigationPath()
}
}
enum Destination: Hashable {
case detail(Item.ID)
case settings
case profile(User.ID)
}
struct RootView: View {
@State private var router = Router()
var body: some View {
NavigationStack(path: $router.path) {
HomeView()
.navigationDestination(for: Destination.self) { dest in
switch dest {
case .detail(let id): ItemDetailView(itemID: id)
case .settings: SettingsView()
case .profile(let id): ProfileView(userID: id)
}
}
}
.environment(router)
}
}
性能
为大型集合使用惰性容器
LazyVStack 和 LazyHStack 仅在视图可见时才创建它们:
ScrollView {
LazyVStack(spacing: 8) {
ForEach(items) { item in
ItemRow(item: item)
}
}
}
稳定的标识符
在 ForEach 中始终使用稳定、唯一的 ID —— 避免使用数组索引:
// Use Identifiable conformance or explicit id
ForEach(items, id: \.stableID) { item in
ItemRow(item: item)
}
避免在 body 中进行昂贵操作
- 切勿在
body内执行 I/O、网络调用或繁重计算 - 使用
.task {}处理异步工作 —— 当视图消失时它会自动取消 - 在滚动视图中谨慎使用
.sensoryFeedback()和.geometryGroup() - 在列表中最小化使用
.shadow()、.blur()和.mask()—— 它们会触发屏幕外渲染
遵循 Equatable
对于 body 计算昂贵的视图,遵循 Equatable 以跳过不必要的重新渲染:
struct ExpensiveChartView: View, Equatable {
let dataPoints: [DataPoint] // DataPoint must conform to Equatable
static func == (lhs: Self, rhs: Self) -> Bool {
lhs.dataPoints == rhs.dataPoints
}
var body: some View {
// Complex chart rendering
}
}
预览
使用 #Preview 宏配合内联模拟数据以进行快速迭代:
#Preview("Empty state") {
ItemListView(viewModel: ItemListViewModel(repository: EmptyMockRepository()))
}
#Preview("Loaded") {
ItemListView(viewModel: ItemListViewModel(repository: PopulatedMockRepository()))
}
应避免的反模式
- 在新代码中使用
ObservableObject/@Published/@StateObject/@EnvironmentObject—— 迁移到@Observable - 将异步工作直接放在
body或init中 —— 使用.task {}或显式的加载方法 - 在不拥有数据的子视图中将视图模型创建为
@State—— 改为从父视图传递 - 使用
AnyView类型擦除 —— 对于条件视图,优先选择@ViewBuilder或Group - 在向 Actor 传递数据或从 Actor 接收数据时忽略
Sendable要求
参考
查看技能:swift-actor-persistence 以了解基于 Actor 的持久化模式。
查看技能:swift-protocol-di-testing 以了解基于协议的 DI 和使用 Swift Testing 进行测试。
Alternatives
Compare before choosing
dpearson2699/swift-ios-skills
swiftui-patterns
Builds and reviews SwiftUI views with modern MV architecture, state, composition, isolated previews, and migration guidance. Covers @Observable ownership, @State/@Bindable/@Environment wiring, view decomposition, ViewModifiers, environment values, .task loading, iOS 26+ handoffs, Writing Tools, clipboard availability, and performance. Use when structuring SwiftUI state, managing @Observable, composing views, previewing meaningful UI states, or correcting SwiftUI patterns.
affaan-m/ECC
swiftui-patterns
SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.
affaan-m/ECC
swiftui-patterns
Use it for design tasks; the detail page covers purpose, installation, and practical steps.
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program