swift-api-design-guidelines-skill

Review Swift API call sites to spot ambiguity in naming, parameter roles, and overload readability. This process assesses declarations and call sites together to identify confusing or unclear Swift API surfaces and improve overall clarity.

Refactor existing Swift interfaces by renaming declarations, reworking argument labels, and clarifying summaries. This strengthens documentation to match behavior precisely and ensures the API reads naturally at the point of use.

Add documentation comments and symbol markup to Swift declarations when designing new APIs or refactoring existing ones. Every public declaration requires an accurate documentation summary to resolve ambiguity in parameters and weakly typed overloads.

Resolve ambiguity in Swift API parameters and weakly typed overloads by starting from use-site examples. This ensures fluent English-like call patterns and correct mutating/nonmutating naming pairs across declarations and overload sets.

Yes, you can use Swift API Design Guidelines for reviewing call-site fluency across declarations and overload sets. It helps identify ambiguity in parameter roles and ensures consistent symbol markup throughout the interface.