CtrlK
BlogDocsLog inGet started
Tessl Logo

apple-app-development

This skill should be used when the user asks to "create a SwiftUI view", "build an iOS app", "set up an Xcode project", "review Apple platform code", "add a widget", "create a watchOS app", "build for visionOS", "fix SwiftUI layout", or when generating any Swift code targeting Apple platforms (iOS, iPadOS, macOS, tvOS, watchOS, visionOS). Provides modern SwiftUI-first best practices covering UI patterns, app lifecycle, navigation, project structure, and platform-specific guidance. Use together with `swift-development` for Swift language fundamentals. Always generates Swift unless the project explicitly requires Objective-C.

75

1.20x
Quality

86%

Does it follow best practices?

Impact

90%

1.20x

Average score across 1 eval scenario

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A thorough, highly actionable SwiftUI skill with excellent progressive disclosure and concrete code. It is somewhat verbose in its inline worked examples and lacks explicit validation-checkpoint workflows for fragile operations.

Suggestions

Trim the inline design-token, MVVM, and TCA code blocks to minimal illustrative snippets and push full worked versions into reference files to improve conciseness.

Add an explicit sequenced workflow with validation checkpoints for risky operations such as UIKit→SwiftUI migration and multi-target build setup (e.g., verify target membership / build succeeds before proceeding).

Move the lengthy TCA alternative architecture into a reference file, keeping only a one-line pointer and the 'when to use' guidance inline.

DimensionReasoningScore

Conciseness

Mostly efficient rules and tables, but the fully worked design-token enums, MVVM, and TCA reducer examples run long and could be condensed or moved to references; not every token earns its place.

2 / 3

Actionability

Executable, copy-paste-ready Swift throughout — `@Observable` ViewModels, MVVM State/ViewModel/View, TCA reducer, and concrete design tokens — with specific, runnable examples.

3 / 3

Workflow Clarity

Well organized by topic with a useful Common Mistakes table, but it is a patterns reference rather than a sequenced workflow, and lacks explicit validation checkpoints for risky operations (e.g., migration, multi-target builds).

2 / 3

Progressive Disclosure

Clear overview in SKILL.md with well-signaled, one-level-deep references to 20 real `references/*.md` files (all verified present), split by platform and feature with easy navigation tables.

3 / 3

Total

10

/

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.

A strong, trigger-rich description that uses third person, names concrete actions, and cleanly scopes the skill against its sibling. Slightly long, but every clause earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "create a SwiftUI view", "build an iOS app", "set up an Xcode project", "add a widget", "fix SwiftUI layout" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("SwiftUI-first best practices covering UI patterns, app lifecycle, navigation, project structure") and when ("when the user asks to..." trigger list).

3 / 3

Trigger Term Quality

Natural phrasings a user would actually say ("build an iOS app", "add a widget", "fix SwiftUI layout") with good coverage across Apple platforms.

3 / 3

Distinctiveness Conflict Risk

Clear Apple-platform niche with distinct triggers and an explicit boundary against the sibling `swift-development` skill, making misfires unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
provectus/awos-recruitment
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.