Skill detail
mies
Design taste skill for ruthless reduction and craft in user-facing interfaces, including dashboards, with tokens, hierarchy, states, and motion. Relevant to dashboard craft but general interface design.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: mies description: Use this skill when creating, redesigning, critiquing, reducing, polishing, hardening, or making design decisions for a user-facing interface, brand surface, product UI, component, dashboard, flow, app shell, onboarding, empty state, or visual system. Applies Mies van der Rohe-inspired restraint, the Interface Craft workflow, and anti-generic design discipline. Not for backend-only work. argument-hint: "[mode, description, or file path]" --- # Mies A design taste skill for ruthless reduction and exacting craft. Ask "why is this here?" of every element. If it cannot answer, remove it. If it survives, make it immaculate — proportion, spacing, alignment, type, hierarchy, state, motion, copy, and material tuned until they feel inevitable. The result should feel calm, confident, expensive, and human. Restraint is not emptiness: warmth comes from intentional use, humane copy, thoughtful defaults, resilient states, and details that prove someone imagined a real person using the interface. (Named for Mies van der Rohe — use the spirit, not the imitation: "less is more," "God is in the details.") ## Source order Interface Craft is the operating loop: notice, frame, explore range, choose structure, compose, tune in the real interface, critique, reduce, prove. Impeccable and Taste are bias checks: register fit, anti-default discipline, current standards, visual verification. Mies is the filter: fewer decisions, stronger reasons, better details. When sources disagree, prefer the existing product system, then platform/category convention, then the Mies foundation. Novelty is allowed only after the baseline is met and the deviation has a user or brand reason. ## Modes Infer the mode from the request; if the user names one, follow it. Read only the one referenced file the mode needs. - **Frame** — plan the design decision and diverge from the category default before building. `references/workflow.md` - **Set** — establish the reusable foundation (tokens, type, color, spacing, radius, states, vibe, character). `references/design-system.md` + `templates/` - **Compose** — build or redesign a surface. `references/workflow.md`, the register in `references/registers.md`, and reusable moves in `references/patterns.md` - **Inspect** — critique an existing surface. `references/critique.md` - **Refine** — subtract, tune, then prove: remove what doesn't earn its place, polish what remains, and harden for real data, edges, a11y, responsiveness. `references/refine.md` - **Move** — motion, choreography, tactile feel, live tuning. `references/motion-and-tuning.md` - **Word** — write or audit interface copy: warm, clear, nothing excessive, no overexplaining, and free of AI tells. `references/copy.md` For new products, new visual directions, and redesigns, route **Frame → Set → Compose** unless a current foundation already exists. For small obvious fixes, state the design read briefly and proceed. ## First read Before design work, infer (ask only when a wrong guess causes real rework): - **Surface** — brand, product, dashboard, form, editor, mobile, onboarding, content, component, or flow. - **User & scene** — who, in what state of mind, doing what task, on what device, under what pressure. - **Register** — brand creates an impression; product serves a task. - **Existing system** — components, tokens, type, icons, spacing, imagery, platform conventions, design docs. - **Facets** — 3-5 perceptions the work must create (calm, expert, durable, warm, fast, crafted, trustworthy, inventive). - **Vibe & character** — the atmosphere to hold and violate; the imagined hand behind the work. - **Anti-reference & reflex risk** — what this must not become, and the category/AI default it could fall into. When direction matters, say: `Reading this as: <surface> for <user/context>, needing <facets>, with <register> restraint.` Tune silently on five dials — density (sparse↔operational), expression (quiet↔distinctive), motion (still↔cRead the full source on GitHub (opens external page)