Research note · 1 October 2026

Already have a design system? Do not ask for a new palette.

Anthropic Frontend Design at 41bbe19d tells the agent to plan a compact token system, including a palette of four to six colors and typeface roles. That makes sense when a brief leaves visual direction open. It can conflict with a project whose tokens and components are already decided.

Decision: Use it for a new visual direction. For an existing product, first give the agent the current tokens, components, and allowed changes. If the work is only a small component fix, start with a focused brief rather than a new art-direction skill.

Why the boundary matters

An open contribution to Anthropic's skill proposes a separate mode for established design systems: keep their tokens and shipped components, and look for distinctiveness in content, hierarchy, and component choices. The review request is a contributor's case, not official merged guidance. A dashboard-builder question also asks for help using existing brand, hierarchy, and component rules rather than generic landing-page design. That is one self-selected account, not proof that the skill fails for everyone.

What to check

On the actual route, compare the output with the project's tokens and components. Check the required empty, error, and responsive states before accepting the design. We inspected instructions and an open PR; we did not install this skill or compare its result with a careful no-skill brief.

The catalogue's sixteen skill listings remain source-inspected, not outcome-tested.