Interface Design

Operating contract for crafted product interfaces: dashboards, admin panels, SaaS apps, tools, settings pages, data interfaces, and interactive products. This skill is not for marketing pages or campaigns; route those to /frontend-design.

Invocation Triggers

Use this skill when the user asks to design, build, critique, improve, or systematize:

• Dashboards, admin panels, SaaS apps, internal tools, settings pages, data-heavy screens, and product workflows.
• Navigation, data surfaces, forms, tables, cards, panels, filters, charts, controls, and reusable interface systems.
• Interface craft: visual hierarchy, product-domain expression, typography, spacing, depth, surfaces, tokens, states, and consistency.
• .interface-design/system.md creation, use, audit, extraction, or update.

When Not to Use

• Landing pages, marketing sites, campaigns, ads, or brand-only work with no product interface.
• Pure backend, API, data, DevOps, or CLI tasks with no screen or interaction surface.
• Generic frontend implementation when the user only wants mechanical code changes and no interface design judgment.
• Tasks better handled by a more specific skill, unless interface craft is central.