{
  "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": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/swift-architecture-skill",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=swift-architecture-skill",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "references/clean-architecture.md",
      "references/mvi.md",
      "references/mvvm.md",
      "references/reactive.md",
      "references/selection-guide.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "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."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "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."
        },
        {
          "label": "Upgrade existing",
          "body": "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."
        }
      ]
    },
    "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."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/swift-architecture-skill",
    "agentPageUrl": "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"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "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."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "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."
      },
      {
        "label": "Upgrade existing",
        "body": "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."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Overview",
        "body": "Use this skill to pick the best Swift architecture playbook for SwiftUI/UIKit codebases and apply it to the user’s task."
      },
      {
        "title": "Step 1: Analyze the Request Context",
        "body": "Before selecting an architecture, capture:\n\ntask type (new feature, refactor, PR review, debugging)\nUI stack (SwiftUI, UIKit, or mixed)\nscope (single screen, multi-screen, app-wide)\nexisting conventions to preserve"
      },
      {
        "title": "Step 2: Select the Architecture",
        "body": "If the user explicitly names an architecture, treat it as the initial candidate and run a fit check before committing:\n\nvalidate against UI stack fit (SwiftUI/UIKit/mixed), state complexity, effect orchestration needs, team familiarity, and existing codebase conventions\nif it fits, proceed with the requested architecture\nif it mismatches key constraints, explicitly explain the mismatch and recommend the closest-fit alternative from references/selection-guide.md\nif the user still insists on a mismatched architecture, proceed with a risk-mitigated plan and state the risks up front\n\nWhen 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.\n\nArchitecture reference mapping:\n\nMVVM → references/mvvm.md\nMVI → references/mvi.md\nTCA → references/tca.md\nClean Architecture → references/clean-architecture.md\nVIPER → references/viper.md\nReactive → references/reactive.md"
      },
      {
        "title": "Step 3: Analyze Existing Codebase (When Applicable)",
        "body": "When code already exists:\n\ndetect current architecture and DI style\nnote concurrency model (async/await, Combine, GCD, mixed)\nalign recommendations to local conventions"
      },
      {
        "title": "Step 4: Produce Concrete Deliverables",
        "body": "Read the selected architecture reference and convert its guidance into deliverables tailored to the user's request:\n\nFile and module structure: directory layout with file names specific to the feature\nState and dependency boundaries: concrete types, protocols, and injection points\nAsync strategy: cancellation, actor isolation, and error paths\nTesting strategy: what to test, how to stub dependencies, and example test structure\nMigration path (for refactors): incremental steps to move from current to target architecture\nUI stack adaptation: where SwiftUI and UIKit guidance should differ for the chosen architecture"
      },
      {
        "title": "Step 5: Validate with Checklist",
        "body": "End with the architecture-specific PR review checklist from the reference file, adapted to the user's feature."
      },
      {
        "title": "Output Requirements",
        "body": "Keep recommendations scoped to the requested feature or review task.\nPrefer protocol-based dependency injection and explicit state modeling.\nFlag anti-patterns found in existing code and provide direct fixes.\nInclude cancellation and error handling in all async flows.\nFor explicit architecture requests, include a short fit result (fit or mismatch) with 1-2 reasons.\nFor mismatch cases, include one closest-fit alternative and why it better matches the stated constraints.\nWhen writing code, include only the patterns relevant to the task — do not dump entire playbooks.\nTreat reference snippets as illustrative by default; add full compile scaffolding only if the user asks for runnable code.\nAsk only minimum blocking questions; otherwise proceed with explicit assumptions stated up front.\nWhen reviewing PRs, use the architecture-specific checklist and call out specific violations with line-level fixes."
      }
    ],
    "body": "Swift Architecture Skill\nOverview\n\nUse this skill to pick the best Swift architecture playbook for SwiftUI/UIKit codebases and apply it to the user’s task.\n\nWorkflow\nStep 1: Analyze the Request Context\n\nBefore selecting an architecture, capture:\n\ntask type (new feature, refactor, PR review, debugging)\nUI stack (SwiftUI, UIKit, or mixed)\nscope (single screen, multi-screen, app-wide)\nexisting conventions to preserve\nStep 2: Select the Architecture\n\nIf the user explicitly names an architecture, treat it as the initial candidate and run a fit check before committing:\n\nvalidate against UI stack fit (SwiftUI/UIKit/mixed), state complexity, effect orchestration needs, team familiarity, and existing codebase conventions\nif it fits, proceed with the requested architecture\nif it mismatches key constraints, explicitly explain the mismatch and recommend the closest-fit alternative from references/selection-guide.md\nif the user still insists on a mismatched architecture, proceed with a risk-mitigated plan and state the risks up front\n\nWhen 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.\n\nArchitecture reference mapping:\n\nMVVM → references/mvvm.md\nMVI → references/mvi.md\nTCA → references/tca.md\nClean Architecture → references/clean-architecture.md\nVIPER → references/viper.md\nReactive → references/reactive.md\nStep 3: Analyze Existing Codebase (When Applicable)\n\nWhen code already exists:\n\ndetect current architecture and DI style\nnote concurrency model (async/await, Combine, GCD, mixed)\nalign recommendations to local conventions\nStep 4: Produce Concrete Deliverables\n\nRead the selected architecture reference and convert its guidance into deliverables tailored to the user's request:\n\nFile and module structure: directory layout with file names specific to the feature\nState and dependency boundaries: concrete types, protocols, and injection points\nAsync strategy: cancellation, actor isolation, and error paths\nTesting strategy: what to test, how to stub dependencies, and example test structure\nMigration path (for refactors): incremental steps to move from current to target architecture\nUI stack adaptation: where SwiftUI and UIKit guidance should differ for the chosen architecture\nStep 5: Validate with Checklist\n\nEnd with the architecture-specific PR review checklist from the reference file, adapted to the user's feature.\n\nOutput Requirements\nKeep recommendations scoped to the requested feature or review task.\nPrefer protocol-based dependency injection and explicit state modeling.\nFlag anti-patterns found in existing code and provide direct fixes.\nInclude cancellation and error handling in all async flows.\nFor explicit architecture requests, include a short fit result (fit or mismatch) with 1-2 reasons.\nFor mismatch cases, include one closest-fit alternative and why it better matches the stated constraints.\nWhen writing code, include only the patterns relevant to the task — do not dump entire playbooks.\nTreat reference snippets as illustrative by default; add full compile scaffolding only if the user asks for runnable code.\nAsk only minimum blocking questions; otherwise proceed with explicit assumptions stated up front.\nWhen reviewing PRs, use the architecture-specific checklist and call out specific violations with line-level fixes."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/efremidze/swift-architecture-skill",
    "publisherUrl": "https://clawhub.ai/efremidze/swift-architecture-skill",
    "owner": "efremidze",
    "version": "0.3.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "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"
  }
}