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.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill swiftui-ui-patterns86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 92%
↑ 1.37xAgent success when using this skill
Validation for skill structure
Discovery
75%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 solid description that clearly communicates both purpose and trigger conditions. The explicit 'Use when...' clause with multiple scenarios is a strength. However, it could benefit from more specific concrete actions and additional natural trigger terms that users commonly use when working with SwiftUI.
Suggestions
Add more specific concrete actions like 'create navigation hierarchies', 'implement custom view modifiers', 'build responsive layouts with stacks and grids'
Include additional natural trigger terms users might say: '@State', '@Binding', 'VStack', 'HStack', 'iOS interface', 'declarative UI'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SwiftUI) and mentions some actions like 'building views and components', 'creating or refactoring UI', 'designing tab architecture', but lacks concrete specific actions like 'create navigation stacks', 'implement custom modifiers', or 'build list views'. | 2 / 3 |
Completeness | Clearly answers both what ('Best practices and example-driven guidance for building SwiftUI views and components') and when ('Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns'). | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'SwiftUI', 'TabView', 'views', 'components', 'UI', but misses common variations users might say such as 'iOS UI', 'Apple UI framework', '@State', '@Binding', 'VStack', 'HStack', or file extensions like '.swift'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on SwiftUI specifically, with mentions of TabView and component patterns, creates a clear niche that is unlikely to conflict with general iOS development skills or other UI framework skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured SwiftUI skill with excellent conciseness and actionability. The code examples are executable and the progressive disclosure to component references is well-organized. The main weakness is the workflow section which could benefit from more explicit validation steps and error recovery guidance.
Suggestions
Add explicit validation checkpoints to the 'Workflow for a new SwiftUI view' section, such as 'Build and verify no compiler errors before proceeding' after step 3
Include guidance on what to check during the build validation step and how to handle common SwiftUI compilation errors
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with SwiftUI. No unnecessary explanations of basic concepts; every section provides actionable guidance without padding. | 3 / 3 |
Actionability | Provides concrete, executable Swift code examples for sheet patterns, clear step-by-step workflows, and specific commands like `rg "TabView\("` for discovery. Code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The 'Workflow for a new SwiftUI view' section lists clear steps but lacks explicit validation checkpoints. Step 6 mentions 'validate with a build' but doesn't specify what to check or how to handle failures. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear navigation to external references (`references/components-index.md`, `references/app-scaffolding-wiring.md`). Content is appropriately split with one-level-deep references clearly signaled. | 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.