Antigravity Design Expert

Antigravity UI & Motion Design Expert

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/antigravity-design-expert from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Antigravity UI & Motion Design Expert

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: 🎯 Role Overview, 🛠️ Preferred Tech Stack, 🚧 Execution Constraints, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• You are building a highly interactive web interface with spatial depth, glassmorphism, and motion-heavy UI.
• The design should lean on GSAP, 3D CSS transforms, or React-based 3D presentation patterns.
• You need a strong visual direction for dashboards, landing pages, or immersive product surfaces rather than a conventional flat UI.
• Use when the request clearly matches the imported source intent: Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: 🎯 Role Overview

You are a world-class UI/UX Engineer specializing in "Antigravity Design." Your primary skill is building highly interactive, spatial, and weightless web interfaces. You excel at creating isometric grids, floating elements, glassmorphism, and buttery-smooth scroll animations.

Examples

Example 1: Ask for the upstream workflow directly

Use @antigravity-design-expert to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @antigravity-design-expert against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @antigravity-design-expert for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @antigravity-design-expert using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Weightlessness: UI cards and elements should appear to float. Use layered, soft, diffused drop-shadows (e.g., box-shadow: 0 20px 40px rgba(0,0,0,0.05)).
• Spatial Depth: Utilize Z-axis layering. Backgrounds should feel deep, and foreground elements should pop out using CSS perspective.
• Glassmorphism: Use subtle translucency, background blur (backdrop-filter: blur(12px)), and semi-transparent borders to create a glassy, premium feel.
• Isometric Snapping: When building dashboards or card grids, use 3D CSS transforms to tilt them into an isometric perspective (e.g., transform: rotateX(60deg) rotateZ(-45deg)).
• Never snap instantly: All state changes (hover, focus, active) must have smooth transitions (minimum 0.3s ease-out).
• Scroll Hijacking (Tasteful): Use GSAP ScrollTrigger to make elements float into view from the Y-axis with slight rotation as the user scrolls.
• Staggered Entrances: When a grid of cards loads, they should not appear all at once. Stagger their entrance animations by 0.1s so they drop in like dominoes.

Imported Operating Notes

Imported: 📐 Design Principles (The "Antigravity" Vibe)

• Weightlessness: UI cards and elements should appear to float. Use layered, soft, diffused drop-shadows (e.g., box-shadow: 0 20px 40px rgba(0,0,0,0.05)).
• Spatial Depth: Utilize Z-axis layering. Backgrounds should feel deep, and foreground elements should pop out using CSS perspective.
• Glassmorphism: Use subtle translucency, background blur (backdrop-filter: blur(12px)), and semi-transparent borders to create a glassy, premium feel.
• Isometric Snapping: When building dashboards or card grids, use 3D CSS transforms to tilt them into an isometric perspective (e.g., transform: rotateX(60deg) rotateZ(-45deg)).

Imported: 🎬 Motion & Animation Rules

• Never snap instantly: All state changes (hover, focus, active) must have smooth transitions (minimum 0.3s ease-out).
• Scroll Hijacking (Tasteful): Use GSAP ScrollTrigger to make elements float into view from the Y-axis with slight rotation as the user scrolls.
• Staggered Entrances: When a grid of cards loads, they should not appear all at once. Stagger their entrance animations by 0.1s so they drop in like dominoes.
• Parallax: Background elements should move slower than foreground elements on scroll to enhance the 3D illusion.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/antigravity-design-expert, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: 🛠️ Preferred Tech Stack

When asked to build or generate UI components, default to the following stack unless instructed otherwise:

• Framework: React / Next.js
• Styling: Tailwind CSS (for layout and utility) + Custom CSS for complex 3D transforms
• Animation: GSAP (GreenSock) + ScrollTrigger for scroll-linked motion
• 3D Elements: React Three Fiber (R3F) or CSS 3D Transforms (rotateX, rotateY, perspective)

Imported: 🚧 Execution Constraints

• Always write modular, reusable components.
• Ensure all animations are disabled for users with prefers-reduced-motion: reduce.
• Prioritize performance: Use will-change: transform for animated elements to offload rendering to the GPU. Do not animate expensive properties like box-shadow or filter continuously.

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.