swiftui
Skill1 starsChanged 16 days agoMITView on GitHub
SwiftUI interface work on Apple platforms. Use when choosing SwiftUI versus UIKit; building, reviewing, or restructuring SwiftUI views, state flow, navigation, presentation, collection interactions, toolbars, remote images, document apps, accessibility semantics, Liquid Glass, or SDK migration fixes; or applying a diagnosed SwiftUI performance fix.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- turkeryildirim/ai-skillstheir own version, first seen Nov 1, 2026
- g-cqd/skillstheir own version, first seen Oct 23, 2026
- caglarbaranbora/Apple-Agent-Kittheir own version, first seen Oct 13, 2026
- FradSer/skillstheir own version, first seen Oct 13, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- 31Carlton7/skillstheir own version, first seen Oct 8, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- Prisma-Labs-Dev/apple-skills★ 336same name
- G1Joshi/Agent-Skills★ 15same name
- FradSer/skills★ 4same name
- moasq/ios-dev-agent★ 4same name
- turkeryildirim/ai-skills★ 4same name
- 31Carlton7/skills★ 2same name
- g-cqd/skills★ 2same name
- caglarbaranbora/Apple-Agent-Kit★ 1same name
- Chaeguevara/Skills★ 0same name
- Fe2-O3/swift-field-guide★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-loginSkill
- animateSkill
- app-intentsSkill
- app-store-connectSkill
- architectSkill
- arenaSkill
- blast-radiusSkill
- codebase-designSkill
- code-qualitySkill
- correctSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- eli5Skill
- engineering-principlesSkill
- gauntlet-loopSkill
- gh-stackSkill
- goal-swarmSkill
- grillingSkill
- grill-with-docsSkill
- handoffSkill
- howSkill
- improve-codebase-architectureSkill
- ios-hapticsSkill
- koubouSkill
- mergeSkill
- orchestrationSkill
- prototypeSkill
- prSkill
- react-best-practicesSkill
- react-doctorSkill
- reframeSkill
- repo-cleanupSkill
- researchSkill
- retroSkill
- review-fix-loopSkill
- reviewSkill
- review-sweepSkill
- seoSkill
- setup-sreestackSkill
- show-dont-tellSkill
- showroomSkill
- snipsnap-do-choresSkill
- snip-snapSkill
- swift-testing-modernizationSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- ui-designSkill
- uikitSkill
- verifySkill
- wayfinderSkill
- web-component-inspirationSkill
- whySkill
- writing-for-agentsSkill
- xcode-security-auditSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Read only the references needed for the task:
- Distinctive: line 54
Prefer native containers and controls for the target platform.
- Distinctive: line 79
After performance diagnosis identifies the bottleneck, use the data-flow and composition guidance here to narrow invalidation or reduce …
“Common” is measured: kept by at least 6 in 10 of the 9 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.
Files
SwiftUI
Shape the interface around SwiftUI's ownership, identity, and environment rather than reproducing an imperative view hierarchy. Preserve the product's existing architecture and deployment targets unless the task changes them.
For an authorized build or fix, implement and test the workflow below. For a plan or review, leave the product unchanged and turn its implementation and test steps into exact proposed changes, findings, and checks.
Workflow
- Inspect the affected scene, views, models, deployment targets, and existing design system. Trace each mutable value to its source of truth and each user action to the code that owns its effect.
- Read only the references needed for the task:
- Model the Domain for state ownership and domain shapes; Boundary Discipline for interface boundaries; and Make Operations Idempotent when effects can overlap, repeat, or outlive their view. Apply these through SwiftUI's state, identity, and lifecycle rules below.
- Choosing SwiftUI or UIKit when the framework
is not fixed or the work could introduce a framework boundary. If UIKit owns
the affected surface, continue with
uikitand end this workflow. For a hybrid, name the boundary and continue here only for the SwiftUI-owned side. - State and data flow for ownership, Observation, bindings, environment values, or editable drafts.
- Composition and identity for view boundaries, collection identity, update scope, or restructuring a large view.
- Navigation and presentation for stacks, split views, routes, sheets, dialogs, or restoration.
- SDK 27 migration when an Xcode 27 build
introduces
@State, result-builder, or preview diagnostics. - Collection interactions for reordering or swipe actions in lists, stacks, grids, or custom layouts.
- Toolbars for overflow, pinned items, visibility priority, or minimization behavior.
- Remote images for
AsyncImageloading, request policy, session choice, or caching. - Document apps for creating or migrating a document-based app, viewer, reader, or writer.
- Materials and Liquid Glass when adopting current platform materials or reviewing custom glass effects.
- Make the source of truth and view identity explicit before changing layout. Give each view only the values, bindings, and actions it needs. Keep durable storage and business rules outside transient view state.
- Prefer native containers and controls for the target platform. Add a UIKit or AppKit bridge at a deliberate boundary when SwiftUI lacks the required behavior; keep lifecycle and ownership on one side of that boundary.
- For interactive components, give immediate feedback and keep loading, empty, disabled, error, and overflow states close to the action or content they describe. Prevent interrupted or repeated async work from letting an older result overwrite the current state. Prefer platform controls and strong defaults over extra options; preserve valid activation and cancellation. When sizing a button, inspect its visible bounds and hit region after styling; compare the hit region, not the label frame, with the platform's button guidance.
- Preserve useful accessibility semantics. Expose the control's name, value, state, and actions, and keep focus and announcements aligned with the task and reading order rather than an incidental view hierarchy. Announce visible async status, validation, and errors when focus does not move and the change would otherwise be missed.
- Build the affected targets and exercise main, edge-state, interruption, and
repeated-input transitions. When behavior or accessibility is in scope,
exercise the supported touch, pointer, keyboard, focus, announcement, and
VoiceOver reading paths. Use
verifyfor visual or interactive acceptance checks. Useanimatefor motion design,ios-hapticsfor iOS tactile feedback,ui-designfor visual hierarchy and token-system work, anddiagnosing-bugswhen a failure or performance regression needs investigation.
After performance diagnosis identifies the bottleneck, use the data-flow and composition guidance here to narrow invalidation or reduce body work without changing behavior.
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
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.

