swiftui-patterns

Best practices and example-driven guidance for building native macOS SwiftUI scenes and components, including windows, commands, toolbars, settings, split views, inspectors, menu bar extras, and keyboard-driven workflows. Use when creating or refactoring macOS SwiftUI UI, choosing scene types, wiring menus or settings, or needing desktop-specific component patterns and examples.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/swiftui-patterns/SKILL.md

Quality

Content

71%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.

The content is well-structured and actionable with executable examples, a concrete file layout, a state-ownership table, and properly signaled one-level-deep references that all exist. Its main weakness is redundancy: several rules are restated across General Rules, code examples, and Anti-Patterns, which hurts token efficiency.

Suggestions

Consolidate the repeated sidebar/opaque-background and 30-char menu-bar guidance so each rule appears once (e.g., state it in General Rules and reference it from Anti-Patterns rather than re-explaining).

Tighten the 'Workflow For A New macOS Scene Or View' validation step into an explicit build -> fix -> rebuild loop instead of a 'quick usability pass'.

Add one or two more executable code examples for other common cases (e.g., a Settings scene or commands/menu wiring) to broaden actionability coverage.

Dimension	Reasoning	Score
Conciseness	The body mostly assumes Claude's competence with no elementary SwiftUI explanations, but the same guidance is repeated across sections (e.g., the 30-char menu-bar limit, opaque sidebar backgrounds, single-ContentView, and Window-vs-WindowGroup appear in General Rules, Recommended Pattern code, and Anti-Patterns), so it could be tightened.	3 / 5
Actionability	Provides executable, copy-paste-ready Swift for the sidebar row and split-view background patterns, a concrete state-ownership table, a file/folder structure, and real commands ('git rev-parse --is-inside-work-tree', 'git init'), but examples cover only a couple of common cases rather than the full range.	4 / 5
Workflow Clarity	'Workflow For A New macOS Scene Or View' and the 'Pre-Edit Checklist' give a clear sequenced process with a build/usability validation step, but the validation checkpoint ('quick usability pass') is somewhat soft and lacks an explicit fix-and-retry loop.	4 / 5
Progressive Disclosure	The body is a clear overview with a 'Cross-Cutting References' section that signals six one-level-deep reference files (components-index, windowing, settings, commands-menus, split-inspectors, menu-bar-extra), all of which exist in references/, making navigation easy.	5 / 5
	Total	16 / 20 Passed

Description

83%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.

The description is strong: it clearly states what the skill covers, provides an explicit 'Use when' trigger clause with concrete phrases, and carves a distinct SwiftUI-on-macOS niche. It is slightly soft on action verbs and missing some synonym triggers, keeping specificity and trigger quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete scene/component types ('windows, commands, toolbars, settings, split views, inspectors, menu bar extras, and keyboard-driven workflows') with actionable verbs like 'building', 'creating or refactoring', 'choosing', and 'wiring', but the leading 'best practices and example-driven guidance' framing softens the action list slightly, leaving minor gaps versus fully crisp action verbs.	4 / 5
Completeness	Explicitly answers 'what' (building native macOS SwiftUI scenes and components with a comprehensive enumeration) and 'when' via a concrete 'Use when creating or refactoring macOS SwiftUI UI, choosing scene types, wiring menus or settings, or needing desktop-specific component patterns and examples.' clause.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('macOS SwiftUI UI', 'menus', 'settings', 'scene types', 'toolbars') with good coverage, but lacks some synonyms/common variants and has no file-extension triggers, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	The 'native macOS SwiftUI scenes and components' niche is clearly carved and routes SwiftUI-inexpressible cases to the sibling 'appkit-interop' skill, but the existence of that closely related skill leaves minor overlap risk.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: robinebers/openusage
Path: .agents/skills/swiftui-patterns/SKILL.md
Commit: 2270d5f

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.