| name | swiftui-implementation |
| description | Implement, refactor, or review macOS-first SwiftUI features using modern APIs, maintainable view composition, correct data flow, performance checks, and project validation. |
| license | MIT |
| metadata | {"version":"2.0","provenance":"Adapted from twostraws/swiftui-agent-skill and local template conventions; see NOTICE.md."} |
SwiftUI implementation
Use this skill for any SwiftUI code change. Load only the related domain skills.
Read first
AGENTS.md and the relevant document under docs/.- Neighboring files in the feature.
references/modern-api.md and references/view-composition.md.- Other skills as needed:
- state/dependencies:
../swift-architecture/SKILL.md
- asynchronous work:
../swift-concurrency/SKILL.md
- navigation, sheets, alerts:
../swiftui-navigation/SKILL.md
- accessibility:
../apple-accessibility/SKILL.md
- visual and interaction behaviour:
../apple-design-review/SKILL.md
- typography:
../apple-typography/SKILL.md
- profiling/performance:
../swiftui-performance/SKILL.md
- runtime/layout hardening:
../swiftui-hardening/SKILL.md
- tests:
../swift-testing/SKILL.md
- style/tooling:
../swift-style-tooling/SKILL.md
- package products, targets, and builds:
../apple-project-workflows/SKILL.md
- user-facing text:
../apple-localization/SKILL.md
- permissions, data, files, network, secrets:
../apple-privacy-security/SKILL.md
- distribution implications:
../apple-release/SKILL.md
Implementation workflow
- Define the user outcome, affected macOS versions, and any explicit secondary application target.
- Enumerate loading, populated, empty, search-empty, failure, permission, offline, and cancellation states that apply.
- Identify the state owner, dependency boundary, navigation value, and test seam before writing views.
- Implement the narrowest vertical slice with system components.
- Extract meaningful subviews into feature-owned files; do not create abstractions with only one speculative use.
- Add deterministic tests for pure behaviour and state transitions.
- Review current APIs, view identity, accessibility, macOS interaction, and performance.
- Run the relevant
make validate, make lint, make test, make package-build, and assembled-app checks. Report any command not run.
Baseline policy
- Use Swift 6.2 strict concurrency and current macOS 26 APIs directly; do not add availability fallbacks.
- Prefer pure SwiftUI. Add an AppKit bridge only when SwiftUI lacks the required capability, and isolate it at a named boundary.
- Do not add third-party packages without explicit justification and approval.
- Keep one meaningful type per file and organise by feature.
- Report genuine correctness, accessibility, performance, or maintenance issues; do not invent findings to fill a review.
Review output
Group findings by file. For each issue, give the line or symbol, consequence, applicable rule, and smallest correction. End with a prioritised list and validation status. Skip files without findings.
