swiftui-core
SwiftUI fundamentals for all Apple platforms. Use when building views, navigation, data persistence, or state management with SwiftUI across iOS, macOS, iPadOS, watchOS, visionOS.
What this skill does
# SwiftUI Core SwiftUI fundamentals shared across all Apple platforms. ## Agent Workflow (MANDATORY) Before ANY implementation, use `TeamCreate` to spawn 3 agents: 1. **fuse-ai-pilot:explore-codebase** - Analyze existing SwiftUI patterns 2. **fuse-ai-pilot:research-expert** - Verify latest SwiftUI docs via Context7/Exa 3. **mcp__apple-docs__search_apple_docs** - Check SwiftUI view patterns After implementation, run **fuse-ai-pilot:sniper** for validation. --- ## Overview ### When to Use - Building SwiftUI views and components - Implementing navigation (NavigationStack, SplitView) - Data persistence with SwiftData - State management (@State, @Observable) - Custom view modifiers and layouts ### Why SwiftUI Core | Feature | Benefit | |---------|---------| | Declarative UI | Less code, automatic updates | | Cross-platform | Same code for iOS/macOS/watchOS/visionOS | | @Observable | Simple reactive state | | SwiftData | Modern persistence with minimal code | --- ## Key Concepts ### Views & Modifiers Composable UI building blocks. Extract subviews at 30+ lines. ### Navigation NavigationStack for stack-based, NavigationSplitView for multi-column. ### SwiftData Modern persistence with @Model. Replaces Core Data for most use cases. ### State Management @State for local, @Observable for shared, @Environment for injection. --- ## Reference Guide | Need | Reference | |------|-----------| | Views, modifiers, layouts | [views-modifiers.md](references/views-modifiers.md) | | NavigationStack, deep linking | [navigation.md](references/navigation.md) | | SwiftData, @Query, CloudKit | [data-swiftdata.md](references/data-swiftdata.md) | | @State, @Observable, Environment | [state-management.md](references/state-management.md) | | Liquid Glass all platforms | [liquid-glass.md](references/liquid-glass.md) | | Siri, Shortcuts, App Intents | [app-intents.md](references/app-intents.md) | --- ## Best Practices 1. **Small views** - Extract at 30+ lines 2. **Composition** - Use ViewBuilder and modifiers 3. **Preview-driven** - Always include #Preview 4. **Semantic colors** - Use .primary, .secondary 5. **Accessibility** - Add labels to icons 6. **Platform adaptation** - Check sizeClass for responsive layouts
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.