SwiftUI MVVM Structure

Table of Contents

• •1. Directory Structure ... L15-L40
• •2. Naming Conventions ..... L42-L80
• •3. Organization Rules ..... L82-L110
• •4. Feature Example ........... L112-L140

1. Directory Structure

ProjectName/
├── App/
│   └── ProjectNameApp.swift
├── Core/
│   ├── Extensions/
│   ├── Utilities/
│   └── Network/
├── Features/
│   └── FeatureName/
│       ├── Views/
│       ├── ViewModels/
│       ├── Models/
│       └── Services/
├── .claude/shared/
│   ├── Components/
│   ├── Styles/
│   └── Modifiers/
├── Resources/
└── Tests/

Folder Purposes

2. Naming Conventions

Folder Naming

• •Features/ - Feature modules by functionality
• •Core/ - App-wide shared code
• •.claude/shared/ - Reusable UI components
• •Services/ - Business logic, API services
• •Resources/ - Assets, Localizable, Info.plist

File Naming

Component Naming

3. Organization Rules

MVVM Responsibilities

Rules

1. •Each feature is a separate folder in Features/
2. •Each feature has subfolders: Views/, ViewModels/, Models/, Services/
3. •View contains UI only, no business logic
4. •ViewModel contains state and business logic
5. •Model is data structure only
6. •Service handles API and data persistence
7. •Components in .claude/shared/ are reusable across features

Dependencies Direction

View → ViewModel → Service → Model
  ↓         ↓          ↓
  UI      Logic      Data

• •View depends on ViewModel
• •ViewModel depends on Service
• •Service depends on Model
• •Model has no dependencies

4. Feature Example

Authentication Feature

Features/
└── Authentication/
    ├── Views/
    │   ├── LoginView.swift
    │   ├── RegisterView.swift
    │   └── Components/
    │       ├── AuthHeader.swift
    │       └── SocialLoginButtons.swift
    ├── ViewModels/
    │   ├── LoginViewModel.swift
    │   └── RegisterViewModel.swift
    ├── Models/
    │   ├── User.swift
    │   ├── LoginRequest.swift
    │   └── LoginResponse.swift
    └── Services/
        ├── AuthService.swift
        └── AuthServiceProtocol.swift

File Contents Overview

Checklist

When creating new feature:

• • Create folder in Features/[FeatureName]/
• • Create subfolders: Views/, ViewModels/, Models/, Services/
• • Follow naming conventions
• • Keep View logic-free
• • Keep Model data-only

When creating new screen:

• • Create [Name]View.swift in Views/
• • Create [Name]ViewModel.swift in ViewModels/
• • Create models if needed in Models/
• • Add Preview for View

When creating reusable component:

• • Place in .claude/shared/Components/[Type]/
• • Make it configurable via parameters
• • Add Preview
• • Document usage