Swift Api Design Guidelines

Enforces the official Swift API Design Guidelines with decision tables and concrete rules for argument labels, mutating/nonmutating pairs, and side-effect naming. You'll want this when you're stuck on whether to use `sorted()` or `sorting()`, when to omit the first argument label, or how to name a Boolean property so it reads like an assertion. The prepositional phrase rule and grammatical phrase rule are spelled out with examples, and there's a clear -ed/-ing suffix guide that explains why it's `sorted()` but `strippingNewlines()`. Targets Swift 6.3 and stays focused on naming conventions, routing type-system questions to other skills. Most useful during API design reviews or when refactoring for call-site clarity.

skills.sh installs: 3K
GitHub stars: 1.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add dpearson2699/swift-ios-skills --skill swift-api-design-guidelines --agent claude-code

Installs into .claude/skills of the current project.

Files

Swift API Design Guidelines

Apply the Swift API Design Guidelines to naming, labels, documentation, and call-site clarity. For mixed requests, handle the API-design portion here and route language/type-system work to swift-language, concurrency to swift-concurrency, and lint configuration to swiftlint.