cg-web-designer

Before any code, Claude clarifies the site's purpose, audience, primary action, content and constraints. A vague brief gets turned into concrete design rules, with follow-up questions where the answers actually change the work.

Copy and structure are treated as part of UX, not decoration added afterwards. Every page gets a defined purpose, the question it answers, its evidence, and its primary action — before anything is laid out.

The longest chapter in the skill is a catalogue of the defaults generated websites fall into — interchangeable hero sections, three identical feature cards, gradient text, pill buttons, fade-up on every section — and the instruction to challenge each one rather than ship it.

WCAG 2.2 as the accessibility baseline, Core Web Vitals as the performance target, plus SEO, responsive behaviour, states, and a launch checklist. The skill also forbids claiming compliance that was never tested.

This is the part worth reading twice, because it is what makes the output usable rather than merely plausible:

Iterative, not rigidly linear — discovery can change strategy, testing can change wireframes, implementation constraints can change visual design. But upstream reasoning is never skipped just because coding is faster.