skills.rest
tanujsutaria
tanujsutariaCOMMUNITY
Explore all skills by this author →
GitHub

swiftui-architect

Plan SwiftUI view hierarchies and MVVM state management for VitalArc features.

1|Updated Jan 25, 2026
Search Tags:#architecture#plan#SwiftUI#design-system#MVVM#VitalArc
One-click install
npx skills add https://github.com/tanujsutaria/VitalArc --skill swiftui-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swiftui-architect
Source: https://github.com/tanujsutaria/VitalArc/tree/main/.claude/skills/swiftui-architect
Command: npx skills add https://github.com/tanujsutaria/VitalArc --skill swiftui-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps plan and standardize SwiftUI view hierarchies and MVVM-based state management for VitalArc features, ensuring consistency across screens and modules.

Core Features & Use Cases

  • Plan complete UI architectures for new screens, complex components, and navigation flows that align with VitalArc's design system.
  • Define a reusable ViewModel and view hierarchy pattern to promote consistency, testability, and scalable maintenance.
  • Use-case examples: wire a new onboarding screen from header to content, or design a multi-tab feature with nested views and state bindings.

Quick Start

Provide a concise, actionable UI plan for a new feature, including the Screen View, top-level sections, and the ViewModel pattern, following VitalArc design guidelines.

Frequently Asked Questions about swiftui-architect

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

FAQPage Schema
How do I plan SwiftUI view hierarchies for new app screens?▼

Plan SwiftUI architectures by defining a complete UI structure with a Screen View, ViewModel, and token-based design system usage to standardize view hierarchies and MVVM state management across feature modules.

What is the best way to structure SwiftUI MVVM state management?▼

Structure SwiftUI MVVM state management by defining a reusable ViewModel pattern alongside a standardized view hierarchy, promoting testability and scalable maintenance across complex components.

Can I use this to plan navigation flows and multi-tab features in SwiftUI?▼

Yes, you can plan navigation flows and multi-tab features by defining nested views and state bindings within the architecture, ensuring adherence to the VitalArc design system across modules.

Does this architecture planning approach support token-based design systems?▼

Yes, this architecture planning approach supports token-based design systems by requiring all UI plans to specify token-based design system usage for Screen Views and sections, ensuring consistent visual alignment.

When do I need to define a complete UI plan for a SwiftUI feature?▼

You need to define a complete UI plan when planning new screens, complex components, or navigation flows to ensure consistent MVVM state management and design system adherence across modules.

Related Skills

Explore More Design & Creative Skills→
wpankwpank
11

design-system-patterns

Define design token hierarchies and theme switching for multi-brand systems.

Community
Advanced
co-labs-coco-labs-co

swiftui-mvvm-pattern

Create SwiftUI views with ObservableObject ViewModels and @Published data binding.

Official
Intermediate
snailb1007snailb1007

maui-mvvm

Bind MAUI UI development to MVVM with Views, ViewModels, Models, and services.

Community
Intermediate
tuliopc23tuliopc23

axiom-swiftui-architecture

Guide SwiftUI architecture choices and refactor logic out of views.

Community
Advanced