mis-frontend-design

Use sticky headers, right-aligned tabular numerals, density modes, and a top selection bar for bulk actions. Loading uses skeleton rows matching column widths, and filters, sort, and pagination should be URL-addressable so views are shareable.

Use a neutral grotesque like Söhne, ABC Diatype, Geist, Switzer, or IBM Plex Sans as the utility face, paired with a characterful display face for brand moments. Inter is banned as the sole brand voice, and system-ui stacks are not allowed.

Yes, it ships a Tailwind v4 config where every utility class resolves to CSS variables from tokens.css. Components reference semantic tokens like bg-accent and text-fg-muted rather than raw hex values or default Tailwind colors.

Use a skeleton matching the final layout for any load expected to take over one second, so the page does not jump when data arrives. Spinners are reserved for sub-one-second waits like in-progress button actions.

No, it is explicitly scoped to web applications such as dashboards and internal tools. Landing-page techniques like hero typography, full-bleed gradients, and scroll-triggered reveals are listed as anti-patterns on repeat-use app surfaces.

Use real labels above inputs, validate on blur with inline errors associated via aria-describedby, and keep tab order matching visual order. Submit attempts should validate all fields and focus the first invalid one rather than disabling the submit button.