swift-style

Enforce Swift naming, type semantics, error handling, and concurrency guidelines.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/dimitriRemoiville/cc-mobile --skill swift-style-dimitriremoiville
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swift-style
Source: https://github.com/dimitriRemoiville/cc-mobile/tree/main/plugins/cc-mobile-ios/skills/swift-style
Command: npx skills add https://github.com/dimitriRemoiville/cc-mobile --skill swift-style-dimitriremoiville

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swift coding conventions and idioms enforced on this project. Load whenever writing or reviewing Swift — naming, value vs. reference types, optionals, error handling, concurrency, Sendable, access control, and when to use extensions / protocols / generics.

Core Features & Use Cases

  • Naming: UpperCamelCase for types, lowerCamelCase for members, protocol naming.
  • Type semantics & optionals: Prefer value types, safe unwraps, explicit handling.
  • Error handling & concurrency: Async/await patterns, structured error mapping. Use Case: When starting a new Swift module, apply the swift-style guidelines to naming and architecture.

Quick Start

Review and apply the swift-style guidelines when editing Swift files in this project.

Frequently Asked Questions about swift-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent Swift coding conventions across a project?

Enforce Swift coding conventions by applying rules for naming, value vs. reference types, optionals, and error handling during code reviews. This ensures consistent style and idioms across the project.

What are the best practices for naming types and protocols in Swift?

Best practices for Swift naming include using UpperCamelCase for types and lowerCamelCase for members. Protocol naming guidelines are also enforced to maintain clarity and consistency across your codebase.

When should I use value types instead of reference types in Swift?

Use value types in Swift to ensure predictable state management and avoid shared state issues. The conventions prefer value types over reference types, enforcing safer data models and explicit optional handling.

Does this approach cover async/await patterns and Sendable concurrency?

Yes, it covers async/await patterns and Sendable concurrency by enforcing structured error mapping. It provides specific guidelines for safely managing concurrency scenarios and structured error handling in Swift.

How do I structure error handling and protocol usage in a new Swift module?

Structure error handling in a new Swift module by applying structured error mapping and specific guidelines for protocol usage. This ensures safe unwraps and consistent architecture when starting development.