{"version":"2.1.273","anchor":"design-system-token-card-paths-get-a-project-prefix-when","canonical_anchor":"design-system-token-card-paths-get-a-project-prefix-when","heading":"Design-system token card paths get a 'project\/' prefix when applicable","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/design-system-token-card-paths-get-a-project-prefix-when","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Design-system token card paths get a 'project\/' prefix when applicable\n\nDesign-system token card file paths can now be prefixed with 'project\/' under certain conditions\n\n**What**\n\nWhen Claude Code reads a design system's token cards (files like `api\/tokens.md` and `tokens.json`) for a file-backed artifact, it can now look for those files under a `project\/` prefix, if the design system's own documentation lists a path matching a specific marker.\n\n**Why**\n\nThis lets token-card lookups match design systems that organize their files under a `project\/` folder, mirroring similar prefix handling already used elsewhere for card-reading.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}