skills.rest
productengineered
productengineeredCOMMUNITY
Explore all skills by this author →
GitHub

architecture-patterns

Guides macOS Swift/SwiftUI architectural decisions using SOLID, DRY, and Clean principles.

Updated Apr 9, 2026
Search Tags:#architecture#swift#macos#swiftui#solid#clean-architecture#dry
One-click install
npx skills add https://github.com/productengineered/parsely --skill architecture-patterns-productengineered
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/productengineered/parsely/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/productengineered/parsely --skill architecture-patterns-productengineered

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference material for architectural decisions in macOS Swift/SwiftUI applications, helping teams choose structured patterns over ad-hoc coding.

Core Features & Use Cases

  • SOLID, DRY, and Clean Architecture principles with practical guidance for domain, data, and presentation layers.
  • Design-pattern checklists and coupling/cohesion guidance to evaluate and improve code structure.
  • Real-world use cases and code example snippets to inform architecture decisions during reviews and refactors.

Quick Start

Review the Architecture & Design Patterns guide and start applying SOLID, DRY, and Clean Architecture principles to your macOS SwiftUI project.

Frequently Asked Questions about architecture-patterns

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

FAQPage Schema
How do I apply Clean Architecture and SOLID principles in a SwiftUI macOS app?▼

Apply Clean Architecture and SOLID principles in a SwiftUI macOS app by consolidating domain, data, and presentation layer guidance. Use design-pattern checklists to evaluate structure, dependencies, and layering during code reviews and refactors.

What is the best way to structure dependencies in a macOS Swift project?▼

The best way to structure dependencies in a macOS Swift project is using Clean Architecture rules to manage coupling and cohesion. This ensures dependencies point inward toward domain layers, preventing ad-hoc coding and structural decay.

When do I need Clean Architecture for my Swift application?▼

You need Clean Architecture for your Swift application when evaluating complex structure, dependencies, and layering during project inception or refactors. It replaces ad-hoc coding with structured, pattern-based practices for robust macOS apps.

Does this architecture guidance work for both new Swift projects and refactoring existing ones?▼

Yes, this architecture guidance works for both new Swift projects and refactoring existing ones. It provides actionable design guidance and code example snippets to inform architecture decisions during project inception, code reviews, and major refactors.

How do I evaluate coupling and cohesion in SwiftUI code reviews?▼

Evaluate coupling and cohesion in SwiftUI code reviews using design-pattern checklists based on SOLID and DRY principles. This guidance helps identify structural improvements and ensures proper separation of domain, data, and presentation layers.

Related Skills

Explore More Software Engineering Skills→
dagbadagba
3

architecture-patterns

Guide iOS teams in selecting MVVM, TCA, or Clean Architecture by feature complexity.

Community
Basic
marcosd4hmarcosd4h
17

import-export-resolver

Resolve PE import and export relationships across analyzed modules.

Community
Advanced
multiplex-aimultiplex-ai
2

android-clean-architecture

Defines modular Clean Architecture layers and dependency rules for Android and Kotlin Multiplatform projects.

Official
Advanced
hoonsubinhoonsubin

clean-architecture

Guides implementing Clean Architecture principles for scalable, maintainable software design.

Community
Advanced