ios-swift-api-design-reviewer

Installation
SKILL.md

Swift API Design Review

What “good” looks like

  • Prioritize clarity at the call site, even if the declaration becomes a bit longer.
  • Follow established standard library conventions so your API “feels Swift”.
  • Prefer precise words over generic ones (data, info, manager, handler, util).

Naming Rules (Types, Properties, Methods)

  • Clear at point of use, not at declaration.
  • Omit needless words, but do not remove words that carry meaning.
  • lowerCamelCase: functions, methods, properties, enum cases.
  • UpperCamelCase: types, protocols.
  • Avoid “noise” suffixes like String, Array, Data unless they add meaning.

Boolean naming

  • Prefer predicates: is, has, can, should, did.
Related skills

More from desquared/agents-rules-skills

Installs
10
GitHub Stars
3
First Seen
Mar 13, 2026