agentleFS
lingyiredlingyired/status-trio/.agents/skills/swiftui-pro/SKILL.md

swiftui-pro

Skill1.8k starsChanged 14 days agoApache-2.0View on GitHub

Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.

18 other projects use a version of this, 16 of them edited.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 2 mentionsOct 2026: 0 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the lingyired/status-trio repository that our weekly crawl found: only 3 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Used with

Projects with it also use swift-concurrency-pro, swift-architecture-skill and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • twostrawsSkill

    swift-concurrency-pro

    Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.

    Also in 8 projects that use this

  • molayabSkill

    swift-architecture-skill

    Swift architecture patterns and playbooks for MVVM, TCA, Clean Architecture, and more.

    Also in 4 projects that use this

  • twostrawsSkill

    swiftdata-pro

    Writes, reviews, and improves SwiftData code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use SwiftData.

    Also in 4 projects that use this

  • Erikote04Skill

    swift-api-design-guidelines-skill

    Write, review, or improve Swift APIs using Swift API Design Guidelines for naming, argument labels, documentation comments, terminology, and general conventions. Use when designing new APIs, refactoring existing interfaces, or reviewing API clarity and fluency.

    Also in 3 projects that use this

  • malpernSkill

    asc-xcode-build

    Build, archive, export, and manage Xcode version/build numbers with asc and xcodebuild before uploading to App Store Connect. Use when you need to create an IPA or PKG for upload.

    Also in 4 projects that use this

  • malpernSkill

    asc-cli-usage

    Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.

    Also in 4 projects that use this

  • +3 more from malpern

The file

We split this skill into the rules it gives an agent

11 rules. 3 are common, 0 are distinctive, and 8 are very specific to this project.

  • 3

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for deprecated API using references/api.md.

    line 16
  2. Very specific:

    Check that views, modifiers, and animations have been written optimally using references/views.md.

    line 17
  3. Very specific:

    Ensure navigation is updated and performant using references/navigation.md.

    line 19
  4. Very specific:

    Ensure the code uses designs that are accessible and compliant with Apple's Human Interface Guidelines using references/design.md.

    line 20
  5. Very specific:

    Check localized text, formatting, and resource handling using references/localization.md.

    line 23
  6. Very specific:

    Ensure the code is able to run efficiently using references/performance.md.

    line 24
  7. Common:

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

    line 28
  8. Very specific:

    Keep references/performance-plus.md out of routine reviews.

    line 30
  9. Common:

    Do not introduce third-party frameworks without asking first.

    line 41
  10. Common:

    Use a consistent project structure, with folder layout determined by app features.

    line 43
  11. Very specific:

    Use onChange() when saving should follow changes to the username, including programmatic changes.

    line 98

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

ContentView.swift

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

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

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

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

// 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().

// Before
TextField("Username", text: Binding(
    get: { model.username },
    set: { newValue in model.username = newValue; 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.