Design & frontend
Practical guides for design and frontend work done with Claude's help — component systems, accessible HTML, CSS iteration, and reviewing what Claude generates for the specific mistakes it still tends to make. These are written for people evaluating Claude's output critically, not for people looking for a prompt that magically produces a finished design.
Most "AI for design" content falls into one of two unhelpful extremes: breathless claims that a model can now replace a designer outright, or dismissive claims that the output is never usable past a rough sketch. Neither matches what actually happens in practice on a real project. Claude is genuinely useful for a specific set of design and frontend tasks — generating a first pass at a component system, catching an accessibility issue a human reviewer might skim past, iterating on CSS faster than typing every value by hand — and genuinely unreliable at others, particularly anything requiring taste-level judgment about a brand or a specific visual identity. This cluster tries to be specific about which is which, task by task, rather than making a general claim either way.
If you're reviewing output someone else generated rather than generating your own, reviewing a Claude-generated UI for real issues and common CSS mistakes Claude still makes are the two most directly useful starting points.
Using Claude for component design systems
Prompting Claude for accessible HTML
Iterating on CSS with Claude without losing the thread
Claude and Figma handoff workflows
Reviewing a Claude-generated UI for real issues
Getting consistent design tokens from Claude
Using Claude to audit a design for contrast
Prompting Claude for responsive layouts
Claude for design critique, not just generation
Writing a design brief Claude can actually use
Common CSS mistakes Claude still makes