coding-best-practices

Apply modern Swift and macOS coding standards to codebases.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill coding-best-practices-jtvaris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-best-practices
Source: https://github.com/jtvaris/sunday-night-dynasty/tree/main/.agents/skills/macos-development/coding-best-practices
Command: npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill coding-best-practices-jtvaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

macOS Swift projects often drift from modern idioms and architectural best practices, making code harder to maintain and scale. This guide provides pragmatic, actionable guidance to apply SOLID, DRY, Clean Architecture, and concurrency patterns across macOS codebases.

Core Features & Use Cases

  • Core guidance across Swift language, architecture principles, data persistence, code organization, and concurrency.
  • Actionable feedback with concrete before/after examples and checklists for teams.
  • Reusable references and templates to enforce consistent review practices.

Quick Start

Audit your macOS project against these guidelines and implement one improvement this week.

Frequently Asked Questions about coding-best-practices

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

FAQPage Schema
How do I apply modern Swift concurrency patterns in a macOS project?

Modern Swift concurrency in macOS projects requires safe concurrency practices, enforcing modular design and strict boundaries. This prevents data races by structuring asynchronous workflows with actors and structured concurrency templates.

What's the best way to architect a scalable macOS app with SwiftData?

Scalable macOS app architecture with SwiftData enforces Clean Architecture and SOLID principles. This ensures separation of concerns, making your data persistence layer modular, testable, and easier to maintain.

How does dependency injection improve Swift code organization for macOS?

Dependency injection improves Swift code organization by decoupling components and enforcing modular design. This makes your macOS codebase easier to scale, test, and review against DRY principles.

Can I use this to review Swift 6+ codebases for best practices?

Yes, you can review Swift 6+ codebases using actionable checklists and before/after examples. This enforces consistent review practices for architecture, data persistence, and concurrency standards.

When do I need to refactor macOS code for Swift 6+ compatibility?

You need to refactor macOS code for Swift 6+ when your project drifts from modern idioms, making it hard to maintain. Apply SOLID, DRY, and safe concurrency patterns to restore architectural integrity.