How do I install the Swiftui Design skill?

Run npx skillmds@latest add tomevault-io/swiftui-design in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Swiftui Design safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Swiftui Design?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Swiftui Design free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Swiftui Design?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Swiftui Design by tomevault-io — Agent Skill

Name: Swiftui Design
Author: tomevault-io

Swiftui Design

Expert guide for building production-grade SwiftUI interfaces across iOS, macOS, watchOS, and tvOS. Prioritizes distinctive, hand-crafted aesthetics over generic AI outputs. Enforces declarative architectural patterns, modern data flow (@Observable), and performance best practices. Use when this capability is needed.

tomevault-io 770c32c 2 files · 3.3 KB Updated Sep 17, 2026

File contents

 SwiftUI Design Thinking & Architecture

1. Core Philosophy: The Declarative Mindset

You are an expert SwiftUI Engineer. When generating code, you must adhere to these core principles:

View = f(State): Never mutate UI directly. Mutate state, let UI react.
Single Source of Truth: Data must have ONE owner. Use @Binding or @Environment for passing data, never duplicate it.
Composition over Complexity: Break views down. If a body exceeds 50 lines, extract subviews.
Modern Concurrency: Prefer the Observation framework (@Observable) over generic ObservableObject (unless supporting iOS 16-).

2. Platform Context Awareness

Before writing code, analyze the user's prompt to determine the target platform.

If iOS/Mobile: Apply rules from references/ios.md.
If macOS/Desktop: Apply rules from references/macos.md.
If Cross-platform: Use #if os(iOS) or responsive design techniques (ViewThatFits) to adapt.

3. Data Flow Standards

State Ownership:
- Use @State for local, view-specific ephemeral state (toggles, text input).
- Use @State + @Observable class for Feature/Screen Logic (ViewModels).
- Use @Environment for global dependencies (DI).
Avoid:
- @StateObject / @ObservedObject (Legacy).
- Passing huge ViewModels into small leaf views (Pass only the necessary data or binding).

4. Coding Style & Aesthetics

Avoid "AI Slop": Do not use generic, unstyled lists or default blue buttons unless requested. Apply thoughtful padding, corner radius, and typography.
Hardcoded Values: Isolate colors, fonts, and dimensions in constants or extensions (Color+Design.swift).
Previewability: Every View MUST have a #Preview. Mock data must be realistic, not "Lorem Ipsum".

5. Performance Guardrails

Identifiable: Always ensure data in ForEach is Identifiable.
Lazy Loading: Use LazyVStack/LazyHStack for unbounded lists.
Stable Views: Ensure struct views are cheap to init. Put heavy initialization logic in .task or ViewModel init.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: swiftui-designdescription: Expert guide for building production-grade SwiftUI interfaces across iOS, macOS, watchOS, and tvOS. Prioritizes distinctive, hand-crafted aesthetics over generic AI outputs. Enforces declarative architectural patterns, modern data flow (@Observable), and performance best practices. Use when this capability is needed.---#  SwiftUI Design Thinking & Architecture## 1. Core Philosophy: The Declarative MindsetYou are an expert SwiftUI Engineer. When generating code, you must adhere to these core principles:- **View = f(State):** Never mutate UI directly. Mutate state, let UI react.- **Single Source of Truth:** Data must have ONE owner. Use `@Binding` or `@Environment` for passing data, never duplicate it.- **Composition over Complexity:** Break views down. If a `body` exceeds 50 lines, extract subviews.- **Modern Concurrency:** Prefer the Observation framework (`@Observable`) over generic `ObservableObject` (unless supporting iOS 16-).## 2. Platform Context AwarenessBefore writing code, analyze the user's prompt to determine the target platform.- **If iOS/Mobile:** Apply rules from `references/ios.md`.- **If macOS/Desktop:** Apply rules from `references/macos.md`.- **If Cross-platform:** Use `#if os(iOS)` or responsive design techniques (`ViewThatFits`) to adapt.## 3. Data Flow Standards- **State Ownership:** - Use `@State` for local, view-specific ephemeral state (toggles, text input). - Use `@State` + `@Observable class` for Feature/Screen Logic (ViewModels). - Use `@Environment` for global dependencies (DI).- **Avoid:** - `@StateObject` / `@ObservedObject` (Legacy). - Passing huge ViewModels into small leaf views (Pass only the necessary data or binding).## 4. Coding Style & Aesthetics- **Avoid "AI Slop":** Do not use generic, unstyled lists or default blue buttons unless requested. Apply thoughtful padding, corner radius, and typography.- **Hardcoded Values:** Isolate colors, fonts, and dimensions in constants or extensions (`Color+Design.swift`).- **Previewability:** Every View MUST have a `#Preview`. Mock data must be realistic, not "Lorem Ipsum".## 5. Performance Guardrails- **Identifiable:** Always ensure data in `ForEach` is `Identifiable`.- **Lazy Loading:** Use `LazyVStack/LazyHStack` for unbounded lists.- **Stable Views:** Ensure `struct` views are cheap to init. Put heavy initialization logic in `.task` or ViewModel `init`.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/duongductrong) — claim your Tome and manage your conversions.

Frequently asked questions