swift-conventions

Enforce Swift naming, access control, and async/await conventions.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/heikopanjas/agent-skills --skill swift-conventions-heikopanjas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swift-conventions
Source: https://github.com/heikopanjas/agent-skills/tree/main/swift-conventions
Command: npx skills add https://github.com/heikopanjas/agent-skills --skill swift-conventions-heikopanjas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swift development often suffers from inconsistent naming, scattered access control, and varied async/await usage, causing maintainability and onboarding friction.

Core Features & Use Cases

  • Naming conventions for types, properties, and functions to ensure readability and consistency
  • Explicit access control guidance and best practices for public, internal, and private APIs
  • Consistent async/await usage patterns and error handling for reliability
  • Documentation style guidance and usage of MARKs to organize codebases

Quick Start

Apply these conventions to a Swift project by updating a sample file to adhere to the described naming, access control, and async/await patterns.

Frequently Asked Questions about swift-conventions

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

FAQPage Schema
What are the best Swift coding conventions for a growing team?

Swift coding conventions for scaling teams center on consistent naming, explicit access control, and reliable async/await patterns. Applying these standards across writing, review, and refactoring reduces onboarding friction and improves codebase maintainability.

How do I enforce consistent naming and access control in a Swift project?

To enforce naming and access control in Swift, apply explicit access modifiers for public, internal, and private APIs alongside standardized naming conventions for types, properties, and functions. This ensures readability and consistency across the entire codebase.

What is the recommended async await usage pattern in Swift?

Consistent async/await usage patterns in Swift focus on standardized error handling and reliable asynchronous execution. Applying these conventions during code review and refactoring ensures your concurrent code remains maintainable and predictable.

How do I organize a Swift codebase with MARKs and documentation?

Organize a Swift codebase by applying documentation style guidance and using MARKs to structure files logically. This convention improves code navigation and onboarding by making the architecture and section boundaries immediately clear to developers.

Does this cover SwiftUI practices as well as general Swift coding standards?

Yes, these Swift coding conventions cover SwiftUI practices alongside general coding standards. They apply to writing, reviewing, and refactoring tasks, ensuring consistent naming, access control, and async/await usage across both standard and SwiftUI views.