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 UI への Liquid Glass の導入から、既存機能のリファクタリング、使用コードの正確性、パフォーマンス、デザイン整合性のレビューまでをカバーします。開発者は、このスキルにより Liquid Glass のベストプラクティスに沿った実装を迅速に行え、iOS の最新ビジュアルエフェクトを活用したモダンな UI 構築が可能になります。主に Claude Code や Cursor などの AI エージェント向けに設計されており、プロジェクト内の SwiftUI コードを分析・修正する際に機能します。
npx skills add https://github.com/dimillian/skills/tree/main/skills/swiftui-liquid-glassiOS 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".