A cyberpunk toy-robot landing page gives Nick Babich a test case for the Design plugin in Claude Code. Writing for UX Planet, he starts with /design:design-critique this design, then uses the findings to request changes:

And the nice thing about doing a critique in Claude Code is that you can use a report that AI generated for you as an input. You can provide a follow-up prompt asking AI to fix the issues it found for you.

He narrows the next pass to the primary button with /design:ux-copy primary call to action button:

The great thing about Claude is that it has a project context. It means that it can use the knowledge it has about this particular product and business to find the right words.

Similar to the previous task, Claude generated a nice report with suggested text labels. I can also prompt Claude to change the call-to-action button text to the first option it suggests (Reserve a unit).

I’d check what the button actually commits the customer to before accepting that suggestion. A reservation is a specific promise, and the copy needs to match what happens after clicking.

Babich finishes with /design:design-handoff this design and a warning about what goes to engineering:

Similar to an AI-generated design critique, it’s not a good idea to use a design handoff file as-is without any changes. You need to review the file, validate the information in it, and only after that send it to the dev team.

Take ownership of what the AI generates.