swiftui-view-refactor
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.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill swiftui-view-refactor94
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (SwiftUI view refactoring), lists specific capabilities (structure, dependency injection, Observation usage), and provides explicit trigger conditions. The description uses appropriate third-person voice and includes domain-specific terminology that users would naturally use when requesting this type of help.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Refactor and review SwiftUI view files', 'consistent structure', 'dependency injection', 'Observation usage', 'handle view models safely', 'standardize how dependencies and @Observable state are initialized and passed'. | 3 / 3 |
Completeness | Clearly answers both what ('Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage') AND when ('Use when asked to clean up a SwiftUI view's layout/ordering, handle view models safely, or standardize how dependencies and @Observable state are initialized'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'SwiftUI', 'view', 'clean up', 'layout', 'ordering', 'view models', 'dependencies', '@Observable', 'refactor', 'review'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to SwiftUI views with distinct triggers around '@Observable', 'dependency injection', 'view models', and SwiftUI-specific patterns. Unlikely to conflict with general code review or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill for SwiftUI view refactoring with clear structure and executable examples. The workflow is well-sequenced and the progressive disclosure is appropriate. Minor verbosity in explaining patterns Claude likely knows (MV concepts, basic SwiftUI) prevents a perfect conciseness score.
Suggestions
Trim the MV pattern explanation in section 2 - Claude understands these concepts; focus on the specific conventions to apply rather than explaining why MV is preferred
Consolidate the three view extraction examples into one comprehensive example that shows the progression, reducing redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy (e.g., explaining MV patterns that Claude likely knows, multiple similar examples for view extraction). Some sections could be tightened without losing clarity. | 2 / 3 |
Actionability | Provides concrete, executable Swift code examples throughout. The ordering rules are specific, the workflow steps are clear, and examples are copy-paste ready with real SwiftUI patterns. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with explicit ordering. For a refactoring skill, the steps are appropriately ordered (reorder → apply patterns → validate structure → confirm usage → preserve behavior). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, Core Guidelines, Workflow, Notes, Large-view handling). References external file (references/mv-patterns.md) appropriately for deeper rationale. Content is appropriately split for a skill of this scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.