How do I install the Implement Swiftui IOS skill?

Run npx skillmds@latest add 0xkoru/implement-swiftui-ios 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 Implement Swiftui IOS safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Implement Swiftui IOS?

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 Implement Swiftui IOS free to use?

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

Who published Implement Swiftui IOS?

0xKoru (@0xkoru) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Implement Swiftui IOS by 0xkoru — Agent Skill

Name: Implement Swiftui IOS
Rating: 4.5 (4 reviews)
Author: 0xKoru

Implement Swiftui IOS

Implement iOS and iPadOS interfaces with SwiftUI using native Apple HIG patterns. Use when Codex needs to write, refactor, or review SwiftUI screens, NavigationStack flows, TabView layouts, forms, settings sheets, lists, toolbars, accessibility modifiers, Dynamic Type support, SF Symbols, semantic colors, materials, and adaptive iPad layouts.

0xKoru Updated Sep 22, 2026

File contents

Implement SwiftUI iOS

Use this skill when the desired output is SwiftUI code, not only a visual concept.

Workflow

Inspect the existing app architecture before adding views. Follow local state, routing, dependency injection, style, and preview patterns.
Map the screen to native SwiftUI containers: NavigationStack, TabView, List, Form, ScrollView, Grid, ToolbarItem, sheet, confirmationDialog, and alert.
Use semantic platform APIs before custom styling: foregroundStyle, tint, font, buttonStyle, controlSize, labelStyle, presentationDetents, and system materials.
Implement accessibility while building: labels, hints only when useful, traits, sort priority, focus, minimum target size, Dynamic Type, Reduce Motion, and color contrast.
Add previews that exercise at least light/dark mode, large text, and small-screen layout when the project supports previews.
Verify with the app's build/test workflow or explain the blocker.

SwiftUI Design Rules

Prefer native controls over custom clones. Only custom-build controls when the product needs behavior the system does not provide.
Use SF Symbols through Image(systemName:). Pair icons with text unless the icon is universally recognized or has an accessibility label.
Use semantic colors such as .primary, .secondary, .tint, .background, and platform materials. Avoid hardcoded colors unless creating a brand accent.
Use .dynamicTypeSize(...) only to constrain layouts when necessary; do not disable accessibility sizes casually.
Keep forms in Form or grouped List patterns. Avoid building settings as arbitrary stacks.
Use .toolbarTitleDisplayMode(.inline) for compact modal settings; use large titles for content hubs.
Make tappable rows obvious and keep destructive actions visibly distinct.

References

Read references/swiftui-ios-patterns.md for implementation patterns and examples.

---name: implement-swiftui-iosdescription: Implement iOS and iPadOS interfaces with SwiftUI using native Apple HIG patterns. Use when Codex needs to write, refactor, or review SwiftUI screens, NavigationStack flows, TabView layouts, forms, settings sheets, lists, toolbars, accessibility modifiers, Dynamic Type support, SF Symbols, semantic colors, materials, and adaptive iPad layouts.---# Implement SwiftUI iOSUse this skill when the desired output is SwiftUI code, not only a visual concept.## Workflow1. Inspect the existing app architecture before adding views. Follow local state, routing, dependency injection, style, and preview patterns.2. Map the screen to native SwiftUI containers: `NavigationStack`, `TabView`, `List`, `Form`, `ScrollView`, `Grid`, `ToolbarItem`, `sheet`, `confirmationDialog`, and `alert`.3. Use semantic platform APIs before custom styling: `foregroundStyle`, `tint`, `font`, `buttonStyle`, `controlSize`, `labelStyle`, `presentationDetents`, and system materials.4. Implement accessibility while building: labels, hints only when useful, traits, sort priority, focus, minimum target size, Dynamic Type, Reduce Motion, and color contrast.5. Add previews that exercise at least light/dark mode, large text, and small-screen layout when the project supports previews.6. Verify with the app's build/test workflow or explain the blocker.## SwiftUI Design Rules- Prefer native controls over custom clones. Only custom-build controls when the product needs behavior the system does not provide.- Use SF Symbols through `Image(systemName:)`. Pair icons with text unless the icon is universally recognized or has an accessibility label.- Use semantic colors such as `.primary`, `.secondary`, `.tint`, `.background`, and platform materials. Avoid hardcoded colors unless creating a brand accent.- Use `.dynamicTypeSize(...)` only to constrain layouts when necessary; do not disable accessibility sizes casually.- Keep forms in `Form` or grouped `List` patterns. Avoid building settings as arbitrary stacks.- Use `.toolbarTitleDisplayMode(.inline)` for compact modal settings; use large titles for content hubs.- Make tappable rows obvious and keep destructive actions visibly distinct.## ReferencesRead `references/swiftui-ios-patterns.md` for implementation patterns and examples.

Frequently asked questions