coding-best-practices

Audit macOS Swift code for SOLID, Swift 6 concurrency, and SwiftData compliance.

27|5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/bocan/bocan-music --skill coding-best-practices-bocan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-best-practices
Source: https://github.com/bocan/bocan-music/tree/main/.claude/skills/macos/coding-best-practices
Command: npx skills add https://github.com/bocan/bocan-music --skill coding-best-practices-bocan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the issue of unmaintainable, buggy, or non-idiomatic macOS Swift code that fails to follow modern Swift 6+ standards, SOLID principles, and macOS-specific best practices, leading to technical debt, performance issues, and poor app quality.

Core Features & Use Cases

  • Code Quality Audits: Reviews macOS Swift code for adherence to SOLID, DRY, and Clean Architecture principles.
  • Modern Pattern Guidance: Provides actionable recommendations for Swift 6 concurrency, SwiftData persistence, and SwiftUI/AppKit best practices.
  • Use Case: Perfect for macOS developers refactoring legacy codebases, enforcing team coding standards, or preparing native apps for macOS 26 (Tahoe) deployment.

Quick Start

Request a code review of your macOS Swift project's view model layer to identify concurrency safety issues and SOLID principle violations.

Frequently Asked Questions about coding-best-practices

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

FAQPage Schema
How do I fix Swift 6 structured concurrency safety issues in my macOS app?

Fix Swift 6 structured concurrency safety issues by auditing view model layers for actor isolation, sendable conformance, and data race violations to eliminate crashes and technical debt in macOS applications.

What are the best practices for migrating to SwiftData persistence in macOS?

Migrating to SwiftData persistence requires validating adherence to modern SwiftData patterns, ensuring clean architecture separation, and replacing legacy Core Data stacks to achieve macOS 26 Tahoe deployment readiness.

Can I use this to enforce team coding standards for SOLID principles in Swift?

Yes, you can enforce team coding standards by auditing Swift codebases against SOLID and DRY principles, generating actionable refactoring recommendations to resolve violations and unify team architecture patterns.

What is the best way to refactor a legacy macOS Swift codebase for modern architecture?

The best way to refactor a legacy macOS Swift codebase involves reviewing modular architecture requirements, identifying SOLID principle violations, and applying Swift 6 concurrency rules to resolve technical debt.

Does my macOS app need SwiftUI or AppKit best practices for a pre-release quality audit?

A pre-release quality audit requires validating both SwiftUI and AppKit best practices to ensure your native macOS application meets modern platform-specific standards before macOS 26 Tahoe deployment.

Why does my macOS Swift code keep crashing after upgrading to Swift 6?

Swift 6 code crashes often occur due to non-compliant structured concurrency rules and data race violations, requiring a dedicated code review to identify and refactor unsafe concurrent access patterns.