swiftui-development
Master SwiftUI - Declarative UI, state management, animations, modern iOS development
What this skill does
# SwiftUI Development Skill
> Build modern, declarative iOS interfaces with SwiftUI
## Learning Objectives
By completing this skill, you will:
- Create declarative UIs with SwiftUI views
- Master state management (@State, @Binding, @Observable)
- Implement complex navigation with NavigationStack
- Create fluid animations and transitions
- Build production-ready SwiftUI applications
## Prerequisites
| Requirement | Level |
|-------------|-------|
| iOS Fundamentals | Completed |
| Swift | Intermediate |
| Functional programming concepts | Basic |
## Curriculum
### Module 1: SwiftUI Fundamentals (4 hours)
**Topics:**
- View protocol and body
- ViewBuilder and composition
- Modifiers and their order
- @ViewBuilder for custom containers
- Environment and preferences
**Code Examples:**
```swift
// Basic view composition
struct ProfileView: View {
let user: User
var body: some View {
VStack(spacing: 16) {
ProfileImage(url: user.avatarURL)
Text(user.name)
.font(.title)
.fontWeight(.bold)
Text(user.bio)
.font(.body)
.foregroundStyle(.secondary)
.multilineTextAlignment(.center)
}
.padding()
}
}
// Custom container with ViewBuilder
struct Card<Content: View>: View {
let content: Content
init(@ViewBuilder content: () -> Content) {
self.content = content()
}
var body: some View {
content
.padding()
.background(.background)
.clipShape(RoundedRectangle(cornerRadius: 12))
.shadow(radius: 4)
}
}
```
**Checkpoint:** Build profile card component
---
### Module 2: State Management (6 hours)
**Topics:**
- @State for local state
- @Binding for two-way binding
- @StateObject vs @ObservedObject
- @EnvironmentObject for shared state
- @Observable (iOS 17+)
- Combine integration
**State Hierarchy:**
```
@State → Local, value type
@Binding → Pass to child, two-way
@StateObject → Own the object, create once
@ObservedObject → Don't own, receive from parent
@EnvironmentObject → Shared globally
@Observable → Modern replacement (iOS 17+)
```
**Modern Approach (iOS 17+):**
```swift
@Observable
final class UserViewModel {
var user: User?
var isLoading = false
var error: Error?
private let service: UserServiceProtocol
init(service: UserServiceProtocol = UserService()) {
self.service = service
}
func loadUser() async {
isLoading = true
defer { isLoading = false }
do {
user = try await service.fetchCurrentUser()
} catch {
self.error = error
}
}
}
struct UserView: View {
@State private var viewModel = UserViewModel()
var body: some View {
Group {
if viewModel.isLoading {
ProgressView()
} else if let user = viewModel.user {
UserContent(user: user)
}
}
.task {
await viewModel.loadUser()
}
}
}
```
**Checkpoint:** Build stateful form with validation
---
### Module 3: Navigation (5 hours)
**Topics:**
- NavigationStack (iOS 16+)
- NavigationPath for programmatic navigation
- NavigationSplitView for iPad
- Sheet, fullScreenCover, alert
- Deep linking with URL schemes
**Navigation Stack:**
```swift
enum Route: Hashable {
case profile(userId: String)
case settings
case detail(item: Item)
}
struct ContentView: View {
@State private var path = NavigationPath()
var body: some View {
NavigationStack(path: $path) {
HomeView(navigate: navigate)
.navigationDestination(for: Route.self) { route in
switch route {
case .profile(let userId):
ProfileView(userId: userId)
case .settings:
SettingsView()
case .detail(let item):
DetailView(item: item)
}
}
}
}
private func navigate(to route: Route) {
path.append(route)
}
private func popToRoot() {
path.removeLast(path.count)
}
}
```
**Checkpoint:** Build multi-screen navigation flow
---
### Module 4: Lists & Grids (4 hours)
**Topics:**
- List and ForEach
- LazyVStack and LazyVGrid
- Swipe actions and context menus
- Searchable modifier
- Pull-to-refresh
**Grid Layout:**
```swift
struct PhotoGrid: View {
let photos: [Photo]
private let columns = [
GridItem(.adaptive(minimum: 100, maximum: 150), spacing: 8)
]
var body: some View {
ScrollView {
LazyVGrid(columns: columns, spacing: 8) {
ForEach(photos) { photo in
AsyncImage(url: photo.thumbnailURL) { phase in
switch phase {
case .empty:
Rectangle()
.fill(.quaternary)
case .success(let image):
image
.resizable()
.scaledToFill()
case .failure:
Image(systemName: "photo")
@unknown default:
EmptyView()
}
}
.frame(height: 100)
.clipShape(RoundedRectangle(cornerRadius: 8))
}
}
.padding()
}
}
}
```
**Checkpoint:** Build searchable photo grid
---
### Module 5: Animations (4 hours)
**Topics:**
- Implicit animations (.animation)
- Explicit animations (withAnimation)
- Transitions
- matchedGeometryEffect
- Phase animator (iOS 17+)
**Animation Examples:**
```swift
// Implicit animation
struct ExpandableCard: View {
@State private var isExpanded = false
var body: some View {
VStack {
Text("Title")
.font(.headline)
if isExpanded {
Text("Detailed content here...")
.transition(.opacity.combined(with: .move(edge: .top)))
}
}
.frame(maxWidth: .infinity)
.padding()
.background(.background)
.clipShape(RoundedRectangle(cornerRadius: 12))
.onTapGesture {
withAnimation(.spring(response: 0.4, dampingFraction: 0.8)) {
isExpanded.toggle()
}
}
}
}
// Matched geometry effect
struct CardTransition: View {
@Namespace private var animation
@State private var selectedCard: Card?
var body: some View {
ZStack {
if let card = selectedCard {
DetailView(card: card)
.matchedGeometryEffect(id: card.id, in: animation)
.onTapGesture { selectedCard = nil }
} else {
LazyVGrid(columns: columns) {
ForEach(cards) { card in
CardView(card: card)
.matchedGeometryEffect(id: card.id, in: animation)
.onTapGesture { selectedCard = card }
}
}
}
}
.animation(.spring(response: 0.5), value: selectedCard)
}
}
```
**Checkpoint:** Create hero animation transition
---
### Module 6: Custom Modifiers & Styles (3 hours)
**Topics:**
- ViewModifier protocol
- ButtonStyle, LabelStyle
- Custom environment values
- Preference keys
- View extensions
**Custom Modifier:**
```swift
struct CardStyle: ViewModifier {
let isHighlighted: Bool
func body(content: Content) -> some View {
content
.padding()
.background(.background)
.clipShape(RoundedRectangle(cornerRadius: 12))
.shadow(
color: isHighlighted ? .aRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.