CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ivan-magda/uikit-expert

Write, review, or improve UIKit code following best practices for view controller lifecycle, Auto Layout, collection views, navigation, animation, memory management, and modern iOS 18–26 APIs. Use when building new UIKit features, refactoring existing views or view controllers, reviewing code quality, adopting modern UIKit patterns (diffable data sources, compositional layout, cell configuration), or bridging UIKit with SwiftUI. Does not cover SwiftUI-only code.

Quality

91%

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

Overview
Quality
Evals
Security
Files

Quality

Content

86%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 overview skill: actionable at the API level, split appropriately across 14 verified one-level-deep reference files, with clear mode-based workflows and a gated review checklist. The main improvements are removing the repeated deployment-target gating statements and adding an explicit re-validation step to the Improve and Implement workflows.

Suggestions

State the deployment-target gating rule once (e.g., in the 'Before any mode' section) and reference it from the Implement steps, Adaptive guideline, and Modern APIs checklist item instead of repeating it.

Close the loop on the Improve and Implement workflows by adding a final step such as 're-run the Review Checklist gates after changes' so all three modes end in explicit validation.

Consolidate the duplicated deallocation-verification guidance (Lifecycle and Memory sections both say to verify dealloc via deinit) into one location.

DimensionReasoningScore

Conciseness

The body is dense and high-value ("Decoded bitmap size = width × height × 4 bytes (a 12MP photo = ~48MB RAM)") with no explanations of concepts Claude already knows, but deployment-target gating is repeated in the Workflows intro, Implement step 8, the Adaptive guideline, and the Modern APIs checklist, and deinit-verification appears in both the Lifecycle and Memory sections.

4 / 5

Actionability

Guidance is fully concrete: exact API names, exact call orderings ("addChild → addSubview → didMove(toParent:)"), two complete executable Swift examples (Auto Layout batch activation, diffable data source with CellRegistration), a Deprecated → Modern table with API names and versions, and specific API calls like "setConstraints(_:activeWhenNearEdge:)".

5 / 5

Workflow Clarity

Three clearly signaled entry-point modes, an ordered 8-step Implement sequence, and a Review checklist with pass/fail gates plus a fail → fix-per-guideline feedback loop; however, only the Review mode closes the loop — Improve and Implement lack an explicit final re-validation step.

4 / 5

Progressive Disclosure

Each Core Guideline links to its reference file (all 14 exist, verified on disk), references are one level deep with full standalone content, a References section gives one-line descriptions, and the Overview explicitly instructs naming tools instead of reproducing walkthrough steps.

5 / 5

Total

18

/

20

Passed

Description

92%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 that clearly states capabilities, includes an explicit and specific "Use when..." clause with natural trigger terms, and defines its boundary against SwiftUI-only work. The only gap is a few missing natural synonyms (e.g., table view) that would improve trigger coverage.

DimensionReasoningScore

Specificity

"Write, review, or improve UIKit code" names three concrete actions, then comprehensively enumerates the domains (view controller lifecycle, Auto Layout, collection views, navigation, animation, memory management, modern iOS 18–26 APIs) and specific patterns ("diffable data sources, compositional layout, cell configuration"), all in third-person voice.

5 / 5

Completeness

The description explicitly answers both what ("Write, review, or improve UIKit code following best practices for...") and when ("Use when building new UIKit features, refactoring..., reviewing code quality, adopting modern UIKit patterns..., or bridging UIKit with SwiftUI"), with concrete trigger phrases plus a boundary clause ("Does not cover SwiftUI-only code").

5 / 5

Trigger Term Quality

Natural terms like "UIKit", "view controller", "Auto Layout", "refactoring existing views or view controllers", "reviewing code quality", and "bridging UIKit with SwiftUI" cover what users would say, but common variations such as "table view"/"UITableView", "scroll view", and "constraints" are missing.

4 / 5

Distinctiveness Conflict Risk

"UIKit" carves out a clear niche with distinct triggers, and the explicit exclusion "Does not cover SwiftUI-only code" minimizes overlap risk with a SwiftUI skill while the "bridging UIKit with SwiftUI" trigger captures the interop case.

5 / 5

Total

19

/

20

Passed

Validation

100%

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.

Reviewed

On this page