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

92%

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

Quality

Content

85%

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

The body is well-structured, actionable, and uses progressive disclosure effectively with real reference files. Its main weakness is conciseness: several rules (sidebar backgrounds, menu-bar text cap, single-file structure) are repeated across General Rules, pattern sections, and Anti-Patterns.

Suggestions

Consolidate the "avoid opaque custom Color fills on NavigationSplitView sidebars/root panes" guidance so it appears once; cross-reference it from the Anti-Patterns list instead of restating the full rationale three times.

Merge the duplicated 30-character menu-bar-item cap and the Window-vs-WindowGroup launch guidance into a single location rather than repeating them in both General Rules and Anti-Patterns.

Tighten the New App File Structure and Pre-Edit Checklist sections, which overlap on folder/state guidance, into one consolidated scaffold checklist.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient and assumes Claude's competence (no basic SwiftUI explanations), but several guidelines are restated multiple times — the "avoid opaque custom Color fills on sidebars" rule appears in General Rules, the Split-View Background Pattern, and Anti-Patterns, and the 30-char menu-bar cap and single-file anti-pattern each repeat — so it could be tightened.	2 / 3
Actionability	Provides executable Swift code examples (sidebar row pattern, split-view do/don't backgrounds), a concrete file/folder structure, a state-ownership table, and specific commands like `git rev-parse --is-inside-work-tree`, giving copy-paste-ready guidance.	3 / 3
Workflow Clarity	Includes a numbered 7-step "Workflow For A New macOS Scene Or View" with an explicit validation step ("Validate the flow with a build and a quick usability pass") plus a "Pre-Edit Checklist", sequencing the multi-step process with checkpoints.	3 / 3
Progressive Disclosure	SKILL.md is a clear overview with a "Cross-Cutting References" section pointing to six real one-level-deep reference files (verified present in references/), each signaled with its scope and an entry-point index, keeping detail appropriately offloaded.	3 / 3
	Total	11 / 12 Passed

Description

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.

The description is specific, uses third person, and provides an explicit "Use when" trigger covering both what the skill does and when to apply it. Trigger terms are natural and well-distributed, and the niche is clearly distinct.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "building native macOS SwiftUI scenes and components, including windows, commands, toolbars, settings, split views, inspectors, menu bar extras, and keyboard-driven workflows" — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly states what it does (best practices/guidance for building SwiftUI scenes and components) and when to use it via an explicit "Use when creating or refactoring macOS SwiftUI UI, choosing scene types, wiring menus or settings..." clause, answering both what and when.	3 / 3
Trigger Term Quality	Covers natural terms users would say — "macOS SwiftUI UI", "windows", "commands", "toolbars", "settings", "split views", "inspectors", "menu bar extras", "menus", "scene types" — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to native macOS SwiftUI scenes/components with distinct, platform-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: 9d2bf09

Reviewed: about 13 hours 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.