swiftui-patterns

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

Quality

79%

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 ./plugins/build-macos-apps/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.

A well-structured, navigable macOS SwiftUI skill with concrete API-level guidance and clean progressive disclosure to verified reference files. Its main weakness is repeated restatement of the same rules across Quick Start, General Rules, and Anti-Patterns.

Suggestions

Consolidate the rules that currently appear in both General Rules and Anti-Patterns (menu-bar 30-char cap, WindowGroup-vs-Window launch, opaque sidebar fills, sidebar-row density) into a single authoritative section and have the other section cross-reference it, to reduce token redundancy.

Add one or two minimal inline Swift snippets (e.g., a WindowGroup+Settings scene skeleton and a NavigationSplitView sidebar) so the core patterns are copy-paste ready without requiring a reference round-trip.

Strengthen the workflow validation step into an explicit feedback loop: 'build → fix compile errors → rebuild → usability pass', mirroring the validate→fix→retry pattern expected for fragile operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes SwiftUI competence, but several rules are stated redundantly across Quick Start, General Rules, and Anti-Patterns (the 30-char menu-bar cap, WindowGroup-vs-Window launch guidance, opaque-sidebar-fill rule, and sidebar-row density guidance each repeat), which is more than minor padding and pulls it down from a 4.	3 / 5
Actionability	Provides concrete, specific guidance — exact scene types, specific APIs (NSApp.setActivationPolicy(.regular), @SceneStorage), a file/folder structure, and a state-ownership table; as an instruction-only skill it lacks inline Swift code examples but the API-level guidance is actionable, so it lands at anchor 4.	4 / 5
Workflow Clarity	Two clearly sequenced workflows (7-step scene workflow and 5-step pre-edit checklist) with a final build/usability validation step, but the validation is a single soft checkpoint without an explicit validate→fix→retry feedback loop, leaving it just below anchor 5.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview deferring detail to six real, one-level-deep references/*.md files, all well-signaled in a Cross-Cutting References section with one-line descriptions plus inline pointers; verified the referenced files exist, matching the anchor-5 example.	5 / 5
	Total	16 / 20 Passed

Description

87%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, third-person description with an explicit 'Use when' clause and concrete desktop trigger terms. Its only weakness is that the capability verbs are slightly generic ('Build', 'shaping') despite a rich list of scene/component targets.

Dimension	Reasoning	Score
Specificity	Names the domain ('Build macOS SwiftUI scenes and components') plus several concrete capability areas (windows, commands, toolbars, settings, split views, inspectors); falls short of anchor 5 because the actions collapse into one main verb ('Build'/'shaping') rather than a list of distinct concrete actions.	4 / 5
Completeness	Explicitly answers what ('Build macOS SwiftUI scenes and components with desktop patterns') and when ('Use when shaping windows, commands, toolbars, settings, split views, or inspectors') with concrete trigger phrases, matching the anchor-5 example.	5 / 5
Trigger Term Quality	'shaping windows, commands, toolbars, settings, split views, or inspectors' are natural desktop terms users would say; good coverage but missing some common variations (menu bar extra, inspector panel, sidebar), so it sits at anchor 4 rather than a comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The 'macOS SwiftUI scenes and components' desktop framing carves a clear niche with distinct triggers and minimal overlap with sibling skills like appkit-interop, matching the anchor-5 clear-niche example.	5 / 5
	Total	18 / 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: openai/plugins
Path: plugins/build-macos-apps/skills/swiftui-patterns/SKILL.md
Commit: d416fd5

Reviewed: 12 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.