CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swiftui-gestures

Builds or reviews SwiftUI tap, press, drag, magnify, and rotate interactions, including gesture composition, transient GestureState, custom gestures, and parent/child conflict resolution. Use for gesture recognition, arbitration, state, migration, or interaction bugs.

Quality

86%

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

78%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, lean reference skill with executable-style Swift examples, a useful review checklist, and exemplary progressive disclosure to a single one-level-deep reference file. The main gaps are snippet self-containment (undeclared properties, missing View wrappers) and the absence of an explicit verification step when writing or fixing gesture code.

Suggestions

Make the core code snippets self-contained — declare currentScale/currentAngle and wrap fragments in a minimal View struct — so they are copy-paste executable.

Add an explicit verification step after the Review Checklist (e.g., compile check or simulator test of the corrected gesture) to close the fix → validate feedback loop.

Trim the redundancy between Common Mistakes and the Review Checklist, and consider dropping the Contents TOC, to tighten token usage.

DimensionReasoningScore

Conciseness

The body is lean — a compact gesture table, terse code, and decision rules with no padding or explanations of concepts Claude already knows — but the Contents TOC and the Review Checklist partially duplicating Common Mistakes ("MagnifyGesture / RotateGesture on iOS 17+" appears in both) could be trimmed. Not 5: these minor redundancies mean not every token earns its place; not 3: there is no unnecessary explanation to remove.

4 / 5

Actionability

Concrete Swift snippets cover every core gesture plus composition (e.g., the LongPressGesture/.updating example and the MagnifyGesture.simultaneously(with: RotateGesture()) example), but several fragments are not self-contained: `currentScale`/`currentAngle` are undeclared in the Magnify/Rotate lines and snippets omit enclosing View structs. Not 5: not fully copy-paste ready; not 3: the examples are real executable-style Swift, not pseudocode.

4 / 5

Workflow Clarity

The Review Checklist supplies concrete checkpoints for review mode ("Correct modern gesture types used", "Bounds clamped on persisted pinch/rotation values in .onEnded") and sections flow concepts → mistakes → checklist, but there is no explicit sequence and no compile/test verification step for code the skill writes or fixes. Not 5: validation is checklist-only with no verify step or error-recovery loop; not 3: the checklist provides most checkpoints and the topical flow is clear.

4 / 5

Progressive Disclosure

Clear overview in SKILL.md with one well-signaled, one-level-deep reference — "Full recipes, pinch-to-zoom-pan, drag-to-reorder, and UIKit interop: references/gesture-patterns.md" — and the bundle file exists, contains the promised recipes, and links only back to SKILL.md (no nested references). The split is appropriate: overview and core patterns inline, advanced recipes in the reference.

5 / 5

Total

17

/

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 with an explicit what and an explicit "Use for" when-clause, and concrete enumeration of the gesture domain. The only weaknesses are missing natural synonyms (pinch, zoom, swipe) and slightly broad trigger words ("state", "migration") that could pull in adjacent SwiftUI skills.

DimensionReasoningScore

Specificity

"Builds or reviews" plus a comprehensive enumeration — "tap, press, drag, magnify, and rotate interactions, including gesture composition, transient GestureState, custom gestures, and parent/child conflict resolution" — lists multiple concrete actions covering the full gesture domain. Not 4: coverage is comprehensive rather than leaving minor gaps (discrete and continuous gestures, composition, state, custom gestures, and conflict resolution are all named).

5 / 5

Completeness

Explicitly answers both parts: what ("Builds or reviews SwiftUI tap, press, drag, magnify, and rotate interactions...") and when ("Use for gesture recognition, arbitration, state, migration, or interaction bugs") with concrete trigger phrases. Not 4: the "Use for" clause is explicit and specific rather than only weakly stated.

5 / 5

Trigger Term Quality

Natural phrases like "tap, press, drag", "gesture recognition", and "interaction bugs" are present and would be said by users, but common synonyms are missing — "pinch"/"zoom" (users say these, not "magnify"), "swipe", and "long press". Not 5: synonym coverage is incomplete; not 3: the included keywords are natural user language, not just technical jargon.

4 / 5

Distinctiveness Conflict Risk

Clear SwiftUI-gesture niche with distinct triggers, but "state" and "migration" in the when-clause are broad enough to overlap with adjacent skills (e.g., SwiftUI state management or UIKit-to-SwiftUI migration). Not 5: that minor overlap risk exists; not 3: the domain is far more specific than "somewhat specific".

4 / 5

Total

18

/

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.

Repository

thienqo/ios-skills

Path

skills/swiftui-gestures/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.