{"version":"2.1.246","anchor":"artifact-guidance-routes-decks-and-documents-through-the-typ","canonical_anchor":"artifact-guidance-routes-decks-and-documents-through-the-typ","heading":"Artifact guidance routes decks and documents through the type list first","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/artifact-guidance-routes-decks-and-documents-through-the-typ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Artifact guidance routes decks and documents through the type list first\n\nAsking for a deck, document or design now sends Claude to check artifact types first.\n\n**What**\n\nWhen you ask for a slide deck, presentation, a document or report for others to read, or a visual design, Claude Code is now told to look up the available artifact types before loading a skill or writing a file, and to prefer a listed type even over a skill that would emit a .pptx or .docx.\n\n**Details**\n\n- The file-format route is now described as correct only when you actually want the file format itself.\n- Questions about which types or templates exist trigger a lookup before answering.\n- Where creating from a type is not available in the session, the model offers to make it another way instead.\n\n**Evidence**\n\n`prefer a listed type that fits, even over a skill that would produce it as a file format such as .pptx or .docx`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}