interface-kit

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

Updated May 26, 2026
One-click install
npx skills add https://github.com/KinalVR-Expo2026/KinalVR-Client --skill interface-kit-kinalvr-expo2026
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interface-kit
Source: https://github.com/KinalVR-Expo2026/KinalVR-Client/tree/main/.claude/.agents/skills/interface-kit
Command: npx skills add https://github.com/KinalVR-Expo2026/KinalVR-Client --skill interface-kit-kinalvr-expo2026

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend implementations often ship with inconsistent spacing, weak typography, missing accessibility support, and generic aesthetics. This Skill provides a single actionable reference covering the HOW of UI implementation so interfaces meet accessibility, performance, and design quality standards. ## Core Features & Use Cases - Design Implementation Standards: Covers typography setup, HSL semantic color tokens, concentric border radius, 4/8px spacing scales, and layered shadows with copy-paste CSS patterns. - Motion & Interaction Guidance: Provides a frequency-based animation decision framework, custom easing curves, stagger patterns, and reduced-motion handling. - Accessibility & Review Checklists: Ships WCAG 2.1 AA audit guidance, component patterns for Radix/shadcn, and a 30-item pre-delivery review checklist. - Use Case: When asked to build a landing page or polish a component, the Skill supplies concrete defaults for fonts, colors, animation durations, focus management, and ARIA attributes so the output passes keyboard navigation and contrast requirements. ## Quick Start Ask the AI to build a responsive pricing page component following the interface-kit guidelines for typography, color tokens, and accessibility.

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 Radix and shadcn?

Use Radix UI primitives for focus trapping, ARIA attributes, and keyboard navigation, then style them with Tailwind and CVA variants. The component-patterns reference includes copy-paste implementations for buttons, dialogs, selects, sheets, toasts, and forms.

What animation duration should UI elements use?

Match 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. Use custom cubic-bezier easing curves instead of built-in keywords.

Does this work with an existing design system or DESIGN.md?

Yes. If a DESIGN.md exists at the project root, its tokens and specifications override all defaults in the Skill. The implementation guidance on accessibility, motion, and component craft applies regardless of which design system is active.

How do I meet WCAG AA contrast requirements in dark mode?

Test contrast separately in dark mode using desaturated tonal variants rather than inverted colors. Normal text needs 4.5:1 and large text 3:1; verify with Chrome DevTools or axe-core since light-mode passing pairs often fail in dark.

Why does nested UI with rounded corners look off?

Nested elements need concentric border radius: outer radius equals inner radius plus padding. Using the same radius on parent and child makes corners look bloated; the review checklist includes before-and-after values to verify the fix.

When should I avoid animating a UI interaction?

Skip animation entirely for actions performed 100+ times per day, such as keyboard shortcuts and tab switches. Also respect prefers-reduced-motion and gate hover effects behind a hover-capable media query for touch devices.