8 October 2026 · Pinned-source recheck
Your design brief outranks a skill’s default palette.
The pinned Anthropic Frontend Design skill asks for a palette and type plan. It also says to follow a brief that fixes the visual direction. Our catalogue previously described it as asking for new choices without stating that override. That was too broad.
Choose the route by your task
| Your task | Start here | Check |
|---|---|---|
| Existing product system | Give the agent the actual token files, components, route, and required states. Try the task with a careful brief before adding the skill. | If the skill’s plan replaces fixed tokens or components, reject that plan. Its instruction says the brief wins; we have not tested the result. |
| New page with open visual direction | The skill is a task-fit option for making a deliberate visual plan before code. | Inspect the rendered page and compare it with the same task without the skill. A source read does not prove improvement. |
| Image already approved as a visual target | Give the agent the image and implementation constraints; a design-direction skill may be redundant. | Compare the rendered output with the reference and count correction rounds. One community discussion reports that conversion can take many iterations; that is not a benchmark. |
What the source does not settle
An open contributor pull request proposes detailed instructions for established design systems. It is not part of this pinned skill. The current instruction to obey a fixed brief is useful, but it does not show that an agent will preserve an actual product system. None of the sixteen catalogue listings has a pool-run no-skill result comparison.