How do I install the IOS Swiftui MCP skill?

Run npx skillmds@latest add yenhao-huang/ios-swiftui-mcp 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 IOS Swiftui MCP safe to use?

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

Which AI agents work with IOS Swiftui MCP?

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 IOS Swiftui MCP free to use?

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

Who published IOS Swiftui MCP?

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

IOS Swiftui MCP by yenhao-huang — Agent Skill

Name: IOS Swiftui MCP
Author: yenhao-huang

IOS Swiftui MCP

Select and verify MCP tools for Swift, SwiftUI, Xcode, profiling, previews, and Apple documentation, and apply the personal apple_query_any_img photo-search project context. Use for iOS tool selection, SwiftUI development workflows, or the ColNomic and Qdrant iPhone photo-search project.

yenhao-huang Updated Sep 21, 2026

File contents

iOS SwiftUI MCP Guide

Workflow

Read STATE.md; reset it from references/template/STATE.template.md for a new run. Identify whether the request is tool selection or work on ~/Desktop/apple_query_any_img.
For the photo-search project, inspect the live project before assuming its structure, runtime, or current plan. Read references/photo-search-survey.md only when competitive or architecture context is relevant.
For MCP recommendations, verify current repository activity, compatibility, installation method, permissions, and supported Codex client before recommending a tool. Treat the reference list as a dated snapshot.
Prefer an already configured, least-privilege tool that directly supports the requested Apple documentation, build, preview, test, simulator, or profiling action.
Execute or document the selected workflow and verify its observable output, such as build result, screenshot, test report, profiling trace, or retrieved documentation.
Record project path, selected tool, compatibility evidence, operation, and validation in STATE.md.

Rules

Do not assume an MCP server supports Codex because it supports another client.
Do not reuse stale star counts as current popularity evidence.
Do not install or enable an MCP server unless the user requests setup; when setup is requested, document exact rollback and validate the lifecycle.
Preserve the user's existing project layout rather than depending on the excluded project-convention skill.

Output

Return the chosen approach, verified compatibility, commands or actions, result evidence, and any project-specific caveats.

---name: ios-swiftui-mcpdescription: Select and verify MCP tools for Swift, SwiftUI, Xcode, profiling, previews, and Apple documentation, and apply the personal apple_query_any_img photo-search project context. Use for iOS tool selection, SwiftUI development workflows, or the ColNomic and Qdrant iPhone photo-search project.---# iOS SwiftUI MCP Guide## Workflow1. Read `STATE.md`; reset it from `references/template/STATE.template.md` for a new run. Identify whether the request is tool selection or work on `~/Desktop/apple_query_any_img`.2. For the photo-search project, inspect the live project before assuming its structure, runtime, or current plan. Read `references/photo-search-survey.md` only when competitive or architecture context is relevant.3. For MCP recommendations, verify current repository activity, compatibility, installation method, permissions, and supported Codex client before recommending a tool. Treat the reference list as a dated snapshot.4. Prefer an already configured, least-privilege tool that directly supports the requested Apple documentation, build, preview, test, simulator, or profiling action.5. Execute or document the selected workflow and verify its observable output, such as build result, screenshot, test report, profiling trace, or retrieved documentation.6. Record project path, selected tool, compatibility evidence, operation, and validation in `STATE.md`.## Rules- Do not assume an MCP server supports Codex because it supports another client.- Do not reuse stale star counts as current popularity evidence.- Do not install or enable an MCP server unless the user requests setup; when setup is requested, document exact rollback and validate the lifecycle.- Preserve the user's existing project layout rather than depending on the excluded `project-convention` skill.## OutputReturn the chosen approach, verified compatibility, commands or actions,result evidence, and any project-specific caveats.

Frequently asked questions