{"version":"2.1.239","anchor":"markdown-files-saved-with-a-byte-order-mark-now-have-their-f","canonical_anchor":"markdown-files-saved-with-a-byte-order-mark-now-have-their-f","heading":"Markdown files saved with a byte-order mark now have their frontmatter read","tier":"notice","area":"Frontmatter","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/markdown-files-saved-with-a-byte-order-mark-now-have-their-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Markdown files saved with a byte-order mark now have their frontmatter read\n\nAgents, commands, skills and CLAUDE.md files saved with a byte-order mark now have their frontmatter read.\n\n**What**\n\nAgent, command, skill and CLAUDE.md-style files saved with a UTF-8 byte-order mark had their YAML frontmatter treated as ordinary body text. All three frontmatter parsers now strip the mark first.\n\n**Details**\n\n- Covers the generic parser, the multi-file loader that reports \"Could not read\", and the agent\/skill parser that special-cases a leading `---`.\n\n**Evidence**\n\n`e.charCodeAt(0) === 65279 ? e.slice(1) : e`\n\n- Area: Frontmatter\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}