interface-design
Interface design for dashboards, admin panels, and tools that avoids generic defaults through intentional domain exploration and systemic craft.
- Start with intent exploration: identify the specific human user, their core task, and the emotional quality the interface should convey before touching code
- Conduct domain exploration to uncover product-specific concepts, color worlds, and signature elements that distinguish the design from templates
- Apply subtle layering through whisper-quiet surface elevation, border progression, and token architecture that creates hierarchy without harsh visual jumps
- Build infinite expression by rejecting identical patterns—every interface should emerge from its specific task and context, never look AI-templated
- Establish systemic intent where every decision (color, spacing, depth, typography) reinforces the stated feel across all components, not just surface-level styling
Interface Design
Build product interfaces with the craft of a top design team — Linear, Vercel, Stripe, Apple. The difference between those and generic output is not talent. It is that every decision was decided, the hierarchy is unmistakable, and a hundred small details are correct at once. This skill is how you get there.
Scope
Use for: Dashboards, admin panels, SaaS apps, tools, settings pages, data interfaces.
Not for: Landing pages, marketing sites, campaigns, brand-only work. Use a marketing/frontend design skill for those.
This skill is self-contained: direction, visual hierarchy, design-system architecture, and the polish and motion essentials needed to ship production-grade UI all live here.
The Problem
You will generate generic output. Your training has seen thousands of dashboards, and the patterns are strong. You can follow this entire process — explore the domain, name a signature, state your intent — and still produce a template: warm colors on cold structures, friendly fonts on generic layouts.
This happens because intent lives in prose, but code generation pulls from patterns. The gap between them is where defaults win. Process helps, but it doesn't guarantee craft. You have to catch yourself, and you have to know the concrete moves that defaults don't.