Design for speed and utility.
"Prioritize layout rendering speed, clean typography, and strict utility."
Why this exists
A sluggish interface is a broken interface. We design layouts that load instantly and respond immediately. If a page takes longer than 200ms to respond to a click, users feel the drag. Design is the logical arrangement of how a user moves through a system, not just decoration.
Operational Flow
Start with typography: Establish your typographic scale and vertical rhythm before you draw containers or cards.
Style in grayscale: Verify contrast and visual balance in monochrome before adding color.
Cut the assets: Remove decorative graphics, massive hero images, and slow animations. If an asset is not functional, delete it.
Write CSS mentally: Ensure mockups translate directly into clean, semantic HTML and CSS without nested hacks.
What good looks like
- A user executes primary workflows in under three clicks.
- Contrast ratios exceed accessibility minimums without needing a separate high-contrast mode.
- Layout elements scale fluidly without causing layout shifts during loading.
What NOT to do
- Don't add decorative elements that serve no functional purpose.
- Don't introduce page transitions or animations that delay user actions.
- Don't copy generic dashboard templates just because they are familiar.
Design is not cosmetics. It is the logical arrangement of functionality. If a design looks beautiful but slows down the user, it is bad design.