interface-design

Designs and refines product UI with domain-driven visual systems, tokens, and hierarchy.

3|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/langgenius/due-date-hq-jwl --skill interface-design-langgenius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interface-design
Source: https://github.com/langgenius/due-date-hq-jwl/tree/main/.claude/skills/interface-design
Command: npx skills add https://github.com/langgenius/due-date-hq-jwl --skill interface-design-langgenius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interfaces tend to look generic because defaults win over deliberate design decisions. This Skill enforces a craft-first process for dashboards, admin panels, SaaS apps, and data interfaces so every layout, color, type, and spacing choice is intentional and tied to the product's domain. ## Core Features & Use Cases - Domain-driven direction: Explores the product's world to derive a color palette, signature element, and rejected defaults before any code is written. - Design-system architecture: Defines token structure, type scale ratios, spacing grids, elevation levels, and depth strategies for consistent UI. - Polish and motion rules: Covers states, hit areas, tabular numbers, concentric radius, sub-300ms animations, and reduced-motion support. - Use Case: When redesigning a SaaS settings page, the Skill produces a domain exploration, a proposed direction with palette and signature, then implements components using existing primitives and verifies hierarchy with squint and swap tests. ## Quick Start Use the interface-design skill to redesign this dashboard with a domain-specific visual direction and consistent design tokens.

Frequently Asked Questions about interface-design

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

FAQPage Schema
How do I make an AI-generated dashboard look less generic?

Start with domain exploration: name concepts, colors, and a signature element from the product's world before writing code. Then enforce hierarchy through one focal point, a type scale ratio, and deliberate density instead of default templates.

What is the process for designing a SaaS interface with this skill?

Define intent (user, task, feel), explore the product domain for palette and signature, propose a direction with rejected defaults, then build using existing components and tokens. Verify with squint, swap, signature, and token tests before presenting.

Does this skill work for landing pages or marketing sites?

No. The skill explicitly scopes itself to product UI such as dashboards, admin panels, tools, and settings pages. Marketing pages, campaigns, and brand-only work should use a separate marketing or frontend design skill.

Should I hand-roll custom dropdowns and dialogs in product UI?

No. Use native HTML elements first, then battle-tested headless primitives like Radix UI or React Aria for stateful controls. Hand-rolling is a last resort and requires full keyboard navigation, focus management, and ARIA support.

What are the motion and animation rules for polished UI?

Keep UI animations under 300ms, use custom ease-out curves, animate only transform and opacity, and never scale from zero. High-frequency actions get no animation, and prefers-reduced-motion must be respected.