swift

Enforce Swift coding conventions, concurrency safety, and review checklists.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill swift-pyl-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swift
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/swift
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill swift-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents fragile or inconsistent Swift code by forcing clear documentation constraints for formatting, immutability, naming, error handling, and Swift 6 concurrency.

Core Features & Use Cases

  • Swift conventions & constraints: Enforces SwiftFormat/SwiftLint usage and consistency across Swift sources and Xcode/SPM projects.
  • Correctness-focused design: Requires immutability defaults, Apple API naming guidance, typed error documentation, and structured concurrency patterns.
  • Safety-first review: Provides a security and concurrency/memory review checklist suitable for PRs and code-review gates in iOS/macOS apps and SwiftUI codebases.
  • Verification-ready build guidance: Specifies build, lint, and test commands to keep CI outputs predictable and actionable.

Quick Start

Activate the swift skill when you need an AI to review or generate Swift specs for an iOS/macOS project (including SwiftUI and concurrency) and to produce code-review-ready documentation and constraints.

Frequently Asked Questions about swift

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

FAQPage Schema
How do I enforce Swift 6 strict concurrency rules in a SwiftUI codebase?▼

To enforce Swift 6 strict concurrency rules in a SwiftUI codebase, apply Sendable conformance and structured actor patterns to prevent data races. This ensures concurrency safety by validating typed errors and memory management through a dedicated review checklist.

What is the best way to set up SwiftLint and SwiftFormat consistency for Xcode projects?▼

Setting up SwiftLint and SwiftFormat consistency for Xcode projects involves applying automated formatting and immutability constraints across Swift sources. This ensures predictable CI outputs by standardizing naming conventions and enforcing Apple API design guidelines.

Why does my Swift code review checklist need typed error documentation?▼

Typed error documentation is needed in a Swift code review checklist because it forces explicit error handling and structured concurrency patterns. This prevents fragile code by making failure states verifiable during security and memory review gates.

Can I use structured concurrency patterns for SPM Package.swift verification?▼

Yes, you can use structured concurrency patterns for SPM Package.swift verification by aligning Swift 6 strict concurrency rules with Sendable types and actors. This produces verifiable build and test commands that keep CI outputs predictable.

Does SwiftFormat alignment work with code-generation workflows in iOS apps?▼

SwiftFormat alignment works with code-generation workflows in iOS apps by enforcing consistent immutability defaults and naming rules across generated sources. This ensures the generated code remains verifiable and passes security and concurrency review gates.

When do I need a security and memory review gate for Swift code?▼

You need a security and memory review gate for Swift code when building iOS/macOS apps or SwiftUI codebases that require strict concurrency safety. This gate validates typed errors, Sendable conformance, and structured concurrency patterns to prevent data races.