Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Productivity
Swiftui Ui Patterns
Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.
skill openclawclawhub Free
Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.
β¬ 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/app-wiring.md, references/components-index.md, references/controls.md, references/deeplinks.md, references/focus.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
- 1.0.2
Provenance
- Publisher
- Dimillian
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Quick start
Choose a track based on your goal:
Existing project
Identify the feature or screen and the primary interaction model (list, detail, editor, settings, tabbed). Find a nearby example in the repo with rg "TabView\(" or similar, then read the closest SwiftUI view. Apply local conventions: prefer SwiftUI-native state, keep state local when possible, and use environment injection for shared dependencies. Choose the relevant component reference from references/components-index.md and follow its guidance. Build the view with small, focused subviews and SwiftUI-native data flow.
New project scaffolding
Start with references/app-scaffolding-wiring.md to wire TabView + NavigationStack + sheets. Add a minimal AppTab and RouterPath based on the provided skeletons. Choose the next component reference based on the UI you need first (TabView, NavigationStack, Sheets). Expand the route and sheet enums as new screens are added.
General rules to follow
Use modern SwiftUI state (@State, @Binding, @Observable, @Environment) and avoid unnecessary view models. Prefer composition; keep views small and focused. Use async/await with .task and explicit loading/error states. Maintain existing legacy patterns only when editing legacy files. Follow the project's formatter and style guide. Sheets: Prefer .sheet(item:) over .sheet(isPresented:) when state represents a selected model. Avoid if let inside a sheet body. Sheets should own their actions and call dismiss() internally instead of forwarding onCancel/onConfirm closures.
Workflow for a new SwiftUI view
Define the view's state and its ownership location. Identify dependencies to inject via @Environment. Sketch the view hierarchy and extract repeated parts into subviews. Implement async loading with .task and explicit state enum if needed. Add accessibility labels or identifiers when the UI is interactive. Validate with a build and update usage callsites if needed.
Component references
Use references/components-index.md as the entry point. Each component reference should include: Intent and best-fit scenarios. Minimal usage pattern with local conventions. Pitfalls and performance notes. Paths to existing examples in the current repo.
Item-driven sheet (preferred)
@State private var selectedItem: Item? .sheet(item: $selectedItem) { item in EditItemSheet(item: item) }
Sheet owns its actions
struct EditItemSheet: View { @Environment(\.dismiss) private var dismiss @Environment(Store.self) private var store let item: Item @State private var isSaving = false var body: some View { VStack { Button(isSaving ? "Savingβ¦" : "Save") { Task { await save() } } } } private func save() async { isSaving = true await store.save(item) dismiss() } }
Adding a new component reference
Create references/<component>.md. Keep it short and actionable; link to concrete files in the current repo. Update references/components-index.md with the new entry.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- SKILL.md
- references/app-wiring.md
- references/components-index.md
- references/controls.md
- references/deeplinks.md
- references/focus.md