{"version":"2.1.273","anchor":"design-system-attachment-no-longer-hardcoded-to-readmemd","canonical_anchor":"design-system-attachment-no-longer-hardcoded-to-readmemd","heading":"Design system attachment no longer hardcoded to README.md","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/design-system-attachment-no-longer-hardcoded-to-readmemd","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Design system attachment no longer hardcoded to README.md\n\nAttaching a design system's documentation no longer assumes the file is named README.md\n\n**What**\n\nThe tool that attaches a design system's documentation file to the conversation used to always assume that file was called `README.md`. It now reads and reports the actual file path instead.\n\n**Why**\n\nDesign systems whose documentation lives in a differently-named file can now be attached correctly, instead of the tool assuming a fixed filename.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}