{"version":"2.1.277","anchor":"artifact-tool-guidance-expanded-to-cover-creating-and-readin","canonical_anchor":"artifact-tool-guidance-expanded-to-cover-creating-and-readin","heading":"Artifact tool guidance expanded to cover creating and reading design systems","tier":"internal","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/artifact-tool-guidance-expanded-to-cover-creating-and-readin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Artifact tool guidance expanded to cover creating and reading design systems\n\nArtifact tool instructions now explicitly cover creating and reading design systems\n\n**What**\n\nThe internal instructions that tell the model how to find and use artifact types now explicitly mention design systems, including ones built from your own codebase, as something the quickstart and list-types steps should handle. A new rule classifies design-system requests under an `intent: \"other\"` category, and a new instruction tells the model to look up and read an existing design-system artifact when answering questions about it, falling back to searching your files if no such artifact is listed.\n\n**Why**\n\nThis makes Claude Code better able to recognize design-system-related requests and answer questions about an existing design system using the artifact itself, rather than treating it like an unrecognized artifact type.\n\n- Area: Artifact Publish\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}