ios-std

Propose iOS coding standards and templates for SwiftUI and MVVM architectures.

3|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/edfenton/claude-skills --skill ios-std
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-std
Source: https://github.com/edfenton/claude-skills/tree/main/ios/ios-std
Command: npx skills add https://github.com/edfenton/claude-skills --skill ios-std

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coding standards and templates to enforce consistent iOS app architecture (SwiftUI, MVVM, offline-first, logging) across teams.

Core Features & Use Cases

  • Enforces MVVM boundaries and SwiftUI conventions to produce testable, maintainable code.
  • Provides a persistence boundary for offline-first apps, plus a standard logging strategy and a suite of testing templates.
  • Use Case: As a new iOS feature is added, follow these conventions to ensure a cohesive project structure and predictable behavior.

Quick Start

Create a sample feature following the MVVM and SwiftUI conventions to validate consistency in your iOS project.

Frequently Asked Questions about ios-std

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

FAQPage Schema
What are the best coding standards for maintaining a consistent SwiftUI and MVVM architecture across an iOS team?

Coding standards for SwiftUI and MVVM enforce consistent iOS app architecture by providing templates for project structure, naming conventions, and offline-first boundaries. These standards ensure teams produce testable and maintainable code.

How do I structure an iOS app to support offline-first persistence and standard logging?

To structure an offline-first iOS app, apply a defined persistence boundary and a standard logging strategy. This approach provides ready-to-use boundaries for data persistence and notifications within your SwiftUI project.

Can I use these iOS coding conventions to scaffold a new feature in an existing project?

Yes, you can use these conventions to scaffold new iOS features. By following the provided MVVM and SwiftUI templates, you validate consistency and ensure a cohesive project structure as your application grows.

Does following MVVM boundaries in SwiftUI actually improve iOS app testing?

Yes, enforcing MVVM boundaries in SwiftUI directly improves iOS app testing. The standards provide a suite of testing templates and clear guidance for validation, ensuring your code remains predictable and testable.

What is the standard way to enforce MVVM boundaries and naming conventions in a SwiftUI project?

The standard way to enforce MVVM boundaries in a SwiftUI project is by applying reusable reference patterns and scaffolding documentation. This unified structure provides clear architectural boundaries for all developers.