tdg-personal/liquid-glass-design
iOS 26 Liquid Glass design system — dynamic glass material with blur, reflection, and interactive morphing for SwiftUI, UIKit, and WidgetKit.
68
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
54%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 effectively identifies a clear, distinctive niche (iOS 26 Liquid Glass design system) with good natural trigger terms covering relevant frameworks and visual concepts. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill, and the capability description reads more like a tagline than a list of concrete actions the skill enables.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about implementing Liquid Glass effects, glass-style UI components, or iOS 26 visual design in SwiftUI, UIKit, or WidgetKit.'
List specific concrete actions the skill performs, e.g., 'Creates glass material views, applies dynamic blur and reflection effects, implements interactive morphing transitions, builds glass-style widgets.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (iOS 26 Liquid Glass design system) and some actions/capabilities (blur, reflection, interactive morphing), but doesn't list concrete discrete actions like 'create glass panels', 'apply blur effects', 'implement morphing animations'. The capabilities are more descriptive of the system than specific actions the skill performs. | 2 / 3 |
Completeness | Describes what the skill covers (Liquid Glass design system with specific visual properties and frameworks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also more of a label than a clear explanation, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Liquid Glass', 'blur', 'reflection', 'morphing', 'SwiftUI', 'UIKit', 'WidgetKit', 'iOS 26', 'glass material', 'dynamic glass'. These cover the key terms a developer working with this design system would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'iOS 26 Liquid Glass' is a very specific niche with clear domain boundaries. It's unlikely to conflict with other skills since it targets a particular Apple design system, specific frameworks (SwiftUI, UIKit, WidgetKit), and specific visual effects (glass material, morphing). | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable code examples covering three Apple frameworks. Its main weaknesses are moderate verbosity (some redundant sections and overly detailed UIKit boilerplate) and a monolithic structure that could benefit from splitting framework-specific details into separate files. The skill would also benefit from trimming sections that overlap in purpose.
Suggestions
Remove or merge the overlapping 'When to Activate' and 'When to Use' sections — they convey nearly identical information.
Split UIKit and WidgetKit patterns into separate reference files (e.g., UIKIT.md, WIDGETKIT.md) and link from the main skill to improve progressive disclosure.
Trim the UIKit basic example — the full Auto Layout constraint setup is boilerplate Claude already knows; focus on the UIGlassEffect-specific API surface.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes some unnecessary sections like 'When to Activate' and 'When to Use' which overlap significantly. The UIKit example is verbose with full constraint setup code that Claude could infer. The 'Key Design Decisions' table restates information already evident from the code examples. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready Swift code examples for SwiftUI, UIKit, and WidgetKit. Each pattern includes concrete API calls with specific modifiers, parameters, and complete code blocks that can be directly used. | 3 / 3 |
Workflow Clarity | The skill covers individual patterns well but lacks explicit workflow sequencing for multi-step processes like migrating existing blur effects to Liquid Glass or building a complete glass-based UI. The morphing transitions section shows a clear pattern but there are no validation checkpoints for ensuring glass effects render correctly. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping by framework (SwiftUI, UIKit, WidgetKit), but it's a monolithic document with no references to external files. The UIKit and WidgetKit sections could be split into separate reference files, with SKILL.md serving as a concise overview pointing to them. | 2 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents