CtrlK
BlogDocsLog inGet started
Tessl Logo

liquid-glass-design

iOS 26 Liquid Glass design system — dynamic glass material with blur, reflection, and interactive morphing for SwiftUI, UIKit, and WidgetKit.

55

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/liquid-glass-design/SKILL.md

The canonical home for this skill is tdg-personal/liquid-glass-design

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable, packed with executable Swift across SwiftUI, UIKit, and WidgetKit, and assumes Claude's competence without padding. It loses points on conciseness from redundant trigger sections, on workflow clarity from absent explicit validation checkpoints, and on progressive disclosure from keeping all framework material in one monolithic file rather than splitting into reference files.

Suggestions

Consolidate the overlapping "When to Activate" and "When to Use" sections into a single trigger section and trim the opening paragraph that restates the description.

Add an explicit validation/verification checkpoint after the core application patterns (e.g. 'Verify the glass renders in light, dark, and tinted modes and check text contrast before shipping').

Move the full UIKit and WidgetKit pattern sections into one-level-deep reference files (e.g. UIKit.md, WidgetKit.md) so SKILL.md stays a concise overview with clearly signaled navigation.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable code and concise guidance without explaining basic concepts Claude already knows, matching the level-2 anchor; it is not 3 because the opening paragraph restates the description and the "When to Activate" and "When to Use" sections overlap, so it could be tightened.

2 / 3

Actionability

Concrete, copy-paste-ready Swift is provided throughout (`.glassEffect()`, `.buttonStyle(.glass)`, `UIGlassEffect()`, `.containerBackground(for: .widget)`) with specific modifiers and parameters, matching the level-3 'fully executable code/commands; specific examples'.

3 / 3

Workflow Clarity

Patterns are organized by framework and step, but there are no explicit validation checkpoints or feedback loops in the application flow; verification items appear only as best-practice bullets ('Test across appearances', 'Ensure accessibility contrast'), matching the level-2 'steps listed but validation gaps' anchor.

2 / 3

Progressive Disclosure

The single SKILL.md is well-organized with clear sections and no broken/nested references, but at ~280 lines it is monolithic with full per-framework (SwiftUI/UIKit/WidgetKit) content inline that could be split into one-level-deep reference files; no bundle files exist, matching the level-2 'content that should be separate is inline' anchor rather than the level-3 split-overview pattern.

2 / 3

Total

9

/

12

Passed

Description

57%

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 specific and distinctive, clearly scoping the iOS 26 Liquid Glass niche and frameworks, but it omits an explicit 'Use when...' trigger clause and relies on noun-phrase features rather than action verbs, capping completeness and trigger-term coverage at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when building iOS 26+ apps with glass-style buttons, cards, toolbars, widgets, or Liquid Glass effects'.

Reframe the feature list with action verbs (e.g. 'Apply glass effects, customize tint and shape, build glass buttons, animate morphing transitions') to lift specificity to 3.

Include common user phrasings such as 'glass effect,' 'iOS 26 design language,' and 'blur material' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Quotes "dynamic glass material with blur, reflection, and interactive morphing for SwiftUI, UIKit, and WidgetKit" name the domain and concrete features plus three frameworks, but the description uses noun phrases rather than concrete action verbs (e.g. apply, implement, migrate), so it is not the level-3 'lists multiple specific concrete actions'.

2 / 3

Completeness

The "what" is clear ("iOS 26 Liquid Glass design system — dynamic glass material..."), but there is no explicit "Use when..." trigger clause, which the guidelines cap at 2; it is not 1 because the what is strong and scope is implied by the framework list.

2 / 3

Trigger Term Quality

Natural terms like "Liquid Glass," "iOS 26," and "SwiftUI, UIKit, WidgetKit" are present, matching the level-2 'some relevant keywords' anchor; it falls short of 3 because common variations a user might say ("glass effect," "iOS 26 design language," "blur effect") are absent.

2 / 3

Distinctiveness Conflict Risk

"iOS 26 Liquid Glass design system" plus SwiftUI/UIKit/WidgetKit is a clear, narrow niche unlikely to trigger for unrelated skills, matching the level-3 'clear niche with distinct triggers'.

3 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
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.