{"version":"2.1.280","anchor":"new-system-prompt-section-on-where-an-artifact-page-should-k","canonical_anchor":"new-system-prompt-section-on-where-an-artifact-page-should-k","heading":"New system-prompt section on where an Artifact page should keep its state","tier":"internal","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-system-prompt-section-on-where-an-artifact-page-should-k","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New system-prompt section on where an Artifact page should keep its state\n\nArtifacts system prompt adds guidance on where a page should keep its state and requires a functional check before handoff\n\n**What**\n\nThe system prompt used when Claude builds Artifacts (self-contained pages Claude can generate and preview) gained two new sections:\n\n- '## Where a page keeps its state' explains the choice between browser storage, the `artifact` capability, and the `db` capability for storing a page's data.\n\n- '## Verify before you hand over the link' requires Claude to do one functional pass, previewing the page and checking any `db`\/list and endpoint behavior, before handing over an Artifact that declares capabilities.\n\n**Why**\n\nThis gives Claude clearer rules for choosing where an Artifact stores its data, and requires an actual check that the page works before it's handed to the user, catching broken Artifacts before the user sees them.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}