← ClaudeAtlas

design-engineeringlisted

Design an interface: what goes on the screen, what it is called, how it is grouped and ordered, which states exist and how each one is drawn, how it holds up when resized, translated or fed bad data, and whether anyone can reach it by keyboard. Reads the project's own design system first. Hands the finishing pass to attention-to-detail. Use when building a new screen, component or flow, when restructuring an existing one, when deciding what to show or where to put it, when a layout breaks at some width, or when reviewing an interface as a whole. Triggers on design, UI, interface, screen, page, view, component, widget, layout, hierarchy, information architecture, empty state, loading state, error state, skeleton, responsive, breakpoint, mobile, dark mode, theme, contrast, accessibility, keyboard, copy, label, microcopy.
Udhay-Adithya/skills · ★ 0 · Web & Frontend · score 70
Install: claude install-skill Udhay-Adithya/skills
# Design engineering Deciding what the interface is: what appears, what it is called, how it is grouped and ordered, which states it has, and whether it survives a small screen, a long translation and a user with no mouse. This is the design layer. The finishing layer is `attention-to-detail`, and this skill depends on it: get the structure right here, then hand over for the craft. ## 1. Read the project first Never design against a blank page when a design system already exists. ```bash ls pubspec.yaml package.json 2>/dev/null ``` Then find and read, before deciding anything: - **The theme.** Where colours, spacing and radii come from. `lib/core/theme/` in a Flutter project, `tailwind.config` or a `@theme` block or a `:root` on the web. - **The nearest existing screen.** Whatever already does something similar is the strongest available statement of how this project does things. Extend it rather than inventing a sibling. - **The shared components.** What already exists that nearly does this. - **The copy.** Find the translation call and the locale files, and list the noun used for each object and the verb used for each action. New copy uses the terms already on that list. A new pattern needs a reason. "The existing one did not fit" is a reason; not having looked is not. ## 2. Structure ### Hierarchy first The most important thing sits near the top and the leading edge. Within a row, the identifying content leads and the metadata and actions trail. Visua