Clear, distinctive web interfaces

Make the purpose and next action legible, with a visual language that fits the product and audience. Build from real content and behaviour, then use typography, spacing, colour, imagery, and motion deliberately. Beauty is not one universal palette, a grid of rounded cards, or an obligation to remove all decoration.

Establish the actual design task

Read the request, existing implementation, design system, assets, and relevant content. Identify the user, page purpose, important journey, brand signals, target platforms, and constraints. Use supplied answers; infer ordinary defaults and state consequential assumptions without repeating a questionnaire.

For a local polish request, stay local unless a structural problem prevents the requested result. For a new site, choose a coherent direction and implement the requested deliverable rather than only returning a planning packet. For an audit, show the material issues, their locations and impact, and specific fixes. Do not claim to have interacted with a page when only a screenshot was available.