ios-naming-conventions

Naming conventions in Swift enforce consistency by establishing rules for types (PascalCase), variables (camelCase), functions (verb-based camelCase), and IBOutlets. This Skill validates your code against these standards, identifying violations like generic abbreviations (`amt` instead of `paymentAmount`) and missing boolean prefixes (`loading` instead of `isLoading`), then generates a structured report of non-conformances.

Inconsistent naming reduces readability, increases onboarding friction, and complicates maintenance. Swift naming conventions establish a shared language across your codebase. Using this Skill during code reviews catches violations before merge, ensuring descriptive identifiers and preventing ambiguous abbreviations that slow down developer understanding.

This Skill performs static analysis on Swift files, validating class names, variables, functions, and IBOutlets against Payoo Merchant project standards. It detects PascalCase violations in types, camelCase deviations in variables, missing verb-based patterns in functions, and absent suffixes in IBOutlets, then outputs a comprehensive violation report.

Yes. Activate this Skill before merging to automatically scan all modified Swift files and generate a naming violations report. It identifies issues like abbreviated variable names, missing boolean prefixes, and non-descriptive identifiers, making it ideal for quality gates and automated code review workflows.

Yes. The Skill includes abbreviation detection to identify and flag common generic names and unclear identifiers. It suggests fixes for patterns like `PayVC` (should be `PaymentViewController`) and `amt` (should be `paymentAmount`), promoting descriptive, self-documenting code.

Run this Skill during developer onboarding to scan existing code and generate a baseline violations report. This teaches naming standards through real-world examples in your codebase, making implicit conventions explicit. Developers see exactly which patterns the project enforces before committing their own code.