Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
47
35%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-design-expert/SKILL.mdQuality
Discovery
32%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 identifies a specific aesthetic niche (glassmorphism, 3D CSS, GSAP) but fails to list concrete actions the skill performs and completely omits a 'Use when...' clause. The language leans toward design jargon ('spatial', 'weightless') rather than terms users would naturally use when requesting help, making it harder for Claude to reliably select this skill.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for glassmorphism effects, GSAP animations, frosted glass UI, 3D transforms, or parallax scrolling in web pages.'
List specific concrete actions the skill performs, e.g., 'Creates glass-effect cards and panels, animates page transitions with GSAP, builds 3D perspective layouts, implements blur and transparency effects.'
Replace abstract adjectives like 'spatial' and 'weightless' with user-facing terms like 'floating elements', 'depth effects', or 'layered transparent UI' that users are more likely to mention.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI/UX engineering) and some characteristics (interactive, spatial, weightless, glassmorphism-based web interfaces) with technologies (GSAP, 3D CSS), but doesn't list concrete actions like 'create animations', 'build glass-effect cards', or 'implement parallax scrolling'. | 2 / 3 |
Completeness | Describes what the skill covers at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric should cap completeness at 2 — and since the 'what' is also vague (no concrete actions), this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'glassmorphism', 'GSAP', '3D CSS', and 'web interfaces', but misses common user terms like 'animation', 'glass effect', 'blur', 'frosted glass', 'parallax', 'hover effects', or 'CSS transforms'. Terms like 'spatial' and 'weightless' are more design-jargon than natural user language. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of glassmorphism, GSAP, and 3D CSS creates some distinctiveness, but 'UI/UX engineering' and 'web interfaces' are broad enough to overlap with general frontend or CSS skills. Without explicit trigger boundaries, it could conflict with other web design skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill establishes a clear visual direction and provides useful specific values (CSS properties, timing, transforms) but falls short on actionability—it describes what to do without providing complete, executable component examples. The lack of any workflow sequencing or validation steps is a significant gap for a skill involving complex multi-step UI construction. The role-play framing and concept explanations waste tokens that could be used for concrete code examples.
Suggestions
Add at least one complete, executable React component example demonstrating the core pattern (e.g., a floating glassmorphism card with GSAP scroll animation and prefers-reduced-motion handling).
Define a clear workflow sequence for building an Antigravity UI component: e.g., 1) scaffold component, 2) apply 3D transforms, 3) add GSAP animations, 4) validate accessibility (prefers-reduced-motion), 5) performance check (will-change usage).
Remove the role overview section ('You are a world-class UI/UX Engineer...') and trim concept explanations—Claude knows what glassmorphism and parallax are. Use the saved tokens for concrete code.
Split detailed GSAP ScrollTrigger patterns and R3F integration examples into referenced files (e.g., GSAP_PATTERNS.md, R3F_EXAMPLES.md) to keep the main skill lean while providing depth.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary framing ('You are a world-class UI/UX Engineer') and explains concepts Claude already knows (what glassmorphism is, what parallax means). The CSS snippets inline are helpful but the role overview section is pure padding. Could be tightened significantly. | 2 / 3 |
Actionability | Provides specific CSS values (shadow values, blur amounts, transform angles, timing values) which is good, but lacks complete executable code examples. No copy-paste ready React components, no GSAP ScrollTrigger setup code, no complete working examples—just inline CSS snippets and descriptions of what to do. | 2 / 3 |
Workflow Clarity | There is no workflow or sequenced process described. The skill covers a complex multi-step domain (building interactive UIs with animations, 3D transforms, accessibility considerations) but presents everything as unordered principles and rules rather than a clear build sequence. No validation checkpoints for performance or accessibility compliance. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with emoji headers, which aids scanning. However, it's a monolithic file with no references to external files for detailed examples, API patterns, or component templates. For a skill this broad, detailed GSAP patterns, component examples, and accessibility testing guidance should be split out. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
b938655
Table of Contents
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.