ClawHub

Swiftui View Refactor

v1.0.0

Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.

⭐ 6· 2.7k·8 current·8 all-time
byPeter Steinberger@steipete
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill's name/description (SwiftUI view refactor) matches the SKILL.md content: style and refactor guidelines for SwiftUI views. It requests no binaries, env vars, or installs that would be unrelated to refactoring Swift source.
✓
Instruction Scope
SKILL.md contains only coding guidelines, examples, and a workflow for refactoring SwiftUI views. It does not instruct the agent to read system files, access credentials, or transmit code to external endpoints. Note: as an instruction-only skill, actual file access depends on what the agent is given at invocation — the skill itself doesn't expand scope.
✓
Install Mechanism
No install spec or code files are included. Nothing is written to disk or downloaded by the skill.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths — proportional to a rules-and-style refactor helper.
✓
Persistence & Privilege
always is false and the skill has no install or persistence steps. disable-model-invocation is false (normal platform default) but there are no other elevated privileges or cross-skill configuration changes requested.
Assessment
This skill appears coherent and low-risk: it only provides refactor rules for SwiftUI code and asks for no credentials or installs. Before applying automated refactors, review diffs or run them in a branch/PR to confirm behavior is unchanged. Don’t include secrets or private credentials in code you paste to any skill. If you’re concerned about an unknown source, prefer manual review or only use the guidelines as a checklist rather than allowing automated edits. If you want to prevent autonomous runs, restrict the skill’s invocation in your agent settings (it is user-invocable and can be allowed/disallowed at install time).

Like a lobster shell, security has layers — review code before you run it.

latestvk973kgyy13sna2kj1vrsdzykkd7ynj97

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments