macos-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 ./.agents/skills/macos-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, actionable patterns skill with strong progressive disclosure and concrete guidance backed by a verified reference bundle. The main weakness is cross-section redundancy that inflates length without adding information.

Suggestions

Consolidate the repeated sidebar opaque-background, Window-vs-WindowGroup launch, and 30-char menu-cap guidance into one canonical location (e.g., General Rules) and have Anti-Patterns reference it rather than restating it, to reduce redundancy and improve conciseness.

Add an explicit error-recovery feedback loop to the scene/view workflow (e.g., 'If the build or usability pass fails, fix the reported issue and re-run before proceeding') to push workflow_clarity to the top anchor.

Include one short assembled example in the body or in a referenced file (e.g., a minimal WindowGroup+Settings+MenuBarExtra App scaffold) to close the actionability gap where only individual APIs are named but no complete usage is shown.

Dimension	Reasoning	Score
Conciseness	The guidance is genuinely opinionated and beyond what Claude already knows, but several points are restated across sections (sidebar opaque-background guidance, Window-vs-WindowGroup launch behavior, and the 30-char menu cap each appear two to three times in Quick Start, General Rules, and Anti-Patterns), so it could be tightened.	3 / 5
Actionability	Concrete and executable guidance throughout — exact commands ("git rev-parse --is-inside-work-tree", "git init"), specific APIs ("NSApp.setActivationPolicy(.regular)", "@NSApplicationDelegateAdaptor"), a 30-character threshold, and a State Ownership decision table — with the minor gap that no fully assembled SwiftUI scene example appears inline (deferred to references).	4 / 5
Workflow Clarity	A clear 7-step "Workflow For A New macOS Scene Or View" plus a "Pre-Edit Checklist" and an explicit validation step ("Validate the flow with a build and a quick usability pass") are present; the gap is the absence of an explicit error-recovery feedback loop (validate -> fix -> re-validate).	4 / 5
Progressive Disclosure	The body is a well-organized overview with a dedicated "Cross-Cutting References" section and inline pointers to six verified, one-level-deep reference files (components-index, windowing, settings, commands-menus, split-inspectors, menu-bar-extra), with detail appropriately split out and easy navigation.	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, well-scoped description that clearly states capability and trigger conditions with concrete, desktop-specific terms. The only mild weakness is limited verb variety and a few missing synonyms, which keeps specificity and trigger quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete component types ("windows, commands, toolbars, settings, split views, or inspectors"), but the action vocabulary is limited to "Build" and "shaping" rather than multiple distinct verbs, leaving minor coverage gaps relative to the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both 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 top anchor.	5 / 5
Trigger Term Quality	Includes natural desktop terms users would say ("windows", "commands", "toolbars", "settings", "split views", "inspectors") with good coverage, but misses common synonyms such as "menu bar", "sidebar", or file extensions that would round it out.	4 / 5
Distinctiveness Conflict Risk	The "macOS SwiftUI scenes and components" scoping plus desktop-specific triggers carve a clear niche distinct from generic SwiftUI or AppKit-interop skills, with minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: robinebers/openusage
Path: .agents/skills/macos-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.