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.
Security Analysis
high confidenceThis is an instruction-only guidance skill for SwiftUI patterns; its declared requirements and runtime instructions match its stated purpose and it does not request credentials, install code, or perform unexpected actions.
The name and description (SwiftUI best practices and examples) align with the provided files: SKILL.md plus multiple component reference docs. The skill declares no binaries, no env vars, and no install steps — all proportional for a documentation-style guidance skill.
Runtime instructions are documentation-driven: advice for scaffolding, state management, sheet patterns, and searching the current repo for examples (e.g., 'rg "TabView("'). The instructions ask the agent to inspect repository files for relevant examples, which is coherent with a coding-assistant use case and does not direct reading or exfiltration of unrelated system data or external endpoints.
No install specification or external downloads are present. This is the lowest-risk class (instruction-only) and nothing is written to disk or fetched as part of an install step.
The skill requests no environment variables, credentials, or config paths. All environment-like concepts in the docs are SwiftUI design constructs (e.g., @Environment, Environment objects) and not runtime platform secrets — proportional to the stated purpose.
Flags show always:false and user-invocable:true (defaults). The skill does not request persistent presence or elevated privileges and contains no instructions to modify other skill or system configurations.
Guidance
This skill is documentation-only and appears safe: it contains best-practice guidance and repo-file references for SwiftUI. Before installing, consider: (1) the agent may read files in your project (the docs explicitly advise searching the repo for examples), so only enable it if you’re comfortable with that level of file access; (2) it does not install or request credentials, so there is no network or secret access implied by the package itself; (3) as with any automated assistant, review its suggested code changes before applying them to ensure they match your project conventions and security requirements.
Latest Release
v1.0.2
- Added macOS settings and menu
More by @Dimillian
Published by @Dimillian on ClawHub
