Loading...
Loading...
Found 55 Skills
Motion design and animation for user interfaces. Use when creating micro-interactions, page transitions, loading states, or any UI animation across web and mobile platforms.
After Effects animation rendering for web and React applications. Use this skill when implementing Lottie animations, JSON vector animations, interactive animated icons, micro-interactions, or loading animations. Triggers on tasks involving Lottie, lottie-web, lottie-react, dotLottie, After Effects JSON export, bodymovin, animated SVG alternatives, or designer-created animations. Complements GSAP ScrollTrigger and Framer Motion for scroll-driven and interactive animations.
Actionable design system complementing official frontend-design plugin. The plugin provides philosophy; this skill provides executable patterns. Invoke when: - Building web components, pages, or applications - Designing UI that needs to stand out (not generic) - Implementing visual polish and micro-interactions - Choosing typography, color palettes, or spatial layouts CRITICAL: Avoid "AI slop" aesthetics. Make creative, unexpected choices. MANDATORY: Consult Gemini before any frontend work. See also: references/dna-codes.md, references/banned-patterns.md
React game UI patterns using shadcn/ui, Tailwind, and Framer Motion for polished game interfaces. Use when building HUDs, resource bars, scoreboards, modals, tooltips, card components, or any game UI. Includes micro-interactions, animations, responsive layouts, and accessibility for games. Triggers on requests for game interface components, UI animations, or shadcn/ui game patterns.
Clinic-architecture-aligned iOS animation craft guidelines for SwiftUI (iOS 26 / Swift 6.2) covering motion tokens, spring physics, gesture continuity, spatial transitions, micro-interactions, and accessibility. Enforces @Equatable on animated views and keeps animation state aligned with Domain/Data feature boundaries. Use when writing, reviewing, or refactoring SwiftUI animation code under the clinic modular MVVM-C architecture.
The canonical rulebook of UI craft and feel. Every element must earn its place and do its one job well; the surface must be tight, clean, calm, and genuinely pleasant to use. The single source of truth that landing-audit grades against and that shipit checks touched UI files against before commit. Use when building or editing ANY user-facing UI, page, screen, hero, or component, or when the user mentions design, layout, hierarchy, typography, color, spacing, contrast, CTAs, or micro-interactions.
Aura - Senior UI/UX Design Architect with 12+ years creating premium digital experiences. Use when designing landing pages, dashboards, mobile apps, design systems, component libraries, or brand-aligned UI. Specializes in React/Tailwind/Framer Motion prototypes, responsive design, micro-interactions, and discovery-first design process.
Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.
Design user interactions, flows, and interface behaviors. Use for wireframes, prototypes, micro-interactions, user flows, state machines, affordance design, and usability reviews. Covers IxD principles, Nielsen heuristics, Fitts's Law, Hick's Law, and emerging paradigms (spatial, conversational, gesture-based interfaces). Keywords: IxD, wireframe, prototype, user flow, micro-interaction, UI state diagram, screen flow, clickable prototype, interaction pattern.
Use this skill when implementing animations, transitions, micro-interactions, or motion design in web applications. Triggers on CSS animations, Framer Motion, GSAP, keyframes, transitions, spring animations, scroll-driven animations, page transitions, loading states, and any task requiring motion or animation implementation.
Activate for animation, transitions, micro-interactions, loading states, and scroll-driven motion.
Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.