{"version":"2.1.273","anchor":"new-artifact-types-slides-and-design-with-file-based-st","canonical_anchor":"new-slides-artifact-type-alongside-design-and-design-syst","heading":"New file-based artifact types: slides and design","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-artifact-types-slides-and-design-with-file-based-st","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New file-based artifact types: slides and design\n\nArtifacts can now be 'slides' and 'design' types stored as project files, alongside the existing design-system type\n\n**What**\n\n- A new `slides` artifact type stores each slide as its own HTML file (`project\/slides\/<id>.html`), with a `project\/deck.json` index describing the deck's order, sections and fonts.\n\n- A new `design` artifact type stores each artboard as its own file under `project\/`, with a `project\/canvas.json` index.\n\n- The instructions Claude Code gives the model for these file-based types were rewritten to explain that content goes into files under `project\/`, tracked with a `createdOnFiles` marker object, and published together in one step.\n\n**Why** Previously, artifact types like these worked through an older \"store document\" model. Storing slides and designs as individual files with an index lets Claude Code build and update multi-file artifacts (a slide deck, a set of design artboards) more directly, and lets the model describe changes file-by-file instead of as one document blob.\n\n- Area: Artifacts\n- Names: `slides`, `design`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5"}