designinglisted

# Visual Design Design so the result cannot be mistaken for a template: every visual choice traceable to the subject, audience, or page job, plus one evidence-backed differentiator a competitor could not justify. The enemy is the transferable default — a design that could accept another product name unchanged. The overcorrection is novelty that obscures content, removes states, or breaks accessibility. A full or bounded redesign fails when the rendered result stays materially interchangeable with the baseline, when supporting regions stay generic while one focal point carries the design, or when a large empty area has no content, grouping, pacing, or staging job. Do not default an open axis — composition, type, chromatic hierarchy, surface treatment, imagery, motion — to absence: restraint on one axis needs a brief-side reason and expression on the others. **After a compaction notice**, resume from the newest `/private/tmp/designing/*/` run directory, not the conversation: Build reopens from its `contract-selected.json`, and `renders/` shows the checkpoints reached. ## Size the request This skill owns a visual change at any file count, because Build dispatches its own builders. A surface whose displayed data, settings or behavior is undecided goes to `shaping` first; a change that also adds state, persistence, a dependency or a network call belongs to `implementing-batch`, which borrows this skill for the look. - **Sketch:** a demo, prototype, or mock the request names