swiftui-liquid-glass 是做什麼的？
使用 iOS 26+ 的 Liquid Glass API 來實作、審查或改善 SwiftUI 功能。當被要求在新的 SwiftUI UI 中採用 Liquid Glass、將現有功能重構成 Liquid Glass，或審查 Liquid Glass 使用方式的正確性、效能及設計一致性時使用。
使用 iOS 26+ 的 Liquid Glass API 來實作、審查或改善 SwiftUI 功能。當被要求在新的 SwiftUI UI 中採用 Liquid Glass、將現有功能重構成 Liquid Glass，或審查 Liquid Glass 使用方式的正確性、效能及設計一致性時使用。
這個技能專門處理 iOS 26+ 引入的 Liquid Glass API（SwiftUI 中一種新式玻璃材質視覺效果）。它能協助開發者在新的 SwiftUI 介面中實作 Liquid Glass 效果，或將現有 UIKit/SwiftUI 元素重構成此視覺風格。同時，它也提供了審查機制，確保現有 Liquid Glass 實作符合正確性、效能最佳化以及 Apple 人機介面設計原則。支援平台為 iOS 26 以上，主要作為 Claude Code 或其他 AI 代理的技能使用，透過閱讀 SKILL.md 文件來理解 Liquid Glass 的使用情境與最佳實踐。該技能的核心價值在於簡化現代 SwiftUI 玻璃材質效果的開發流程，並幫助團隊維持一致的視覺風格。
npx skills add https://github.com/dimillian/skills/tree/main/skills/swiftui-liquid-glass使用 iOS 26+ 的 Liquid Glass API 來實作、審查或改善 SwiftUI 功能。當被要求在新的 SwiftUI UI 中採用 Liquid Glass、將現有功能重構成 Liquid Glass，或審查 Liquid Glass 使用方式的正確性、效能及設計一致性時使用。
This repo contains 7 individual skills — each has its own dedicated page.
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.
Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project. Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode.
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file. Concrete actions include adding Sendable conformance, applying @MainActor annotations, resolving actor isolation warnings, fixing data race diagnostics, and migrating completion handlers to async/await.
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.
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/HStack, managing @State or @Binding, building declarative iOS interfaces, or needing component-specific patterns and examples.
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.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".