swiftui-patterns

Build macOS SwiftUI scenes and components with desktop patterns. Use when shaping windows, commands, toolbars, settings, split views, or inspectors.

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%Weight 40%Scale 1-3

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

The skill body is well-structured, highly actionable, and uses progressive disclosure effectively with verified one-level-deep references and explicit validation in its workflows. Its main weakness is conciseness: several prescriptive rules are duplicated across the General Rules and Anti-Patterns sections.

Suggestions

Deduplicate guidance repeated across sections: the sidebar-row density rules, the MenuBarExtra 30-char cap, the WindowGroup(...,id:)-vs-Window launch advice, and the opaque custom sidebar-background warning each appear in both "General Rules" and "Anti-Patterns" — state each once and cross-reference the other section.

Merge or shrink the "Pre-Edit Checklist For New App Scaffolds", which largely restates the "New app scaffolding" bullets, into a short pre-edit gate to avoid restating the same points twice.

Move the detailed sidebar row-density and background-paint guidance out of the inline "General Rules" list into references/split-inspectors.md (already referenced) and keep only the rule statement in the body.

Dimension	Reasoning	Score
Conciseness	The body gives prescriptive SwiftUI guidance rather than explaining concepts Claude already knows, but several rules are stated twice — sidebar-row density, the 30-char MenuBarExtra cap, WindowGroup-vs-Window launch advice, and opaque custom sidebar backgrounds each appear in both "General Rules" and "Anti-Patterns" — so not every token earns its place.	2 / 3
Actionability	Guidance names exact APIs (@SceneStorage, @AppStorage, @NSApplicationDelegateAdaptor, NSApp.setActivationPolicy(.regular)), concrete commands (git rev-parse --is-inside-work-tree, git init), and a copy-ready App/Views/Models/Stores/Services file layout, which is highly actionable for an instruction skill.	3 / 3
Workflow Clarity	The "Workflow For A New macOS Scene Or View" is a clear 7-step sequence whose final step is an explicit validation checkpoint ("Validate the flow with a build and a quick usability pass"), complemented by a dedicated Pre-Edit Checklist for scaffolds.	3 / 3
Progressive Disclosure	The body is a clear overview with a "Cross-Cutting References" section signaling six one-level-deep reference files (all verified present), using components-index.md as an entry point and deferring detailed examples to references/split-inspectors.md.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, specific, and complete: it states a concrete capability and pairs it with an explicit "Use when" trigger rich in natural desktop/SwiftUI terms. It carves out a clear niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	"Build macOS SwiftUI scenes and components with desktop patterns" and "shaping windows, commands, toolbars, settings, split views, or inspectors" name multiple concrete actions on concrete objects, matching the anchor that lists specific concrete actions rather than vague language.	3 / 3
Completeness	It clearly answers what ("Build macOS SwiftUI scenes and components with desktop patterns") and when via an explicit "Use when shaping…" trigger clause, satisfying both halves of the completeness anchor.	3 / 3
Trigger Term Quality	"windows, commands, toolbars, settings, split views, or inspectors" are natural desktop/SwiftUI terms a user would actually say when reaching for this skill, giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The niche is narrowly scoped to macOS SwiftUI desktop patterns with distinct triggers (windows, commands, toolbars, settings, split views, inspectors), making conflict with other skills unlikely; voice is third-person so no penalty applies.	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: openai/plugins
Path: plugins/build-macos-apps/skills/swiftui-patterns/SKILL.md
Commit: 11c74d6

Reviewed: 17 days 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.