interface-kit

Implements accessible, performant UI components with typography, color, motion, and spatial design guidance.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/taylorelley/skills --skill interface-kit-taylorelley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interface-kit
Source: https://github.com/taylorelley/skills/tree/main/skills/design/interface-kit
Command: npx skills add https://github.com/taylorelley/skills --skill interface-kit-taylorelley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend implementations often ship with generic aesthetics, accessibility gaps, janky animations, and inconsistent spacing. This Skill provides a single actionable reference covering the full implementation stack — typography, color systems, spatial design, motion, component craft, and accessibility — so interfaces meet WCAG AA standards and feel intentionally designed rather than templated. ## Core Features & Use Cases - Priority-Stacked Implementation Guidance: Enforces accessibility and performance as non-negotiable foundations before typography, layout, color, motion, and polish layers. - Component Patterns with shadcn/ui and Radix: Provides CVA-based variant patterns for buttons, forms, dialogs, selects, sheets, toasts, and tables with built-in accessibility behavior. - Motion and Animation Framework: Applies frequency-based animation budgets, custom easing curves, stagger patterns, and reduced-motion handling for 60fps interactions. - Use Case: When asked to build a landing page or dashboard, the Skill guides aesthetic direction selection, HSL semantic token setup, concentric border radius, keyboard navigation, and a 30-item pre-delivery review covering contrast, focus rings, and animation performance. ## Quick Start Use the interface-kit skill to build an accessible, polished pricing page component with dark mode support and staggered enter animations.

Frequently Asked Questions about interface-kit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build accessible UI components with shadcn/ui and Radix?

Use Radix UI primitives for unstyled accessible foundations and compose them with CVA variants for styling. Radix handles focus trapping, ARIA attributes, and keyboard navigation automatically, while Tailwind classes control the visual design.

What animation duration should UI elements use?

Match animation duration to usage frequency: high-frequency actions get no animation, occasional interactions like modals get 150-300ms, and rare moments like onboarding can use 300-500ms. Always use custom cubic-bezier easing curves instead of built-in CSS easings.

How do I meet WCAG AA color contrast requirements?

Normal text requires a 4.5:1 contrast ratio and large text requires 3:1, tested separately in light and dark modes. Use Chrome DevTools or axe-core to verify ratios, and never convey information by color alone — pair it with icons or text labels.

Does this work with Next.js App Router server components?

Yes. Fetch data in server components and pass it as serializable props to client components marked with "use client". This keeps interactive shadcn/ui components on the client while data fetching stays on the server.

Why do nested rounded corners look wrong in my UI?

Nested elements need concentric border radius: outer radius equals inner radius plus padding. If a card has 8px padding and an inner element with 8px radius, the card itself needs a 16px radius to look correct.

When should I avoid animating a UI interaction?

Skip animation entirely for actions performed 100+ times per day, like keyboard shortcuts and command palette actions. Also respect prefers-reduced-motion by reducing animations to near-instant durations for users who opt out.