CtrlK
BlogDocsLog inGet started
Tessl Logo

guide-swiftui-ui-patterns

Best practices and example-driven guidance for building SwiftUI views and components, including navigation hierarchies, custom view modifiers, and responsive layouts with stacks and grids. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens with VStack/HStack, managing @State or @Binding, building declarative iOS interfaces, or needing component-specific patterns and examples.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-architected guide skill: lean, actionable, with a validated multi-step workflow and clean one-level-deep progressive disclosure into a rich references bundle. The only minor weakness is the absence of inline copy-paste code examples, which is appropriately deferred to reference files.

DimensionReasoningScore

Conciseness

Lean and efficient — it never explains concepts Claude already knows (no 'what SwiftUI is' preamble) and every line is a rule, a decision table, or a signaled reference; each token earns its place.

5 / 5

Actionability

Concrete guidance throughout — specific APIs/modifiers, a scenario-to-pattern ownership table, a concrete command (`rg "TabView\"`), and rules like 'prefer `.sheet(item:)` over `.sheet(isPresented:)`' — but inline copy-paste code examples are deferred to references, leaving a minor gap.

4 / 5

Workflow Clarity

The 'Workflow for a new SwiftUI view' is a clear 6-step sequence with explicit validation checkpoints ('Build and verify no compiler errors before proceeding') and a build-fail feedback loop ('read the error message carefully, fix... then rebuild before proceeding').

5 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to one-level-deep references; every referenced file (components-index, scroll-reveal, app-wiring, async-state, navigationstack, sheets, deeplinks, previews, performance) exists and is well-signaled with a Cross-cutting references index for easy navigation.

5 / 5

Total

19

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states both the skill's purpose and a broad set of natural, API-specific trigger phrases. It is concise yet comprehensive, with minimal conflict risk against other skills.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — 'building SwiftUI views and components', 'navigation hierarchies, custom view modifiers, and responsive layouts with stacks and grids' — but is topic-oriented rather than a fully comprehensive action list, so it sits just below the top anchor.

4 / 5

Completeness

Explicitly 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...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrasings a SwiftUI developer would actually say — 'creating or refactoring SwiftUI UI', 'designing tab architecture with TabView', 'composing screens with VStack/HStack', 'managing @State or @Binding' — with concrete API names giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

Clear SwiftUI UI-pattern niche with API-specific triggers (TabView, VStack/HStack, @State/@Binding) making it highly distinct and unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Prisma-Labs-Dev/apple-skills
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.