ios-uikit
UIKit: UIViewController, UITableView/CollectionView, Auto Layout, programmatic UI, UIHostingController bridge
What this skill does
# ios-uikit
## Purpose
This skill equips the AI to assist in iOS app development using UIKit, focusing on building and managing user interfaces with UIViewController, UITableView/CollectionView, Auto Layout, programmatic UI creation, and bridging to SwiftUI via UIHostingController.
## When to Use
Use this skill for iOS projects needing custom views, lists, or layouts without storyboards; ideal for programmatic UI in Swift apps, integrating UIKit with SwiftUI, or handling dynamic content in UITableView; avoid if using SwiftUI exclusively or for non-iOS platforms.
## Key Capabilities
- Manage UIViewController lifecycle: Implement viewDidLoad, viewWillAppear for setup and updates.
- Handle UITableView/CollectionView: Set up data sources, delegates, and cell reuse for efficient list rendering.
- Apply Auto Layout programmatically: Use NSLayoutConstraint to define layouts dynamically, ensuring adaptability to device sizes.
- Create programmatic UI: Build views using UIView subclasses and add subviews via code, bypassing Interface Builder.
- Bridge to SwiftUI: Use UIHostingController to embed SwiftUI views in UIKit apps for mixed architecture support.
## Usage Patterns
To create a UIViewController subclass, define a new class inheriting from UIViewController and override key methods; for example, in a new file, write:
```swift
import UIKit
class MyViewController: UIViewController {
override func viewDidLoad() {
super.viewDidLoad()
view.backgroundColor = .white
}
}
```
For UITableView, implement UITableViewDataSource: Set the data source, define numberOfRowsInSection, and cellForRowAt; ensure to register cell classes like this:
```swift
let tableView = UITableView(frame: view.bounds)
tableView.dataSource = self
tableView.register(UITableViewCell.self, forCellReuseIdentifier: "Cell")
```
When using Auto Layout, add constraints programmatically: Use anchors for positioning, e.g., pin a button to the center:
```swift
let button = UIButton()
view.addSubview(button)
button.centerXAnchor.constraint(equalTo: view.centerXAnchor).isActive = true
```
For UIHostingController bridge, embed a SwiftUI view: Create an instance and set it as the root view controller:
```swift
let hostingController = UIHostingController(rootView: MySwiftUIView())
present(hostingController, animated: true)
```
Always use weak references in delegates to avoid retain cycles, and test on different devices for layout responsiveness.
## Common Commands/API
Key APIs include UIViewController methods like viewDidLoad() for initial setup; for UITableView, use tableView.reloadData() to refresh content. To add Auto Layout constraints, employ NSLayoutConstraint.activate() with an array. Example CLI for building in Xcode: `xcodebuild -scheme MyApp -configuration Debug`. For programmatic UI, use UIView.addSubview() and set frames or constraints. Config format for Info.plist might include UIRequiredDeviceCapabilities for device checks. Auth isn't directly required, but if integrating with services, use env vars like `$API_KEY` in build scripts. Specific pattern: Export as `export API_KEY=your_key` before running `xcodebuild`. Common endpoints aren't applicable here, but for network calls in UIKit, use URLSession with delegates. Code snippet for basic URLSession:
```swift
let session = URLSession.shared
let task = session.dataTask(with: URL(string: "https://example.com")!) { data, response, error in
// Handle response
}
task.resume()
```
For error-free Auto Layout, always call layoutIfNeeded() after updates.
## Integration Notes
Integrate this skill by importing UIKit in Swift files; for SwiftUI bridges, ensure SwiftUI is also imported. When combining with other frameworks, use UIHostingController to wrap SwiftUI views and add as child view controllers. For config, set up in AppDelegate or SceneDelegate, e.g., in application(_:didFinishLaunchingWithOptions:), instantiate and present view controllers. If using pods, add via Podfile: `pod 'SomeUIKitLib'` and run `pod install`. Test integrations in a simulator with `xcrun simctl boot "iPhone 14"` to launch devices. For env vars, reference like `let key = ProcessInfo.processInfo.environment["API_KEY"]` in code. Ensure all views are added to the view hierarchy before applying constraints.
## Error Handling
Handle common errors like Auto Layout conflicts by using visual format language or anchors correctly; debug with Xcode's Debug View Hierarchy. For UITableView, catch data source errors by implementing didSelectRowAt and checking indices. Use try-catch for runtime issues, e.g., in URLSession callbacks, check for errors:
```swift
if let error = error {
print("Error: \(error.localizedDescription)")
return
}
```
For UIViewController, override didReceiveMemoryWarning to release resources. Log errors with os_log or print for debugging, and use guard statements for nil checks in delegates.
## Graph Relationships
- Related to cluster: mobile (e.g., shares tags with android-jetpack for cross-platform UI patterns).
- Connected via tags: uikit (links to swiftui for bridging), ios (connects to xcode-build for development workflows), viewcontroller (relates to navigation-stack for app flow), autolayout (ties to responsive-design for adaptive UIs).
Related 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.