Frontend Design comparison: the first result did not hold
Checked 9 November 2026. A community author ran one landing-page brief six times with Anthropic’s Claude Code Frontend Design plugin and six times without it. The first report said the plugin reduced generic layouts. After rerunning all twelve outputs, the author withdrew the original genericity split and distinctiveness result. Some plugin-off layouts repeated, but that observation does not establish a reliable quality advantage.
The comparison used one brief and the author’s own scoring. It does not identify an immutable plugin revision, independently judge the outputs, or test a working app after use. Do not use the initial numbers as a reason to install the skill.
The current official Claude Code plugin manifest declares version 1.1.1 on a mutable branch. Its current skill file asks the agent to plan a visual direction, review it against the brief, and inspect screenshots where possible. Those instructions do not prove a better result. The older repository-pinned listing in this catalogue is not a verified copy of the current plugin package.
What to do on an existing app
Give the agent the current components, tokens, real content, and screenshots before asking for a visual change. State which routes, interactions, and data behavior must stay the same. Compare the rendered page and those behaviors after the change. A builder asking to restyle an offline educational app names exactly this constraint; the discussion offers both skills and a direct brief, but no measured outcome.
For a new landing page with an open visual direction, Frontend Design remains a task-fit option. For a small fix or a screen bound to an existing system, start with a direct project brief. Neither route has a paired result test from this catalogue.