interface-design

Coordinate craft-driven interface design for dashboards, apps, and data interfaces.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designing interfaces with craft and consistency for dashboards, admin panels, apps, and tools, while avoiding marketing design.

Core Features & Use Cases

  • Intent-first design philosophy that informs typography, navigation, data presentation, and component structure.
  • Provides guidance for domain exploration, signature design elements, and consistent defaults.
  • Use cases include dashboards, SaaS tools, settings pages, and data interfaces, with a focus on producing unique, purposeful UI rather than templated outputs.

Quick Start

Create a tailored interface plan for a dashboard by defining user personas, primary tasks, and a starter component structure.

Frequently Asked Questions about interface-design

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

FAQPage Schema
How do I design consistent dashboards and admin panels without using generic templates?

To design consistent dashboards, apply an intent-first philosophy that defines typography, navigation, and data presentation. This approach ensures unique, purposeful UI rather than templated outputs by establishing a systemic design language with tokens for color, spacing, and interaction states.

What are design tokens and how do they work for SaaS interface consistency?

Design tokens are defined variables for typography, surface elevation, color, spacing, and interaction states. They work by providing consistent defaults across SaaS tools and data interfaces, ensuring cohesive component structure and visual hierarchy throughout the application.

How do I start planning the UI structure for a data interface?

Start planning a data interface by defining user personas, primary tasks, and a starter component structure. This quick start method tailors the interface plan to specific user requirements before establishing domain exploration and signature design elements.

Does this approach work for settings pages and data interfaces, or just marketing sites?

This approach explicitly works for settings pages and data interfaces, actively avoiding marketing design. It focuses entirely on craft-driven interface design for dashboards, admin panels, SaaS tools, and functional apps.

What is the best way to establish a systemic design language for apps?

The best way to establish a systemic design language is by defining specific tokens for typography, surface elevation, color, spacing, and interaction states. This ensures craft and consistency across all dashboards and tools.