{"version":"2.1.271","anchor":"new-designslidesdesign-system-artifact-file-backed-store","canonical_anchor":"new-designslidesdesign-system-artifact-file-backed-store","heading":"Reworked guidance for design\/slides Artifact storage instructions","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-designslidesdesign-system-artifact-file-backed-store","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Reworked guidance for design\/slides Artifact storage instructions\n\nInstructions for how design, slides, and design-system Artifacts store their content (files vs. database) were rewritten and expanded\n\n**What**\n\nThe logic that generates instructions for design, slides, and design-system Artifacts about where their content actually lives was reworked.\n\n- A new lookup table (keyed by `design`, `slides`, `design-system`) and helper functions generate instructions explaining whether an Artifact's content lives in its own published files or in its database-style store, based on an index marker file (`canvas.json`, `deck.json`, or `design-system.json`).\n\n- A migration note clarifies that a design-system's content can move from the database store to files the first time (or any time) it's opened, and never moves back.\n\n- The write-guidance text shown when reading an Artifact that declares `write_db` was rewritten: it now factors in file-list instructions and produces different text depending on whether the type is file-based, plus trailing instructions about published files.\n\n**Why**\n\nThis should make Claude's guidance about where to write changes to a design\/slides Artifact more accurate, since the storage model (files vs. database) can differ by type and can change over an Artifact's lifetime.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}