apple-ui

Build SwiftUI views and navigation flows from feature specs for Apple platforms.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/glwr/ai-coding-base --skill apple-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apple-ui
Source: https://github.com/glwr/ai-coding-base/tree/main/apple/.claude/skills/apple-ui
Command: npx skills add https://github.com/glwr/ai-coding-base --skill apple-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build SwiftUI interfaces and navigation efficiently after architecture has been designed, reducing boilerplate and ensuring consistency across Apple platforms.

Core Features & Use Cases

  • SwiftUI view generation: Create views and navigation flows that follow the project's design system and patterns.
  • Architecture-driven UI: Implement screens from feature specs and tech design documents.
  • Cross-platform consistency: Apply the same UI patterns on iOS, macOS, and other Apple platforms.

Quick Start

Create the initial SwiftUI view module following the architecture design and update CLAUDE.md with stack, navigation, and styling choices.

Frequently Asked Questions about apple-ui

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

FAQPage Schema
How do I build SwiftUI views from feature specs?

To build SwiftUI views from feature specs, translate architecture designs and tech patterns into navigable views, data binding, and screen flows for iOS and macOS. This approach ensures UI consistency and reduces boilerplate across Apple platforms.

How does MVVM architecture work with SwiftUI navigation flows?

MVVM architecture with SwiftUI navigation separates screen flows and data binding from view logic. By following project patterns, you wire views to ViewModels, ensuring navigable interfaces that leverage the design system consistently across iOS and macOS.

Can I use the same SwiftUI UI patterns for iOS and macOS?

Yes, you can apply the same SwiftUI UI patterns for iOS and macOS. Architecture-driven UI implementation ensures cross-platform consistency by leveraging a shared design system and navigation patterns across all Apple platforms.

What's the best way to wire SwiftUI data binding for new screens?

The best way to wire SwiftUI data binding for new screens is to follow the project's existing MVVM or architecture patterns. Implement screens from feature specs by referencing guidance in context/patterns.md and docs/design-system.md for consistent data flows.

Do I need architecture designs before implementing SwiftUI interfaces?

Yes, you need architecture designs before implementing SwiftUI interfaces. This Skill builds and wires views efficiently after architecture has been designed, translating feature specs and tech patterns into navigable views rather than creating the architecture itself.