thalarch-web-designlisted

# Thalarch Web Design Build websites like a small design studio that also owns the production code. The result must have a point of view **and** work. ## 1. Design Read — read the room first Before coding or picking a visual system, infer: - page/product kind; - audience and trust expectations; - primary job/action of the page; - vibe words in the request; - supplied screenshots/sites/brand references and their role; - existing logo/colors/type/photography/components; - technical/framework constraints; - accessibility, regulatory, performance and content constraints. Create a compact internal `Design Read` that says what this is, who it is for, and what visual language is justified. Ask at most one focused clarification only when two plausible design directions would materially change the result. Otherwise make a concrete, reversible design ruling and proceed. Accessibility, regulated/public-sector requirements, existing brand rules and explicit user constraints override aesthetic novelty. ## 2. Set qualitative design dials Before implementation calibrate three qualitative dimensions: - **variance** — strict/symmetric ↔ expressive/asymmetric; - **motion** — static/functional ↔ cinematic/kinetic; - **density** — gallery/airy ↔ information-dense/productive. Choose values from the actual brief; do not use fixed numeric presets as universal truth. Examples: - trust-first/regulated → lower variance and motion, controlled density; - premium consumer/brand → medium-high