CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

67%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, highly actionable macOS SwiftUI patterns skill with real one-level reference files and concrete code. Its main weaknesses are redundancy — the sidebar-density and background rules are each stated three times — and inline pattern sections that overlap with the bundle's reference files, which inflates token cost without adding guidance.

Suggestions

Consolidate the sidebar-density guidance: state the rule once (in General Rules or the Recommended Sidebar Row Pattern) and let Anti-Patterns reference it rather than restate it at length.

Merge the Split-View Background Pattern's prose into the split-inspectors.md reference, keeping only a one-line pointer plus the minimal code example in SKILL.md.

Replace the generic "Validate the flow with a build" step with an explicit command (e.g. the referenced script/build_and_run.sh) and a fix-and-retry instruction to make the workflow checkpoint executable.

DimensionReasoningScore

Conciseness

The body is mostly dense, non-obvious desktop guidance (e.g. "Treat Window(...) as a better fit for auxiliary/on-demand singleton windows"), but several rules are restated two to three times across sections: the sidebar row density rule appears in General Rules ("at most one leading icon, one strong title line"), again in the Recommended Sidebar Row Pattern ("one icon maximum and one or two text lines maximum"), and a third time in Anti-Patterns ("three or more text lines"). The opaque-background rule is similarly repeated in General Rules, the Split-View Background Pattern, and Anti-Patterns. This repetition could be consolidated without losing clarity.

3 / 5

Actionability

Guidance is mostly executable: two complete compile-ready Swift examples (sidebar row and split-view background, each with a positive and negative variant), concrete commands ("git rev-parse --is-inside-work-tree"), and specific thresholds ("Cap visible menu item text at 30 characters", "roughly under 50 lines"). Minor gap: it delegates to the appkit-interop and build-run-debug skills and their reference files, which are not part of this bundle and cannot be verified here, leaving a small unexecutable seam.

4 / 5

Workflow Clarity

The Quick Start tracks, Pre-Edit Checklist, and the 7-step "Workflow For A New macOS Scene Or View" give a clear sequence with most checkpoints present, including a validation step ("Validate the flow with a build and a quick usability pass"). It falls short of a 5 because validation is a one-line mention rather than an explicit validate-fix-retry loop with commands, and the destructive-operation guard ("Do not initialize a nested repo inside an existing parent checkout") has no accompanying verification step.

4 / 5

Progressive Disclosure

Structure is good: the Cross-Cutting References section signals all six reference files (all of which exist in references/ and are one level deep) with one-line descriptions, and components-index.md is designated as the entry point. It is not a 5 because the two large Recommended Pattern sections (sidebar row, split-view background) inline substantial pattern content that overlaps with split-inspectors.md territory and duplicates guidance already stated in General Rules, so the SKILL.md is longer than a pure overview needs to be.

4 / 5

Total

15

/

20

Passed

Description

88%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 description in third-person voice that clearly states what the skill covers and when to use it, with an explicit Use-when clause and concrete domain triggers. Only slight improvements are available: adding a few more natural synonyms and sharpening the boundary against adjacent SwiftUI/AppKit skills.

DimensionReasoningScore

Specificity

It lists multiple specific concrete capabilities — "building native macOS SwiftUI scenes and components, including windows, commands, toolbars, settings, split views, inspectors, menu bar extras, and keyboard-driven workflows" — with comprehensive coverage of the skill's scope, matching the 5 anchor ("Lists multiple specific concrete actions; comprehensive coverage"). It is not a 4 because no meaningful capability area of the skill (per the body) is left unlisted.

5 / 5

Completeness

It explicitly answers both: the "what" ("Best practices and example-driven guidance for building native macOS SwiftUI scenes and components...") and the "when" via a concrete "Use when creating or refactoring macOS SwiftUI UI, choosing scene types, wiring menus or settings..." clause, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "creating or refactoring macOS SwiftUI UI", "choosing scene types", "wiring menus or settings", "desktop-specific component patterns" — phrases a user would plausibly say. It misses some common variations like "macOS app", "SwiftUI views", or "desktop app", keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"native macOS SwiftUI" carves out a clear niche with distinct desktop triggers (menu bar extras, split views, scenes), but the description could fire for general SwiftUI work that happens to target macOS, including territory the body defers to the appkit-interop skill — minor overlap risk with closely related skills rather than minimal.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

robinebers/openusage

Path

.agents/skills/swiftui-patterns/SKILL.md

Reviewed

Table of Contents

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.