> ios-xcode
Xcode setup and tooling guidance for iOS 26 / Swift 6.2 clinic modular MVVM-C projects covering project configuration, SwiftData container wiring, testing, debugging, profiling, and distribution workflows. Use when configuring App-target infrastructure or day-to-day tooling around clinic architecture modules.
curl "https://skillshub.wtf/pproenca/dot-skills/ios-xcode?format=md"iOS Xcode & Tooling Best Practices
Comprehensive guide for Xcode project configuration, SwiftData persistence, testing, debugging, profiling, and app distribution. Contains 19 rules across 6 categories.
Clinic Architecture Contract (iOS 26 / Swift 6.2)
All guidance in this skill assumes the clinic modular MVVM-C architecture:
- Feature modules import
Domain+DesignSystemonly (neverData, never sibling features) - App target is the convergence point and owns
DependencyContainer, concrete coordinators, and Route Shell wiring Domainstays pure Swift and defines models plus repository,*Coordinating,ErrorRouting, andAppErrorcontractsDataowns SwiftData/network/sync/retry/background I/O and implements Domain protocols- Read/write flow defaults to stale-while-revalidate reads and optimistic queued writes
- ViewModels call repository protocols directly (no default use-case/interactor layer)
When to Apply
Reference these guidelines when:
- Setting up Xcode projects with AppStorage, ScenePhase, or widgets
- Implementing SwiftData models, queries, and CRUD operations
- Writing tests with Swift Testing framework
- Debugging with breakpoints and console output
- Profiling performance with Instruments
- Distributing apps via TestFlight
- Building for visionOS or integrating ML features
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | SwiftData & Persistence | CRITICAL | data- |
| 2 | Project & Platform | HIGH | platform- |
| 3 | Testing | HIGH | test- |
| 4 | Debugging & Profiling | MEDIUM-HIGH | debug-, perf- |
| 5 | Distribution | MEDIUM | dist- |
| 6 | Specialty Platforms | MEDIUM | ml-, spatial- |
Quick Reference
1. Project & Platform (HIGH)
platform-app-storage- Use AppStorage for user preferencesplatform-scene-phase- Respond to app lifecycle with ScenePhaseplatform-widget-integration- Design for widget and Live Activity integrationplatform-system-features- Integrate system features natively
2. SwiftData & Persistence (CRITICAL)
data-model-macro- Define models with @Model macrodata-query-for-fetching- Use @Query for fetching datadata-model-container- Configure model containersdata-relationships- Define model relationshipsdata-crud-operations- Implement CRUD operations
3. Testing (HIGH)
test-swift-testing- Use Swift Testing frameworktest-preview-sample-data- Create preview sample datatest-preview-macro- Use #Preview macro for rapid iteration
4. Debugging & Profiling (MEDIUM-HIGH)
debug-breakpoints- Use breakpoints for debuggingdebug-console-output- Use console output for debuggingperf-instruments-profiling- Profile SwiftUI with Instruments
5. Distribution (MEDIUM)
dist-testflight- Distribute via TestFlightdist-app-icons- Design app icons for distribution
6. Specialty Platforms (MEDIUM)
ml-natural-language- Integrate Natural Language MLspatial-visionos-windows- Build for visionOS spatial computing
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions - Category structure and impact levels
- Rule template - Template for adding new rules
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
> related_skills --same-repo
> rust-write-tests
Skill for writing expert-level Rust tests. Teaches the "What Could Break?" framework, five transformations from superficial to expert tests, flake hunting protocol, intent-based assertions, naming conventions, and a mandatory self-review checklist. Triggers on writing Rust tests, designing test cases, improving test quality, or reviewing test coverage.
> rust-implement
Write production-grade Rust code using a multi-pass approach. Design types first, then implement, then simplify, then verify with automated lint. Use this skill whenever writing new Rust functions, structs, modules, or features. Triggers on Rust implementation, new Rust code, Rust functions, Rust modules, error handling in Rust, async Rust, or type design in Rust.
> valid-skill
A valid test skill with proper formatting. This skill should pass all validations and serves as a reference for the expected format.
> too-long-skill
This skill has more than 500 lines which should fail validation.