← ClaudeAtlas

refresh-swiftlisted

Research current Swift/SwiftUI/platform best practices from gold-standard sources and update the docs/setup/swift/ reference files and the modern-swiftui.md guardrails stub. Also refreshes the App Store submission facts embedded in the appstore-preflight skill. Use when the user says "refresh swift", "update swift guidance", "refresh swift best practices", or "refresh swiftui".
rterakedis/leanwheel-skills · ★ 2 · AI & Automation · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Refresh Swift Best Practices Skill **Goal:** Research the current state of Swift language, SwiftUI, concurrency, testing, and platform-specific patterns from primary sources and update the sectioned reference docs in `docs/setup/swift/` plus the `modern-swiftui.md` guardrails stub in the skills repo. These files are baked into every new Apple platform project — keeping them current is critical for guiding correct architectural choices. The same run also refreshes the App Store submission facts embedded in the `appstore-preflight` skill (Step 4) — those shift on the same iOS/Xcode cadence. **Scope:** iOS 18 through the current stable release only. **Hard exclude** any pre-release, beta, or unannounced OS API. When in doubt, omit. **Version-axis rules (prevents drift):** 1. **Verify version names before writing any header.** Search for the current stable iOS/macOS/Swift/Xcode versions first — never infer the next version by incrementing (Apple jumped iOS 18 → iOS 26; a past run invented a phantom "iOS 19" from that assumption). Every fact written must cite a real, shipped version string. 2. **Concurrency and testing guidance is keyed to the Swift language version** (e.g. Swift 6.2), not the iOS version — label and research those files on that axis. 3. For every file, the research question is **"what changed since this file's `Updated:` date?"** against the current stable release — not a fixed "iOS 18+?" checklist frozen at authoring time. --- ## Step 1 — Locate Files Fi