Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Swift Architecture Skill
Agent Skill for Swift architecture design and implementation patterns, with architecture-specific playbooks and review checklists. Use when designing new fea...
skill openclawclawhub Free
Agent Skill for Swift architecture design and implementation patterns, with architecture-specific playbooks and review checklists. Use when designing new fea...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/clean-architecture.md, references/mvi.md, references/mvvm.md, references/reactive.md, references/selection-guide.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.3.1
Provenance
- Publisher
- efremidze
- Source page
- View original listing
- Canonical URL
- Open canonical page
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.
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- SKILL.md
- references/clean-architecture.md
- references/mvi.md
- references/mvvm.md
- references/reactive.md
- references/selection-guide.md