Replies from the design service are now validated against per-method schemas.
What's wrong with this entry?
Replies from the design service are now checked against a schema chosen by the method name, covering listing and reading projects and files, finalising a plan, writing and deleting files, registering and unregistering assets, creating a project and reporting validation.
- Writing without a plan token still hard-fails in non-interactive sessions, telling you to finalise a plan first.
writing without a plan_token requires a one-time interactive project approval
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
New /design skill drafts multi-artboard canvases as an Artifact, gated off
Both mention design
-
v2.1.235
Claude Design state moved off module globals onto a per-session object
Both mention design
-
v2.1.238
A
/designcommand that drafts a design on a canvas artifactBoth mention design