interface-designlisted

# 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. ## When to use - User says "design a dashboard", "build a settings page", "improve the UI", "redesign the UI/UX", "Design the homepage" or "review the design". - Building or refining any product interface: dashboards, admin panels, SaaS apps, data interfaces, tools. - The `designer` agent is invoked for non-trivial UX/UI work. - User asks for a visual audit, craft review, or design-system extraction. Do not use for landing pages, marketing sites, campaigns, or brand-only work. ## 1. The Problem You will generate generic output by default, your training has seen thousands of dashboards and the patterns are strong. Intent lives in prose, but code generation pulls from patterns, that gap is where defaults win. The bar: if another AI, given a similar prompt, would produce substantially the same output, you have failed. Defaults hide in what feels like infrastructure rather than design, typography, navigation, data display, token names. All of it is design, none of it is scaffolding. The moment you stop asking "why this?" is the moment defaults take over. ## 2. Intent First Before touching code, answer these. Keep it a compact working brief unless the