library-management

To apply extracted brand design tokens, the Skill copies design-tokens.css, design-tokens.json, and DESIGN.md from your local design library into the target project directory while merging Tailwind configuration and previewing destructive changes.

Managing a local design library involves registering, listing, and removing extracted brand systems using an index.json file as the single source of truth, storing slug, source URL, extraction date, and path for each brand.

Yes, you can merge Tailwind configuration when applying a brand design. The Skill preserves existing Tailwind configuration while merging new settings during the design-tokens application process.

To re-index after manual edits, the Skill scans brand directories and updates the index.json file to ensure your local design library reflects changes made to metadata.json or stored design artefacts.

Applying design tokens does not blindly overwrite files. The Skill previews destructive changes before copying design-tokens.css, design-tokens.json, or DESIGN.md into your target project to preserve existing configurations.

A metadata.json file is required in the brand folder to register it in the design library. The folder should also contain design artefacts like design-tokens.css, design-tokens.json, and DESIGN.md for project application.