Agent skill

Swiftui Pro

by twostraws in twostraws/SwiftUI-Agent-Skill

Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance.

MITAuto-check passedMobile

Install Swiftui Pro

skills CLI
$ npx skills add twostraws/SwiftUI-Agent-Skill --skill swiftui-pro -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install twostraws/SwiftUI-Agent-Skill swiftui-pro --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/twostraws/SwiftUI-Agent-Skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/swiftui-pro .claude/skills/swiftui-pro && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
swiftui-pro
GitHub stars
5.2k
Used in
2 other repos
Token cost
~1.5k tokens
SKILL.md length
678 words
Files
18 (incl. references, assets)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance.

  • Works in 11 steps: Check for deprecated API using… → Check that views, modifiers, and… → Validate that data flow is configured… → …
  • Reviewing SwiftUI projects
  • SKILL.md covers Core Instructions, Output Format and References
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Swiftui Pro is an agent skill from twostraws/SwiftUI-Agent-Skill. Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 21 other files, including reference files and assets (for example `.claude-plugin/plugin.json`, `agents/openai.yaml` and `references/accessibility.md`).

It sits in Mobile, covering iOS development. It works with SwiftUI. The repository describes itself as: SwiftUI agent skill for Claude Code, Codex, and other AI tools. The licence is MIT.

When your agent uses it

  • Reviewing SwiftUI projects
  • Tasks that involve iOS development

Example prompts

  • “/swiftui-pro”

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Check for deprecated API using references/api.md.
  2. Check that views, modifiers, and animations have been written optimally using references/views.md.
  3. Validate that data flow is configured correctly using references/data.md.
  4. Ensure navigation is updated and performant using references/navigation.md.
  5. Ensure the code uses designs that are accessible and compliant with Apple's Human Interface Guidelines using references/design.md.
  6. Review layout behavior as windows resize, including iPad multitasking and folding iPhone Duo, using references/resizability.md.
  7. Validate accessibility compliance including Dynamic Type, VoiceOver, and Reduce Motion using references/accessibility.md.
  8. Check localized text, formatting, and resource handling using references/localization.md.
  9. Ensure the code is able to run efficiently using references/performance.md.
  10. Quick validation of Swift code using references/swift.md.
  11. Final code hygiene check using references/hygiene.md.

What it can do on your machine

Read from SKILL.md and the folder at commit f980071. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are swift).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Swiftui Pro loads about 1.5k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 678 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from twostraws/SwiftUI-Agent-Skill at commit f980071, republished under its MIT licence (© twostraws). 678 words, ~1,498 tokens.

Download SKILL.mdSave it as .claude/skills/swiftui-pro/SKILL.md (or your agent's skills folder). This skill also uses 17 other files; get the full folder from GitHub.
name
swiftui-pro
description
Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.
license
MIT
metadata.author
Paul Hudson
metadata.version
2.0.0

Review Swift and SwiftUI code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems – do not nitpick or invent issues.

Include deprecated API in review findings. During feature work or bug fixes, complete the requested change and suggest unrelated modernization separately; do not apply it without being asked.

Review process:

  1. Check for deprecated API using references/api.md.
  2. Check that views, modifiers, and animations have been written optimally using references/views.md.
  3. Validate that data flow is configured correctly using references/data.md.
  4. Ensure navigation is updated and performant using references/navigation.md.
  5. Ensure the code uses designs that are accessible and compliant with Apple's Human Interface Guidelines using references/design.md.
  6. Review layout behavior as windows resize, including iPad multitasking and folding iPhone Duo, using references/resizability.md.
  7. Validate accessibility compliance including Dynamic Type, VoiceOver, and Reduce Motion using references/accessibility.md.
  8. Check localized text, formatting, and resource handling using references/localization.md.
  9. Ensure the code is able to run efficiently using references/performance.md.
  10. Quick validation of Swift code using references/swift.md.
  11. Final code hygiene check using references/hygiene.md.

If doing a partial review, load only the relevant reference files.

Keep references/performance-plus.md out of routine reviews. Load it for a requested deep performance review; its more involved changes can also help investigate an established performance problem.

Core Instructions

  • iOS 27 exists, and is the default deployment target for new apps.
  • Xcode 27.1 and the corresponding 27.1 platform releases are available. Do not dismiss their APIs as speculative.
  • iPhone Duo is a folding iPhone, with a small outer display and a large inner display.
  • Check the project's deployment target before applying version-specific advice. Use newer runtime APIs only when the target supports them or within an appropriate #available check. Keep the existing target unchanged. Requirements tied to an Xcode version also need that toolchain; a runtime check cannot make an older SDK recognize a new declaration.
  • Target Swift 6.4 or later, using modern Swift concurrency.
  • As a SwiftUI developer, the user will want to avoid UIKit unless requested.
  • Do not introduce third-party frameworks without asking first.
  • Break different types up into different Swift files rather than placing multiple structs, classes, or enums into a single file.
  • Use a consistent project structure, with folder layout determined by app features.

Output Format

Organize findings by file. For each issue:

  1. State the file and relevant line(s).
  2. Name the rule being violated (e.g., "Use foregroundStyle() instead of foregroundColor()").
  3. Show a brief before/after code fix.

Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.

Example output:

Show full SKILL.md (248 more words)Show less
ContentView.swift

Line 12: Use foregroundStyle() instead of foregroundColor().

swift
// Before
Text("Hello").foregroundColor(.red)

// After
Text("Hello").foregroundStyle(.red)

Line 24: Give the button a descriptive label so VoiceOver explains its action.

swift
// Before
Button(action: addUser) {
    Image(systemName: "plus")
}

// After
Button("Add User", systemImage: "plus", action: addUser)

Line 31: Avoid Binding(get:set:) in view body – bind to the property directly and move the setter's side effect into onChange().

swift
// Before
TextField("Username", text: Binding(
    get: { model.username },
    set: { model.username = $0; model.save() }
))

// After
TextField("Username", text: $model.username)
    .onChange(of: model.username) {
        model.save()
    }

Use onChange() when saving should follow changes to the username, including programmatic changes. Equal-value assignments will not trigger a save.

Summary
  1. Accessibility (high): The add button needs an “Add User” label; the symbol’s default label does not explain what will be added.
  2. Deprecated API (medium): foregroundColor() on line 12 should be foregroundStyle().
  3. Data flow (medium): The manual binding on line 31 is fragile and harder to maintain.

End of example.

References

  • references/accessibility.md - Dynamic Type, VoiceOver, Reduce Motion, and other accessibility requirements.
  • references/api.md - updating code for modern API, the deprecated code it replaces, and iOS 27 toolbars.
  • references/design.md - guidance for building accessible apps that meet Apple's Human Interface Guidelines.
  • references/hygiene.md - making code compile cleanly and be maintainable in the long term.
  • references/localization.md - localizable text, resource bundles, and locale-aware presentation.
  • references/navigation.md - navigation using NavigationStack/NavigationSplitView, plus alerts, confirmation dialogs, and sheets.
  • references/performance.md - optimizing SwiftUI code for maximum performance.
  • references/performance-plus.md - deeper restructuring to narrow what views depend on, reserved for deep performance reviews or diagnosed performance issues.
  • references/resizability.md - changing window sizes, adaptive bars, safe areas, and iPhone Duo layouts.
  • references/data.md - data flow, shared state, and property wrappers.
  • references/swift.md - tips on writing modern Swift code, including using Swift Concurrency effectively.
  • references/views.md - view structure, composition, animation, reordering, and swipe actions.

© twostraws, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 17 other files (references, assets) in swiftui-pro of twostraws/SwiftUI-Agent-Skill.

  • SKILL.md
  • .claude-plugin/plugin.json
  • agents/openai.yaml
  • assets/swiftui-pro-icon.png
  • assets/swiftui-pro-icon.svg
  • references/accessibility.md
  • references/api.md
  • references/data.md
  • references/design.md
  • references/hygiene.md
  • references/localization.md
  • references/navigation.md
  • references/performance-plus.md
  • references/performance.md
  • references/resizability.md
  • references/swift.md
  • references/views.md
  • … and 1 more

Open the folder on GitHubat commit f980071

Used in 2 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in twostraws/SwiftUI-Agent-Skill, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Swiftui Pro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Swiftui Pro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Swiftui Pro this skilltwostraws/SwiftUI-Agent-Skill5.2k2 repos~1.5kAutomated safety check: PassMIT
Swiftui UI PatternsAFK-surf/OpenBridge4304 repos~887Automated safety check: PassMIT
Swiftui Performance Auditharperreed/dotfiles3348 repos~1.4kAutomated safety check: PassNone
Hig Project Contextraintree-technology/hig-doctor1435 repos~1.2kAutomated safety check: PassMIT
Hig Components Contentraintree-technology/hig-doctor1435 repos~1.3kAutomated safety check: PassMIT
Chunuiliseami/ChunUI531—~642Automated safety check: PassMIT

Similar skills

  • Swiftui UI Patterns

    AFK-surf/OpenBridge

    Best practices and example-driven guidance for building SwiftUI views and components.

    430 GitHub starsUsed in 4 repos~887 tokens
    MobileAuto-check passed
  • Swiftui Performance Audit

    harperreed/dotfiles

    Audit and improve SwiftUI runtime performance from code review and architecture.

    334 GitHub starsUsed in 8 repos~1.4k tokens
    MobileAuto-check passed
  • Hig Project Context

    raintree-technology/hig-doctor

    Create or update a shared Apple design context document that other HIG skills use to tailor guidance.

    143 GitHub starsUsed in 5 repos~1.2k tokens
    MobileAuto-check passed
  • Hig Components Content

    raintree-technology/hig-doctor

    Apple Human Interface Guidelines for content display components.

    143 GitHub starsUsed in 5 repos~1.3k tokens
    MobileAuto-check passed
  • Chunui

    liseami/ChunUI

    Build iOS apps with the ChunUI design system (Monochrome texture extracted from the production app Zinner/Chat0IM).

    531 GitHub stars~642 tokensUpdated 15 days ago
    MobileAuto-check passed
  • Logo To Swiftui Draw

    RhuanCruz/swiftui-logo-draw

    Transforma a imagem (PNG) de um logo num Shape do SwiftUI e num componente que desenha o contorno a traço e depois preenche (splash screen, loading, hero).

    159 GitHub stars~1.7k tokensUpdated 1 mo ago
    MobileAuto-check passed

Works with

Categories

Questions about Swiftui Pro

What does Swiftui Pro do?

Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Swiftui Pro is an agent skill from twostraws/SwiftUI-Agent-Skill. Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance.

When should I use Swiftui Pro?

Swiftui Pro fits situations like: reviewing SwiftUI projects; tasks that involve iOS development.

How do I install Swiftui Pro in Claude Code?

Run `npx skills add twostraws/SwiftUI-Agent-Skill --skill swiftui-pro -a claude-code`. Or copy the skill folder (swiftui-pro in twostraws/SwiftUI-Agent-Skill) into .claude/skills/swiftui-pro in your project. Claude Code loads it when a task matches its description.

How do I install Swiftui Pro in Codex?

Run `npx skills add twostraws/SwiftUI-Agent-Skill --skill swiftui-pro -a codex`. Or copy the skill folder (swiftui-pro in twostraws/SwiftUI-Agent-Skill) into .agents/skills/swiftui-pro in your project. Codex loads it when a task matches its description.

Can I use Swiftui Pro in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add twostraws/SwiftUI-Agent-Skill --skill swiftui-pro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swiftui-pro, .gemini/skills/swiftui-pro, .github/skills/swiftui-pro and .opencode/skills/swiftui-pro in your project.

What does Swiftui Pro need to run?

SKILL.md names no scripts, command-line tools or credentials: Swiftui Pro is instructions for the agent only.

Does Swiftui Pro access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Swiftui Pro safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Swiftui Pro use?

Swiftui Pro is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Swiftui Pro use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Swiftui Pro?

Skills that share tags, products or a category with Swiftui Pro: Swiftui UI Patterns (AFK-surf/OpenBridge, 430 stars), Swiftui Performance Audit (harperreed/dotfiles, 334 stars), Hig Project Context (raintree-technology/hig-doctor, 143 stars) and Hig Components Content (raintree-technology/hig-doctor, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Swiftui Pro?

twostraws (a GitHub user) maintains it in twostraws/SwiftUI-Agent-Skill, which has 5,197 GitHub stars. The repository was last updated on October 7, 2026.

Source: twostraws/SwiftUI-Agent-Skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.