interface-design

Define domain vocabulary, color world, and default patterns for dashboard interfaces.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interface design often suffers from inconsistent intent, weak alignment between business goals and user experience, and fragmented patterns across dashboards and admin panels.

Core Features & Use Cases

  • Domain-driven exploration: codifies product vocabulary for dashboards, admin tools, and data interfaces.
  • Color world and typography guidance: establishes a cohesive visual language that scales across projects.
  • Signature and defaults: defines a unique design signature and a reusable baseline of patterns for cross-product consistency.
  • Use Case: rapidly craft a cohesive analytics dashboard with consistent navigation, data visualization, and controls.

Quick Start

Describe the domain concepts, color world, and signature for a SaaS admin dashboard to start shaping a unique, intent-driven interface.

Frequently Asked Questions about interface-design

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

FAQPage Schema
What is domain-driven interface design for SaaS dashboards?

Domain-driven interface design codifies product vocabulary and visual language to produce consistent dashboards and admin panels. It aligns business goals with user experience by defining a unique design signature and reusable baseline patterns.

How do I build a consistent admin panel design system?

To build a consistent admin panel design system, define the domain concepts, color world, and typography guidance. Establish a unique design signature and a reusable baseline of default patterns to ensure cross-product consistency.

Can I use this approach for early design explorations and component governance?

Yes, this approach applies to early concept framing and component-driven UI governance across SaaS products. It helps shape unique, intent-driven interfaces by documenting dependencies and default patterns for dashboards.

What's the best way to establish a cohesive color world and typography for data interfaces?

The best way to establish a cohesive color world and typography is to codify the product vocabulary first. This creates a scalable visual language that defines a unique signature and reusable baseline of patterns for data interfaces.

Why does my dashboard interface design suffer from inconsistent intent?

Dashboard interface design suffers from inconsistent intent due to weak alignment between business goals and user experience, alongside fragmented patterns. Solving this requires codifying domain vocabulary and establishing a unique design signature.

Do I need to document dependencies and components for an analytics dashboard?

Yes, documenting dependencies and components is required for an analytics dashboard. It satisfies the requirements for identifying domain vocabulary, establishing a color world, and defining a set of default patterns for UI governance.