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%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.

The body is highly actionable and well-structured for progressive disclosure, with executable code and a comprehensive one-level reference system. It is held back only by some restated basics and a redundant mistakes table that inflate tokens, and by the absence of explicit validation checkpoints in its workflows.

Suggestions

Trim restated basics (e.g. "@MainActor for UI-updating code", "Never block the main thread") and the naming-convention rows that overlap with general Swift knowledge, since these are covered by the sibling swift-development skill.

Drop or condense the "Quick Reference: Common Mistakes" table where it merely restates rules already in the Important Rules and Code Style sections, to reduce redundancy.

Add explicit validation/feedback steps to the few procedural sequences (e.g. "define design tokens -> apply at root -> verify no raw values remain") to lift workflow clarity above the checkpoint-absent anchor.

DimensionReasoningScore

Conciseness

Largely efficient with focused code and terse rules, but restates some basics Claude already knows ("@MainActor for UI", "never block the main thread") and duplicates several rules in the "Common Mistakes" table, so it is mostly rather than fully efficient.

3 / 5

Actionability

Provides complete, copy-paste-ready Swift examples (design tokens, @Observable, MVVM, TCA reducer) plus a concrete project tree and specific references, covering the common cases.

5 / 5

Workflow Clarity

Sequences are present (numbered design-token steps, MVVM State/ViewModel/View, project structure) but lack explicit validation checkpoints or feedback loops, matching the "steps listed but validation gaps" anchor.

3 / 5

Progressive Disclosure

Clear overview with a dedicated Reference Files section and platform/feature tables, all references one level deep and verified to exist, with bulk detail appropriately split into separate files.

5 / 5

Total

16

/

20

Passed

Description

100%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.

The description is strong across all dimensions: concrete actions, natural trigger phrases, explicit what/when guidance, and a clear niche with an explicit sibling-skill boundary. It matches the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("create a SwiftUI view", "build an iOS app", "review Apple platform code", "fix SwiftUI layout") plus comprehensive coverage of UI patterns, lifecycle, navigation, project structure, and platform-specific guidance.

5 / 5

Completeness

Explicitly answers both "what" (SwiftUI-first best practices covering UI patterns, lifecycle, navigation, project structure) and "when" with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("create a SwiftUI view", "add a widget", "fix SwiftUI layout") with comprehensive coverage of platform synonyms (iOS, iPadOS, macOS, tvOS, watchOS, visionOS).

5 / 5

Distinctiveness Conflict Risk

Clear Apple-platform SwiftUI niche with distinct triggers and an explicit boundary carve-out with the `swift-development` skill, minimizing conflict risk.

5 / 5

Total

20

/

20

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.