How do I install the Build Swiftui Interface skill?

Run npx skillmds add thedixitjain/build-swiftui-interface in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Build Swiftui Interface safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build Swiftui Interface?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build Swiftui Interface free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Build Swiftui Interface?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build Swiftui Interface by thedixitjain

Name: Build Swiftui Interface
Rating: 4.2 (5 reviews)
Author: thedixitjain

File contents

Build SwiftUI Interface

Use Memi to establish the Apple-platform contract before editing source. Pair this skill with OpenAI's build-ios-apps plugin skills when they are installed and the task needs simulator, profiling, App Intents, or detailed framework guidance.

Compact preflight

npx -y @memi-design/cli@2.6.2 ios brief --platform ios --intent "<task>" --detail compact --json

Inspect the actual project next: deployment target, Swift language mode, shared schemes, local components, assets, navigation, state ownership, test targets, and nearby implementation patterns.

File contract

Preview every generated byte before writing:

npx -y @memi-design/cli@2.6.2 ios scaffold FeatureName \
  --kind screen \
  --module AppModule \
  --output-root Sources \
  --tests-root Tests \
  --json

Use --write only after the paths and source match the repository. Memi writes a spec, SwiftUI view, preview, screen model when needed, and Swift Testing file. It does not mutate .xcodeproj or .xcworkspace, and it refuses silent overwrites.

Implementation rules

Reuse local SwiftUI components and semantic assets before adding primitives.
Keep state ownership narrow; keep I/O and expensive work out of body.
Define loading, empty, populated, error, Dynamic Type, VoiceOver, reduced-motion, and dark-appearance states.
Gate newer APIs. Liquid Glass requires an iOS 26+ branch and a behaviorally equivalent fallback.
Treat June 2026 APIs by their documented availability; do not invent an iOS version label.
Preserve the existing architecture and project-generation workflow.

Verification receipt

Run the repository's canonical commands. When none exist, discover shared schemes and explicit destinations with xcodebuild -list -json and xcrun simctl list devices available, then build and test the smallest target.

Report exact commands, files, deployment assumptions, simulator flow, accessibility states, and anything not executed. A source review is not simulator proof, and a simulator build is not signing or App Store proof.

Source: hashgraph-online/awesome-codex-plugins → plugins/sarveshsea/memi/skills/build-swiftui-interface/SKILL.md

---name: build-swiftui-interfacedescription: Use when a coding agent must design, scaffold, implement, or verify an iOS or macOS SwiftUI interface with Apple-platform state, accessibility, availability, testing, and Xcode evidence.---# Build SwiftUI InterfaceUse Memi to establish the Apple-platform contract before editing source. Pair this skill with OpenAI's `build-ios-apps` plugin skills when they are installed and the task needs simulator, profiling, App Intents, or detailed framework guidance.## Compact preflight```bashnpx -y @memi-design/cli@2.6.2 ios brief --platform ios --intent "<task>" --detail compact --json```Inspect the actual project next: deployment target, Swift language mode, shared schemes, local components, assets, navigation, state ownership, test targets, and nearby implementation patterns.## File contractPreview every generated byte before writing:```bashnpx -y @memi-design/cli@2.6.2 ios scaffold FeatureName \ --kind screen \ --module AppModule \ --output-root Sources \ --tests-root Tests \ --json```Use `--write` only after the paths and source match the repository. Memi writes a spec, SwiftUI view, preview, screen model when needed, and Swift Testing file. It does not mutate `.xcodeproj` or `.xcworkspace`, and it refuses silent overwrites.## Implementation rules1. Reuse local SwiftUI components and semantic assets before adding primitives.2. Keep state ownership narrow; keep I/O and expensive work out of `body`.3. Define loading, empty, populated, error, Dynamic Type, VoiceOver, reduced-motion, and dark-appearance states.4. Gate newer APIs. Liquid Glass requires an iOS 26+ branch and a behaviorally equivalent fallback.5. Treat June 2026 APIs by their documented availability; do not invent an iOS version label.6. Preserve the existing architecture and project-generation workflow.## Verification receiptRun the repository's canonical commands. When none exist, discover shared schemes and explicit destinations with `xcodebuild -list -json` and `xcrun simctl list devices available`, then build and test the smallest target.Report exact commands, files, deployment assumptions, simulator flow, accessibility states, and anything not executed. A source review is not simulator proof, and a simulator build is not signing or App Store proof.---**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/sarveshsea/memi/skills/build-swiftui-interface/SKILL.md`

Frequently asked questions