swift-api-design-guidelines-skill

Improve Swift API design by analyzing existing declarations against established naming conventions and argument labeling rules to ensure intent is explicit. Refactoring guidance adjusts names and documentation comments to prioritize clarity at the point of use.

Best practices for Swift naming conventions involve applying established patterns for factory methods and mutating/nonmutating pairs to ensure consistency. This refactoring process evaluates call sites to make interfaces fluent and idiomatic.

Argument labeling affects Swift API review by ensuring declarations prioritize clarity and maintain consistency across the codebase. Adjusting labels during code review makes call sites unambiguous and improves overall interface fluency.

Yes, you can use Swift API design guidelines to create new idiomatic declarations by applying established patterns for parameter defaults and factory methods. This ensures new feature designs are fluent and consistent before finalizing implementation.

Refactor Swift API surfaces for documentation standards when interfaces become ambiguous, difficult to read, or inconsistent with the language's design philosophy. Updating documentation comments ensures intent remains explicit across the codebase.

Yes, this approach evaluates existing declarations and call sites to provide actionable refactoring advice tailored to your current codebase patterns. It ensures all API surfaces maintain consistency while prioritizing clarity at the point of use.