{"version":"2.1.232","anchor":"design-skill-now-required-for-markdown-artifacts-too","canonical_anchor":"design-skill-now-required-for-markdown-artifacts-too","heading":"Design skill now required for Markdown artifacts too","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/design-skill-now-required-for-markdown-artifacts-too","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Design skill now required for Markdown artifacts too\n\nClaude loads the design skill before writing any artifact, Markdown included, except workshop docs.\n\n**What**\n\nClaude must load the design skill before writing an artifact file whether the output is HTML or Markdown, and choosing the format is treated as part of the design decision rather than a shortcut. Workshop documents remain the one exception.\n\n**Evidence**\n\n`Format is part of that decision: choose Markdown because the deliverable calls for it, never for speed.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}