How do I install the Swiftui Backports skill?

Run npx skillmds@latest add shaps80/swiftui-backports in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Swiftui Backports safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Swiftui Backports?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Swiftui Backports free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Swiftui Backports?

shaps80 (@shaps80) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Swiftui Backports by shaps80 — Agent Skill

Name: Swiftui Backports
Author: shaps80

Swiftui Backports

Find SwiftUIBackports replacements for SwiftUI APIs unavailable on a project deployment target. Use for Swift/SwiftUI compiler availability errors, old iOS/tvOS/watchOS/macOS targets, or when implementing SwiftUI app features that may benefit from SwiftUIBackports.

shaps80 93f2692 2 files · 32.8 KB Updated Sep 17, 2026

File contents

SwiftUI Backports

When SwiftUI API is newer than the deployment target, check the bundled backport index before hand-rolling compatibility code or raising the target.

Workflow

Confirm the availability need.
- Use this for compiler availability errors, planned use of modern SwiftUI APIs, or user requests to support older OS versions.
- Find deployment target in Package.swift, .xcodeproj/project.pbxproj, .xcconfig, or target settings.
Check whether SwiftUIBackports is available.
- Search for SwiftUIBackports, SwiftBackports, or existing .backport usage.
- If absent, suggest adding https://github.com/shaps80/SwiftUIBackports only when it fits the project. Do not add it unless asked.
Search the index.
- Use rg -i "<api-name>|<related-term>" references/Backports.jsonl first.
- Read only matching JSONL records when possible; the first line is metadata, remaining lines are backport records.
- Match by name first, then by kind and namespace.
- If the project has an installed SwiftUIBackports checkout, you may confirm against its source when uncertain.
Decide native vs backport.
- If target platform is marked unavailable, do not suggest that backport.
- If deployment target is lower than the entry's deprecated version, use or suggest the backport.
- If deployment target is at or above deprecated, prefer native SwiftUI.
Use the discovered API.
- View modifiers: .backport.foo(...)
- Types/views: usually Backport.Foo; use Backport<Any>.Foo if the compiler needs the fully qualified namespace.
- Environment values: use the indexed environment key, such as @Environment(\.backportRequestReview).
If no index match exists, say no backport was found and choose another compatibility path.

Do not implement new SwiftUIBackports APIs from this skill. This is for consuming the library.

Example

sheetContent
    .backport.presentationDetents([.medium, .large])

Backport.LabeledContent("", value: 0)

@Environment(\.backportRequestReview) private var requestReview

---name: swiftui-backportsdescription: Find SwiftUIBackports replacements for SwiftUI APIs unavailable on a project deployment target. Use for Swift/SwiftUI compiler availability errors, old iOS/tvOS/watchOS/macOS targets, or when implementing SwiftUI app features that may benefit from SwiftUIBackports.---# SwiftUI BackportsWhen SwiftUI API is newer than the deployment target, check the bundled backport index before hand-rolling compatibility code or raising the target.## Workflow1. Confirm the availability need. - Use this for compiler availability errors, planned use of modern SwiftUI APIs, or user requests to support older OS versions. - Find deployment target in `Package.swift`, `.xcodeproj/project.pbxproj`, `.xcconfig`, or target settings.2. Check whether `SwiftUIBackports` is available. - Search for `SwiftUIBackports`, `SwiftBackports`, or existing `.backport` usage. - If absent, suggest adding `https://github.com/shaps80/SwiftUIBackports` only when it fits the project. Do not add it unless asked.3. Search the index. - Use `rg -i "<api-name>|<related-term>" references/Backports.jsonl` first. - Read only matching JSONL records when possible; the first line is metadata, remaining lines are backport records. - Match by `name` first, then by `kind` and `namespace`. - If the project has an installed `SwiftUIBackports` checkout, you may confirm against its source when uncertain.4. Decide native vs backport. - If target platform is marked `unavailable`, do not suggest that backport. - If deployment target is lower than the entry's `deprecated` version, use or suggest the backport. - If deployment target is at or above `deprecated`, prefer native SwiftUI.5. Use the discovered API. - View modifiers: `.backport.foo(...)` - Types/views: usually `Backport.Foo`; use `Backport<Any>.Foo` if the compiler needs the fully qualified namespace. - Environment values: use the indexed environment key, such as `@Environment(\.backportRequestReview)`.6. If no index match exists, say no backport was found and choose another compatibility path.Do not implement new SwiftUIBackports APIs from this skill. This is for consuming the library.## Example```swiftsheetContent .backport.presentationDetents([.medium, .large])Backport.LabeledContent("", value: 0)@Environment(\.backportRequestReview) private var requestReview```

Frequently asked questions