SwiftUI interfaces
Build data-driven views, navigation, forms, lists, adaptive layouts, previews, states, and accessible controls.
Codex Skills for iOS Development give Codex structured instructions for building Swift and SwiftUI features, managing app data and lifecycle, integrating Apple frameworks, testing accessibility, diagnosing performance, and preparing App Store builds. Download the skills for iPhone and iPad work that must respect platform behavior and project-specific deployment settings.
task: complete ios application development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffStrong ios application development work depends on context, explicit decisions, and checks that match the real environment.
These skills give Codex a specialist workflow for ios application development while preserving local conventions, important constraints, and human review.
Build data-driven views, navigation, forms, lists, adaptive layouts, previews, states, and accessible controls.
Define model ownership, observation, dependencies, persistence, concurrency, errors, and boundaries between SwiftUI and UIKit.
Work with notifications, deep links, background tasks, files, networking, privacy permissions, StoreKit, and system services.
Run unit and UI tests, accessibility checks, profiling, device builds, signing checks, and release preparation.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Read targets, deployment versions, packages, entitlements, capabilities, schemes, architecture, and tests.
Identify sources of truth, async work, navigation, persistence, permissions, foreground and background behavior.
Use Swift concurrency, system components, adaptive layout, localization, accessibility, and existing project patterns.
Test key tasks, text sizes, VoiceOver, permissions, poor networks, performance, packaging, and upgrade behavior.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Build modern data-driven iPhone and iPad interfaces with Apple platform conventions.
Maintain view controllers, Auto Layout, delegates, lifecycle behavior, and gradual SwiftUI adoption.
Connect Apple services, packages, persistence, networking, background work, and privacy controls.
Check signing, entitlements, assets, privacy declarations, versions, TestFlight, and App Store requirements.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable ios application development work with a visible process.
Build and maintain native features, tests, integrations, performance, and releases.
Apply consistent architecture, design, accessibility, privacy, and device-testing practices.
Move from prototype to maintainable project structure and release-ready behavior.
Introduce new SwiftUI views without breaking existing lifecycle and navigation.
The skills assist development but do not replace device testing, signing authority, privacy review, App Store policy checks, or release approval.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with the included ios application development guidance, checks, and supporting files.
Use project scope for local rules and versions, or personal scope for a reusable workflow.
Document the tools, audience, standards, source material, constraints, and approval rules for this ios application development work.
Provide the intended outcome, important edge cases, required checks, and expected handoff.
Practical answers about capabilities, limits, setup, and review.
Yes. They follow the framework mix already used in the project and can support incremental integration.
Yes, when the project targets iPadOS. Layout, multitasking, input, navigation, and window behavior must be tested.
Yes. The workflow includes Dynamic Type, VoiceOver, Voice Control, contrast, labels, focus, and real task testing.
Submission requires authorized developer credentials, signing, privacy information, store metadata, and human approval.
The deployment target and Xcode project define the available APIs and compatibility requirements.
Clear context. Purposeful work. Relevant checks. A result others can understand.