rules-swift

Enforce Swift coding rules by applying PascalCase for types, camelCase for functions, guard-heavy logic, and swift-format formatting to keep code aligned with Apple API Design Guidelines. Structuring files with MARK sections also keeps modules readable and consistent.

The best way to handle Swift errors is using throwing errors with typed enums, Result usage, and explicit guard statements. You should prefer value types and default immutability with let while avoiding force unwraps to keep failure paths clear and safe.

Prevent retain cycles in Swift concurrency by adopting modern async/await, actors, and TaskGroup patterns while explicitly avoiding force unwraps. Documenting override rationales for concurrency rules ensures your asynchronous code remains safe and consistent.

Yes, this Swift style guidance supports both XCTest and Swift Testing workflows. It enforces testing rules that keep Swift projects consistent with Apple API Design Guidelines regardless of the testing framework you choose for your modules.

You should prefer structs and immutability in Swift to ensure type safety and prevent unintended side effects. Using let for default immutability and favoring value types keeps your code predictable while aligning with Apple API Design Guidelines.

You need to override universal coding rules for Swift when your project requires specific naming, formatting, testing, error handling, immutability, or concurrency patterns. Documenting the override rationales ensures your Swift code stays aligned with Apple API Design Guidelines.