# Send Swift Architecture Skill to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "swift-architecture-skill", "name": "Swift Architecture Skill", "source": "tencent", "type": "skill", "category": "AI 智能", "sourceUrl": "https://clawhub.ai/efremidze/swift-architecture-skill", "canonicalUrl": "https://clawhub.ai/efremidze/swift-architecture-skill", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/swift-architecture-skill", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=swift-architecture-skill", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "references/clean-architecture.md", "references/mvi.md", "references/mvvm.md", "references/reactive.md", "references/selection-guide.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/swift-architecture-skill" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/swift-architecture-skill", "downloadUrl": "https://openagent3.xyz/downloads/swift-architecture-skill", "agentUrl": "https://openagent3.xyz/skills/swift-architecture-skill/agent", "manifestUrl": "https://openagent3.xyz/skills/swift-architecture-skill/agent.json", "briefUrl": "https://openagent3.xyz/skills/swift-architecture-skill/agent.md" } } ``` ## Documentation ### Overview Use this skill to pick the best Swift architecture playbook for SwiftUI/UIKit codebases and apply it to the user’s task. ### Step 1: Analyze the Request Context Before selecting an architecture, capture: task type (new feature, refactor, PR review, debugging) UI stack (SwiftUI, UIKit, or mixed) scope (single screen, multi-screen, app-wide) existing conventions to preserve ### Step 2: Select the Architecture If the user explicitly names an architecture, treat it as the initial candidate and run a fit check before committing: validate against UI stack fit (SwiftUI/UIKit/mixed), state complexity, effect orchestration needs, team familiarity, and existing codebase conventions if it fits, proceed with the requested architecture if it mismatches key constraints, explicitly explain the mismatch and recommend the closest-fit alternative from references/selection-guide.md if the user still insists on a mismatched architecture, proceed with a risk-mitigated plan and state the risks up front When no architecture is named, load references/selection-guide.md and infer the best fit from stated constraints (state complexity, team familiarity, testing goals, effect orchestration needs, and framework preferences). Explain the recommendation briefly. Architecture reference mapping: MVVM → references/mvvm.md MVI → references/mvi.md TCA → references/tca.md Clean Architecture → references/clean-architecture.md VIPER → references/viper.md Reactive → references/reactive.md ### Step 3: Analyze Existing Codebase (When Applicable) When code already exists: detect current architecture and DI style note concurrency model (async/await, Combine, GCD, mixed) align recommendations to local conventions ### Step 4: Produce Concrete Deliverables Read the selected architecture reference and convert its guidance into deliverables tailored to the user's request: File and module structure: directory layout with file names specific to the feature State and dependency boundaries: concrete types, protocols, and injection points Async strategy: cancellation, actor isolation, and error paths Testing strategy: what to test, how to stub dependencies, and example test structure Migration path (for refactors): incremental steps to move from current to target architecture UI stack adaptation: where SwiftUI and UIKit guidance should differ for the chosen architecture ### Step 5: Validate with Checklist End with the architecture-specific PR review checklist from the reference file, adapted to the user's feature. ### Output Requirements Keep recommendations scoped to the requested feature or review task. Prefer protocol-based dependency injection and explicit state modeling. Flag anti-patterns found in existing code and provide direct fixes. Include cancellation and error handling in all async flows. For explicit architecture requests, include a short fit result (fit or mismatch) with 1-2 reasons. For mismatch cases, include one closest-fit alternative and why it better matches the stated constraints. When writing code, include only the patterns relevant to the task — do not dump entire playbooks. Treat reference snippets as illustrative by default; add full compile scaffolding only if the user asks for runnable code. Ask only minimum blocking questions; otherwise proceed with explicit assumptions stated up front. When reviewing PRs, use the architecture-specific checklist and call out specific violations with line-level fixes. ## Trust - Source: tencent - Verification: Indexed source record - Publisher: efremidze - Version: 0.3.1 ## Source health - Status: healthy - Source download looks usable. - Yavira can redirect you to the upstream package for this source. - Health scope: source - Reason: direct_download_ok - Checked at: 2026-04-30T16:55:25.780Z - Expires at: 2026-05-07T16:55:25.780Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/swift-architecture-skill) - [Send to Agent page](https://openagent3.xyz/skills/swift-architecture-skill/agent) - [JSON manifest](https://openagent3.xyz/skills/swift-architecture-skill/agent.json) - [Markdown brief](https://openagent3.xyz/skills/swift-architecture-skill/agent.md) - [Download page](https://openagent3.xyz/downloads/swift-architecture-skill)