swiftui-pro
Skill52 starsChanged 49 days agoMITView on GitHub
Write and review Bloom macOS SwiftUI views for data flow, accessibility, API correctness and measured performance.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- lingyired/status-triotheir own version, first seen Nov 8, 2026
- tornikegomareli/Skillstheir own version, first seen Nov 8, 2026
- kelvinkosbab/KozBontheir own version, first seen Nov 6, 2026
- molayab/swift-cli-managertheir own version, first seen Nov 1, 2026
- VelimirMueller/claude-skillstheir own version, first seen Nov 1, 2026
- VelimirMueller/ai-development-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use swift-architecture-skill, swiftdata-pro 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.
molayabSkillswift-architecture-skill
Swift architecture patterns and playbooks for MVVM, TCA, Clean Architecture, and more.
Also in 4 projects that use this
twostrawsSkillswiftdata-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
Erikote04Skillswift-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
malpernSkillasc-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
malpernSkillasc-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
OpenAISkillswiftui-ui-patterns
Build and refactor SwiftUI UI with component patterns and examples. Use when shaping navigation, state, layouts, controls, or screen composition.
Also in 5 projects that use this
- +3 more from malpern
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- twostraws/SwiftUI-Agent-Skill★ 6.4ksame name
- lingyired/status-trio★ 1.8ksame name
- kingsidharth/skills★ 17same name
- ingpoc/SKILLS★ 9same name
- 199-biotechnologies/swiftui-claude-skills★ 7same name
- VelimirMueller/ai-development-skills★ 7same name
- VelimirMueller/claude-skills★ 7same name
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificer★ 6same name
- kelvinkosbab/KozBon★ 5same name
- deonmenezes/mobile-app-skill★ 4same name
8 more not listed
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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bloom-dev-buildSkill
- bloom-releaseSkill
- swift-concurrency-proSkill
- swift-testing-proSkill
The file
Files
SwiftUI in Bloom
Bloom targets macOS 26 and Swift 6.2, as declared in Package.swift. Follow CLAUDE.md for
architecture and file organisation. AppKit integration is intentional; do not apply iOS-only
rules or replace working bridges simply because a SwiftUI API exists.
For a review, report actionable defects with file locations and their effects. For an edit, make the requested change. Avoid sweeping API migrations, fixed review templates and stylistic findings without a concrete benefit.
Load only the references relevant to the code:
- Data: state ownership, observation and bindings.
- Views: composition, actions, previews and animation.
- API: API migrations and platform availability.
- Navigation: navigation state, sheets and dialogs.
- Accessibility: labels, keyboard access, contrast and motion.
- Design: Bloom's design system and native Mac layout.
- Performance: identity, observation boundaries and expensive work.
- Swift: language and Foundation choices affecting UI code.
- Hygiene: project validation and handling sensitive data.
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.

