[feat] Modular Brandbook Versioning & Automation for KU6K #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces a comprehensive modular brandbook architecture for the KU6K design system, implementing independent semantic versioning for each module and automated change tracking and version bumping workflow.
Details
--ku6k-prefix) for all tokens, including dark mode as a separate module.Why
Testing
brandbook:version-checkto validate all module versions, changelogs, and tags (all checks passing).pnpm run buildand full Next.js build (all modules and app compile correctly).Breaking Changes
See included documentation (
brandbook/docs/) for full strategy, migration guidelines, and usage examples. All changes comply with KU6K Essential UI system standards, and future module updates will follow the established process.